Is DVD Rebuilder still the best solution around?

[rhaz]

It's been like ten years of using DVD Rebuilder and CCE2, since it doesn't support CCE3 and last version was updated like when? Six years ago? Does it even support multiple threads? Encoding today with it feels so outdated and slow...

Well anyway, I want to ask hardcore DVD fans (since DVD isn't that popular anymore since Blu-rays, but still a lot of titles comes out on DVD only) what is the best solution today to compress the DVDs to 4.37 DVDRs? is it still DVDRB with CCE2? Really outdated and hard to believe if it's best solution around.

So please share your thoughts what are the best current setups to get best quality encodes and use up CPU resources respectively?

[setarip_old]

Hi!

1) At this, the Doom9 Forum, referring to any program as "best" is not appreciated, as "best" is subjective.

2) Suffice it to say that "DVD Rebuilder" despite, or perhaps due to its lack of recent changes, still appears to be a very much favored DVD conversion/ compression program.

[rhaz]

I meant not the best program, but best settings and encoders, and I mentioned DVD Rebuilder because it's its subforum, I didn't name any other software. I was wondering maybe there were better settings and encoders than CCE2 for DVD Rebuilder? Since there's CCE3, but can't run.

[jdobbs]

I can't think of any other method that will give you comparable results in terms of quality. But, that doesn't necessarily imply "best". There are, for example, faster methods and perhaps methods that don't burden you with as many options. I think that's probably the only thing I would change if I had to do it again. Most of the settings never need to be changed, and some of them sound like gibberish to someone who is unfamiliar with MPEG terms. I just added too many settings in order to try and satisfy everyone. More hidden options and fewer menu/settings dialog options probably would have been better.

The main reason it is no longer developed is that I stopped getting consequential bug reports, and frankly ran out of meaningful new features to add. That, and the fact that I started spending most of my free time on BD Rebuilder.

I decided not to support CCE3 because I got tired of the authors completely revamping their settings layout with every new release (resulting in many hours of recoding on my part). It is also my belief that HCEncode has progressed to a point at which its quality is as good as CCE -- and its price (free) is better.

[rhaz]

Hey thanks for reply. Last version was released like over two years ago for CCE3, so just stick with that for example. Would be really nice. And does anyone know if there's difference between 5 passes or is it 10 passes (in picture quality terms)? And does it use up all threads in i3? Because when encoding I can do anything while at it, feels like it's not using up the resources. So, if there's no bugs, would be nice to improve it in other ways, not just bugs. Oh and like I said before, a lot of DVDs, especially the local ones I get, on smaller countries you know, local distributors don't do Blu-rays simply because the market is too small, or movie budget was too low and etc. So abandoning DVDRB just because of Blu-ray superiority is sad ;/

[jdobbs]

Hey thanks for reply. Last version was released like over two years ago for CCE3, so just stick with that for example. Would be really nice. And does anyone know if there's difference between 5 passes or is it 10 passes (in picture quality terms)? And does it use up all threads in i3? Because when encoding I can do anything while at it, feels like it's not using up the resources. So, if there's no bugs, would be nice to improve it in other ways, not just bugs. Oh and like I said before, a lot of DVDs, especially the local ones I get, on smaller countries you know, local distributors don't do Blu-rays simply because the market is too small, or movie budget was too low and etc. So abandoning DVDRB just because of Blu-ray superiority is sad ;/Honestly you get close to 99% of what you can expect at 2 passes. A third pass will get you to the best you will see. Anything beyond that is just placebo. Custom Technology (the people who develop CCE) used to tell you that you hit the maximum quality threshold at 3 passes in their manual -- but I think they decided the multiple pass thing was too good of a sales point and they took it out.

In theoretical terms you should have all the data you need to do an optimal encode after a single analytical pass... so two passes should be the maximum ever needed.

[thescrapyard]

I have tried a few encoders, but for quality over speed nothing touches DVD-RB as it basically takes the source DVD apart and rebuilds it to match the available bitrate, which is why its much slower than those that get their speed from trying (and usually failing) to remove the bitrates of the sources they 'think' you won't notice, its IS noticeable especially now on very large LED TVs that are 60" and upwards with screen quality much much clearer than 5 years ago where the majority were still using tubed TV's that maybe reached 27" if you had the money and space

DVD-RB is probably one of the very few encoders that FULLY supports AviSynth, so that factor on its own is a massive plus point for anybody processing very old DVDs and trying to clean them up and keeping the originals that are now probably deleted so very difficult to buy again if damaged

I still run DVD-RB but use it with AviSynth 2.6.0.4 and HCEnc 0.27 without any issues in multi-threaded support for AviSynth. Unless I'm running very slow filters can quite easily achieve 150+ FPS without much effort and without any filtering easily reach 300+ FPS so its not slow, the slow issues are usually down to the users hardware. HCEnc will happily take a smuch CPU as it can take almost to 100%, it your CPU isn't running at 100% its because HCEnc can't run any faster due to the massive increases in CPU and memory speeds from 5 years ago so just doesn't need to take all your CPU cycles

I haven't updated my CPU or memory in about 2 years now, but I am running an Intel i5 2500k running at 4.5ghz with 16GB of pretty fast memory so unless I upgrade to an i7 then I'm not really going to see much more of a speed increase, and its not worth the extra £200 it will cost me for maybe 20% speed increase, as the Intel i5 is running about its limits with an air cooler (but its a BIG very efficient air cooler so isn't overworked heat wise in an Antec 1200 case with plenty of cooling fans keeping ambient temps down)

HCEnc pretty much matches CCE2, and 2 passes is plenty unless your really anal and want to push it to 9 passes using CCE. Each pass after 2 passes is much much more time for very little gain as each pass just adjusts the bitrate tighter and tighter for some scenes. Very high action movies (like Star Wars) apparently did see the extra passes help. But they are a minority and the majority manage with 2 passes

If your using an i3 then your not getting the best from your system as well, have a quick read of this I just found that hopefully explains it

http://www.pugetsystems.com/labs/articles/Haswell-Core-i3-vs-i5-vs-i7-Which-is-right-for-you-475/

http://www.pcworld.idg.com.au/article/386100/what_difference_between_an_intel_core_i3_i5_i7_/

[dr_ml422]

Is the Pro Version still available for donation support? If so please let me know so I can get it. I've been playing around with some of the more modern apps, and actually haven't seen much to be really that impressed. I downloaded the free version and about 3 times it got stuck on that M2 V file. I read up and saw it might either be an AviSynth issue, or support for more movies with Angles etc... This was with CCE 2.76. I switched to HCEnc and had no problem. I noticed in the install it gives you where to point the different CCE versions. I chose the option with just CCE 2 and pointed it to the CCE 2.76 .exe. Anyway I'm very much interested in getting the Pro Version.
Let me know if this is the correct thread also. I'm new. Thanks.
Does CCE have to be opened up and tinkered with also?

[thescrapyard]

As far as I know the PRO version is still available. I recently reinstalled DVD-Pro and got my PRO keyfile from my email address. I registered literally years ago

Sometimes there can be a delay between registering and getting your keyfile, depends how busy he is, but a quick email usually gets it much quicker than waiting for him to update the DVD-RB Pro keys

I've tried a few similar software but always go back to DVD-RB Pro. Its not as fast as some, but thats for the reason of HCEnc and quality is better than speed. It also fixes some DVDs that simply won't play correctly, but DVD-RB Pro fixes any crappy authoring errors by companies rushing out cheap DVDs



If you are also interested in video to DVD, have a look at AVStoDVD. Similar idea but accepts pretty much any video file source and converts it to a true DVD, with menu if needed, and also uses AviSynth and HCEnc so teh quality is about a sbest a syou can get. The fact that it supports AviSynth is a BIG plus point. I also have VSO ComvertXtoDVD but don't use that much anymore as its so slow compared to AVStoDVD even if using AviSynth filters

https://sites.google.com/site/avstodvdmain/



You can also use the last version of HCEnc 0.28, just replace the one in the HCEnc folder with the one from HCENc 0.28, BUT you NEED to rename it from HCenc_028.exe to HCbatch.exe for it to work

http://hank315.nl/



You can also update the included AviSynth to the last release, I think its 2.60 as I use AviSynth+ instead for true multithreading and improved filters

https://www.videohelp.com/software/Avisynth

http://avisynth.nl/index.php/Main_Page



Just loaded up DVD-RB Pro and its now recognising AviSynth+ as installed, that used to be a royal pain to get to work, but I guess the AviSynth+ installer does a much better job than it did when it was first released

AviSynth+, in my opinion, is much faster and has a LOT of multi-threading support now built-in instead of a hack. Also, a LOT of older and new AviSynth filters have been updated with bugs finally fixed or improved and also now available in 64-bit versions

https://github.com/pinterf/AviSynthPlus/releases

https://forum.doom9.org/showthread.php?t=175170

https://forum.doom9.org/showthread.php?t=168856

[jdobbs]

If you want the Pro Version just send an Amazon gift card to dvd-rb@jdobbs.net. Mention DVD-RB Pro in the comment accompanying the donation. If you've ever donated before (to DVD-RB or BD-RB) you can just send an e-mail request to that address (mention your registered e-mail address) and download links will be forwarded to you. Once you are a VIP you stay that way for life.

[gonca]

If you want the Pro Version just send an Amazon gift card
Based on your location make sure it is Amazon.com, not uk, ca or whatever

[dr_ml422]

@jdobbs Thank you so much! Everything should be soon its way really soon. I have a quick question. Should CCE be set up to run as is on windows 10 or should I use the compatibility option for some other version of MS? Thanks.

I forgot to mention my e-mail address with the donation from Amazon. Do they send you a link or something or do they handle the rest of the transaction? Thanks.

@thescrapyard Yes the latest Avisynth is working, though I think its the 32 bit version. Will the 64 bit version work with DVD Rebuilder Basic or Pro? I wonder if it'll make a difference. Sometimes the 64 bit version of apps dealing with video don't really make that much of a splash. Might just give that HCenc 0.28 a shot if the latest DVD-RB Pro doesn't already include it.

[jdobbs]

@jdobbs Thank you so much! Everything should be soon its way really soon. I have a quick question. Should CCE be set up to run as is on windows 10 or should I use the compatibility option for some other version of MS? Thanks.

I forgot to mention my e-mail address with the donation from Amazon. Do they send you a link or something or do they handle the rest of the transaction? Thanks.

@thescrapyard Yes the latest Avisynth is working, though I think its the 32 bit version. Will the 64 bit version work with DVD Rebuilder Basic or Pro? I wonder if it'll make a difference. Sometimes the 64 bit version of apps dealing with video don't really make that much of a splash. Might just give that HCenc 0.28 a shot if the latest DVD-RB Pro doesn't already include it.If CCE was already installed on your system when you upgraded to Windows 10 there should be no issues (that's what I did). But honestly, I stopped using CCE and went with HCEncoder exclusively -- as I think it rose to a quality level that was equal to CCE.

I sent you a PM regarding your e-mail address.

In my tests I only saw negligible differences when I used the 64 bit version so I've stuck with the 32 bit.

[dr_ml422]

If CCE was already installed on your system when you upgraded to Windows 10 there should be no issues (that's what I did). But honestly, I stopped using CCE and went with HCEncoder exclusively -- as I think it rose to a quality level that was equal to CCE.

I sent you a PM regarding your e-mail address.

In my tests I only saw negligible differences when I used the 64 bit version so I've stuck with the 32 bit.

Thank you very much.

I installed CCE afterwards and the only issue that came up was when writing the M2V file which on another thread explained it was due to either Angles or interleaves on the source. Same source HCEncoder took care of except for 2 which probably was taken care of in the Pro Version. Should I use the DVD Rebuilder Pro as is or do that small hack to include the 0.28 version if not included already? Thanks.

64 bit computing is only advantageous with certain computer tasks. Even burning will not produce better results with a 64 bit burning app if there is one.

[jdobbs]

Thank you very much.

I installed CCE afterwards and the only issue that came up was when writing the M2V file which on another thread explained it was due to either Angles or interleaves on the source. Same source HCEncoder took care of except for 2 which probably was taken care of in the Pro Version. Should I use the DVD Rebuilder Pro as is or do that small hack to include the 0.28 version if not included already? Thanks.

64 bit computing is only advantageous with certain computer tasks. Even burning will not produce better results with a 64 bit burning app if there is one.I would just use the version that is included with DVD-RB. Most of the changes involved in later versions don't necessarily apply to the DVD-RB uses it.

[dr_ml422]

Everything is great! Unbelievable job when encoding to DVD-5 from default DVD-9 commercial DVDs. I just want to ask if you noticed a small bug when making changes to the current project and then commencing as usual? I had made several 100% no compression backups with no problems. I changed settings to HC Full backup of Movies and Menus etc... and loaded the file. I had create iso image and burn with imgburn checked, as well as delete all files after successful completion. What happened was some image way over @6GB plus and so no way to burn to DVD-5. Used common sense and closed DVD Rebuilder Pro, then opened and set same movie after another clean rip and this time burn directly from file with imgburn no iso. Results were immaculate albeit a small bit of extra material with the output size. So I'm thinking just maybe it still had the 100% no compression going on without closing? After closing and reopening was the refresh settings applied? Thanks.

[dr_ml422]

I just put in my first clean rip after reinstalling and a pop-up told me the settings I'm using are going to cause oversizing. Now I checked no director's comments and even set extras to slideshow. I really don't think it should be saying anything like this since a fixed DVD-5 setting is in place? Has to be small bug. Had no problems with DVD-RB Basic. Oh Menu Encoding was checked. I'll put the same flic in and just do a normal backup to see what happens.

[jdobbs]

It isn't a bug. You've implemented a non-standard setting that overrides sizing. If you don't want to have sizing issues... don't use a setting that causes it.

If you had posted the exact message you got -- I may have been able to tell you which setting is the issue... but "a pop-up" doesn't help much. But usually it is because you have used the segment editor and forced the condition.

[dr_ml422]

I'm using the Rockas interface and there's no start button anywhere? I see my movie, the audio, everything just no button to start the 1click mode? Weird.

It isn't a bug. You've implemented a non-standard setting that overrides sizing. If you don't want to have sizing issues... don't use a setting that causes it.

If you had posted the exact message you got -- I may have been able to tell you which setting is the issue... but "a pop-up" doesn't help much. But usually it is because you have used the segment editor and forced the condition.

Which setting as I don't even know how to set anything up other than default? Here's the log of that job. First I didn't run that job after I got that pop up. I set it to HC=Encoder, DVD-5 output and to basic Full backup with menus etc... If there's a default button then I'll hit that, though it's been kinda buggy.

[19:30:00] One Click encoding activated...
-----------------
[19:30:01] Phase I, PREPARATION started.
- DVD-RB v1.28.2
- AVISYNTH 2.6.0.6
- HC v0.23.0.0 encoder selected
- Source: GODS_OF_EGYPT
- VTS_01: 3,227,379 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 220,039 frames.
-- Building .AVS and .ECL files
- VTS_06: 111,892 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 9,212 frames.
-- Building .AVS and .ECL files
- VTS_07: 63,059 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 4,937 frames.
-- Building .AVS and .ECL files
- VTS_08: 395,963 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 32,552 frames.
-- Building .AVS and .ECL files
- VTS_14: 3,227,379 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 220,039 frames.
-- Building .AVS and .ECL files
- VTS_15: 3,227,379 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 220,039 frames.
-- Building .AVS and .ECL files
- VTS_16: 3,227,379 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 220,039 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: .1%
- Overall Bitrate : 500/400Kbs
- Space for Video : 12,046KB
- HIGH/LOW/TYPICAL Bitrates: 400/400/400 Kbs
[19:40:04] Phase I, PREPARATION completed in 10 minutes.
[19:40:04] Phase II ENCODING started
- Extracting Video for VTS_01 segment 0
- Extracting Video for VTS_01 segment 1
- Extracting Video for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Extracting Video for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Extracting Video for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Extracting Video for VTS_06 segment 3
- Creating M2V for VTS_07 segment 0
- Extracting Video for VTS_07 segment 1
- Creating M2V for VTS_07 segment 2
- Creating M2V for VTS_08 segment 0
- Creating M2V for VTS_08 segment 1
- Extracting Video for VTS_08 segment 2
- Extracting Video for VTS_14 segment 0
- Extracting Video for VTS_14 segment 1
- Extracting Video for VTS_14 segment 2
- Creating M2V for VTS_14 segment 3
- Creating M2V for VTS_14 segment 4
- Extracting Video for VTS_14 segment 5
- Creating M2V for VTS_14 segment 6
- Creating M2V for VTS_14 segment 7
- Creating M2V for VTS_14 segment 8
- Creating M2V for VTS_14 segment 9
- Creating M2V for VTS_14 segment 10
- Creating M2V for VTS_14 segment 11
- Creating M2V for VTS_14 segment 12
- Creating M2V for VTS_14 segment 13
- Creating M2V for VTS_14 segment 14
- Creating M2V for VTS_14 segment 15
- Creating M2V for VTS_14 segment 16
- Creating M2V for VTS_14 segment 17
- Creating M2V for VTS_14 segment 18
- Creating M2V for VTS_14 segment 19
- Creating M2V for VTS_14 segment 20
- Creating M2V for VTS_14 segment 21
- Creating M2V for VTS_14 segment 22
- Extracting Video for VTS_14 segment 23
- Creating M2V for VTS_14 segment 24
- Extracting Video for VTS_15 segment 0
- Extracting Video for VTS_15 segment 1
- Extracting Video for VTS_15 segment 2
- Creating M2V for VTS_15 segment 3
- Creating M2V for VTS_15 segment 4
- Extracting Video for VTS_15 segment 5
- Creating M2V for VTS_15 segment 6
- Creating M2V for VTS_15 segment 7
- Creating M2V for VTS_15 segment 8
- Creating M2V for VTS_15 segment 9
- Creating M2V for VTS_15 segment 10
- Creating M2V for VTS_15 segment 11
- Creating M2V for VTS_15 segment 12
- Creating M2V for VTS_15 segment 13
- Creating M2V for VTS_15 segment 14
- Creating M2V for VTS_15 segment 15
- Creating M2V for VTS_15 segment 16
- Creating M2V for VTS_15 segment 17
- Creating M2V for VTS_15 segment 18
- Creating M2V for VTS_15 segment 19
- Creating M2V for VTS_15 segment 20
- Creating M2V for VTS_15 segment 21
- Creating M2V for VTS_15 segment 22
- Extracting Video for VTS_15 segment 23
- Creating M2V for VTS_15 segment 24
- Extracting Video for VTS_16 segment 0
- Creating M2V for VTS_16 segment 1
- Creating M2V for VTS_16 segment 2
- Creating M2V for VTS_16 segment 3
- Creating M2V for VTS_16 segment 4
- Creating M2V for VTS_16 segment 5
- Creating M2V for VTS_16 segment 6
- Creating M2V for VTS_16 segment 7
- Creating M2V for VTS_16 segment 8
- Creating M2V for VTS_16 segment 9
- Creating M2V for VTS_16 segment 10
- Creating M2V for VTS_16 segment 11
- Creating M2V for VTS_16 segment 12
- Creating M2V for VTS_16 segment 13
- Creating M2V for VTS_16 segment 14
- Creating M2V for VTS_16 segment 15
- Creating M2V for VTS_16 segment 16
- Creating M2V for VTS_16 segment 17
- Extracting Video for VTS_16 segment 18
[23:13:48] Phase II ENCODING completed in 213 minutes.
[23:13:48] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 4 VOBID 2 CELLID 1
- Rebuilding seg 5 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 6 VOBID 3 CELLID 1
- Rebuilding seg 7 VOBID 3 CELLID 2
- Rebuilding seg 8 VOBID 3 CELLID 3
- Rebuilding seg 9 VOBID 3 CELLID 4
- Rebuilding seg 10 VOBID 3 CELLID 5
- Rebuilding seg 11 VOBID 3 CELLID 6
- Rebuilding seg 12 VOBID 3 CELLID 7
- Rebuilding seg 13 VOBID 3 CELLID 8
- Rebuilding seg 14 VOBID 3 CELLID 9
- Rebuilding seg 15 VOBID 3 CELLID 10
- Rebuilding seg 16 VOBID 3 CELLID 11
- Rebuilding seg 17 VOBID 3 CELLID 12
- Rebuilding seg 18 VOBID 3 CELLID 13
- Rebuilding seg 19 VOBID 3 CELLID 14
- Rebuilding seg 20 VOBID 3 CELLID 15
- Rebuilding seg 21 VOBID 3 CELLID 16
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 22 VOBID 4 CELLID 1
- Rebuilding seg 23 VOBID 4 CELLID 2
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_06
- 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
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Updating TMAP table...
- Processing VTS_07
- 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
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- 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
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
- Processing VTS_14
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 4 VOBID 2 CELLID 1
- Rebuilding seg 5 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 6 VOBID 3 CELLID 1
- Rebuilding seg 7 VOBID 3 CELLID 2
- Rebuilding seg 8 VOBID 3 CELLID 3
- Rebuilding seg 9 VOBID 3 CELLID 4
- Rebuilding seg 10 VOBID 3 CELLID 5
- Rebuilding seg 11 VOBID 3 CELLID 6
- Rebuilding seg 12 VOBID 3 CELLID 7
- Rebuilding seg 13 VOBID 3 CELLID 8
- Rebuilding seg 14 VOBID 3 CELLID 9
- Rebuilding seg 15 VOBID 3 CELLID 10
- Rebuilding seg 16 VOBID 3 CELLID 11
- Rebuilding seg 17 VOBID 3 CELLID 12
- Rebuilding seg 18 VOBID 3 CELLID 13
- Rebuilding seg 19 VOBID 3 CELLID 14
- Rebuilding seg 20 VOBID 3 CELLID 15
- Rebuilding seg 21 VOBID 3 CELLID 16
- Rebuilding seg 22 VOBID 3 CELLID 17
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 23 VOBID 4 CELLID 1
- Rebuilding seg 24 VOBID 4 CELLID 2
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_14_0.IFO
- Updating TMAP table...
- Processing VTS_15
- 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
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 4 VOBID 2 CELLID 1
- Rebuilding seg 5 VOBID 2 CELLID 2
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 6 VOBID 3 CELLID 1
- Rebuilding seg 7 VOBID 3 CELLID 2
- Rebuilding seg 8 VOBID 3 CELLID 3
- Rebuilding seg 9 VOBID 3 CELLID 4
- Rebuilding seg 10 VOBID 3 CELLID 5
- Rebuilding seg 11 VOBID 3 CELLID 6
- Rebuilding seg 12 VOBID 3 CELLID 7
- Rebuilding seg 13 VOBID 3 CELLID 8
- Rebuilding seg 14 VOBID 3 CELLID 9
- Rebuilding seg 15 VOBID 3 CELLID 10
- Rebuilding seg 16 VOBID 3 CELLID 11
- Rebuilding seg 17 VOBID 3 CELLID 12
- Rebuilding seg 18 VOBID 3 CELLID 13
- Rebuilding seg 19 VOBID 3 CELLID 14
- Rebuilding seg 20 VOBID 3 CELLID 15
- Rebuilding seg 21 VOBID 3 CELLID 16
- Rebuilding seg 22 VOBID 3 CELLID 17
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 23 VOBID 4 CELLID 1
- Rebuilding seg 24 VOBID 4 CELLID 2
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_15_0.IFO
- Updating TMAP table...
- Processing VTS_16
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 3 CELLID 1
- Rebuilding seg 2 VOBID 3 CELLID 2
- Rebuilding seg 3 VOBID 3 CELLID 3
- Rebuilding seg 4 VOBID 3 CELLID 4
- Rebuilding seg 5 VOBID 3 CELLID 5
- Rebuilding seg 6 VOBID 3 CELLID 6
- Rebuilding seg 7 VOBID 3 CELLID 7
- Rebuilding seg 8 VOBID 3 CELLID 8
- Rebuilding seg 9 VOBID 3 CELLID 9
- Rebuilding seg 10 VOBID 3 CELLID 10
- Rebuilding seg 11 VOBID 3 CELLID 11
- Rebuilding seg 12 VOBID 3 CELLID 12
- Rebuilding seg 13 VOBID 3 CELLID 13
- Rebuilding seg 14 VOBID 3 CELLID 14
- Rebuilding seg 15 VOBID 3 CELLID 15
- Rebuilding seg 16 VOBID 3 CELLID 16
- Rebuilding seg 17 VOBID 3 CELLID 17
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 18 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_16_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[23:34:37] Phase III, REBUILD completed in 21 minutes.

Done.
[23:34:37] PREPARE/ENCODE/REBUILD completed in 244 min.
If you need anymore info let me know. Thanks.

[dr_ml422]

For w/e reason DVD-RB when using the .iso to imgBurn option doesn't complete it and if you have delete files after completion of .iso and delete after burning you just lose all that time. Here's the log or at least this is what I know is the log.

[19:40:12] One Click encoding activated...
-----------------
[19:40:13] Phase I, PREPARATION started.
- DVD-RB v1.28.2
- AVISYNTH 2.6.0.6
- HC v0.23.0.0 encoder selected
- Source: EL_CAPO_1
- VTS_01: 378,525 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,911 frames.
-- Building .AVS and .ECL files
- VTS_02: 376,410 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,491 frames.
-- Building .AVS and .ECL files
- VTS_03: 341,403 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 73,016 frames.
-- Building .AVS and .ECL files
- VTS_04: 348,443 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 72,521 frames.
-- Building .AVS and .ECL files
- VTS_05: 377,507 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 76,496 frames.
-- Building .AVS and .ECL files
- VTS_06: 388,463 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,881 frames.
-- Building .AVS and .ECL files
- VTS_07: 369,558 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 74,876 frames.
-- Building .AVS and .ECL files
- VTS_08: 370,439 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 75,118 frames.
-- Building .AVS and .ECL files
- VTS_09: 375,394 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 78,176 frames.
-- Building .AVS and .ECL files
- VTS_13: 367,185 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 76,376 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 53.6%
- Overall Bitrate : 1,121/897Kbs
- Space for Video : 3,482,424KB
- HIGH/LOW/TYPICAL Bitrates: 2,025/471/897 Kbs
[19:44:38] Phase I, PREPARATION completed in 4 minutes.
[19:44:38] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Extracting Video for VTS_01 segment 7
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Creating M2V for VTS_02 segment 3
- Creating M2V for VTS_02 segment 4
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Extracting Video for VTS_02 segment 7
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Creating M2V for VTS_03 segment 3
- Creating M2V for VTS_03 segment 4
- Creating M2V for VTS_03 segment 5
- Creating M2V for VTS_03 segment 6
- Extracting Video for VTS_03 segment 7
- 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
- Extracting Video for VTS_04 segment 7
- 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
- Creating M2V for VTS_05 segment 4
- Creating M2V for VTS_05 segment 5
- Creating M2V for VTS_05 segment 6
- Extracting Video for VTS_05 segment 7
- Creating M2V for VTS_06 segment 0
- Creating M2V for VTS_06 segment 1
- Creating M2V for VTS_06 segment 2
- Creating M2V for VTS_06 segment 3
- Creating M2V for VTS_06 segment 4
- Creating M2V for VTS_06 segment 5
- Creating M2V for VTS_06 segment 6
- Extracting Video for VTS_06 segment 7
- Creating M2V for VTS_07 segment 0
- Creating M2V for VTS_07 segment 1
- Creating M2V for VTS_07 segment 2
- Creating M2V for VTS_07 segment 3
- Creating M2V for VTS_07 segment 4
- Creating M2V for VTS_07 segment 5
- Creating M2V for VTS_07 segment 6
- Extracting Video for VTS_07 segment 7
- Creating M2V for VTS_08 segment 0
- Creating M2V for VTS_08 segment 1
- Creating M2V for VTS_08 segment 2
- Creating M2V for VTS_08 segment 3
- Creating M2V for VTS_08 segment 4
- Creating M2V for VTS_08 segment 5
- Creating M2V for VTS_08 segment 6
- Creating M2V for VTS_08 segment 7
- Creating M2V for VTS_09 segment 0
- Creating M2V for VTS_09 segment 1
- Creating M2V for VTS_09 segment 2
- Creating M2V for VTS_09 segment 3
- Creating M2V for VTS_09 segment 4
- Creating M2V for VTS_09 segment 5
- Creating M2V for VTS_09 segment 6
- Extracting Video for VTS_09 segment 7
- Creating M2V for VTS_13 segment 0
- Creating M2V for VTS_13 segment 1
- Creating M2V for VTS_13 segment 2
- Creating M2V for VTS_13 segment 3
- Creating M2V for VTS_13 segment 4
- Creating M2V for VTS_13 segment 5
- Creating M2V for VTS_13 segment 6
- Extracting Video for VTS_13 segment 7
[21:53:56] Phase II ENCODING completed in 129 minutes.
[21:53:56] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Processing VTS_03
- 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
- Updating NAVPACKS for VOBID_01
- 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
- Updating NAVPACKS for VOBID_01
- 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
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_05_0.IFO
- Updating TMAP table...
- Processing VTS_06
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_06_0.IFO
- Updating TMAP table...
- Processing VTS_07
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_07_0.IFO
- Updating TMAP table...
- Processing VTS_08
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_08_0.IFO
- Updating TMAP table...
- Processing VTS_09
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_09_0.IFO
- Updating TMAP table...
- Processing VTS_13
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_13_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- Removing DVD files
- ISO Image successfully created.
- Writing ISO image to DVD...
- Error on Write-To-Disc. Check drive/disc.
- ISO Image WAS NOT successfully written.
- ISO Image was not deleted.
[22:22:21] Phase III, REBUILD completed in 29 minutes.

Done.
[22:22:21] PREPARE/ENCODE/REBUILD completed in 162 min.
Every single time I've used the iso setting this happens. Seems that imgburn automatically thinks it's dual layer and opens up the disc-break window? Now there shouldn't be any need for this if the DVD-5 is 4.38GB. Now the only times it has worked is straight to file burning with imgBurn.

I caught that other mistake which I must have checked off the New Style Editor option thinking it was default. Can you maybe at least implement a default button so in case anything goes wrong one can restore to default? Thanks. Only thing I found was a Restore to Default with the Menus.

[dr_ml422]

I was lucky and used the 3 phrase option to finish rebuilding that oversized .iso. The file was still there and so something told me to hit the rebuild button. Since it wasn't converted to a .iso it came out very nice just a tad larger. The issue is even when it targets on point using the ImgBurn option to burn as iso adds a tad more as is normal. The copies are great! Quality is way better than any compression/transcoding app out there. I might lower the default a tad to compensate for any oversizing whether .iso related or not.

How's the DVD-BD Pro coming along? There is a nice quality upgrade with Blu-ray imho. Excuse the separate post, the mobile version doesn't let me save the edit.

[jdobbs]

I have no plans to have a BD-RB Pro version. I only accept voluntary donations.

[dr_ml422]

My bad, I thought there was one because of the DVD-RB Pro. I'm noticing the slight increase in output with episodic DVDs. Might just be too much to get quality when source is almost 8GB. I'll revert back to Default and put a regular DVD in see what happens. Thanks. I'll check out the BD-Rebuilder soon enough.

[manolito]

It's nice to see that I am not the only person left who still creates DVDs... :p

You might be interested in having another high quality choice for the encoder in DVD-RB. Take a look here:
https://forum.doom9.org/showthread.php?p=1698765#post1698765


Cheers
manolito

[dr_ml422]

[QUOTE=manolito;1869122]It's nice to see that I am not the only person left who still creates DVDs... :p

You might be interested in having another high quality choice for the encoder in DVD-RB. Take a look here:
https://forum.doom9.org/showthread.php?p=1698765#post1698765

Thanks manolito. It's really great to have alternatives as something always pops up. Is this good to go w/the Pro Version of DVD-RB?

I'm also going to give that Avs2dvd a go. What do you think about it? Only ones I'm using now is ConvertXtoVideo and VidCoder. Seems VSO doesn't want to pay the h.264 fee because that's what's down along with the Hardware Optimization not working.

They use ffmpeg for their software. In ConvertXToDVD they also optimize the output as it's almost always @2.7gb more or less. There's a way to make video look just like the original and at way smaller sizes than the norm we see. I just don't know why they don't use it or exactly what it is.

I unchecked the CC option on DVD-RB Pro and the oversizing stopped. Have you run many jobs using the CC option to see about that? Thanks.

Other than that I really have to admit that DVD-RB Pro using HCEnc is unbelievable. Close to 8gb regular and episodic DVDs look like the original.


Cheers

The mobile version isn't working that great. It won't let me reply with quotes from my phone.

[manolito]

It's really great to have alternatives as something always pops up. Is this good to go w/the Pro Version of DVD-RB?

Yes, it works nicely with the Pro version of DVD-RB. Just remember that you need to turn off the "Multiple Encoder Processes" option. And for the FFmpeg version I really recommend the version from the "ffmpeg_IMPORTANT.txt" file.

Basically this "use_ffmpeg" plugin was a byproduct of my FF_VBR plugins for AVStoDVD and DVDStyler. In DVD-RB it should replace the QuEnc encoder which is really too old and deprecated.


I am very familiar with AVStoDVD, I have been involved in its development for some years. You cannot really compare it to DVD-RB, though. DVD-RB can only take a DVD structure as the input, but then it keeps the original menu intact. And the output quality is the best you can get, no comparison to the transcoders like DVDShrink.

AVStoDVD will not preserve the original menues if your source is a DVD. If you need menues you will have to create your own. But it takes (almost) any videos as the source and converts them to a DVD compatible format, and it uses highest quality encoders for this.

Another software for DVD creation you might like is DVDStyler. Basically it does the same things as AVStoDVD, but its scope is more on creating menues instead of transcoding quality. It only uses FFmpeg for transcoding, this really compromised quality until a few years ago. Not any more, the author integrated my FFmpeg_VBR plugin seamlessly into his software, and now you can get very high quality encodes with DVDStyler. If you care about elaborate menues you should definitely give it a try.


Cheers
manolito

[dr_ml422]

manolito how would you compare the quality of AVStoDVD and ConvertXToDVD? Would you say it's comparable, maybe better? Thanks.

[manolito]

Quality is in the eye of the beholder... :rolleyes:

ConvertXtoDVD is based on FFmpeg, it can use single pass and 2-pass VBR methods. Single-pass is based on a modified "Constant Quantizer" method, and for higher bitrates the quality is good. But for medium or lower bitrates the 2-pass method creates a much better bitrate distribution between the complex and the simpler parts of the source.

AVStoDVD uses FFmpeg only for very high bitrates by default, in most cases HCenc will be used (always in 2-pass VBR mode for a multicore CPU). Most people will agree that HCenc produces a better quality than FFmpeg, but this really depends on many factors. There is no doubt that FFmpeg can create very high quality results when the appropriate parameters are used.

The reason I started my FFmpeg_VBR plugin project was that forum member Fishman0919 requested this for AVStoDVD. He was adamant that at least for lower bitrates below 3500 kbps FFmpeg produced a better quality output than HCenc. I have no idea if this is always true, but when you use the VBR plugin then FFmeg is no longer restricted to the default "Constant Bitrate" mode, so it can also be used for medium and low bitrates. Users have to decide for themselves which quality they like better. And in AVStoDVD this means that users have a choice between two high quality encoders while ConvertXtoDVD users are tied to FFmpeg.


Cheers
manolito

[dr_ml422]

well I just did a conversion of the first x-men movie from 1080p to DVD and I used HCenc in one pass VBR and the output was remarkable! For some reason it complained about a quantizer setting, though it still went all the way. I guess if you leave it at smart detection that's where ffmpeg will jump in at the higher bitrate? Or will HCenc always do a 2 pass even if one pass VBR was chosen? So in DVD-RB and AVStoDVD we have a choice of one or two VBR with ffmpeg correct? Thanks.

[manolito]

Looks like you mixed up things a little bit... :eek:

If you just started with AVStoDVD, please leave the settings at their default values for now. For the encoder selection "Smart Selection" is the default, and the actual selection is based on the video bitrate.

By using "Smart Selection" option, AVStoDVD will automatically select one of the other 3 encoding profiles, with the following rationale:
IF the CPU is multi-core:
· "FFmpeg CBR 1-pass" is selected when calculated video bitrate is > 6000 kbps
· "HCenc VBR 2-pass" is selected when calculated video bitrate is < 6000 kbps
IF the CPU is single-core:
· "FFmpeg CBR 1-pass" is selected when calculated video bitrate is > 6500 kbps
· "HCenc VBR 1-pass" is selected when calculated video bitrate is < 6500 kbps and > 4500 kbps
· "HCenc VBR 2-pass" is selected when calculated video bitrate is < 4500 kbps

Of course you can override all these bitrate thresholds (read the help file), but you should know what you are doing. Turning off "Smart Selection" will always override the automatic settings for encoder selection. So if you specify HCenc 1-pass VBR then this will be used no matter what.

So in DVD-RB and AVStoDVD we have a choice of one or two VBR with ffmpeg correct? Thanks.

No. In DVD-RB after installing the "use_ffmpeg" plugin this is correct, but not for AVStoDVD. AVStoDVD can only use FFmpeg in CBR mode (without B-frames which makes it very inefficient). If you want to use FFmpeg VBR modes in AVStoDVD you first need to download and install my FFmpeg_VBR plugin. This is not meant for novices, I suggest that you first familiarize yourself with AVStoDVD without any additional plugins.

[dr_ml422]

By using FFmpeg when the bitrate is > 6000kbps are you suggesting FFmpeg is better than HCenc? Or it's just a better encoder at those higher bitrates, or it's just preference for AVStoDVD? I can't notice anything wrong w/HCenc VBR 1-pass. Looks magnificent. On my 3rd encode already. If it makes it inefficient by using FFmpeg in CBR mode then why is it programmed that way? I just read the Read Me file before and I still haven't seen how to get the Progress Status Window going. All I see is a lot of figures and numbers in a window interface. From what I gather around most don't think too highly of FFmpeg. Reason I went straight to HCenc VBR 1 Pass was because of the outstanding results with DVD-RB Pro. It's working w/no errors whatsoever. My source files have been all 1080p. I'll go to see now where that Progress Window Button is. Why the different names for Titleset and DVD Label btw? Usually same for both. Anyway I'm so glad I found this here because things don't look too well over in VSO land as there still isn't no new update with their version of AVStoDVD, specifically the ConvertXToVideo which also puts out to NTSC DVD.

Have you ever figured out or were curious how some optimize their output file so that a completely merged source file will still be basically the same file size though actually play double etc... the length after merging? I couldn't believe it when I used WinXDVD's VideoProc by Digiarty and saw it happen. Only thing w/them they just weren't consistent and support was virtually non-existent. Really blew my mind! I'll post back if I can't get this Preview Window started. Thanks.

For the life of me I can't find the Progress Status Window, unless the User GUI instructions are old . I found everyting else like Jobs Options, Preview Title Window etc... , I just in no way, form or fashion have a colorful window with progress bars etc... Will someone kindly point me to it, or is this window I see with all these stats the one? Sure isn't colorful etc... as in the Note file.

Ok so the Progress Window doesn't open during the encoding. It just reports afterwards. Well you live and you learn. Lol... I used the default on the 4th X-Men 1080p file and a second pass really didn't add anything to what 1 pass did previously. Seems HCenc is just fine with one pass. I do have to report and I think it was noted previously, that it was pretty quick even during 2 pass. I was reaching upwards 70+ fps with AVStoDVD. I saw some older posts and just for the record the latest version is using HCenc 0.28 which I think is the latest. Great app. I will continue to learn. I'm still confused as to why FFmpeg is default at higher Bitrates, though supposedly outstanding at middle to lower Bitrates. It has to be the difference between VBR and CBR. VBR w/the plugin and CBR as is straight out the gate.

[manolito]

By using FFmpeg when the bitrate is > 6000kbps are you suggesting FFmpeg is better than HCenc? Or it's just a better encoder at those higher bitrates, or it's just preference for AVStoDVD?

No, I said just the opposite thing. FFmpeg (especially in the way it is used by AVStoDVD) is certainly inferior to HCenc. The reason it is used by default for very high bitrates is that it is faster than HCenc, and at such high bitrates you won't be able to see any quality flaws. You can get out better quality from FFMmpeg if you use different parameters and switch to 2-pass VBR, but this requires using the FFmpeg_VBR plugin.

If you are happy with HCenc (as most users are), by all means use it. In HCenc the 1-pass quality can be almost as good as the 2-pass quality. But every once in a while you might come across a source file where 1-pass is unable to reach the specified output file size. And the main reason why 1-pass is no longer used by default if your CPU has more than one core is that HCenc makes very good use of all the CPU cores so 2-pass can be almost as fast as 1-pass.

FFmpeg is a console application without a GUI, and the console window is all you get. The FFmpeg devs decided to not integrate a progress bar into the console window, probably because it would slow down encoding. There are some third party wrapper scripts for FFmpeg which implement a progress bar, but they are based on Python or other languages. Not so easy for most users. For me (coming from the good old DOS times) the FFmpeg console window looks just fine, it provides a lot of information.

A DVD can have several title sets, so it makes sense to have a different title name for each title set, but only 1 DVD label for the whole disk. And these strings can be edited by the user.

[dr_ml422]

Thank you manolito. Now I understand. Also I know I posted it on the AVStoDVD thread, though I found the culprit with that file and others similar. It seems AVStoDVD won't distinguish Dual audio files straight off the back anyway. I think if all you have is English as primary, and there's another audio file, it will not know this and error out. That Wolverine mp4 file has Dual audio. One English and one Hindu. So since English is primary and there's a dual audio it will get trumped up and error out. Isn't there a way to just make it acknowledge all the audio tracks and then one can choose? This has to be the culprit because I put in another MP4 file and it took it like a baby.

I had to use ConvertXToDVD as it automatically separates whatever audio and after your selection knows what to do. I thought it was the .srt file, though I took it out and still had that error message. If I put another language in the preferences, if allowed, then it will acknowledge it and proceed as usual. Only thing I can think of as it was playable and readable everywhere else.

[manolito]

I think if all you have is English as primary, and there's another audio file, it will not know this and error out. That Wolverine mp4 file has Dual audio. One English and one Hindu. So since English is primary and there's a dual audio it will get trumped up and error out. Isn't there a way to just make it acknowledge all the audio tracks and then one can choose? This has to be the culprit because I put in another MP4 file and it took it like a baby.

Of course AVStoDVD supports multiple audio tracks (up to 3). When you load a source file with more than 1 audio track, you will see the following audio selection window:

https://i.postimg.cc/q75gRtJD/audioselect.png (https://postimages.org/)

In this window you can tick or untick the audio tracks you want, then you close the window by pressing the "x" in the upper right corner (there is no explicit "OK" button).

If I remember correctly your peferred audio language was English for both the primary and secondary audio. Therefore another window will pop up asking you if you want to alter the secondary audio language to Hindu or not.

IMO all this is easy and straightforward...


You should post AVStoDVD related questions in the AVStoDVD thread, this thread is about DVD-Rebuilder after all...

[dr_ml422]

My bad. I then have posted over there.

[dr_ml422]

Any alternative to ImgBurn for making the .iso? It's a pain in the ykw when you get that "It's the end of the world" message for not finding a layer break. I know you can uncheck this in ImgBurn options, though why replace the other app ? Unless you're output is a DVD-5 and best be under size ImgBurn not best option for .iso and Dual Layer. Just a concern. Thanks.

[manolito]

If your output fits on a DVD-5 then ImgBurn should never give you this "End of the world" message, simply because no layer break is necessary.

To make an ISO image from a folder containing a DVD structure the only alternative I am aware of is mkisofs. It is a command line tool with lots of options. There is a GUI for it, get it at VideoHelp:
https://www.videohelp.com/software/Folder2Iso

Good luck
manolito

[dr_ml422]

Thanks Manolito.

It's when the output is to DVD-9 that it either comes up with that "End of the world" pop up or as I mentioned you have to be present to aid in the Layer break. Unless I check it off in options in ImgBurn, which I can do. I know most will use DVD-RB for DVD-5 output so not many will encounter this. I'm going to look into that guide for mkisofs. I think I used it once and it was very good. Matter of fact I first discovered it via DVD-RB.

Great tool! They used mkisofs and came up with Folder2Iso. In a snap you have your .iso and no Layer Break to worry about. I'm also in correspondence with LG, ASUS, etc... regarding automatic DVD-ROM bitsetting with their drives. LG at least now has there more recent drives automatically bitsetting without an option for the user. I'm waiting for a Swap from them with New Firmware regarding this matter.

[jososo]

DVD Rebuilder still the best in 2019...
and CCE still the best too:
CCE (https://zupimages.net/viewer.php?id=19/49/7mx4.jpg)
HCenc (https://zupimages.net/viewer.php?id=19/49/v1ej.jpg) you can see macroblocks
ConvertXtoDVD (https://zupimages.net/viewer.php?id=19/49/gr4u.jpg) bof
DVD2one (https://zupimages.net/viewer.php?id=19/49/xdgr.jpg) so smooth very surprise by the backup quality
CloneDVD (https://zupimages.net/viewer.php?id=19/49/k7o5.jpg) so bad
MagicDVDCopier (https://zupimages.net/viewer.php?id=19/49/6pj2.jpg) horrible

Video frame from Gladiator dvd backup
DVD9 to DVD5 movie only with all tracks and subtitles
2600 kbps approx
All latest encoders version except CCE : Cinema Craft Encoder Basic Ver. 2.70.01
All genuine paid license software

[dr_ml422]

For some reason DVD Rebuilder Pro went over to 4.4GB instead of the default DVD-5. Is this a quality control mechanism ensuring a nice viewable output, or just a possible defect in the source rip? Mind you the disc was unplayable in the DVD Player, though opened up in one of my PC players. Thanks.

Twice now with same DVD.

[manolito]

Overshooting the desired target size happens frequently, it is more likely to happen with 1-pass encodes than with 2-pass encodes. A specific encoder may be more prone to it than a different encoder. And it has a lot to do with the source characteristics.

DVD-RB has some hidden settings in "Rebuilder.ini" where the number of target sectors can be changed. You can find this in the Rebuilder help file under "Hidden Settings".
All optional settings MUST be placed in the '[Options]' section of the .ini file, otherwise they will be ignored. Any settings changed here will not be activated until the next time you run DVD-RB.

Target Output Size

TargetSectors= nnnn
CCETargetSectors=nnnn
ReJigTargetSectors=nnnn
QuEncTargetSectors=nnnn
HCTargetSectors=nnnn
ProcodertSectors=nnnn


Use Sectors, 1 sector = 2Kb.
Example: CCETargetSectors=2236400

As a reference the default for DVD-RB is 2236400 sectors and the maximum for a DVD-5 is around 2267500. You should always leave a some room for error.

TargetSectors will be the default for all methods. Other, mode specific, target sector settings will override it when using that mode.


Cheers
manolito

[dr_ml422]

I'm not going to make too much of an issue with this, though a couple of bytes here and there and you're looking at DVD DL instead of DVD-5. I went in there and didn't see the default value. Is it hidden? Also does HCenc permit 2 pass encodes because I couldn't find any setting for 2 pass encoding. Thanks.

[manolito]

AFAIK HCenc uses 2-pass by default unless you explicitly specify 1-pass. Of course you will not see any TargetSectors entry in the INI file, the default value is used unless the user enters the desired TargetSector value.

If you result is only slightly oversized (less than 10%) then I would recommend to use DVDShrink or DVD2one to reduce the size. The quality loss will be minimal for such low reduction values.

[dr_ml422]

Thanks manolito. Everything is working fine! I'm going to search for the Closed Captioning use with DVD-RB Pro. I know I either posted a question about it or saw how to use it.

Ok so I couldn't find how to use the closed captioning option. Can you point me to where it's at? I checked the Help Files etc... and couldn't find anything. Thanks.

[manolito]

I found this in the DVD-RB version history from April 30th, 2006 (v1.09.3) - only applies to the Pro version:
As closed captioning support appears to be stable, it has been removed from "beta" status and can now be enabled/disabled from the "Settings" menu.

[Emulgator]

And it says "Keep Closed Captions" only , so I guess that one can not mux CC in ?
Haven't used it for some time, got to fire it up again at a point when I have a CC project.
Well, DLP can mux CC in.

[dr_ml422]

I found this in the DVD-RB version history from April 30th, 2006 (v1.09.3) - only applies to the Pro version:

Hi manolito, I couldn't get any precise guide/suggestion as how to actually use the Closed Caption option. At least I couldn't find any. Do we just have to enable it and that's that? Thanks.

[manolito]

I do not use the Pro version, so I cannot test it. But if I understand Emulgator correctly then this option only has an effect if the source already has Closed Captions. Then if you enable the option these Closed Captions will be kept, if the option is disabled then they will be removed.