Quote:
Quote:
|
Quote:
Let me tell you that I have never ever tried to add a VOBfile to a DVDLab project. Usually I only do M2Vs and AC3s and have DVDLab mux them and I never get such a message. |
Quote:
Have you tried using MPEG Validator to analyze your source, and then the chunks :?: http://sr2.mytempdir.com/144314 -kwag |
Or make a quick test Rui :idea:
After you chop all your pieces (I post three VOBs on the example), and assuming your original VOB is named VTS_01_2.VOB, do this on a command prompt: copy /B VTS_01_2.VOB.kutter.1.VOB + VTS_01_2.VOB.kutter.1.VOB + VTS_01_2.VOB.kutter.1.VOB joined.vob Now the file "joined.vob" should be an identical bit by bit to the file VTS_01_2.VOB -kwag |
Stand by.
Working on many tests to see if it has to do with the chunks or with DVDLab. I'll be back in '5. Cheers |
I did many tests but none suited my needs.
So I went for one last and very long test. I added 2 vobfiles with 2 full movies that I just extracted to my HDD with DVDDecrypter. And this time there were no messages and the muxing went well from the begining until the end. I just burnt it to a DVD-RW and it's playing fine in the living room. So the issues that I had earlier must come from the chunks done by Kutter. Or maybe I'm missing something... |
Hmm, I just did the copy test, and the final joined VOB is identical to the source :roll:
Code:
C:\kutter>fc joined.vob h:\RED_PLANET\VIDEO_TS\VTS_01_2.VOB Unless the headers are buggy, and I'm not correctly tagging the cuts on the individual pieces. I'll do more tests. -kwag |
@rds_correia & Kwag
Thanks guys for the extensive testing you have both done, I am sorry I haven't had time to test myself but I was backing up one of my DVD's It is a shame about the 2Gb limitation of PB, I wish the developer of this programming language would fix this issuse as it holds back the excellent developers here who use it such as Karl and Andrej. Hopefully that 64bit binary Inc supplied will come in use. I hope to run some tests myself today. :) About the Open GOPs in DVD-Lab, I get this notification also when adding a .mpv stream made by CCE from my DVD sources but it doesn't affect the authoring and I have no probs when I watch the backups on my SAP. I just thought that info might come in useful. :) |
Quote:
It was my experience a time ago while programed a tool. I dont know if in this case it could be important. Edited: I worked with mpgs and not with vobs. |
Quote:
|
Quote:
Cheers |
@Boulder,
I also tried the FC /B. Result C:\kutter>fc /B joined.vob h:\RED_PLANET\VIDEO_TS\VTS_01_2.VOB Comparing files joined.vob and H:\RED_PLANET\VIDEO_TS\VTS_01_2.VOB FC: no differences encountered I suspect I might have a bug in the end header on the chunks. As a matter of fact, this has to be the problem, because the way it's suppposed to work is that each chunk is a valid MPEG file with start and end headers. So a join of all chunks shouldn't be the same as the original, because each chunk has to have added ending headers. I'll fix this today :) @All, Thanks for all the feedback :!: -kwag |
You won't loose informations by cutting if encoding the mpegs using SEQ Header at every Gop. Thats normally the "default" as mpeg was also meant to be a streaming format.
And here Kutter should ONLY cut at SeqHeaders. That header can be easely parsed as it begins using ..... Code:
If ReadFile(#File_Temp, p_filename) ; open file for read-only The "Parser" searches in the opened file till he founds a sequence header, then do a FileSeek(Loc()-3) so you get again in front of the $B3010000 Long value and THERE you do your cuts! If only ONE Seq Header at the beginning of the source is found then you MUST parse it completely and add it to your cutted target chunks at their very beginnings! I Missed something: You cant cut mpegs just by bytes! You have to cut at an I Frame startpoint. Do look at the (if available) mpeg2schnitt sources, there you can see how its being done :) |
Quote:
Quote:
Quote:
Actually this one you posted is a little simpler than the one I had, but if it ain't broke, don't fix it ;) Now there's something that just came to my mind. What happens if an actual header sequence pattern shows up in the data (video) part :!: What I mean is, in standard data communications, if a control/command pattern is part of the data, it's usualy preceded by some escape sequence. This way, you can differentiate from actual headers or from data. So what happens in an MPEG stream, when a header byte pattern is part of the data :?: If it's not preceeded by some escape sequence, this can (and will!) throw off any decoder, because it thinks it's a start of a sequence header, when in fact it's actual data :roll: Anyone ever thought about this, or did I miss something in the MPEG protocol :?: -kwag |
Man!!
I know you're probably right but I'm affraid I didn't catch up a word of what you wrote in the last paragraph :lol:. Cheers |
Don't worry about it Rui :lol:
-kwag |
I do think these 4 bytes in their count are something like protected!?
Cause if not, such a parser would sometimes put out garbage - and that never happened to me. |
Quote:
Quote:
That would make the pattern 00, 00 ,01, B3, 2D, 01 much more difficult to produce in actual data, but it still CAN happen :!: -kwag |
@Rui,
Did you try importing .M2V file chunks into DVDLab :?: I just tried importing several .M2V chunks into TMPGEnc DVD Author, and there were no errors. The original VOB file was demuxed to .M2V with TMPGEnc tools to produce the file, which I then chopped up with Kutter. http://www.digitalfaq.com/archives/i.../2005/09/3.png -kwag |
No Karl, unfortunately I didn't try that.
I only tried it on VOBfiles. Today I'm encoding. Tomorrow I may find time to test it on M2Vs ;-). Cheers |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.