New CCE SP 2.70.02.00

[Fishman0919]

New CCE SP 2.70.02.00

Download: http://www.cinemacraft.com/eng/download.html#sp

Change Log: http://www.cinemacraft.com/files/txt/sh27020e.txt

New GUI, smaller more like CCE 2.50
New Updated encoder engine to 2.70 rev.8.
more....

[unplugged]

Originally posted by Fishman0919
New GUI, smaller more like CCE 2.50
Smaller? I don't see it any way smaller
Originally posted by Fishman0919
New Updated encoder engine to 2.70 rev.8.
Oh, hoping this is something borrowed from Pro version (enhanced).

[Matthew]

It seems like command-line support has gone bye bye :(

[Fishman0919]

If you uninstall any previous ver (2.66 and up) the window (sorry not GUI) is small like 2.50

[hobyho]

Originally posted by Matthew
It seems like command-line support has gone bye bye :(

I don't know how you come to that conclusion, command-line support is still there.

[Matthew]

Originally posted by hobyho
I don't know how you come to that conclusion, command-line support is still there.

I ran the same command and ecl that works just find in .05, and while the ecl loaded, encoding didn't start automatically. I'll re-install it and have another go then.

[Fishman0919]

I noticed that it won't auto start with .ecl files when I tried to use CCE 2.70.02.00 with DVD-RB.

[hobyho]

Strange it works fine for me with Rebuilder, however OPV prediction using RBOpt shows the symptoms you describe (that is, it will not start to encode without manual intervention).

[drob]

I can confirm that, ecl would load but wont start encoding.

[hobyho]

I started a post here with a solution

http://forum.doom9.org/showthread.php?s=&threadid=89943

Basically what needs to be done is the encoder needs to be set to minimised for it to auto-start encoding, which is an option in RB.

[drob]

Originally posted by hobyho
I started a post here with a solution

http://forum.doom9.org/showthread.php?s=&threadid=89943

Basically what needs to be done is the encoder needs to be set to minimised for it to auto-start encoding, which is an option in RB.

Problem is this may work for RB but with AutoQ there is no such option, and running a command line straight to cce doesn't work.

[Matthew]

I don't use RB either, hopefully it's just a bug and a fixed version will be released soon.

[archaeo]

Re: "Updated encoder engine to 2.70 rev.8"
unplugged wrote: "Oh, hoping this is something borrowed from Pro version (enhanced).

Apparently it's not a major change...

I posted this is another thread, but in case you haven't seen it:

from Cinema Craft Tech Support:

Regarding 2.70 rev.8 encoder engine update - It's a bug fix version.

The problem was DC coefficients' value going beyond MPEG2/Video
(ISO/IEC 13818-2) standard at some situation.

Such situation occurs when there is quite low distortion and
high in contrast of luminance or chrominance.

[Amnon82]

AutoQ 1.3.3 supports now the newish version.

[Amnon82]

Use EclStart to get the full batchmode back ...

[P0l1m0rph1c]

Btw, now that we talk about CCE bugs, am I the only one having a memory access violation at the end of every encode with every 2.70.xx.xx versions?

This only happens when exiting from a command line batch encoding in CCE.

[Amnon82]

@P0l1m0rph1c: Maybe Ur the only one. I do also batchencodes via EclStart with my tool AutoQ. Memory errors I don't get. Some User of my program have memory errors when thy closing my program. This happend only if they opened a AVS with a XviD-Source in it. With MPEG2Source there isn't such a error.

[Matthew]

Originally posted by P0l1m0rph1c
Btw, now that we talk about CCE bugs, am I the only one having a memory access violation at the end of every encode with every 2.70.xx.xx versions?

I get that, but only when re-encoding xvids. I used to get this on an earlier version of CCE too, but a new koepi binary was released and the problem went away. Now it's back again with 2.70.