DVD2OneX 1.2 broke my DVD2OneX 1.1.1?

[DreamStatic]

I tried out DVD2OneX 1.2 and it seems to not work correctly? Even though I have it set to encode to 4450 MB it is encoding down to 2.1 GB - 2.9 GB. What gives? It was super fast doing it though!! So I am curious anyone know of a fix for it?

Now when I try to revert back to DVD2OneX 1.1.1 it does the same thing? I tried to delete the prefs and reregister. But it won't take the serial anymore? So at the moment I am stalled, which isn't good.

Thanks for any and all help!!!

[galactica]

I believe the serial will only unlock the 1st OSX version, i could be wrong though.

do you still have that?
if not, contact dvd2one im sure they will straighten you out.

[Ladd]

I tried out DVD2OneX 1.2 and it seems to not work correctly? Even though I have it set to encode to 4450 MB it is encoding down to 2.1 GB - 2.9 GB.

I've had the exact same thing happen with multiple tries of DVD2oneX 1.2.0 using the "Disk Copy" setting. Final output size varied from 2.1 to 2.9, depending on if Variable or Constant was selected.

Switching back to version 1.1.1 works fine, however, so I didn't see the problem continue as you had.

[DreamStatic]

Got it all straightened out, thanks for the input!

[galactica]

just out of curiosity, what did you do to straighten it out?

[Ladd]

just out of curiosity, what did you do to straighten it out?

I would love to hear this also.

Here are my tests from today:

Output VIDEO_TS folder sizes I'm getting when compressing "LOTR -- The Twin Towers" using DVD2oneX 1.2.0:

Output DVD+/- R(W) (fixed at 4472):
Constant = 2.18 GB
Variable = 2.95 GB

Output User Defined (defaults to 1491, set to 4472):
Constant = 2.18
Variable = 2.95

When doing the same tests as above using DVD2oneX 1.1.1, all VIDEO_TS folder sizes are 4.36 GB.

[Ladd]

Success!

I deleted the DVD2oneX preferences (after backing them up), fired up version 1.2.0, entered in my registration number when asked, then re-ran one of the above tests (Output DVD+/- R(W), fixed at 4472, Variable encoding) and the resulting VIDEO_TS folder was 4.36 GB as it should be.

Not sure why the problem with incorrect output size came about to begin with, but glad the solution was easy to implement.