DVD-RB 1.08.1: Target File Warning (Procoder2)

[skybl8zr]

Can't seem to find anything about this topic anywhere. I recently went from DVD-RB 1.04 to 1.08.1 using the same settings together with Procoder 2.04. I rarely change the default settings in DVD-RB except for turning off ConvertToYUY2() and AudioDub(BlankClip()) because I understand they're not needed with Procoder 2. In EclPro.ini I mostly use AlwaysGOP15=1 and leave everything else at their defaults. In Rebuilder.ini I only add TargetSectors=2255783 to prevent oversizing.

Then in 1.08.1 after Prepare and clicking Encode, Procoder 2 opens with a pop up error few seconds later during "Creating M2V for VTS_01 segment 0":

"Target File Warning"

It's something about naming conflicts which leaves me some options whether I want to rename V01000000001001.m2v to V01000000001001_1.m2v and so on, or always overwrite old target files (don't remember all the options but I'll take a screen cap on request).

After experimenting with settings and re-installations I finally turned on ConvertToYUY2() and AudioDub(BlankClip()). Prepared and started encoding sucessfully. Then started all over again but turning off only AudioDub(BlankClip()) leaving ConvertToYUY2() on. I can still encode.

So why is ConvertToYUY2() suddenly needed with Procoder 2? Does this have any negative effects on the encoding process or output video? Furthermore it now seems that the encoding process is much faster than before with 1.04. I always use Mastering quality...

Thanks in advance for any clarification on this matter which is likely to make me lesser confused :confused:

[Rockas]

Haven't you reveived the download link?
Download the latest Rebuilder installation pack (1.09)... it contains a new version of EclPRO.

[jdobbs]

This is a new one to me... I don't think I've ever tried to use ProCoder without ConvertToYUY2()...

[robot1]

Procoder needs ConverttoYUY2()
It could wotks without the line only if you have installed a capable decoder, but I think it's better to stay with the avisynth internal decoder.

It's safe to turn off the usage of AudioDub(BlankClip())

[l8nights]

I've just recieved the target warning mentioned above I just closed the window to see what would happen and it continued.
strange thing I had three instances of procoder going for the remainder of that segment. all doing there job other things of interest are that encode finished @ 99.7% and rebuild completed w/ out a hitch! (I haven't watched the product yet, will do so)

I was using forced reencode and fluxsmooth& undot on a 4.3 gb file that needed some cleaning.

ver 1.09& procoder 2.04 multiple instances.

the error to me was just something to do w/ the naming of the file I thought?!?
no other errors were reported.

[jdobbs]

I just read a note from Robot1 in another thread... you have to have ConvertToYUY2() set because ProCoder doesn't accept YV12 (the default) without a decoder installed.

[l8nights]

This is a new one to me... I don't think I've ever tried to use ProCoder without ConvertToYUY2()...me either, but as for the error closing it and allowing it to run competed the encode

I have watched the movie and all is well Just an anomaly?

[skybl8zr]

Haven't you reveived the download link?
Download the latest Rebuilder installation pack (1.09)... it contains a new version of EclPRO.
I've now upgraded to 1.09 but it didn’t make any difference in this case. I still get the Target File Warning from ProCoder 2 when ConvertToYUY2() isn’t activated.

Procoder needs ConverttoYUY2()
It could wotks without the line only if you have installed a capable decoder, but I think it's better to stay with the avisynth internal decoder.

It's safe to turn off the usage of AudioDub(BlankClip())
Without ConvertToYUY2() in DVD-RB 1.04 I always got satisfying results with ProCoder 2 on mastering quality though it took approx. 400 minutes to encode a 7-8GB source. With ConvertToYUY2() activated it took 190 minutes to encode the 6GB source I used in this case... :eek: But there was undersizing (please see for details further down).

I’ve always had AudioDub(BlankClip()) turned off together with ConvertToYUY2().

I've just recieved the target warning mentioned above I just closed the window to see what would happen and it continued.
Whatever I do at the first Target File Warning whether I click cancel or choose “Change Target Basename” it also continues here but not with normal encoding. From the rebuilder.log:

[17:25:26] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
-- V01000000001001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 0
-- V01000000001001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 0
-- Zero length .M2V file for V01000000001001.
- Creating M2V for VTS_01 segment 1
-- V01000100001002 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 1

…

Then a new Target File Warning pops up and asks if I want to “Change Target Basename” for V01000100001002_1.m2v. And so on.

I just read a note from Robot1 in another thread... you have to have ConvertToYUY2() set because ProCoder doesn't accept YV12 (the default) without a decoder installed.
I’m not sure if I’ve had an alternative decoder other than AviSynth and if I’ve uninstalled it. Maybe that’s the case…

At the time writing this I’ve just completed a second encode using 1.09 with ConvertToYUY2() turned off. Both times the output video was undersized (4.21GB). With first encode (Three Click Mode) I used TargetSectors=2255783 as always (4.35GB output every time until now). For the second encode (One Click Mode ) I used DVD-RB’s default 2236400 sectors. In both cases the output was 4.21GB… :confused:

I’m not sure what to do next. Would it do any good to post my rebuild.ini settings from DVD-RB 1.09 here and/or email you, jdobbs, the whole report or some part of it created by DVD Rebuilder’s Reporter?

BTW, I've enclosed a cap of the Target File Warning.

[jdobbs]

Try creating another directory for use as your work directory and see what happens. From the warning it looks like somehow ProCoder is using that path for a "Global" address????

[robot1]

Without ConvertToYUY2() in DVD-RB 1.04 I always got satisfying results with ProCoder 2 on mastering quality though it took approx. 400 minutes to encode a 7-8GB source. With ConvertToYUY2() activated it took 190 minutes to encode the 6GB source I used in this case... :eek: But there was undersizing (please see for details further down).

ProCoder can't work and must not work without the ConvertToYUY2(). If it worked before, surely you had another decoder installed. Uninstalling some applications, you have removed it later.
Please, don't try DVD-RB without ConverTOYUY2().

For the undersizing issue... I don't know. Usually ProCoder is very strict about sizing, but it could depend from the source.
I think your setup is ok.

[robot1]

Try creating another directory for use as your work directory and see what happens. From the warning it looks like somehow ProCoder is using that path for a "Global" address????
In DVD-RB you get that warning usually when it retries to encode the same segment: ex. you have a 0 bytes segment, and DVD-RB retries it.
To avoid the warning, in the next version EclPRO will delete the target file before starting ProCoder.

[jdobbs]

Oh, ok... makes sense...

[skybl8zr]

Try creating another directory for use as your work directory and see what happens. From the warning it looks like somehow ProCoder is using that path for a "Global" address????
Actually, that was one of the first things I did (the one in the attached screencap is a new work folder). The Target File Warning keeps bugging me only when ConvertToYUY2() is off.

[skybl8zr]

Please, don't try DVD-RB without ConverTOYUY2().

Don't worry, never again :)


For the undersizing issue... I don't know. Usually ProCoder is very strict about sizing, but it could depend from the source.
I think your setup is ok.
I'm currently at my 3rd encode with the same source and have only changed iDCT=3 (32 Bit SSE2/MMX) to Decoder Default. Don't know if it makes any difference concerning the 4.21GB undersizing issue. I still use TargetSectors=2255783.

[skybl8zr]

In DVD-RB you get that warning usually when it retries to encode the same segment: ex. you have a 0 bytes segment, and DVD-RB retries it.
To avoid the warning, in the next version EclPRO will delete the target file before starting ProCoder.
But like mentioned earlier the Target File Warning only occurs when ConvertToYUY2() is off, in my case, that is. So it's already possible to avoid the warning. Just set ConvertToYUY2() to on as you have already convinced me of :) Correct me if I'm wrong but could one imagine that these problems l8nights and myself have experienced lately in terms of target file warning and undersizing is somehow connected with the latest changes in EclPRO? Cause I've never experienced those problems before and I've hardly changed any settings compared with my successful encodes in DVD-RB 1.04/EclPRO 0.52.

[skybl8zr]

FYI, the 3rd encode with DVD-RB 1.09/ProCoder 2 and TargetSectors=2255783 went smootly but still with undersizing. This time not 4.21GB but 4.24GB. I will try uninstall the AviSynth version that came with DVD-RB 1.09 and install the full AviSynth v2.5.6a. I need output video at 4.35GB... not more or less :rolleyes:

[jdobbs]

Something in your version (or settings) of ProCoder has to be causing this. I've been testing ProCoder (v2.01) a lot lately and it always sizes exactly for me. Also -- your TargetSectors value of 2255783 is too large. If sized perfectly you would get 4.388GB -- which, of course, is too big to fit on a DVD+-R...

I guess that's more of an observation than an answer...

[l8nights]

This has been the first and (hopefully the last) time I have seen this error. and yes the convert to yuy2() is checked

I was thinking it may be something more w/ the setting becuse it's a rare occasion that I use filters or the force reencode settings.

In DVD-RB you get that warning usually when it retries to encode the same segment: ex. you have a 0 bytes segment, and DVD-RB retries it.
To avoid the warning, in the next version EclPRO will delete the target file before starting ProCoder.

I will except this as an answer as I found this segment in the log file

[16:21:57] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
-- V01000100002001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 1
[16:23:23] Phase II ENCODING started
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3

by this I'm guessing that encode started again after closing the window w/ out selecting any renaming or overwrite options. so rebuilder caught the mistake??

either way the output was flawless btw title: never ending story R1

[skybl8zr]

Something in your version (or settings) of ProCoder has to be causing this.
It seems not to be the case as I've now downgraded from ProCoder v2.04 to v2.01 for the 4th encode of the same source. The result was a 4.24GB undersize again but this time the encoding process took only 178 minutes on mastering quality. With v2.04 the encoding process took 190-194 minutes (same settings).

For me it looks like the TargetSectors=2255783 in rebuilder.ini is totally ignored. I also tried adding ProcodertSectors=2255783.

[Options]
TargetSectors=2255783
ProcodertSectors=2255783
Mode=3
OneClick=0
ReduceOpt=4
NoWarn=1
AdditionalOutput=1
LogFile=1
QuEncHQ=1
EncoderMinimized=1
RemoveDTS=1
HC_Quality=1
HC_Matrix=1
SkinVersion=12
Skin=Windows Standard
AudioDub=0
QuEncodeType=0
iDCT=3
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
DVD_Label=SHINOBI_HONPEN
DVD_Name=SHINOBI_HONPEN.ISO
MovieOnly=0
HalfD1=000
Convert_16_9=000
DisableInterlace=000
ConvertToYUY2=1
CCE=1
Backcolor=10256482
Completed=3
RemoveDC=1
[Paths]
QuEnc=E:\Programmer\DVD-RB PRO\Encoders\QuEnc\QuEnc.exe
ReJig=E:\Programmer\DVD-RB PRO\Encoders\ReJig\ReJig.exe
HC=E:\Programmer\DVD-RB PRO\Encoders\HC Encoder\HCbatch.EXE
ProCoder=E:\Programmer\DVD-RB PRO\Encoders\EclPro\EclPro.exe
DECOMB=E:\Programmer\AviSynth 2.5\plugins\Decomb521.dll
MPEG2DEC=E:\Programmer\DVD-RB PRO\DGDecode.dll
Working=F:\DVDRIP\WORK\
Output=F:\DVDRIP\OUTPUT\
CCENew=E:\Programmer\Cinema Craft Encoder SP 2.7\cctsp.exe
Source=F:\DVDRIP\SOURCE\SHINOBI_HONPEN\VIDEO_TS\
[Audio]
Selected=101
Remapping=
[Subpictures]
Selected=11


I've been testing ProCoder (v2.01) a lot lately and it always sizes exactly for me. Also -- your TargetSectors value of 2255783 is too large. If sized perfectly you would get 4.388GB -- which, of course, is too big to fit on a DVD+-R...

I guess that's more of an observation than an answer...

Some time ago I only used DVD-RB's default TargetSectors value. But I very often got a 4.37GB output and I've experienced that some standalone players had difficulties with playing the last scene on some DVDs. This problem disappeared altogether when I use TargetSectors=2255783. It has given me a 4.35GB output every time but not anymore it seems... :(

At the time being I suspect that the undersizing has something to do with the source video. I will try encoding another source soon...

[jdobbs]

The default value for TargetSectors is 2236400.... changing it to a larger value could not make it smaller....

Also the correct encoder-specific target value is:

ProcoderTargetSectors=nnnn

Are you absolutely positive that the REBUILDER.INI file you posted is also the one being used by DVD-RB Pro? The fact that you are changing the value and not seeing any change in size is very strange... all the bitrates are calculated using that value. Are you loading a Project file? If so, the REBUILD would use the values in the Project file rather than the ones in your REBUILDER.INI...

Please send me (dvd-rb@dvd-rb.com) your REBUILDER.INF and REBUILDER.ECL files for the encode. That way I can look at all the individual segment sector counts and see what bitrates are being used.

[Added]
There's also the possibility that the encoder has been saturated and won't make it any larger... and that is the maximum size it can output. Another possibility is that the computed output bitrate would have exceeded the maximum (or the original) -- which also would have limited the output size. The reason I ask is that I see you have the 50% reduction of Extras turned on -- and that scenario can cause this. The more I think about it, the more this seems to be logical...

[skybl8zr]

The default value for TargetSectors is 2236400.... changing it to a larger value could not make it smaller....

Also the correct encoder-specific target value is:

ProcoderTargetSectors=nnnn

Are you absolutely positive that the REBUILDER.INI file you posted is also the one being used by DVD-RB Pro? The fact that you are changing the value and not seeing any change in size is very strange... all the bitrates are calculated using that value. Are you loading a Project file? If so, the REBUILD would use the values in the Project file rather than the ones in your REBUILDER.INI...

No, I'm not loading any project file. I have always used TargetSectors=2255783 and not the encoder-specific target value. BTW, you may need to update the DVD Rebuilder Help concerning Hidden Settings where it says ProcodertSectors=nnnn instead of ProcoderTargetSectors=nnnn.

I've encoded a new source with ProcoderTargetSectors=2255783. This time the output size was 4.31GB. Still not the expected 4.35GB.


Please send me (dvd-rb@dvd-rb.com) your REBUILDER.INF and REBUILDER.ECL files for the encode. That way I can look at all the individual segment sector counts and see what bitrates are being used.

I've send you the REBUILDER.INF and REBUILDER.ECL files for the 4th encode with the 4.21GB output undersize, and I appreciate when you've got the time to look through them.