Closed and Open GOP

[Shadoworks]

I hate to bother you. I have been using DVD2AVI for years and never had any problems. Recently I have been playing around with the idea of distributing the vob files to different machines for distributed encoding. It's an ideal that has stuck in my head for many years of slow encoding. Although machines are way faster today and I have the fastest hardware available I'm still stuck on it. So... I've been messing around with it. As you know you can't just split the files normally because you lose frames in between the files. Now that this issue was brought up recently I see your recomendations are to split at a closed GOP. So I have been trying splitting by other means with DVDDecrypter. I've split by every option DVDDecrypter has and I still get the open GOP warning. I thought for sure splitting by cell i.d. would be at a closed GOP but I still get the warning on some files. How do you recommend splitting files at a closed GOP?
The next problem I have had is the way DVDDecrypter names the output files is not accepted by DVD2AVI. Of course if you rename the files to vts_1_1-23 for example it will read them. It opens the first 9 files but will not open them all without manually adding them. There is an average of 20 files when splitting by cell i.d. Is this an issue with renaming the vob files without editing the .ifo file? Or does the ifo have to be edited for DVD2AVI to read the vob's correctly? I am guessing yes.
I'm sorry for my off the wall questions. Your program works perfectly for me when doing normal rips. I just like to explore different possibilities, and I think this is a good adventure. I have three other machines just sitting here on a gigabit LAN that I could surely put to work. Thanks for any info on this subject.

[hakko504]

Originally posted by Shadoworks
I hate to bother you. I have been using DVD2AVI for years and never had any problems. Recently I have been playing around with the idea of distributing the vob files to different machines for distributed encoding. It's an ideal that has stuck in my head for many years of slow encoding. Although machines are way faster today and I have the fastest hardware available I'm still stuck on it. So... I've been messing around with it. As you know you can't just split the files normally because you lose frames in between the files. Now that this issue was brought up recently I see your recomendations are to split at a closed GOP. So I have been trying splitting by other means with DVDDecrypter. I've split by every option DVDDecrypter has and I still get the open GOP warning. I thought for sure splitting by cell i.d. would be at a closed GOP but I still get the warning on some files. How do you recommend splitting files at a closed GOP? Actually this recommendation is somehwat contradictory as it usually isn't possible to decide on whether to split the file at an open/closed GOP. Well prepared DVD's does have closed GOP's at the end of cells, but you can't be sure of that until you've tried.
The next problem I have had is the way DVDDecrypter names the output files is not accepted by DVD2AVI. Of course if you rename the files to vts_1_1-23 for example it will read them. It opens the first 9 files but will not open them all without manually adding them. There is an average of 20 files when splitting by cell i.d. Is this an issue with renaming the vob files without editing the .ifo file? Or does the ifo have to be edited for DVD2AVI to read the vob's correctly? I am guessing yes.Wrong, DVD2AVI does not read the IFO under any circumstances.
I'm sorry for my off the wall questions. Your program works perfectly for me when doing normal rips. I just like to explore different possibilities, and I think this is a good adventure. I have three other machines just sitting here on a gigabit LAN that I could surely put to work. Thanks for any info on this subject. Why not rip the DVD and create the .d2v on one machine, then create 3 AviSynth scripts (1 for each machine) which you then encode separately and put back together afterwards?

[Shadoworks]

Thank you for your quick reply. I have always stuck to the guides and never had many problems with encoding thus never exploring all the aspects of the process, other than setting up the codecs. I will read about this method as I have never had to do it before. Maybe it will be easier than I have made it out to be. Thank you again for your ideas and help.

[Shadoworks]

That was a good idea about making seperate avs scripts and distributing them to different machines. Thanks for your help again.