DVD Rebuilder (CCE One-Click Beta v0.46) Comments and Suggestions

[jdobbs]

Now that's interesting. I'm not sure why it would even make a difference. I'll look at it.

[kbello]

A little think more, i add a 0 byte of VIDEO_TS.VOB in source directory, then get vts sectors and do all process again (prepare, encoding and rebuild) and works fine. I get error 9 when i add 0 byte file without get vts sectors.

I try put 0 byte file in source directory and only do rebuild pass again, works fine too.

[HarryM]

I copy Mpeg2dec3dg.dll to my Avisynth plugins directory, as as mentioned by DVD-Rebuilder installation informations.
I forget to delete (old) Mpeg2dec3.dll...! :confused:

I have actually in Avisynth directory Mpeg2dec3dg.dll and Mpeg2dec3.dll (both of them files). Which one plugins being used (automatically) for mpeg2 decoding???
Must I repeat reencoding?

[WndrBr3d]

So, I'm not a video expert by any means. So if I'm incorrect in this post, please feel free to correct me. :D

Tonight I tried backing up my Voyager Season 1 Box Set. Figured ~3 hours of video per disc would be a good check for DVD-RB.

The output from CCE was -very- jerky and studdery. Sorta like, it'd go back 1 frame every now and then (if that makes any sense).

To check the framerates, I:

1) opened DVD2AVI
2) selected the VOB from the decrypted DVD
3) and hit F8

DVD2AVI says the framerate is 29.970fps

I did the same with one of the M2V files output by CCE and it's framerate was 23.967fps. This strikes me as odd because I double checked the V03A.D2V created by DVD-RB and it had "Frame_Rate=29970"

I'm at a loss. Anywone have an idea??

OH, jdobbs, incase you're reading, I donated $9.05. I know, odd number, but it was all I had in my PayPal account. Again, great program! :D

[DrVenkman]

A little problem I got is that I tried backing up 'Black Hawk Down' R2 Pal. Now the disc itself is around 6.5 Gigs, with about 6 gigs being just the movie. I ran the 'Prepare' stage and got this;

-----------------
Phase I, PREPARATION started - Time: 12:20:21
- VTS_02: 2,878,832 sectors.
-- Scanning and writing .D2V file
-- 207,650/0 FRAMES/RFFS
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 41.4%
- Overall Bitrate : 1,889Kbs
Phase I, PREPARATION complete - Time: 12:25:34

Surely 1.8kbs is a bit low for a movie like BHD? So I started encoding with CCE and worked out roughly (By the file size it was so far compared to the percentage completed) that I would get about a 3-3.5gb output file.

Any suggestions?

[djan]

People, this thread is concerned for "Comments and Suggestions", don't post your bugs and problems here please.

[DrVenkman]

Sorry for posting it here - I'll copy it over to the other thread. But no, it isn't DTS - as far as I'm aware the DTS is only on the Superbit issue of the film.

[SAPSTAR]

Hi,

Few results for the community and jdobbs:

SUPERBIT Crouching Tiger, Hidden Dragon : DVDRB .31, Ecl 1.7b, CCE SP Trial (3 pass + 1 vaf) : Worked perfectly, burned with Nero without any problem. Playing flawless in my Sony DVP NS 715P.

LOONEY TUNES Back In Action : DVDRB .31, Ecl 1.7b, CCE SP Trial (3 pass + 1 vaf) : Worked perfectly, burned with Nero without any problem. Playing flawless in my Sony DVP NS 715P.

PITCH BLACK : DVDRB .31, Ecl 1.7b, CCE SP Trial (DVD Shrink to reduce the extras, then 3 pass + 1 vaf, 4 passes on extras) : Error 0004 , buffer overflow in the rebuild phase :devil: . I'll investigate tonight why. I don't think it's still frame error.

[StifflerStealth]

Originally posted by WndrBr3d
So, I'm not a video expert by any means. So if I'm incorrect in this post, please feel free to correct me. :D

Tonight I tried backing up my Voyager Season 1 Box Set. Figured ~3 hours of video per disc would be a good check for DVD-RB.

The output from CCE was -very- jerky and studdery. Sorta like, it'd go back 1 frame every now and then (if that makes any sense).

To check the framerates, I:

1) opened DVD2AVI
2) selected the VOB from the decrypted DVD
3) and hit F8

DVD2AVI says the framerate is 29.970fps

I did the same with one of the M2V files output by CCE and it's framerate was 23.967fps. This strikes me as odd because I double checked the V03A.D2V created by DVD-RB and it had "Frame_Rate=29970"

I'm at a loss. Anywone have an idea??


DVD-RB Creates 2 d2v files. one labled vo3a.d2v and the other vo3b.d2v. You need to look in the avs files to find out which one is used. For eaxample: mpeg2source("D:\DVDRECODE\D2VAVS\V01B.D2V"). The "a" file has information for 29.97 fps and the "b" file has information for 23.976 fps. It sounds like your files point to the "b" file which means dvd-rb detected it as film. If the video is truely 29.97 fps then this might be a bug in the detection which needs to be posted in the bugs section.

Stiff

[jdobbs]

Originally posted by WndrBr3d
So, I'm not a video expert by any means. So if I'm incorrect in this post, please feel free to correct me. :D

Tonight I tried backing up my Voyager Season 1 Box Set. Figured ~3 hours of video per disc would be a good check for DVD-RB.

The output from CCE was -very- jerky and studdery. Sorta like, it'd go back 1 frame every now and then (if that makes any sense).

To check the framerates, I:

1) opened DVD2AVI
2) selected the VOB from the decrypted DVD
3) and hit F8

DVD2AVI says the framerate is 29.970fps

I did the same with one of the M2V files output by CCE and it's framerate was 23.967fps. This strikes me as odd because I double checked the V03A.D2V created by DVD-RB and it had "Frame_Rate=29970"

I'm at a loss. Anywone have an idea??

OH, jdobbs, incase you're reading, I donated $9.05. I know, odd number, but it was all I had in my PayPal account. Again, great program! :D If it was marked at 23.976 that means it was a FILM source that has telecining. The AVS should point to V03B.D2V. It is normal for the framerate to read as 29.97 after pulldown has been applied (in rebuild). This will all change on the version I'm working right now. There will only be one D2V file and the rebuilt file will match exactly what was in the original.

[nimbles]

hey guys sorry to dredge this up again, but was just looking at a dvd-rb tutorial over on another forum (cdr-dvd base- if i'm allowed to say that), and i'm a bit confused as to how the treatment of interlaced sources work- the tutorial is for pre v31 so has got me thinking what to do for v31 as some options re: audio and interlaced sources are different.

in dvd-rb v31, what happens if you don't use the "deinterlace with decomb" options on an interlaced source?

I'm pretty sure i didn't use it the last time (did an r1 disc, turned it off- then forgot to turn it back on) but i'm not sure that it had any effect.

when you use the deinterlace with decomb, does the the ConvertToYUY2() option need to be unchecked.

Sorry for the newb questions- i'd done 4 successfully without really thinking about what all the options meant! :rolleyes:

[jdobbs]

Originally posted by nimbles
hey guys sorry to dredge this up again, but was just looking at a dvd-rb tutorial over on another forum (cdr-dvd base- if i'm allowed to say that), and i'm a bit confused as to how the treatment of interlaced sources work- the tutorial is for pre v31 so has got me thinking what to do for v31 as some options re: audio and interlaced sources are different.

in dvd-rb v31, what happens if you don't use the "deinterlace with decomb" options on an interlaced source?

I'm pretty sure i didn't use it the last time (did an r1 disc, turned it off- then forgot to turn it back on) but i'm not sure that it had any effect.

when you use the deinterlace with decomb, does the the ConvertToYUY2() option need to be unchecked.

Sorry for the newb questions- i'd done 4 successfully without really thinking about what all the options meant! :rolleyes: That is the goal... the options are for experts -- the defaults should always work. The only time you really need to use this is if you are planning to play your movies back on a computer because some computer players don't handle interlacing well. It "smooths" the edges of frames that result from interlacing. A television is designed to work with interlacing -- so in that case its almost always best to leave it alone.

I don't know what the guide said. Actually I'm surprised there is a "guide" for software that is still in beta. I don't think that will stay current very long.

More importantly -- you'll find that truly interlaced material isn't really that common.

[party_power]

Hi there!
It's my first time in this forum and I've tested the dvd-rb for some time now. It's a great program.
But i have found a little problem with the program when playing the dvd's it produce on my dvd. The problem is not video related or something like that. It has to do with showing time elapsed on the movie, when i use fast reverse then the chapters don't change and the time elapsed goes wrong.
I have tested the dvd-rb v30 and dvd-rb v31, with same results.
When i have used "shrink or IC7" then this problem not exists.
I just want to report this. Maybe others have not seen this problem, because it's not a huge problem..
Maybe the problem is just on my dvd player :)

[jdobbs]

Originally posted by party_power
Hi there!
It's my first time in this forum and I've tested the dvd-rb for some time now. It's a great program.
But i have found a little problem with the program when playing the dvd's it produce on my dvd. The problem is not video related or something like that. It has to do with showing time elapsed on the movie, when i use fast reverse then the chapters don't change and the time elapsed goes wrong.
I have tested the dvd-rb v30 and dvd-rb v31, with same results.
When i have used "shrink or IC7" then this problem not exists.
I just want to report this. Maybe others have not seen this problem, because it's not a huge problem..
Maybe the problem is just on my dvd player :) It could theoretically be your player -- but not likely. There was an earlier post buried somewhere in the mega-trail that mentioned this as well.

[Sir Didymus]

In fact the chapter and time issue has been already reported in more than one place; see for example:

http://forum.doom9.org/showthread.php?s=&threadid=73853&perpage=20&pagenumber=4

[party_power]

Ok. I have not read all threads yet, because im really new here.
But thanks for reply so fast..
Keep up the good work.

[YaoMing11]

Is there a way to set your own compression percentage in DVD-RB?
I made a 200mb sample of an original DVD and I compressed with DVD shrink and IC8. I compressed it to 60% in both so I know the full size will fit on a DVD-5. Is there a way to set 60% compress ratio for a 200mb file in DVD-RB? I'd like to compare it to IC8 and DVDshrink without encoding the whole movie.

[rayvt]

Do a three-phase rebuild. After the prepare phase, edit the control file (rebuilder.ecl or rebuilder.inf) and change the targert bitrate or the compression percentage, as appropriate.

The do ENCODE and REBUILD.

[Knocks]

Downloaded the program for the first time. What a great idea! Thanks a lot. I hope this software becomes as easy to use as DVD Shrink. We really needed an easier solution for those huge movies that Shrink couldn't handle without visible artifacts (under 75% compression). Keep up the good work.

[Joergen]

YaoMing: There really is no comparison.. if your compress goes below ~75% CCE is king.. And it continues to kick ass until around 35% where most material just goes below what MPEG2 can handle

edit; I have to say, I check this forum 10 times a day to see for dvd-rb progress. I havent been this excited since the first version of dvdshrink came out a year ago. :D

[jdobbs]

NEW DVD REBUILDER VERSION 0.39 ATTACHED

Attached is the latest version of DVD ReBuilder. I think you'll find a lot of feature requests and reported bugs addressed in this version -- I've made a lot of changes some of those are:

- Many very large changes and significant enhancements in this version.

- Implemented code that handles STILL frames. Eliminates most if not all of the "0004" error codes. Needs more testing as to how well it works.

- Corrected an error that would cause significant output undersizing when using cell-dynamic bitrate allocation.

- Fixed error in which selected AudioDub(BlankClip())was not properly working upon program load.

- Inserted code that captures and retains the original state of progressive_flag, TFF, and RFF so they can be applied exactly in the rebuild phase. Previously they had been added independently. This should assure a more accurate reproduction of the original DVD.

- Removed the "Automatic FILM" and "Force FILM" options. These were previously used to make a decision (familiar to old CCE method users) as to whether to create an output of 23.976 or 29.97 at the cell level (for either telecining or not telecining for NTSC users). DVD-RB now keeps the original frame structure intact through all three phases -- eliminating annoying conversion errors. These manifest themselves as either a combed appearance on telecined-to-standard or occasional frame jumps on standard-to-telecined conversions. Mixes of the two in the same Cell are no longer a problem. The "AutoFILM Threshold" parameter has also been removed for the same reason.

- Only one .D2V file is written now due to the two changes above so all files refer to the same .D2V. Note: All frame rates for NTSC will list in the D2V file as 23976 regardless of original -- it truly has no purpose in the new method as all frames are treated equally -- please don't change it, as CCE and other encoders can abort on illegal values.

- Encoding speeds for FILM sources should increase through MPEGDEC3DG.DLL due to a reduced complexity in the source stream. My experience is that it improves by about 15% (I went from 1.75 to 2.16). Note that non-telecined source speeds may also appear to increase on NTSC sources due to the fixed 23.976 feeder framerate -- but in reality remain the same (although the CCE "Speed:" scale will appear higher -- the "Elapsed Time:" remains the same).

- Added summary report for each PREPARE that informs you of the maximum and minimum bitrates calculated by cell. Also summarized time in minutes, high bitrate, and low bitrate (per cell) for all batch jobs.

- Fixed an error in which DVD-RB would bomb and abort if the source path is not available during startup. The problem was usually caused by setting the source path to a mountable drive that had been unmounted between DVD-RB runs.

- Fixed an error that was causing a partial frame to be present at the start of each VTS when performing a ReJig encode. The error was caused by DVD-RB's demuxing routine. It is usually seen as a greenish flash and a possible stutter at the start of a chapter.

- Added code the makes it possible to choose which VTSs you want to apply the 4:3->16:9 conversion and also the Half-D1 option. I purposely made it so it doesn't stick between encode -- nothing is more annoying than waiting 5 hours only to find out you accidently did a Half-D1 encode.

As always please post any errors you may find in the error thread and my thanks go to all the incredible beta testers for pointing out the areas most in need of improvement. jdobbs

Note: Updated on 11 April 2004
The following change was made in version 0.34

- Fixed an error in which the input resolution as specified in the IFO file was not being updated when a VTS was converted to Half-D1 and the 16:9 flag was set incorrectly (a stupid bug)

Note: Update again on 12 April 2004
The following changes were made in version 0.35

- Found and fixed an error in the audio masking routines. On certain DVDs the audio was being incorrectly removed on higher number VTSs.

- Fixed an idiotic bug that caused ReJig to get stuck in a forever loop while processing cell files.

Note: Update again on 13 April 2004
The following changes were made in version 0.36

- Added an "Advanced" option in which the "interlaced=true" parameter of ConvertToYUY2() can be disabled. Also moved the DECOMB, 4:3->16:9, and Half-D1 options into the advanced area.

- Added additional helpful data to the VTS listbox. It now tells you the size of the VTS (including menus) and the aspect ratio.

- Fixed (again) an error that was causing 16:9 flags in the IFO to not be updated correctly when using the Convert 4:3->16:9 option.

- Inserted code that does a sanity check before starting encoding to make sure the "PREPARE" pass was performed in the same mode (CCE, ReJig, QuEnc).

- Found and corrected a minor timing discrepancy associated with PTS. This may have an affect on reported chapter point "stuttering" but if is far from conclusive and work continues.

Note: Update again on 13 April 2004
The following changes were made in version 0.37

- Fixed error in which encoding was prevented by the "wrong encoder" error message.

- 0.37a fixed a bug that bombs when attempting to abort an encoding.

Note: Update on 14 April 2004
The following changes were made in version 0.38

- Added code to support "Stop/Pause" function during encode phase. If you stop an encode and then restart, you will be prompted as to whether you wish to continue after the last successful segment, or at the beginning. Please note that if you are running in "Batch" mode -- no prompt will be given and all jobs start at the beginning.

- Added the "offset_line=" to ECL files created under the "CCE SP v2.66+" option, versions 2.67 and above use this instead of "top_first=" -- note that when choosing that option both parameters will be included in the .ECL. On the Version 2.66 SP that I've tested (demo with eclCCE) it doesn't seem to hurt to have the additional parameter in the file. My wish is that they would stop changing parameters and keep upward compatibility in their ECLs.

- Added a sanity check for PREPARE phase to stop bombing when the source or destination fields are empty.

- Fixed bug that was related to sources that use Bottom Field First with CCE. The motion blur, "ghosting" and strange motion should be gone now.

Note: Update on 15 April 2004
The following changes were made in version 0.39

- Fixed a bug in which LPCM that was deselected (chosen to be removed) was not being properly removed or calculated for removal.

- Fixed an error related to field based stream processing. This should eliminate many if not all of the "Error code '9'" messages received in the PREPARE phase. A special thanks to Msc_Alex and RB for helping solve this one.

- Added an INI option making it possible to set the minimum and maximum bitrates when doing CCE VBR encoding. They are min_bitrate=nnnn and max_bitrate=nnnn (in Kbps. Example: max_bitrate=9000). Just set them under [Options] in REBUILDER.INI. No error checking is done on the numbers so take care. This should be changed only by advanced users as setting them incorrectly can seriously degrade the quality of the picture. Also note that hanging them can cause oversized or undersized output.

- Implemented new code for handling BFF sources. Instead of converting to TFF as was done in v0.38, this version duplicates the original more closely (if the source cell was bottom field first, the newly created cell will be also.

- Changed logic in batch mode so the status window isn't cleared for each job and all activity can be printed or reviewed upon completion.


A NEWER VERSION IS AVAILABLE - SEE THE FIRST POST IN THIS THREAD

[nwg]

Excellent, thanks.

[StifflerStealth]

Did I miss the release of v0.32? My last version Dled is v0.31.

Stiff

[wmansir]

Originally posted by StifflerStealth
Did I miss the release of v0.32? My last version Dled is v0.31.

Stiff

No, you didn't miss a release, even the changelog skips v0.32. Since this version contains extensive changes to the way the software operates, I assume Jdobbs kept .32 to himself while working out the major kinks.

[jdobbs]

Originally posted by StifflerStealth
Did I miss the release of v0.32? My last version Dled is v0.31.

Stiff No. It was a small update that I decided not to release. It exists only as a backup in a directory (just in case there is something major wrong with 0.33).

Note: Wow. I noticed when posting earlier that there were 8,303 downloads of version 0.31.

[StifflerStealth]

That makes scense. Nice work on v0.23! I will start an encode tonight before I go to bed.

Stiff

[nwg]

- Fixed an error that was causing a partial frame to be present at the start of each VTS when performing a ReJig encode. The error was caused by DVD-RB's demuxing routine. It is usually seen as a greenish flash and a possible stutter at the start of a chapter.

Is this the same stutter I was getting with CCE. I was getting the same stutter with rejig and CCE.

- Added code the makes it possible to choose which VTSs you want to apply the 4:3->16:9 conversion and also the Half-D1 option.

What benefit does this do? I know it reduces the resolution to 352 x 480/576. Does it use less disc space?

[Joergen]

As the spanish would say, "Excellenté!" (also doubles as a Homer Simpson quote)

[jdobbs]

Originally posted by nwg
Is this the same stutter I was getting with CCE. I was getting the same stutter with rejig and CCE.



What benefit does this do? I know it reduces the resolution to 352 x 480/576. Does it use less disc space? They were requests. It doesn't use less disc space as DVD-RB fills the disc -- but it can give you a better picture within the available bandwidth. When I perfect the ability to allocate different amounts of bandwidth to extras and main movie it will be a way to get a decent picture out of the extras at a very low bitrate. The 16:9 from 4:3 converter is meant to deal with letterboxed (widescreen) movies that are in fact 4:3 with black borders at the top and bottom. It will turn it into a 16:9 anamorphic copy.

I use that feature occasionally because I simply hate playing 4:3 movies on my high-definition 16:9 television, and the "zoom" feature of DVDs and TVs can suck pretty badly... so I put there for convenience.

[Rombaldi]

Originally posted by jdobbs
The 16:9 from 4:3 converter is meant to deal with letterboxed (widescreen) movies that are in fact 4:3 with black borders at the top and bottom. It will turn it into a 16:9 anamorphic copy.

el Stupido question here... can I (safely?) assume that when doing that, that the resultant encoded MPEG2 stream will have the 16:9 flag set and the appro entries in the IFO changed as well?? (I leave the potential insanity of a 16:9 video in the same VTS as a 4:3 menu without an alternate subpicture for the menu as something better not said).

[Joergen]

Amazing stuff!

jdobbs: If I may suggest, you could make the half-d1 automatic if it seems a title goes dangerously low in bitrate when the user fiddles around with the bitrate balance. Or perhaps at least a suggestion box saying ".. bitrate is very low for this item, do you want to half-d1 it" etc.

A similar suggestion box might do well for the anamorphic compression stating that it's "..only for converting a RARE letterbox 4:3 movie to true 16:9 and should not be applied to 2.35:1 anamorphic" that also has "black bars", ie check if the title is already marked 16:9 perhaps.

[jdobbs]

Originally posted by Rombaldi
el Stupido question here... can I (safely?) assume that when doing that, that the resultant encoded MPEG2 stream will have the 16:9 flag set and the appro entries in the IFO changed as well?? (I leave the potential insanity of a 16:9 video in the same VTS as a 4:3 menu without an alternate subpicture for the menu as something better not said). Yes. If you make this selection, the video is tagged at 16:9 and the IFO flag is set during the REBUILD.

[nwg]

The 16:9 from 4:3 converter is meant to deal with letterboxed (widescreen) movies that are in fact 4:3 with black borders at the top and bottom. It will turn it into a 16:9 anamorphic copy.

Thanks for the reply.

Wow, I like that.

I have The Thing and X Files: The Movie which are non anamorphic 16:9. I will have to try that with those ones.

I also can see why the Half D1 maybe useful for extras.

BTW, with Master and Commander the overall percentage was 49% and came out at 3.7GB. It is now 59% (both DTS and DD included). It looks like the undersizing bug is fixed.

[jdobbs]

Originally posted by Joergen
Amazing stuff!

jdobbs: If I may suggest, you could make the half-d1 automatic if it seems a title goes dangerously low in bitrate when the user fiddles around with the bitrate balance. Or perhaps at least a suggestion box saying ".. bitrate is very low for this item, do you want to half-d1 it" etc.

A similar suggestion box might do well for the anamorphic compression stating that it's "..only for converting a RARE letterbox 4:3 movie to true 16:9 and should not be applied to 2.35:1 anamorphic" that also has "black bars", ie check if the title is already marked 16:9 perhaps. Actually I had another resizer that can take a 2.35:1 movie and make it into a 16:9 -- but I pulled it out because... well... it's sacrilege.

[jdobbs]

Originally posted by nwg
Thanks for the reply.

Wow, I like that.

I have The Thing and X Files: The Movie which are non anamorphic 16:9. I will have to try that with those ones.

I also can see why the Half D1 maybe useful for extras.

BTW, with Master and Commander the overall percentage was 49% and came out at 3.7GB. It is now 59% (both DTS and DD included). It looks like the undersizing bug is fixed. Something I forgot to mention because it was obvious to me... but maybe not to everyone... These options won't work with ReJig because it doesn't reencode.

[Joergen]

Yes I remember how one of the most nagging request for dvdshrink in the early days were resolution conversions (and of course it cant cause its a transcoder, well not without losing all quality at the same time!). DVD-RB will kick hiney in this department aswell.

[jdobbs]

Originally posted by nwg
Thanks for the reply.

Wow, I like that.

I have The Thing and X Files: The Movie which are non anamorphic 16:9. I will have to try that with those ones.

I also can see why the Half D1 maybe useful for extras.

BTW, with Master and Commander the overall percentage was 49% and came out at 3.7GB. It is now 59% (both DTS and DD included). It looks like the undersizing bug is fixed. Good. That bug took me forever to find -- and of course it was something simple. In my calculations I was adding the RFF flags to the frame count to get frames-per-second -- but was sometimes doing it twice.

[Rombaldi]

Originally posted by jdobbs
Yes. If you make this selection, the video is tagged at 16:9 and the IFO flag is set during the REBUILD.

Execccccccllent.... MST3K: The Movie, here I come..

now, when you can do PAL>NTSC......

(ducks and runs for the nearest cave...)

[nwg]

Good. That bug took me forever to find -- and of course it was something simple. In my calculations I was adding the RFF flags to the frame count to get frames-per-second -- but was sometimes doing it twice.


I haven't finished the encoding yet but, I am optimistic that it will be ok.

Edit - it tuned out at 4.31GB :)

[Joergen]

Of course PAL users dont need conversions cause NTSC movies show happily on their players thanks to RGB PAL60 (only diff you will notice are a few less horizontal lines like NTSC has, and in case of videogames slightly faster framerate). If a PAL user has a pre 1985 TV that doesnt support PAL60.. let him not watch the damn movie! ;)

[jdobbs]

Originally posted by Rombaldi
Execccccccllent.... MST3K: The Movie, here I come..

now, when you can do PAL>NTSC......

(ducks and runs for the nearest cave...) As you mentioned, though, if the original has a menu in the main VTS or BOV, it's better to leave it unchecked. Most of the time on those movies though, the menus are in the VTS_XX_0.VOB, which is left untouched by DVD-RB.

I could to PAL to NTSC and back... AVISYNTH can do anything.

[Joergen]

Say I actually have an idea that somebody might find useful:

Have the option for a third path for rebuild phase. Ie I have two HD's and like to do HD->HD work with large files (cause its twice as fast naturally). So when I set the working path to the second HD, it would be great to then recompile the compressed m2v back to the first HD again where the source path lies in a different dir (unless processing the source vobs for audio/subs makes this redundant).

[jdobbs]

Originally posted by Joergen
Say I actually have an idea that somebody might find useful:

Have the option for a third path for rebuild phase. Ie I have two HD's and like to do HD->HD work with large files (cause its twice as fast naturally). So when I set the working path to the second HD, it would be great to then recompile the compressed m2v back to the first HD again where the source path lies in a different dir (unless processing the source vobs for audio/subs makes this redundant). When rebuilding both the M2Vs and the original VTSs are providing input (video from the M2Vs and audio/subpictures from the VTS). So you'd still be competing for usage on one or the other... unless of course you used the same drive for phases 1 and 2 and then rebuilt to a 2nd drive. Unfortunately, I'm not sure how much time you will save overall -- rebuilding really doesn't take that long.

[DDogg]

Originally posted by jdobbs
When I perfect the ability to allocate different amounts of bandwidth to extras and main movie it will be a way to get a decent picture out of the extras at a very low bitrate. You may want to grab a copy of "Good Fences" when you start this next phase of BR allocation. This movie could be an iron plated rascal to do. 4:3, full NTSC interlace, 5 freaking trailers of the same spec. The movie alone is going to need 3742 kbps just to do a Q32 equiv. I have not broken it apart yet, but I'm thinking going 1/2D1 on the trailers is the only thing that is going to free up enough available BR to swing it. Btw, love the new structure and log:

-----------------
Phase I, PREPARATION started at 19:36:36
- VTS_01: 3,244,391 sectors.
-- Scanning and writing .D2V file
-- Processed 213,468 frames.
-- Building .AVS and .ECL files
- VTS_02: 237,077 sectors.
-- Scanning and writing .D2V file
-- Processed 16,747 frames.
-- Building .AVS and .ECL files
- VTS_03: 199,497 sectors.
-- Scanning and writing .D2V file
-- Processed 15,186 frames.
-- Building .AVS and .ECL files
- VTS_04: 239,946 sectors.
-- Scanning and writing .D2V file
-- Processed 18,271 frames.
-- Building .AVS and .ECL files
- VTS_05: 38,852 sectors.
-- Scanning and writing .D2V file
-- Processed 2,980 frames.
-- Building .AVS and .ECL files
- VTS_08: 43,985 sectors.
-- Scanning and writing .D2V file
-- Processed 3,372 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 50.0%
- Overall Bitrate : 2,365Kbs
- HIGH/LOW Cell Bitrates: 2,432/500 Kbs
Phase I, PREPARATION completed in 5 minutes.originally posted by jdobbs
Actually I had another resizer that can take a 2.35:1 movie and make it into a 16:9 -- but I pulled it out because... well... it's sacrilege. Yeah, well I wish you had left it in. Those that think it, don't have to use it. They can just squint their eyes instead and bask in the warm feelingez of being non sacriligiousez.:rolleyes:

[Joergen]

I need not squint my eyes on my 32" 16:9 sony wega and it's not even "that big" nor expensive ;) And these days many players tend to have several levels of "zoom" that does the same thing basically.

But I do understand the plight of those 4:3 users.

EDIT: I mean to ask something.

jdobbs: It was unclear from the changelog (countless hours of work again and all appreciated to the most!) if you had ideas for the stuttering some were having or if you did changes that might eliminate it. I've not had stuttering since 0.31 though with CCE.

[DDogg]

Originally posted by jdobbs- Only one .D2V file is written now due to the two changes above so all files refer to the same .D2V. Note: All frame rates for NTSC will list in the D2V file as 23976 regardless of original -- it truly has no purpose in the new method as all frames are treated equally -- please don't change it, as CCE and other encoders can abort on illegal values.
I don't get this yet and could use some help understanding. If my source is 29.97 NTSC Interlaced how can the d2v be showing 23.976 and provide the proper information? Are you actually decrementing? Or, are you saying these new method d2v are now specific only to dvd-rb and can't be used for anything else? I'm trying to use the dvd-rb created d2vs to do bitrate projection which depends on knowing the framerate :confused:

[djkilla]

Looks like this program is making waves. I heard about it at the http://www.altbinariesdvdr.net/ and thought I'd try it out. I have two questions before trying my first DVD.

1) Under 'Mode', what does 'Dynamically Assign Cell Bitrates' do?

2) Under 'Options' and 'Setup', I set the path to MPEG2DEC3DG.DLL. What does the check box 'Add To AVS File' do?

Thanks in advance to *everyone* that helps!

-D j K i l l a-

[jdobbs]

Originally posted by DDogg
I don't get this yet and could use some help understanding. If my source is 29.97 NTSC Interlaced how can the d2v be showing 23.976 and provide the proper information? Are you actually decrementing? Or, are you saying these new method d2v are now specific only to dvd-rb and can't be used for anything else? I'm trying to use the dvd-rb created d2vs to do bitrate projection which depends on knowing the framerate :confused: No I'm not decrementing. Every single frame is being processed end-to-end. But, if you watched a 29.97fps portion it will appear to be slowed down. Essentially I'm saying a frame is a frame.

The idea is that if I record the flags and ignore the rate (make it constant), and then reinsert the flags verbatim on rebuild, I will have a perfect representation of the original (even if it changes to and from telecine every few GOPs -- as some do). I set the framerate back to its correct value at REBUILD also. The only thing that is preserved in the .D2V is TFF -- just to make sure I don't get field shift during encoding.

One big advantage is speed. I've noticed that by taking "Force FILM" out of the equation for FILM sources I can increase the encoder rate significantly.

If you'd like I can still create the original .D2Vs also, it's a couple of lines of code change.

You'll also notice a new file in the directory that ends with .FLG -- it holds the progressive_flag, TFF, and RFF flags for each frame in temporal order. Bits 2,1, and 0 represent progressive_flag, TFF, and RFF respectively.

[jdobbs]

Originally posted by djkilla
Looks like this program is making waves. I heard about it at the http://www.altbinariesdvdr.net/ and thought I'd try it out. I have two questions before trying my first DVD.

1) Under 'Mode', what does 'Dynamically Assign Cell Bitrates' do?

2) Under 'Options' and 'Setup', I set the path to MPEG2DEC3DG.DLL. What does the check box 'Add To AVS File' do?

Thanks in advance to *everyone* that helps!

-D j K i l l a-

1. Dynamically assign cell bitrates analyzes the original stream and gives more bandwidth to cells that needed more in the original encode. If you don't check it, the same average bitrate will be used for the entire set of Cells -- it is debatable how much difference it makes. But I think you are probably always better off settting it on.

2. If you correctly configure MPEG2DEC3DG.DLL by inserting in the plugins directory of AVISYNTH -- you shouldn't need to use this at all. But some 3rd party software has a habit of changing the registry pointer to the plugin directory -- and that can make DVD-RB (and every other AVISYNTH related package for that matter) fail to find a plugin. Setting the path here and checking the box adds a line to every .AVS file that specifically spells out an entire path to the plugin.

[donny74]

Thanks Jdobbs, I definitely noticed the speed increase when encoding. I'm currently backing up my Two Towers_ext 3rd disk which contains tons of "stills" and was unsuccessful during rebuild in v0.31. My encoding speed has gone up from 2.75 in v0.31 to 3.25+ in v0.33. If you can implement any other type of speed boosts that would awesome. As usual keep up the fabulous work . I'll let you know if rebuilding this DVD works in v0.33 or not.

Update: Well v0.33 is getting alot farther along then the previous version. I got the error #0004 at 85% mark of rebuilding w/ v0.31.

With v0.33 this is how far I got before I got that same error:
Movie: LOTR: The Two Towers Extended Disc 3
ECLCCE 1.8B CCE 2.67.0.23

Progress: V06068600687001.M2V
Overall: 100.0%

Updating information in NAVPACKS...
Rebuilding segment 686 VOBID:687 CELLID:1

DVD-RB Error

"DVD Rebuilder experienced a buffer overflow. Error #0004.Process must abort"
"Stop statement encountered"

I was certain this was going to be a successful rebuild but it gave that error at the 100% completion mark of rebuilding...

Jdobbs if you have this DVD can you try it and see if you get the same error? Has anyone been able to back up this DVD? Thanks in advance.