Over size output file

[jdobbs]

jdobbs, why make the DVD into an ISO and then mount it? What is so different from ripping it to the hard drive and calling it from there? Thanks.

I do a lot of testing, so I keep a lot of DVDs on my system at a time. It keeps them organized, and I can just mount them with Daemon Tools when I need to run a REBUILD against them.

[sockeye]

One last question. (sorry about being to lazy to research it), I have just upgraded to the Pro version. Should I uninstall the freeware version first, or install overtop?
Very fast response with the download link, I might add.
sockeye

[linx05]

Ah ok. That's fair enough.

EDIT: The freeware and the PRO are two different programs. So you can safely install both on the computer at the same time. I don't see any reason to have the freeware installed if you have the PRO version. Each to their own I guess.

[NightTran]

the pro version is worth every dime you spend on it

[sockeye]

Ah ok. That's fair enough.

EDIT: The freeware and the PRO are two different programs. So you can safely install both on the computer at the same time. I don't see any reason to have the freeware installed if you have the PRO version. Each to their own I guess.

Ok, thanks for that linx. I appreciate your help.

[blutach]

I guess if you are making an ISO, that should work, so long as DVDRB accepts the corruption still in the IFOs (which is manifest). Some of it is getting pretty crazy lately (eg Saw 3, Open Season). Amazing they are able to be played to tell the truth.

Regards

[NightTran]

I rip this file with ripit did not take out any thing and this is the log from dvd-RB

19:52:44] One Click encoding activated...
-----------------
[19:52:44] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.7.0
- HC encoder selected
- Source: FLYBOYS
- VTS_03: 62,533 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 3,406 frames.
-- Building .AVS and .ECL files
- VTS_04: 3,787,988 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 199,505 frames.
-- Building .AVS and .ECL files
- VTS_05: 210,739 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 13,457 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 39.2%
- Overall Bitrate : 2,768/2,214Kbs
- Space for Video : 2,439,116KB
- HIGH/LOW/TYPICAL Bitrates: 2,794/1,178/2,214 Kbs
[20:00:24] Phase I, PREPARATION completed in 8 minutes.
[20:00:24] Phase II ENCODING started
- Creating M2V for VTS_03 segment 0
- Extracting STILLS for VTS_03 segment 1
- Creating M2V for VTS_04 segment 0
- Creating M2V for VTS_04 segment 1
- Creating M2V for VTS_04 segment 2
- Creating M2V for VTS_04 segment 3
- Creating M2V for VTS_04 segment 4
- Creating M2V for VTS_04 segment 5
- Creating M2V for VTS_04 segment 6
- Creating M2V for VTS_04 segment 7
- Creating M2V for VTS_04 segment 8
- Creating M2V for VTS_04 segment 9
- Creating M2V for VTS_04 segment 10
- Creating M2V for VTS_04 segment 11
- Creating M2V for VTS_04 segment 12
- Creating M2V for VTS_04 segment 13
- Creating M2V for VTS_04 segment 14
- Creating M2V for VTS_04 segment 15
- Creating M2V for VTS_04 segment 16
- Creating M2V for VTS_04 segment 17
- Creating M2V for VTS_04 segment 18
- Creating M2V for VTS_04 segment 19
- Creating M2V for VTS_04 segment 20
- Creating M2V for VTS_04 segment 21
- Creating M2V for VTS_04 segment 22
- Creating M2V for VTS_04 segment 23
- Creating M2V for VTS_04 segment 24
- Creating M2V for VTS_04 segment 25
- Creating M2V for VTS_04 segment 26
- Creating M2V for VTS_04 segment 27
- Creating M2V for VTS_04 segment 28
- Creating M2V for VTS_04 segment 29
- Creating M2V for VTS_04 segment 30
- Creating M2V for VTS_04 segment 31
- Creating M2V for VTS_04 segment 32
- Creating M2V for VTS_04 segment 33
- Creating M2V for VTS_04 segment 34
- Creating M2V for VTS_04 segment 35
- Creating M2V for VTS_04 segment 36
- Creating M2V for VTS_04 segment 37
- Creating M2V for VTS_04 segment 38
- Creating M2V for VTS_04 segment 39
- Creating M2V for VTS_04 segment 40
- Creating M2V for VTS_04 segment 41
- Creating M2V for VTS_04 segment 42
- Creating M2V for VTS_04 segment 43
- Creating M2V for VTS_04 segment 44
- Creating M2V for VTS_04 segment 45
- Extracting STILLS for VTS_04 segment 46
- Creating M2V for VTS_05 segment 0
- Creating M2V for VTS_05 segment 1
- Creating M2V for VTS_05 segment 2
- Creating M2V for VTS_05 segment 3
- Extracting STILLS for VTS_05 segment 4
- Extracting STILLS for VTS_05 segment 5
- Extracting STILLS for VTS_05 segment 6
- Extracting STILLS for VTS_05 segment 7
- Extracting STILLS for VTS_05 segment 8
[22:11:37] Phase II ENCODING completed in 131 minutes.
[22:11:39] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_03
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Processing VTS_04
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 21 VOBID 2 CELLID 1
- Rebuilding seg 22 VOBID 2 CELLID 2
- Rebuilding seg 23 VOBID 2 CELLID 3
- Rebuilding seg 24 VOBID 2 CELLID 4
- Rebuilding seg 25 VOBID 2 CELLID 5
- Rebuilding seg 26 VOBID 2 CELLID 6
- Rebuilding seg 27 VOBID 2 CELLID 7
- Rebuilding seg 28 VOBID 2 CELLID 8
- Rebuilding seg 29 VOBID 2 CELLID 9
- Rebuilding seg 30 VOBID 2 CELLID 10
- Rebuilding seg 31 VOBID 2 CELLID 11
- Rebuilding seg 32 VOBID 2 CELLID 12
- Rebuilding seg 33 VOBID 2 CELLID 13
- Rebuilding seg 34 VOBID 2 CELLID 14
- Rebuilding seg 35 VOBID 2 CELLID 15
- Rebuilding seg 36 VOBID 2 CELLID 16
- Rebuilding seg 37 VOBID 2 CELLID 17
- Rebuilding seg 38 VOBID 2 CELLID 18
- Rebuilding seg 39 VOBID 2 CELLID 19
- Rebuilding seg 40 VOBID 2 CELLID 20
- Rebuilding seg 41 VOBID 2 CELLID 21
- Rebuilding seg 42 VOBID 2 CELLID 22
- Rebuilding seg 43 VOBID 2 CELLID 23
- Rebuilding seg 44 VOBID 2 CELLID 24
- Rebuilding seg 45 VOBID 2 CELLID 25
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 46 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_04_0.IFO
- Updating TMAP table...
- Processing VTS_05
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 2 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 3 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 4 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 5 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 6 VOBID 6 CELLID 1
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 7 VOBID 7 CELLID 1
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 8 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- ISO Image successfully created.
[22:38:22] Phase III, REBUILD completed in 27 minutes.
Done.
[22:38:23] PREPARE/ENCODE/REBUILD completed in 166 min.

The final size is only 4.31

[Dialysis1]

4.31 is the same size I get with all my movies which is slightly more than 98% disc capacity.
Nice.

[NightTran]

4.31 is the same size I get with all my movies which is slightly more than 98% disc capacity.
Nice.

if you see it is 39.2 % and still look good

[Sharc]

19:52:44] One Click encoding activated...
-----------------
[19:52:44] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.7.0
- HC encoder selected
- Source: FLYBOYS

You are using AVISYNTH 2.5.7. From various post it seems that there are still lot ot concerns about using this latest version.

@sockeye:
What AVISYNTH version are you on? You should stick to 2.5.6 to exclude AVISYNTH as a possible source for the trouble.

[techreactor]

You are using AVISYNTH 2.5.7. From various post it seems that there are still lot ot concerns about using this latest version.

OT, avisynth 2.5.7 works fine, its just that most other software/tools need to catch up to it and make changes, compatible with new avisynth version.

[jdobbs]

I can only say that several users have reported problems with AVISYNTH v2.5.7. The problems run the gamut and don't seem to follow any pattern -- except that they all go away when you revert back to v2.5.6. I would highly recommend waiting until v2.5.7 is stable before using it with DVD-RB.

Also... since AVISYNTH is an "AVI Synthesizer" other packages shouldn't have to adapt. The actions of AVISYNTH should all be invisibly implemented. I can understand if some filters need to be adjusted, etc... but packages that are designed to accept AVIs for input (like encoders) shouldn't need to be updated.

[techreactor]

I can only say that several users have reported problems with AVISYNTH v2.5.7. The problems run the gamut and don't seem to follow any pattern -- except that they all go away when you revert back to v2.5.6. I would highly recommend waiting until v2.5.7 is stable before using it with DVD-RB.

Also... since AVISYNTH is an "AVI Synthesizer" other packages shouldn't have to adapt. The actions of AVISYNTH should all be invisibly implemented. I can understand if some filters need to be adjusted, etc... but packages that are designed to accept AVIs for input (like encoders) shouldn't need to be updated.

I do not agree to this statement in its entirety, since after reading this thread you would also understand that avisynth ver 2.5.7 has gone through changes and others need to adapt to it, in this case the changes to the encoder were required. It all depends on how the app/tool is initially coded to adapt, some might not need any change et-all.

[jdobbs]

I would submit that SAPSTAR shouldn't have had to make any changes to his software. I'm not sure what he ended up having to change in AQM, and it's good that he is willing to adapt to AVISYNTH 2.5.7 -- but he shouldn't have had to. The functions of the supporting DLL should have been contained. Of course, not knowing the details its possible that something in AQM wasn't meeting the original interface standards (especially since that specific problem was reported as not happening with other encoders).

The point I'm making is that a supporting utility shouldn't require all those programs calling it to adapt when it changes. That's just not the way it's supposed to work. That would be like Microsoft changing the WINSCK interface at the API level and telling everybody in the world to change the way they use TCP/IP == oh and by the way all Web Browsers, FTP, TELNET, Downloading, and Communications software will stop working in the meantime. When that sort of change is necessary, they add the new functionality -- but they grandfather in the legacy interaces so prior applications continue to work.

Since I'm sure the guys at SourceForge know that -- I would assume that the oddities reported in v2.5.7 are simply bugs in that software and they will get ironed out over time. In the meantime -- I'd recommend using v2.5.6.

[sockeye]

I am posting back to let everyone know that I resolved my issue of oversize file output. Unfortunately, I used more than 1 variable on my successful encode, so I cannot say with certainty what the problem was.
The following is what led up to my success:

After upgrading to V1.21, I ran my original file of FlyBoys (as I describe in post #1) thru DVDRB, at default settings, and the output was still oversized. (actually slightly bigger)
After reading the posts about AviSynth being a possible cause of the problem, (thanks Sharc, for bringing that possibility up) I realized that I was using 2.5.5. (I've got a lot to learn)
I updated to AviSynth 2.5.6,(thankyou jdobbs for your input about .7) checked movie and menus only, chose "best" for HC output, processed my original file, and ended up with a final output of 4.33gb.

I'm not sure if my success was because of:
1 Some extras being blanked by checking movie and menus (now available to me in Pro)
2 Updating AviSynth
3 Choosing a better quality output with HC (don't think so, but, I used normal originally)

If it would help, I could try again, eliminating the variables, but I suspect more experienced users will have an answer to what caused my initial problem.
Many thanks to everyone who helped me thru this
sockeye