speeding up dvd rb with DualDVDRB

[UncasMS]

DualDVDRB seems a tempting tool for those of you using either:

- a dualcore cpu
- a Pentium 4 HT

with either HC Enc or QuEnc as your encoder

experimental support for procoder (lovely!) has been added but i havent had any luck getting it started yet


DualDVDRB seems to support rebuilder FREE as well as PRO version

so all of you who own a dualcore or p4 ht should give it a try
...and let's hear some opinions/results please!

[UncasMS]

latest bugfixed release available now

runs fine

http://forum.doom9.org/showthread.php?p=777203#post777203

[Rumbah]

For Procoder support you need a new version of EclPro that you can grab here.

[UncasMS]

hello & welcome rumbah and thanx a ton for your nifty tool!

in addition to the brandnew eclpro version from robot1 one might need to mention that your dualdvdrb needs two different directories/instances of this new eclpro version poiting to only ONE installed version of procoder2

[davewill]

I'm running an AMD Athlon 64, am I out of luck?

[anonymez]

thanks uncas, i'll give it a shot, should i post results here?

[UncasMS]

I'm running an AMD Athlon 64, am I out of luck?

actually yes and no, davewill

the A64 is a marvellous cpu so you shouldnt be that much out of luck but this tool wont speed up the already fast A64 anymore

you might benefit from dualdvdrb when using machines with dualcore/two cpu/p4 ht and one of those cores is bored stiff

dualdvdrb helps using ~100% of the systems available power

i ran dualdvdrb last nite on my A64 single core with procoder and there was no difference in time at all converting my favourite testmovie van helsing

it took excactly the same time on my single core

should i post results here?

yes please!

[UncasMS]

here's how to use dualdvdrb with rb + procoder2 (no other version of procoder supported!)

1. download the necessary files:
dualdvdrb + new version of eclpro

2. copy the dualdvdrb files to any directory you want

3. copy eclpro TWO times to your harddrive into two different directories!

4. point both eclpro.exe to your procoder2.exe

5. in rebuilder make sure to point to dualdvdrb.exe instead of eclpro.exe

[davewill]

Thanks for the info UncasMS. I appreciate the help!

[l8nights]

This app is great for use w/ hc or quenc my result's on a p4 w/ ht are in the 15%-20% decreased encode times range w/ the newest version and the eclpro beta!

much thnx to rumbah for this add-on!

w/ procoder2 you will need a true dual core processor which the reported results are similar to that of hc and quenc around 30%-45% decrease in encode times!

[UncasMS]

thanx for posting some results, l8nights!

[pitchblack]

Hello all,

I have testet dualdvdrb with rb + procoder2 and without dualdvdrb, with one Titel, one the same machine and the same conditions (like nothing else than the prozess is running).

At first here are the parts of hardware, what may be of interest to analyse the results:

P4 3,2 GHz HT, 2 GB RAM (4 x 512 MB in Dual Channel), HDD based on different S-ATA drives.


First I gave dualdvdrb its chance, 2 ProCoder2 processes took about 220 minutes for his job.

-------------------------------------------------------------------------
[16:18:39] One Click encoding activated...
-----------------
[16:18:40] Phase I, PREPARATION started.
- VTS_01: 3.124.329 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 174.636 frames.
-- Building .AVS and .ECL files
- VTS_02: 29.897 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2.626 frames.
-- Building .AVS and .ECL files
- VTS_03: 371.084 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 30.909 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 71,0%
- Overall Bitrate : 3.235Kbs
- Space for Video : 3.287.894KB
- HIGH/LOW/TYPICAL Bitrates: 4.026/2.397/3.235 Kbs
[16:22:21] Phase I, PREPARATION completed in 4 minutes.
[16:22:21] 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
- 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
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_03 segment 0
[20:02:29] Phase II ENCODING completed in 220 minutes.
[20:02:29] 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
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
- Rebuilding seg 31 VOBID 1 CELLID 32
- Rebuilding seg 32 VOBID 1 CELLID 33
- 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
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[20:13:55] Phase III, REBUILD completed in 11 minutes.

Done.
[20:13:55] PREPARE/ENCODE/REBUILD completed in 235 min.
----------------------------------------------------------------------

After this I changed back to the normal way, the procoder was in use wirh rebuilder before. It took 270 minutes.

----------------------------------------------------------------------
[20:19:19] One Click encoding activated...
-----------------
[20:19:20] Phase I, PREPARATION started.
- VTS_01: 3.124.329 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 174.636 frames.
-- Building .AVS and .ECL files
- VTS_02: 29.897 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 2.626 frames.
-- Building .AVS and .ECL files
- VTS_03: 371.084 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 30.909 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 71,0%
- Overall Bitrate : 3.235Kbs
- Space for Video : 3.287.894KB
- HIGH/LOW/TYPICAL Bitrates: 4.026/2.397/3.235 Kbs
[20:22:59] Phase I, PREPARATION completed in 3 minutes.
[20:22:59] 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
- 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
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_03 segment 0
[00:52:10] Phase II ENCODING completed in 270 minutes.
[00:52:10] 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
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Rebuilding seg 30 VOBID 1 CELLID 31
- Rebuilding seg 31 VOBID 1 CELLID 32
- Rebuilding seg 32 VOBID 1 CELLID 33
- 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
- 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
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_03_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[01:02:34] Phase III, REBUILD completed in 10 minutes.

Done.
[01:02:34] PREPARE/ENCODE/REBUILD completed in 283 min.
------------------------------------------------------------------------

So at all 50 minutes less, when dualdvdrb is used.

But:

Dualdvdrb (2 processes) used 100% of the CPU, the normal (1 process) way had only small and very shorttimed 99%, so that I would say, that the small differences cannot make a difference of at all 50 minutes.

As I controlled my resources I found out that the dualdvdrb process used more capacity of my 2 GB RAM, at least in the middle one third more.

That is in my oppinion the main reason, why dualdvdrb is faster.

A short look in the past of all or any windows versions says: More RAM, more fun.

So much for now.

CU

[l8nights]

As I controlled my resources I found out that the dualdvdrb process used more capacity of my 2 GB RAM, at least in the middle one third more.

what speed ram are you using??
this is interesting as many have stated it not working I'm only using 512 but am a week or so out of an upgrade, so I'll have to run a couple more test's then!
I wonder what mode are you using in procoder2?? in mastering quality my processor is maxedw/ one instance not even cce can do that!

[pitchblack]

Hi l8nights,

I am using DDR 400 MHz CL2.5 Ram.

@l8night: are you using 512 MB RAM in one piece? Or 2 x 256 MB?

At least 512MB is in my oppinion not a standard Size for encoding.

Just having a test with another title:

I am using mastering quality as standard setting.

ProCoder Single Mode is using round about 519 MB physikal RAM, taking 99% of my CPU capacitiy.

Now ProCoder in Dual Mode:

is using round about 800 -1000+ MB physikal RAM, taking 99% of my CPU capacitiy.

[l8nights]

I'm using matched pairs 512 total but I may just forego the ram in attempt to get my processor in matched pairs if I can steal some of my money back (first from the government then from the wife )