Newest DoCCE4U Version

[hendrix]

Sweet - thanks bro

[sidders]

@69MwS

So, as I am a PAL user, should I just rename them to .mpv, using a batch file?

Which file will ReAuthorist tell Scenarist to look for?

Is there something that tells DoCCE4U that it should run pulldown on it?
I'm sure this has only happened in the last couple of versions.

[69Mws]

Originally posted by sidders
@69MwS

So, as I am a PAL user, should I just rename them to .mpv, using a batch file?

Which file will ReAuthorist tell Scenarist to look for?

Is there something that tells DoCCE4U that it should run pulldown on it?
I'm sure this has only happened in the last couple of versions.

The new naming came up with DoCCE4U 1.0.1.2

For me RA always points to the mpv, never to the mpv.m2v, so I have to rename the re-encoded Streams. You can easily check that in the RA Script by opening it in any texteditor.

It's up to you whether you use my tiny batchfile or do it manually :)

I don't think that there's really a pulldown running on the files, it's just that they are named in another way.

I'm sure BBWoof will fix that soon :)

Greetz
69Mws

[sidders]

Cheers mate, thanks for your help

[Eyes`Only]

If you like to ease up the process of renaming a little bit, just do the following:

- Open any texteditor
- type ren *.mpv.m2v *.
- save it with the ending "bat" (e.g. rename.bat)


For NTSC, this is terribly incorrect, and will screw up most NTSC projects, as we need most of our *mpv.m2v files (just not the ones with nopull in them). Do NOT use this batch file. Rather, use:

ren *.nopull.mpv.m2v *.

[69Mws]

Originally posted by Eyes`Only
For NTSC, this is terribly incorrect, and will screw up most NTSC projects, as we need most of our *mpv.m2v files (just not the ones with nopull in them). Do NOT use this batch file. Rather, use:

ren *.nopull.mpv.m2v *.

I was wondering too, because it was told that there should be no probs with the file-endings when dealing with NTSC :confused:

Greetz
69Mws

[sidders]

My filenaes didn't have NOPULL in them, just the ending mpv.m2v.
Should they have NOPULL in the filename if it's a PAL project?

[69Mws]

Originally posted by sidders
My filenaes didn't have NOPULL in them, just the ending mpv.m2v.
Should they have NOPULL in the filename if it's a PAL project?

I never had nopull in the filename when dealing with PAL. That can only occur with NTSC as far as I understand.

Greetz
69Mws

[Eyes`Only]

nah you wont see nopull files for PAL. But since NTSC users also read this thread, we need to make sure they dont try the ren *.mpv.m2v *. line, because it will seriously screw up RA's success rate (as in very little possibility of success!)

[69Mws]

Yup people, read carefully.

My advice is to take a look in the RA Script at first before doing any renaming and not to rename your files in any case, especially when you're dealing with NTSC material!

Hope I made myself clear once and for all.... :devil:

Greetz
69Mws

[D3s7]

for those of you who are lazy like me use this to rename all the .nopull files

CD to your root rip dir and type:
for /r %a in (*nopull.mpv.mpv) do ren %a *.

works like a charm

[Eyes`Only]

no need now. 1.0.1.4 is out :D

[D3s7]

as usual i'm late :D

[sidders]

Where? It's not on the website yet

[D3s7]

nawt on da website it's not :D

on doom9dls though :D

[sidders]

I see....going there now.....

[hendrix]

Originally posted by Eyes`Only
no need now. 1.0.1.4 is out :D

i agree - 1.0.1.4 is a 1.0.1.3 bugfix :D

[FunkeeC]

Does these new DoCCE4U work with cce 2.5? The last version i could get to work was 1.0.1.0 Am i missing something? thanks

[hendrix]

1.0.1.4 works perfectly with cce 2.5

[jerschwab]

I'm with FunkeeC, I can only get 1.0.1.0 to work properly with CCE v2.50. The newer versions (since adding support for CCE 2.66) haven't worked properly. It does 1st pass, but not 2nd pass.

[BBWoof]

It appears that I've broken support for 2.50. I have a 4 day weekend this week, so I should have more than enough time to figure it out and get another release out.

BBWoof

[hendrix]

i have no problems with 1.0.1.4 w/cce 2.5 in multipass mode

[Discoboy]

Hi,
Very minor issue. I found with 1.0.1.4. when starting up DoCCE4U, CCE ver. 2.66.00.10 is reported, but I am using CCE ver. 2.67.00.10.

[BBWoof]

Originally posted by Discoboy
Hi,
Very minor issue. I found with 1.0.1.4. when starting up DoCCE4U, CCE ver. 2.66.00.10 is reported, but I am using CCE ver. 2.67.00.10.

Whoops, gotta fix that.

BBWoof

[BBWoof]

I've been working on the program this morning trying to fix the bug with CCE 2.50, and have discovered that the only way it can be fixed is to revert to EclCCE 1.4b. Without modifying any of my code, I switched back to 1.4b and CCE 2.50 works fine.

BBWoof

[trigger638]

BB looks like your site is down. Or at least the link to the DoCCE4U.

By the way I was using version 1.0.1.2 just fine with cce2.5, but 1.0.1.3 it was deffinatly broke if that helps.

Thanks

[ShaneZ]

Originally posted by trigger638
BB looks like your site is down. Or at least the link to the DoCCE4U.

By the way I was using version 1.0.1.2 just fine with cce2.5, but 1.0.1.3 it was deffinatly broke if that helps.

Thanks

The site went down for a while because the ISP was having trouble. Everything should be up and running fine. You must have caught it during downtime.

:(

[SVCD4Me]

.

[R3VOLV3R]

I don't know if this a bug in ReAuthorist or DoCCE4U but...

The BIAS value does not show up correctly in DoCCE4U 1.0.1.4
whenever it is passed from ReAuthorist RC3.

The highest BIAS value in DoCCE4U that appears is 50 even
though ReAuthorist assigns the BIAS value to let's say 62.
BIAS value 50 and lower shows up correctly in DoCCE4U.

I always have to manually adjust the BIAS value in DoCCE4U
to match that of ReAuthorist.

Like I stated at the top, or maybe it is a bug in ReAuthorist
calculations and the BIAS value shouldn't go any higher than 50.

Well just something I discovered.

[BBWoof]

It's not a bug with either. It's something that hasn't been implemented yet. Aqua is working on exporting all the data, which he has finished with RA 1.0.0 and DoCCE4U 1.0.1.5 will import and save it.

BBWoof

[stopthepain]

I hope this is not a stupid question, I looked through the forums (and even gave google a shot ;) )
Does anyone know where I can get a copy of EclCCE 1.4b? I am having the problem when DoCCE4U finishes, I end up with a 1kb m2v file. It sounds like the fix is going to EclCCE 1.4b, but I cant for the life of me find it. Can anyone help?

[hendrix]

actually you may want to download eclcce 1.5a - its in the downloads

[Eyes`Only]

You are either kidding, or you have the search skills of a braised donut. A simple forum search for "eclcce" will suffice.

[RB]

Latest version of EclCCE can always be found in the CCE forum, sticky thread labeled "EclCCE...".

[brashquido]

Originally posted by Eyes`Only
You are either kidding, or you have the search skills of a braised donut. A simple forum search for "eclcce" will suffice.

Mmmmm.....braised donut ;)

[benf2]

I just bought CCE Basic and seems that this prog only wants a trial exe with ecl so I am unable to use DoCCe4u. Any plans on making it compatible?

[D3s7]

good question.

eclcce, the utility used to help along CCE is really only needed because of the limitations due to the trial version... however, it should work just fine w/ the full blown version I'd think

[da_SPiN]

Hi guys,

first of all, thanks for this nice tool.. second, is it possible that CCE SP 2.66.01.01 (Trial)is not supported by version 1.0.1.4 (BETA) of DoCCE4U? I always get the error:

CCE Executable associated with EclCCE is not supported by DoCCE4U. Please reconfigure EclCCE and restart DoCCE4U.

- In the log window it tells me the following: DoCCE4U 1.0.1.4 BETA by BBWoof started
- OS Kernel = Windows_NT (Good)
- ECLCCE executable 1.4c found
- Unknown or unsopported CCE executable found!

Any help? thx guys...

SPiN

[D3s7]

I believe 1.4 of ECLCCE was buggy.. 1.5 is out... try deleting your ECLCCE.INI file and drop in the new ecl and point to your ccesp.exe file again..

[RB]

Originally posted by da_SPiN
CCE Executable associated with EclCCE is not supported by DoCCE4U. Please reconfigure EclCCE and restart DoCCE4U.


DoCCE4U uses EclCCE (see sig) to run CCE. EclCCE also adds support for loading and saving ECL files into CCE 2.66/2.67 (missing in these trial versions). However, this is supported only for CCE 2.66.01.07 and up. So you'll have to use CCE 2.66.01.07 (see Doom9 dowmload section) or CCE 2.67.

[da_SPiN]

updating to version 1.5b of EclCCE didn`t solve the problem... any other hints? thanx in advance

SPiN

[D3s7]

Yeah.. read what RB said :D

[da_SPiN]

ahhhhh, thx RB... you posted the same time I did.... so I`ll try with an upgrade.... thx

SPiN

[benf2]

is there anyway of turning off the feature of DoCCE4u looking for ecl, since i am using a full version (Basic), this isnt needed. Otherwise i cant make use of the prog.

[RB]

DoCCE4U will not work with CCE Basic due to some missing features in CCE Basic.

[benf2]

Not what I wanted to hear, i guess its back to the old way!

[Grimlock]

Originally posted by da_SPiN
ahhhhh, thx RB... you posted the same time I did.... so I`ll try with an upgrade.... thx

SPiN

I was getting that same error. I don't know if this was your problem, but I when I upgraded EclCCE I put it in the same directory as the trial CCE. Turns out you need to put the new EclCEE files in the DoCEE4u directory and overwrite the old ones in order for the upgrade to actually work. That's what I did and that error went away. Good luck!

[BBWoof]

Originally posted by benf2
is there anyway of turning off the feature of DoCCE4u looking for ecl, since i am using a full version (Basic), this isnt needed. Otherwise i cant make use of the prog.

When they named it basic, they really meant it. It only supports 2 Pass VBR and CBR I believe. Also there is no option to add chapter points, only auto I-Frame insertion. Two very big limitations.

BBWoof

[benf2]

Ok, i guess its back to the old way!

Thanks

[orandennison]

First off- thanks to Woofsoft for all of your great work on DoCCE4U, it's a real time-saver.

This possible bug deals with the "Convert chapters to film" checkbox: It doesn't seem to have an effect if you manually uncheck it to override the automatic setting. I found this to be a minor problem since I had already exported my chapters with chapterXtractor intending to use Doom9's method for backing up NTSC dvds with CCE and dvdmaestro, and then I decided to give DoCCE4U 1.0.1.4 a shot instead.

I had set ChapterXtractor to export the chapter list at film speed, so when I imported the chapter list into DoCCE4U I de-checked the "convert chapters to film" checkbox in DoCCE4U since it was unnecessary. After I added the encoding job in DoCCE4U, I double checked the job's settings and the "convert chapters to film" checkbox was filled and the list of chapter points in the box was wrong. I re-unchecked the box and decided to just run the job and see what happened. DoCCE4U still went ahead and converted my chapters to film speed in the ecl- meaning it had converted my chapter points to 20fps or so..

Of course the fix for me is to just export everything at 29.97fps from chapterXtractor and let DoCCE4U do its thing, but I thought I'd let you know that checkbox didn't seem to be working correctly. DoCCE4U will just do what it wants to do by converting the chapters to film speed- even if your chapter list was already set to film speed before you imported it.