Procoder 3

[canadian guy]

I just seen the new encoder on the net,,will rebuilder work with this in the near future,,if so i mite look into this if it is good as they say,, procoder2 works great and i dont want to fix whats not broken,,cheers

[Fishman0919]

Yes, Both Procoder 3 and Rhozet Carbon Coder work fine with DVD-RB. You need EclPro v 1.10 LINK (http://forum.doom9.org/showthread.php?p=1017520#post1017520)

[kumi]

Are there any compelling reasons for upgrading from ProCoder 2 to ProCoder 3? Has the encoding engine been improved? Anything at all relevant to DVD-Rebuilder users?

[Fishman0919]

The biggest difference is speed with dual and quad core processors. Pro 3 and Carbon being faster.
The mpeg2 stream from Pro 2 and Carbon in most cases are the same, bit for bit. Pro 3 is different, sizing smaller (Carbon and Pro 2 sizing for me with DVD-RB at about 4.32g where Pro 3 does 4.30g) but seems to do a little better at lower bitrates then Pro 2.

[jamewoong]

Are there any compelling reasons for upgrading from ProCoder 2 to ProCoder 3? Has the encoding engine been improved? Anything at all relevant to DVD-Rebuilder users?
Yeah, I want to know it too... How about the speed if we're using a system without CORE DUO comparing to Procoder 2? Anyone test it yet?

Between, someone sell it for US $75.00 @ ebay. If there is some accelerations, I think I'm gonna take that deal. :)

It is legit for that guy to sell like it at that price? The retail price is over $400.

[Fishman0919]

Yeah, I want to know it too... How about the speed if we're using a system without CORE DUO comparing to Procoder 2? Anyone test it yet?

Speed on a single core cpu with Pro 3 and Rhozet Carbon Coder is the same as Pro 2.

The only benefit for speed is with dual or quad cores

[kumi]

Pro 3 is different, sizing smaller (Carbon and Pro 2 sizing for me with DVD-RB at about 4.32g where Pro 3 does 4.30g) but seems to do a little better at lower bitrates then Pro 2.
Thanks for your input. Can I ask if this is a subjective impression of yours, or if you've done any metrics, or... ?

[Fishman0919]

Can I ask if this is a subjective impression of yours, or if you've done any metrics, or... ?

Both, Pro 3 does better with metrics and looks better too me. A couple of blink tests at home and I pick Pro 3... 8 out of 10 times.

[march2006]

AFTER USING RB WITH PROCODER3 and dvd is wayoversize
3398MB
any setting in OPTION need to change?THANKS

[Wombler]

AFTER USING RB WITH PROCODER3 and dvd is wayoversize
3398MB
any setting in OPTION need to change?THANKS

3398MB is way below the capacity of a single layer DVD.

It'll fit no problem.


Wombler

[Fishman0919]

3398MB is the total size or...

3398MB oversized

[Wombler]

3398MB is the total size or...

3398MB oversized

Good question.

If it's the latter then it looks as if he hasn't compressed it at all.


Wombler

[march2006]

it's total SIZE when you load in VOBLANKER

[Fishman0919]

Like Wombler said... that will fit on to a single layer DVD

[march2006]

i know but procoder2 size is close to 4477mb
but procoder3 way below.. anyway to set a target to get closer like procoder2? thanks

[Fishman0919]

I've had Pro 3 undersize a little bit.... Pro 2 sizing at 4.32g where Pro 3 does 4.30g.... but thats a whole bunch off... something else is going on.

[Prowler]

Fishman0919 or anyone else using Procoder 3: have ya done anything to change the procoder3 file size and if so what have you changed it to? I would like to get back to 4.32 instead of 4.3 even if it doesn't make a whole lot of difference.

[Fishman0919]

under options in the rebuilder.ini

ProCoderTargetSectors=2250000

seems to get the size for me to 4.33g most of the time

[robot1]

under options in the rebuilder.ini

ProCoderTargetSectors=2250000

seems to get the size for me to 4.33g most of the time

In the Eclpro thread Kumi reports an error with Procoder3.
Have you experienced any errors with this new version?
I think I could change something in Eclpro to get a better sizing with the standard parameters.

[Fishman0919]

No errors with either Carbon or Pro 3.

The size issue is due to Pro 3 rounding down the bitrate a lot.... much like with Procoder Express. I did some tests with the 3 of them (Pro 2, 3 and Carbon), I can't remember the bitrate but it was something like 3661k.... Pro 2 and Carbon rounded down to 3660... fine... but Pro 3 rounds down to 3650k like with Procoder Express.

Edit: If you want robot1, I can sent you any info you need. I just save a .PCP file with the bitrate if 3147k and Pro 3 rounds it down to 3100k.... where Carbon rounds down to 3146k

[robot1]

I've added some code to solve the rounding bug.
Obviously it's a trick: I don't understand why ProCoder3 rounds the bitrate in this way.

EclPRO v1.11 (http://www.savefile.com/files/1147815)

[Fishman0919]

Tried 3 disc.... 4.34gb, 4.33gb, 4.34gb

very nice

[jdobbs]

Thanks robot1. Hope you don't mind if I include this update in the next release of DVD-RB.

[robot1]

Thanks robot1. Hope you don't mind if I include this update in the next release of DVD-RB.

My pleasure.
Anyway, in this build EclPro is not compressed with UPX (hope to avoid false positive in antivirus scanning)

[jdobbs]

Cool. Thanks!

[Fisticuffs]

I get this on Procoder 3:

"One or multiple targets could not be restored from the project file"


I've done the same project on Procoder 2 and it works fine, this only happen on Procoder 3.

Anyone know how to fix this?

[linx05]

Did you update (http://forum.doom9.org/showpost.php?p=1058648&postcount=21) and setup EclPRO?

All these people who can afford Procoder 3, I wish I could!

[Fishman0919]

The mpeg2 stream from Procoder 2 and Procoder 3 are the same. Pro 3 is faster with dual core and quad core cpu's.

[Fisticuffs]

Did you update (http://forum.doom9.org/showpost.php?p=1058648&postcount=21) and setup EclPRO?

All these people who can afford Procoder 3, I wish I could!



Yes, I am already using version 1.11 and I've tried it on more than one movie.

[march2006]

option:
[Options]
Mode=3
OneClick=0
ReduceOpt=0
NoWarn=0
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=1
HC_Quality=1
HC_Matrix=1
SkinVersion=12
AudioDub=1
QuEncodeType=0
iDCT=4
GOP=0
DCPrec=0
MainMatrix=Encoder Default
LowMatrix=Same as Main Feature
VLowMatrix=Same as Main Feature
ExtraMatrix=Same as Main Feature
ProCoder_Quality=4
TargetSectors=2276000
DVD_Label=NO_SELECTION
DVD_Name=NO_SELECTION.ISO
MovieOnly=0
HalfD1=0
Convert_16_9=0
DisableInterlace=0
ConvertToYUY2=1
CCE=2
CCETargetSectors=2276000
Skin=Rebuilder Default
Encode_Processes=1
NewEditor=0
Redistribute=1
Redist_All=1
HC_FOR_REDIST=1
[Paths]
QuEnc=C:\Program Files\DVD-RB PRO\Encoders\QuEnc\QuEnc.exe
ReJig=C:\Program Files\DVD-RB PRO\Encoders\ReJig\ReJig.exe
HC=C:\Program Files\DVD-RB PRO\Encoders\HC Encoder\HCbatch.EXE
FFMPEG=C:\Program Files\DVD-RB PRO\Encoders\FFMpeg\ffmpeg.exe
CMDLINE=C:\Program Files\DVD-RB PRO\Encoders\CMDLINE\mencoder.bat
ProCoder=C:\Program Files\DVD-RB PRO\Encoders\EclPro\EclPro.exe
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb521.dll
NICAUDIO=C:\Program Files\AviSynth 2.5\plugins\nicaudio.dll
MPEG2DEC=C:\Program Files\DVD-RB PRO\DGDecode.dll
Working=C:\
Output=C:\
CCEBasic=C:\Program Files\Custom Technology\Cinema Craft Encoder SP\cct2.exe
CCENEW=C:\Program Files\Custom Technology\Cinema Craft Encoder SP2\ccew.exe
[Audio]
Selected=
[Subpictures]
Selected=


windows vista after encode: undersize only gave me
4371MB TOTAL SIZE

[march2006]

I've added some code to solve the rounding bug.
Obviously it's a trick: I don't understand why ProCoder3 rounds the bitrate in this way.

EclPRO v1.11 (http://www.savefile.com/files/1147815)

your version 1.11 it works with core 2 dual versionright?
should i add this line
ProCoderTargetSectors=2250000 or
TargetSectors=2260000 or
TargetSectors=2276000

TO GET CLOSER TO 4477MB SIZE..
THANKS

[Fishman0919]

v1.11 fixes some undersizing with Pro 3... most discs end up around 4.34gb with the default DVD-RB settings. You always want to leave some headroom on disc.

edit: your version 1.11 it works with core 2 dual versionright?

Pro 3 works with dual cores.... EclPRO just feeds the info to Procoder

[march2006]

thanks... after finished.. size is 4.31GB not any closer to 4.33-4.34

[Fishman0919]

4.31gb is fine... the difference between 4.31gb and 4.34gb is not noticeable visually.