I’ve been using ConvertXtoDVD for a bit, and generally it’s working excellent!
I was sort of wonder how it treated VOB source files. I started with a VOB file that was created by my DVR. After running it through CXtD, the resulting VOB file was quite a bit smaller (even though I selected best quality).
Now, I’m not sure if this means that there’s a quality loss or if CXtD can optimize the “guts” of a VOB file without loss of quality.
Next, I though, what if I ran the output from CXtD back through itself a few times (generations). Here are the resulting file sizes after a few passes of the output back through the program again.
2006-11-05 14:14 846,606,336 SF0.VOB
2006-11-05 15:29 741,677,056 SF1.VOB
2006-11-06 18:21 740,636,672 SF2.VOB
2006-11-07 15:43 740,528,128 SF3.VOB
2006-11-07 16:58 740,700,160 SF4.VOB
Note that SF0.VOB is the output from my DVR. SF1.VOB is the first file created after using CXtD on SF0.VOB.
Once I got SF1.VOB, I captured the CXtD log for the following recodes:
SF1 to SF2
SF2 to SF3
SF3 to SF4
The resulting VOB files get progressively smaller from SF0 to SF3. Then on the last recode (SF3 to SF4), the resulting VOB file gets bigger.
So the big question is, are all the CXtD-generated VOB files (SF1 to SF4) of equal quality, or is there going to be some degeneration on each pass? It might a cool feature if there was an option to use a VOB file AS-IS without any “processing”. The few times I’ve used Nero Recode (for the fancy menus), if it sees a VOB file, it runs it REALLY fast as a direct copy. That can be handy when I want to add a few VOB files to an image along with say one or two AVI files - the VOB files can be considered “copy” only.
Oh, I’ve attached the ConvertXtoDVD log, in case it helps.