CCE 2.5 Compability-Mode with windows 2000 SP2

[bernd_b]

I swear two things:
1. I did(!) use the search
2. I never had problems with cce and dvd2svcd on my computer.

The only thing I did (don't ask why....)
I changed to Windows 2000.

Now with every 4th movie, CCE stops just after about 10-15 seconds while producing the mpv-file (the vaf-production always succeeds).
I can repeat this because it happens whith certain movies every time at the same place.

No crash, high cpu usage, but nothing happens. CCE can be stopped with normal mouse-click - no task manager needed.

Because I did the search thing, I knew that there are quite a lot of tips what to to and I tried all:
- different version of avysynth (2.07, 2.08 and 2.5)
- use mpeg2dec2 instead of the default one
- deactivate anti noise filter
- changed the via 4 in 1 driver
- add resample audio activated
- apply the crc patch

Once again: on this maschine cce ran stable. So I have windows 2000 under suspicion.

What I didn't manage to do was to run cce under the compability mode which is offered in w2000 SP2.

I created a link as described in Microsoft Knowledge Base Article 279792 and did the settings. CCE starts with this link. When I offer DVD2SVCD this link instead of the program file itself, DVD2SVCD stops instead of running CCE giving the message:
read beyond end of file
I tried this with build 110B1 und 113B2.

Any link (what did I miss using search) or idea, how to make CCE run with dvd2svcd under the compability mode?
Has anyone made the experience that this can help at all?

[hoozdapimp]

Here's what I can suggest

Q60: I have CCE Issues (CRC errors, crashing and what not)
A: Here's a few pointers to check:


Don't overclock your CPU/memory.

Decrease the memory timings in your PC's BIOS or use the defaults.

Use the latest BIOS from your mainboard manufacturer.

Make sure your power supply and your PC cooling is good.

Use the latest chipset drivers from your mainboard manufacturer. (VIA 4-in-1)

Do some stability tests like Prime95 and MemTest86. (See Q53)

Use "ResampleAudio(44100)" in your Avisynth script.

Turn off the "Anti noise filter" with CCE in "Encoder" tab.

Verify that the "Max." and "Max. avg" bitrate differs with at least '120' maybe more.

Raise "Luminance Offset" in "DVD2AVI" tab to '5'.

Apply the CRC Patch from the Q&A (Q27).

Use the "MPEG2DEC2.DLL" instead of the "MPEG2DEC.DLL" in "Frameserver" tab.

Set "Intra DC precision" in CCE's "Advanced settings" to '8' or 'Auto'.

Turn off VirtualDub's "AVIFile Proxy mode" see the "readme.txt" in the "VirtualDub\aviproxy" for more on that.

When converting downloaded AVIs make sure with tools like "AviDefreezer" that they are not corrupted somehow.

Use the "Safe mode (frameserving)" option in "Encoder" tab - but be aware, this will decrease encoding speed by about 30%.

Try to use a newer "Avisynth" version instead of the one that comes with the bundle.

Only use "CBR" or "One pass VBR" modes only.

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

Use TMPGEnc instead.

[bernd_b]

Well,

"thanks" for copying Q60 and quoting again all the ideas which can be done to prevent cce to crash.

Maybe I should have come faster to the point:

1. Can anyone say, how(!) to start cce with dvd2svcd(!) in compability mode?
2. Has anyone succeeded with this?

[dvd2svcd]

Well, it is much more likely that you have a hardware issue. I would have done what hoozdapimp did and requoted Q60. Be honest, did you really run Memtest86 for a long time, and also Prime95? Because, the list of tips has fixed every CCE issue known until now.

I doubt dvd2svcd (the program) will accept this but you can try making a batch file from where you start cce. Something like this:

START /SEPARATE YOUR_CCE_FOLDER\cctsp.exe

and save it as cce.bat

And then instead of "OUR_CCE_FOLDER\cctsp.exe" in the encoder tab use cce.bat

But as I said, I doubt it'll work and my money is on a hardware problem (which is much more the case when switching from W98 to W2K because W2K uses a much wider range of the hardware available)

[Holomatrix]

I would have to agree with hoozdapimp and DVD2SVCD because there is no need to run any of thoes programs in compatibility mode. I hope you re-installed the said programs after upgrading to Win2k. I've been running Win2k for years and have not run into issues with CCE or DVD2SVCD in regards to the operating system I was using. Problems were due to another nature. Remember also, that because the change to Win2k you might be running into memory access issues. Try some different RAM and see if you still have problems.
Good luck

[bernd_b]

Thank you very much for your all your answers.

I will quit the compability track because of your experiences it is the wrong and the ".bat"-method didn't work as expected. DVD2SVCD doesn't like to start a ".lnk"-File instead of the refered program itself.

I will do the memory check and see what I get. I didn't think of a hardware problem because the same maschine ran without problems under W98. And I didn't expect a hardware problem to stop cce every time at the same movie at the same place, by the same time running with many other movies without problems. But let's face it.

[bernd_b]

here are four further experiences:

1. memtest30:
I did 2 passes all without errors

2. prime95:
I did the self torture test last night 7 and a half hour.
All tests succeeded.

3. CCE 2.66:
The trial version of CCE 2.66 SP did the encoding of the mentioned movies.
By the way: source was dvd, actually a TV series with 18 parts. CCE 2.5 encoded 15 without problems, but three of them show every time the described behaviour. I tried TMPGenc of course too with success.

4. The problems I have seem to be the same which are described here:
http://forum.doom9.org/showthread.php?s=&threadid=50784&perpage=20&pagenumber=1
but I must confess I can't understand what they are talking about in the later posts

If I were smart, I would downgrade to W98 and see what happens. But I fear I will get rid of CCE 2.5 and be satisfied with tmpgenc.