Is there a way to run two CCE encodes simutaneously?

[Thasp]

When I do DVD9 to DVD5 conversion, it uses 75% of my dual core CPU, which is acceptable. However, when I do HDTV --> DVD compliant MPEG2 encodes, it uses 50-55% of each CPU regardless of version.

Quenc doesn't even use both cores, but I fool it into using both cores by running two encodes at once(I have 5 40 minute transport streams to encode), so each one uses 100% of one of the cores, thus using 100% of the processor. However I can never get QuEnc to give me the quality I want since it always goes way lower in bitrate than what I set it to.

Is there a way to run two CCE encodes at once?

[Amnon82]

Normally CCE is designed for Dual-Cores so CCE is using it already, but not the best way it could. Shure there must be a way. Talk to the coder of the tool your using for Quenc. Darksoul or so.

[Thasp]

Ugh. I just used queenc to make an encode. I set slow and extreme on, and checked trellis/high quality/vbr/two pass. I put 6000 kbps as the value, and for a 41 minute video got a 1 GB file, which translates into an average bitrate under 3400 kbps. What is wrong with this encoder? :( It does this wheather I am upconverting xvids and divxes or downconverting HDTV transport streams.

[Boulder]

Why don't you post in the official QuEnc thread about the undersizing. DragonGodz will probably want to know a thing or two before he can say anything about it.

[Amnon82]

As usual. They start a CCE question and then ...

Avisynth is actually one of the primary limiters of multithreading encoders as well, which is a strong argument in favor of multiprocesses, until multithreaded avisynth is officially released, since Avisynth is used as the source to pretty much everything now.

[Darksoul71]

@Amnon:
As usual. They start a CCE question and then ...


What do you want to indicate ? That AVISynth in the primary limiter for dual core systems during encoding and not CCE ?

Technically I see no reason not doing the same stuff for CCE as for QuEnc (unless the used version of CCE limits you to run only one instance at a time). So a CCE^n in theory should be no problem.

IIRC there were some problems with multiple instances with CCE and DVD-RB and jdobbs removed support for this.

[Boulder]

CCE won't run two instances, at least the v2.70-branch. And it is true that Avisynth is the bottleneck, but v2.6 should do something about that if tsp's multithreading code is added.

[Darksoul71]

Hm, I can´t comment on CCE 2.7 since I never used it but I just tried to launch two instances of CCE 2.5 SP for parallel encoding and everything works fine.

I have not clue wether EclCCE is able two handle two co-existing instances of CCE but with some taylored AutoIt script code and using the PID of each CCE instance I could imagine that "CCE²" is not hard to code. Going the "segmented" route you can quite easily get rid of the AVISynth single thread limitation. At least that was my impression from the numbers I´ve seen.

For my understanding the speed improvement of multithreading is often overestimated.

[Thasp]

I am not expecting a single CCE encode to run with both cores at full load. I would like one encode to run on each core.

I use avisynth scripts with QuEnc now that I fixed my problems with it. It only uses one thread/core per encode, but I can run two encodes, one on each core, thus utilizing the CPU fully. I would like to do this with CCE.

The speed improvement of multithreading increased my output by 2x - instead of one encode being done after a few hours, two were with QuEnc that way.

[Boulder]

You should know that 100% CPU usage does not always mean that the encode goes twice as fast. This has been discussed in the XviD multithreading thread. If the two processes compete of the same resources, the encoding won't run twice as fast as only one instance would run.

[Amnon82]

Like some tests of Darksoul with QuEnc the maximum acheave will be around 60% more than a single core.

[Darksoul71]

..which is of course dependent on your filter configuration. The more cpu-hungry you AVISynth filters are, the lower your speed increase will be, e.g. progressive material without any resize and denoising shows up to 90% increase with QuEnc^n.

[Darksoul71]

I use avisynth scripts with QuEnc now that I fixed my problems with it. It only uses one thread/core per encode, but I can run two encodes, one on each core, thus utilizing the CPU fully. I would like to do this with CCE.
Oh, sry, I thought you wanted to go the "I wanna use both cores for my current encoding"-route. Oh, well, if you are not able to start your CCE version two times (as you can do with QuEnc), there are only two solutions left:
1) Look for another version of CCE (my 2.5 SP runs fine with two instances at the same time)

2) Use another encoder.

Hope this helps,
D$

[Amnon82]

CCE 2.5 was coded for single-core cpus.

I just tested the trial versions of 2.70.02.10 and 2.67.00.27.
I can open both at the same time, but not one of them twice.
Seems it checks if it is already started. I didn't tried differnet versions in the same series (2.70 and 2.67).