PDA

View Full Version : Encoding With Procoder2


Prowler
4th September 2006, 17:47
Using DVDRB v1.10.5 with procoder 2 and just started gettin an error during encoding:

One or more of the Target files you are about to create has a naming conflict.

Then I have to select an option of cancel, overwrite, or change target baseline. I have selected change for a new .M2V file name but the the windows appears again. I can use CCE with no problem on the same files.

DVD-RB log shows:
- Creating M2V for VTS_06 segment 0
- Extracting STILLS for VTS_06 segment 1
-- V06000000001001 no .M2V, retrying.
- Creating M2V for VTS_06 segment 0
-- V06000000001001 no .M2V, retrying.
- Creating M2V for VTS_06 segment 0
- Failed to create M2V: V06000000001001
- The encoder doesn't appear functional.
- Aborting...
Aborted.

Thanks for any help you may be able to offer
Prowler

jdobbs
4th September 2006, 18:07
The error message you mentioned doesn't exist in DVD-RB... so it has to be coming from ProCoder (or ECLPRO). I've never seen it before. Hopefully someone who uses ProCoder a lot can help...

shoarthing
4th September 2006, 18:38
Hi - have only seen this error using Procoder 2.x [& ECLPro] with NuMenu4U - as regards this error message, the option that worked for me was 'replace' or 'overwrite'

^JazzMan^
4th September 2006, 21:16
I think I've had that problem once, try deleting eclpro.ini and then run eclpro.exe so you can reconfigure the settings

cheers

skybl8zr
6th September 2006, 00:43
Using DVDRB v1.10.5 with procoder 2 and just started gettin an error during encoding:

One or more of the Target files you are about to create has a naming conflict.

I only use ProCoder and I can recollect that I've seen this error myself. In fact I think I might have posted a thread about this problem months ago in this forum. I also remember that I easily solved the problem after someone suggested something obvious. I'll go look for the thread now :rolleyes: (I simply can't remember the exact solution but I think it had something to do with uninstalling both ProCoder and DVD-RB, then reinstalling ProCoder and DVD-RB...in that order). Sorry for my bad memory :o

skybl8zr
6th September 2006, 01:39
@Prowler
Sorry for late follow-up (as English isn't my mother language I write soooo slow and I could sit for hours just writing this post :rolleyes:)

Made som diggin and refreshed my old problem I mentioned above. It seems related to yours concerning the naming conflict but maybe the error message has changed since DVD-RB v.1.8.1 when I first ran into the problem. In short I experienced a Target File Warning (http://forum.doom9.org/showthread.php?t=108905) when using DVD-RB v1.08.1 for the first time. Apparently it was because I didn't have ConvertToYUY2() checked (thanks again robot1 for assuring me that ProCoder 2 will not work without ConvertToYUY2() unless you have another capable decoder installed ;)).

But then again another user l8nights experienced the exact same problem as I did although he did have ConvertToYUY2() checked. Still his encoding and I quote...


...would start again after closing the window w/ out selecting any renaming or overwrite options."

I think that warning was fixed from EclPro v1.00 RC1.

To sum things up be sure you have the latest version of EclPro and that ConvertToYUY2() is checked. If that's the case and you still get the error, try uninstalling ProCoder, DVD-RB and everything related to them. Then reinstall ProCoder, then DVD-RB v1.10.5. Then maybe...maybe everything is just downright straightforward again ;)

Prowler
6th September 2006, 03:44
Thank you for all the replies. I will uninstall everything and reinstall everything and see what happens.

skybl8zr I did have the have ConvertToYUY2() checked but thanks for the suggestion!!

^JazzMan^ I did try and del. eclpro.ini and then run eclpro.exe and go through the setup but no change. :-(

If you guys have any other suggestions let me know and again thank you for takin the time to post!!

Prowler

A64
6th September 2006, 08:41
I have run into this on certain disks with both 1.5 and 2.04.02. After deleting the eclpro.ini, when you set it up, state no to the "Force Field Encoding For Interlaced Sources", make sure the Pause=20, Legacy=1 (for 1.5), and AudioDub(BlankClip()) is off. Aviator always failed with the error message until trying these settings. These changes, it went right through on both versions of Procoder. Hope this helps.

Prowler
9th September 2006, 06:11
A64 thanks you for your input also, sorry to report no change. Samer error

I have run into this on certain disks with both 1.5 and 2.04.02. After deleting the eclpro.ini, when you set it up, state no to the "Force Field Encoding For Interlaced Sources", make sure the Pause=20, Legacy=1 (for 1.5), and AudioDub(BlankClip()) is off. Aviator always failed with the error message until trying these settings. These changes, it went right through on both versions of Procoder. Hope this helps. Where would I find the AudioDub(BlankClip()) setting? It is my last option and the only thing I have not tried. ARG. Again thank you all for the help you have offered!!

Rippraff
9th September 2006, 15:54
Where would I find the AudioDub(BlankClip()) setting?
It's under (Settings, depends on your skin) => Options => AVS Options

Cu Rippraff