NEW DoCCE4U Version 1.0.1.1

[BBWoof]

Since this new version is now using EclCCE by RB to control CCE I thought I'd start a new thread since this will probably create new problems.

The new version supports CCE versions 2.50 and 2.66.01.07. As I get the opportunity to test other versions of CCE I'll add them to the supported list.

There are also some additions for the PAL folkes.

Please post your suggestions/bug reports here.

BBWoof

Download at: http://docce4u.panthersden.com

[brashquido]

I'm in a region 4 PAL zone. Is there any advantage moving from 2.50 to 2.66.01.07? If so what are they?

[69Mws]

Thx for this great Release, the PAL extensions are great and I saw in the registry that you also changed the default setting for Luminance Level :)

I experienced small problems, 'cause I had already a configured eclcce on my machine. Always got an error that eclcce is pointing to a wrong CCE Version.

Solution for me: deleted eclcce.ini in the DoCCE4U installation directory, started the eclcce.exe located there and reconfigured the path to CCE 2.66.01.07

Maybe it would be easier to implement the ECLCCE Settings in DoCCE4U, instead using my workaround, if possible.

I'm curious now whether the RoBa-Template works with CCE 2.66.01.07. I once tried loading "RoBa ECL-Files" manually into CCE 2.66.01.07 and it didn't get all the settings right at all (totally wrong bitrate settings).

I'll do a short test today and post the results.

Keep up the great work!

Greetz
69Mws

[Eyes`Only]

Maybe someone familiar with eclcce can help me?

Current config:

DIF4U 1.1.0.17 (duh!)
DoCCE 1.0.1.1
CCE 2.66.01.07
Avisynth 2.51

When eclcce runs, it takes literally 2 seconds and says it's finished. I've even tried loading the .ecls generated by DoCCE4U manually and I get this same behavior. Loading an .avs into eclcce works normally, but then I have to tweak all the CCE settings, and I'm not very familiar with the CCE 2.66 UI yet.

If someone is using this eclcce integration with success, I'd like to know what can be done to fix my issues, please. I have to revert back to CCE 2.50 and DoCCE4U 1.0.1.0 for now.

[69Mws]

Originally posted by Eyes`Only
Maybe someone familiar with eclcce can help me?

Current config:

DIF4U 1.1.0.17 (duh!)
DoCCE 1.0.1.1
CCE 2.66.01.07
Avisynth 2.51

When eclcce runs, it takes literally 2 seconds and says it's finished. I've even tried loading the .ecls generated by DoCCE4U manually and I get this same behavior. Loading an .avs into eclcce works normally, but then I have to tweak all the CCE settings, and I'm not very familiar with the CCE 2.66 UI yet.

If someone is using this eclcce integration with success, I'd like to know what can be done to fix my issues, please. I have to revert back to CCE 2.50 and DoCCE4U 1.0.1.0 for now.

I think I don't get the problem right.

You mean the encoding is finished after 2 seconds?

Maybe try using AviSynth 2.07 in that case.

Update:I have the same "constellation" like you, except I use AviSynth 2.07 instead 2.51 and it all works well (except some issues I posted in this thread). Maybe editing your scipts with this "addaudio-line" could also fix your problem.

Greetz
69Mws

[69Mws]

Uh, I think I found a problem.

There is a setting called "Quality". If this is the setting for Image Quality Priority, then the default setting of 40 is way too high, although the setting in the registry is "16" (decimal). I think the registry key needs another "name" to be recognized by CCE 2.66. I took a look to the registry settings of CCE 2.66. The Key for the Image Quality seems to be named "q_char_f"!

It's also not overwritten, when passed through by ReAuthorist (06.1).

Same with the Bias Setting. The Bias from RA is also ignored.

Processing of RoBa Template seems to work correct nevertheless.

Another strange thing: when I load the created ecl manually into CCE 2.66, the Video Setting Button is disabled :confused:
Update:The Video Button is only disabled when opening manually the ECL from the first RoBa Part. When opening the ECL from RoBa Part 2, the Video Button is no longer disabled. Just FYI.

Greetz
69Mws

[69Mws]

Originally posted by brashquido
I'm in a region 4 PAL zone. Is there any advantage moving from 2.50 to 2.66.01.07? If so what are they?

I experienced CCE 2.66 to be faster than 2.50.

Some people would also say, that it delivers better quality, but I think that's quite hard to tell with the naked eye....

Greetz
69Mws

[69Mws]

And here's another one :D

DoCCE4U names the output-files in another way than before: ....mpv.m2v

This will cause problems when using ReAuthorist, 'cause the created Authoring-Script points to "....mpv" not "....m2v.mpv".

This requires then manual correction of the outputted filenames in order to keep the ReAuthoring Script working.

Greetz
69Mws

[69Mws]

I recognized that the DF-Checkbox (Dropped Frame) is enabled in CCE 2.66 by DoCCE4U.

I don't know exactly how this setting affects the encoding. Is it needed?

Greetz
69Mws

[69Mws]

Hi there, it's me again... ;)

It's not possible to abort encoding via DoCCE4U.

DoCCE4U just hangs then for some seconds, CCE Encoding is progressing normally.

Greetz
69Mws

[69Mws]

Originally posted by Eyes`Only
...but then I have to tweak all the CCE settings, and I'm not very familiar with the CCE 2.66 UI yet.

It's not that hard. The UI looks a bit different and you have some more options.

The "Quantizer Characteristics" is the equivalent to Image Quality Priority.

You can ignore all the other new options like Low Pass Filter, Dithered Quantization, etc.

Just leave them unchecked. This has been a lot tested & discussed in the CCE Section of the Forum and the conclusion was that it would be better to do not use these new options, if I'm not mistaken.

Greetz
69Mws

[Doom9]

ok, I think I found a critter.

My first encoding stopped right at the beginning with a "acmStreamConvert() failed: at least one parameter is invalid. (11)"
I did some testing with manual encodings and eventually noticed that my DC4U generated ecl begins with this:

[item]
title=VTS__01_P01.4~3_1
vid_out=0
vaf_out=1
aud_out=1

And, a manually created that ecl works begins like this:[item]
title=VTS__01_P03.4~3_1.AVS
vid_out=1
vaf_out=1
aud_out=0
So.. the DC4U output contains vid_out=0 meaning video output is disabled. So far so good, it's the first pass after all. But then it contains aud_out=1 and since my input has no audio, audio encoding will fail and will most likely cause the abovementioned error.

[69Mws]

@Doom9:

Strange thing, my test-encode ended without any error.

The "encoding-jobs" were put by ReAuthorist into DoCCE4U and I used the RoBa Template.

Greetz
69Mws

[Doom9]

well... show me your ecl ;)

I switched to v2.66 and got the exact same behaviour as Eyes (also having the exact same setup as him now). And the ECLs still contain audio: [item]
title=VTS__01_P03.4~3_1
vid_out=1
vaf_out=1
aud_out=1
aud_mode=0

I also found the cause for the 2 second encoding in cce 2.66.. I had an immensely large timecode (106h).. if I reset that to all zeroes things work just fine (ok, then there's the activated 3:2 pulldown detection for my pal files which gives me something to think about, and the quality settings could use some changes, too).

[69Mws]

That's from the ECL during the first RoBa-Part:


[item]
title=VTS__01_P01.4~3_1
vid_out=0
vaf_out=1
aud_out=0
aud_mode=0


And that's from the ecl from the second RoBa-Part:

[item]
title=VTS__01_P01.4~3_1
vid_out=1
vaf_out=1
aud_out=0
aud_mode=0


You could try using AviSynth 2.07 or use this addaudio-command (pointing to the addaudio.avsi) instead of ResampleAudio when using AviSynth 2.51

Greetz
69Mws

[Doom9]

69Mws.. you obviously have never tried AviSynth 2.51 ;) DIFU adds the correct scripts. It has nothing to do with AviSynth, the ECLs are simply wrong, it's not that anything would crash or fail because of AviSynth... AviSynth works perfectly, what the fact that I can encode the ECLs after changing some parameter proves beyond reasonable doubt. It may or may not be related to a certain software setup but it most definitely has nothing to do with the AviSynth version (I have both versions installed and have tested them both).

[69Mws]

Oh, I already used AviSynth 2.5 but I have to admit, that I didn't use it together with DIF4U.

I changed back some time ago to 2.07 as it was recommended by Eyes ´Only to be the most "stable" version for DIF4U...ok, that was some time ago....

If it's not AviSynth then I have no clue what's going on, because my ECLs seem to be ok as you can see :confused:

Greetz
69Mws

[BBWoof]

Originally posted by 69Mws
There is a setting called "Quality". If this is the setting for Image Quality Priority, then the default setting of 40 is way too high, although the setting in the registry is "16" (decimal). I think the registry key needs another "name" to be recognized by CCE 2.66. I took a look to the registry settings of CCE 2.66. The Key for the Image Quality seems to be named "q_char_f"!


In the template for DoCCE4U there is a "Quality" setting. In 2.50 this is called "Image Quality Priority" and in 2.66 it's "q_char_f". Rather than have two settings that mean the same thing, I've combined them into one. I've done the same thing with "Timecode" and "Timecode ref offset".


It's also not overwritten, when passed through by ReAuthorist (06.1).

Same with the Bias Setting. The Bias from RA is also ignored.


You're right. I'm waiting for aqua to export those settings so that I can import them into DoCCE4U.


Update:The Video Button is only disabled when opening manually the ECL from the first RoBa Part. When opening the ECL from RoBa Part 2, the Video Button is no longer disabled. Just FYI.


Probably because during the first part of the RoBa encode I don't export video.

BBWoof

[BBWoof]

Originally posted by 69Mws
DoCCE4U names the output-files in another way than before: ....mpv.m2v

This will cause problems when using ReAuthorist, 'cause the created Authoring-Script points to "....mpv" not "....m2v.mpv".


Actually this shouldn't cause any problems at all. RA has already been adapted. But I think it exports to "...mpv.m2v" not "...m2v.mpv". This was done so that all files would end with the same suffix.

BBWoof

[BBWoof]

Originally posted by 69Mws
I recognized that the DF-Checkbox (Dropped Frame) is enabled in CCE 2.66 by DoCCE4U.

I don't know exactly how this setting affects the encoding. Is it needed?

Drop frame is only "needed" if your final material is 23.976 fps or 29.976. The only thing it really changes is the time display in a player, certain frames are not counted toward the time code display. If your source is 23.976 and DoCCE4U runs pulldown on it, it also automatically set Drop Frame to true.

BBWoof

[69Mws]

Originally posted by BBWoof
In the template for DoCCE4U there is a "Quality" setting. In 2.50 this is called "Image Quality Priority" and in 2.66 it's "q_char_f". Rather than have two settings that mean the same thing, I've combined them into one. I've done the same thing with "Timecode" and "Timecode ref offset".
BBWoof

Ok, so you combined them.

If I change the quality setting in the DoCCE4U UI it will be passed through to CCE, but when I try to change the default-setting in the registry to another than 40, it won't be recognized by the DoCCE4U UI when I restart it. What am I doing wrong?

Greetz
69Mws

[69Mws]

Originally posted by BBWoof
Drop frame is only "needed" if your final material is 23.976 fps or 29.976. The only thing it really changes is the time display in a player, certain frames are not counted toward the time code display. If your source is 23.976 and DoCCE4U runs pulldown on it, it also automatically set Drop Frame to true.

BBWoof

Well...but how will it affect my PAL-Stream with 25 FPS :confused:

Greetz
69Mws

[BBWoof]

Originally posted by Doom9
ok, I think I found a critter.

My first encoding stopped right at the beginning with a "acmStreamConvert() failed: at least one parameter is invalid. (11)"

That probably is the problem. I'm checking my registry writing functions now. The aud_out setting is written directly from the template, so whatever the template says is what shows up here. I have found a bug in my code that adds the registry entries. To fix this, run Regedit.exe and find "HKEY_CURRENT_USER\Software\WoofSoft\DoCCE4U\template" and delete it. Then restart DoCCE4U.

I will fix this in the next release.

BBWoof

[BBWoof]

Originally posted by Doom9
I also found the cause for the 2 second encoding in cce 2.66.. I had an immensely large timecode (106h).. if I reset that to all zeroes things work just fine (ok, then there's the activated 3:2 pulldown detection for my pal files which gives me something to think about, and the quality settings could use some changes, too).

I hope the above fix of deleting the template registry entries and rerunning DoCCE4U will fix this problem as well. :(

BBWoof

[69Mws]

Originally posted by BBWoof
Actually this shouldn't cause any problems at all. RA has already been adapted. But I think it exports to "...mpv.m2v" not "...m2v.mpv". This was done so that all files would end with the same suffix.

BBWoof

Sorry, of course you're right, the ending is ...mpv.m2v

But when you press the AuthorIt Button in RA before encoding, it definately points out to "pure" mpv without m2v in the Authoring-Script.

I tested it today with RA 0.6.1

Don't know how the script is written, when I encode first and press afterwards the AuthorIt Button, maybe then it points out to the "new file extension". Have to test that again.

Greetz
69Mws

[Doom9]

I'm encoding using cce 2.66 and Avisynth 2.51 now.. the registry fix worked. Now if only cce 2.66 was faster...

[69Mws]

Originally posted by Doom9
Now if only cce 2.66 was faster...

ok, but the encoding-window of CCE 2.66 looks cooler than in 2.50 :D

[Eyes`Only]

I experienced CCE 2.66 to be faster than 2.50.


HuH? Please report speeds only when sober :P

[Doom9]

@eyes: that's what I've been thinking but there's a number of people out there for whom CCE 2.66 seems to be faster.. I'll deactivate all filtering and run another 20k frame test when I get back to my fast computer.. that will be the last of me speed-testing.

[69Mws]

Well, as I said I experienced it FOR ME ;) to be faster.

With CCE 2.50 I never reached a speed of 1.8 when encoding PAL progressive sources (without any filtering and no other applications running though). At least I reached this speed when using AVS 2.5 (Beta) with mpeg2dec3 on CCE 2.66

(I'm running P4 2.53 Ghz, 1 GB 2700 DDR-RAM, 7200 rpm HDs on a Gigabyte Mainboard with Win2K SP3)

But we all know, that speed depends on several issues nevertheless.... ;)

Greetz
69Mws

[dssgorila]

Im using the latest version i applied the registry tweak already it encodes fine. But the Output File size in docce4u doesnt seem to calculate properly in the previous verison i got 3.14 gigs and now im getting 3.46 MB, its the same file (harry potter 2 movie file) i just wanted to point this out

[BBWoof]

Originally posted by dssgorila
Im using the latest version i applied the registry tweak already it encodes fine. But the Output File size in docce4u doesnt seem to calculate properly in the previous verison i got 3.14 gigs and now im getting 3.46 MB, its the same file (harry potter 2 movie file) i just wanted to point this out

Hmmmm....... :rolleyes: I didn't change anything at all in the filesize calculator.

BBWoof