Invictus grows after shrinking.

[omegaspeedmaster]

I've never had this happen.
I've ripped Invictus to my drive as a full-size movie (title only).
I've then shrunk it to "DVD5" size (4300MB) using DVDFab.

When I try to write the "shrunken" files to a blank DVD using [other software] (the only prog. I've had luck burning with), I get an error that the source is too large.

I've tried to shrink to DVD5 size using DVDFab 5, 6 and 7, and even tried [other software]. After a successful shrink (as reported by the various programs), I still get the message that the source is too large when trying to burn.

Indeed, the size of the VIDEO_TS folder is 4.91GB.

What might be making the file(s) grow after shrinking it?

[AGJ]

Sorry but we can only trouble shoot problems where DVDFab was used for the entire process. So use DVDFab to rip and shrink and burn then if same problem post back with log files created by DVDFab.

[omegaspeedmaster]

As I mentioned, the folder grows to 4.91GB when I try to shrink the un-shrunk main title which has been ripped to my hard drive.

This report was generated by trying to compress and burn in one shot.
The same thing happens when I compress to my hard drive instead of trying to burn.
The folder always grows back to 4.91GB.
very strange.

7/1/2010 8:15:33 PM error Can't write: Size of scanned files is too big for that kind of media
7/1/2010 8:15:33 PM info Scanned files #9, folder #2 - total size 5272377344 b. (4.91 Gb.)
7/1/2010 8:15:33 PM info Inserted media type : DVD-R
7/1/2010 8:15:33 PM info Write started
7/1/2010 8:05:11 PM info New media inserted. Burning layer is ready to write
7/1/2010 8:05:09 PM info Compatible media types : DVD-R, DVD-RW Seq., DVD-RW RO, DVDRAM, DVD+R, DVD+RW, CD-R, CD-RW, DL DVD+R, DL DVD-R
7/1/2010 8:05:09 PM info New Drive selected : 0:1:0 - HL-DT-ST DVDRAM GSA-H42L SL01 [D] (Ide)
7/1/2010 8:04:49 PM info New media inserted. Burning layer is ready to write
7/1/2010 8:04:17 PM info Media removed. Burning layer not ready to write
7/1/2010 8:02:19 PM info New media inserted. Burning layer is ready to write
7/1/2010 8:02:17 PM info Current Drive selected : 0:1:0 - HL-DT-ST DVDRAM GSA-H42L SL01 [D] (Ide)
7/1/2010 8:02:17 PM info Using Patin-Couffin driver Version 1.37, Internal revision 37 - Async. Access mode
7/1/2010 8:02:17 PM info User default language : 1033 (0x0409h) - English (United States)
7/1/2010 8:02:17 PM info System default language : 1033 (0x0409h) - English (United States)
7/1/2010 8:02:17 PM info DLL Version 2.1.7.338
7/1/2010 8:02:17 PM info DLL C:\Program Files\DVDFab 5\vso_hwe.dll
7/1/2010 8:02:17 PM info Version 5, 0, 3, 0
7/1/2010 8:02:17 PM info ExeName : "C:\Program Files\DVDFab 5\DVDFab 5.exe"
7/1/2010 8:02:17 PM info OS : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
7/1/2010 8:02:17 PM info ******************** Report session started ********************

[AGJ]

7/1/2010 8:02:17 PM info Version 5, 0, 3, 0

Update to latest released beta as we do not support old outdated versions of DVDFab. Here is link to latest beta Also use the original DVD not a file saved on computer as we do not know if the other program did anything wrong when it ripped that DVD. Another thing since this was a file already saved on your computer maybe try to Disable Pathplayer to see if that works

[CBR929]

omegaspeedmaster
If I also may add to AGJ excellent advise you should also update your OS from SP2 to SP3 and stay current with all updates
CBR929

[omegaspeedmaster]

Thank you for the advice, but exactly how does any of this affect the fact that a movie that should be shrunk to 4.3GB winds up at 4.91GB?
Does SP3 have a new patch that keeps a file that should be compressed from "blowing up"?

I've never seen this before.
If it's a new copy protection scheme, then so be it.

[AGJ]

I did Invictus with no problems using Just DVDFab so like I said use DVDFab to rip compress and burn and do not use the already saved file on HDD as it was not DVDFab that ripped that file.

DVDFab is tested and updated using all supported OS with all updates that are released so if your computer not up to date then that can be part of the problem