CCE problem

[grenalith]

HI

I keep getting this error message on CCE SP version "Index size too big (260).

anybody know why its doing this, I am trying to convert a AVI to a mpeg2.

Thanks
Stephen

[RoopeT]

What kind of avi? Have you used CCE for succesfully converting avis before?

For example, I don't think CCE can handle avis over 4 Gb, these have to be frameserved with VirtualDub / VFAPI / Avisynth. In any case, I suggest you to try frameserving to CCE.

[snowmoon]

I have not seen CCE ( 2.5 ) handle anything larger than 2.0 GB. You can frameserve or using direct stream copy save it as multiple files and the use CCE to encoder them all as one big file. Under settings you can add additional .avi files that it will concatinate while encoding. It takes .avi's spilt with vdub and other program no problem.

[grenalith]

The AVi is 24.1Gig, it runs for 2 hours.

I used Scenalyzer to captures the footage from a VHS tape using a Dazzle Hollywood bridge.
The AVI according to Scenalyzer was a Type 2 AVI although I have tried a Type 1 AVI in cce and it did exactly the same.

I have never used CCE, I usually us e TMPGenc, but I was hoping to use CCE to speed up the process of converting it to a DVD-R.

[Dragonsf]

I got this error message too.On 100+min avis CCE had no problem, but this particular avi was 144 min.Any ideas?
And how do I frameserve from VDub?CCE 2.6 doesn't recognize the sign-post avi as valid input (tmpgenc can).

[DJRumpy]

You may need a newer version of CCE. The techdocs say version 2.4 (pre 2.5 anyway..I think it was 2.4) had a size limitation (they didn't mention 2.5, but I most certainly trust snowmoon). I know for a fact that 2.64, and 2.66 do not have any size limit. Your problem may lie elsewhere. Examine your AVI with GSpot (find it in the TOOLS section) to identify the codecs used in your avi, and to ensure you have everything installed. You can also scan it for errors in VirtualDub. If your problem is size related, you can also simply try frameserving your AVI with either VirtualDub, or AVISynth. If you are on an old version of CCE, it will eliminate the size problem. It will also bypass problems with AVI files which cannot be fed to CCE directly due to corruption, human error during the AVI creation, etc.

[Dragonsf]

Both avis (one with 104 min and the other one 144 min) are both created with the same codec with VDub from a DVD m2v.The only difference (besdies the content) is the length.Both are DV type-2 and contain no audio.
I'd love to use VDub as frameserver (would save the time I need to convert the m2v to avi).Is it possible to use it with CcE 2.62, and if so, how?
Frameserve works with tmpgenc, but CCE doesn't like (no valid avi) the sign-post file (movie.avi.vdr (or whatever the signpost is called) create by VDub frameserving)

[DJRumpy]

You should frameserve with AVISynth. It can use YUY2 colorspace, which is much faster than the RGB VirtualDub. It's also compatible with version 2.62 of CCE.

If you insist on using VirtualDub, you can use VFAPI to open the frame served file from VirtualDub, to create a psudo AVI, which CCE can read.

More info here:
https://www.videohelp.com/forum/userguides/87270.php

[Dragonsf]

Ok, I got it running.It was tricky though:
1.Started VDub with mpeg as input->frameserving->movie.vdr
2.Opened movie.vdr with tmpgenc,saved as job/project->movie.tpr
3.Opened movie.tpr with vfapi-reader and pressed convert ->movie_tpr.avi
4.Open movie_tpr.avi with CCE, encode->movie.mpv.

Pooh, quite a task.

And it works with the big video too!

[Dragonsf]

After 4 hours of encoding, to my surprise the movie turned out to be completly black.
I tested the same constellation before with a few (10000) frames and it worked perfectly. Any ideas so far?

[DJRumpy]

Did you try opening the .VDR file from VirtualDub, with VFAPI to create a psuedo AVI?

Did you try frameserving with AVISynth?

[Dragonsf]

yes, i opened the vdr with vfapi.I didn't use avisynth!
When I look at the preview (from within CCE), I could see the frames!So, IMHO frameserving works.Tonight I make some experiements, to see what happened.Maybe the problem is due to my anamorphic source (see other thread).

[DJRumpy]

If you use AVISynth, you won't need VFAPI (It's slow anyway). If your using VirtualDub + VFAPI, then you shouldn't need TMPGenc at all. I'm not sure why you tried that config, as VFAPI should open the VirtualDub frameserver file directly, and the ouput can go directly into CCE.

[Dragonsf]

When I try to open the frameserver file directly from VDup, I'm getting a ... is invalid.I can open any mpeg file, but CCE doesn't like the resolution of 768*576 either.
I have to have a look at avisynth- can it open mpegs?
(I once tried to use avisynth with any success, no program liked a input)

[Dragonsf]

Avisynth doesn't work with the CCE 2.62 version but with 2.66 (Trial).
Strange!

[DJRumpy]

When I try to open the frameserver file directly from VDup, I'm getting a ... is invalid.I can open any mpeg file, but CCE doesn't like the resolution of 768*576 either.

DragonSF, you cannot open the VirtualDub frameserver file in CCE (they tell me the newest versions will though). You must open the frameserver file from VirtualDub, with VFAPI. The file that VFAPI creates is the one that you open in CCE.

VirtualDub -> VFAPI -> CCE

You seem a little confused on that part, but you'll get it. Save frameserve file in VDub. Open Frameserve file from VDub in VFAPI, and create psuedo AVI. Open psuedo AVI file from VFAPI in CCE.

Avisynth doesn't work with the CCE 2.62 version but with 2.66 (Trial).
Strange!

It should would with both of those versions. Did you get a specific error? AVISynth will open MPEG's via DVD2AVI project file (Open the MPEG in DVD2AVI, and save it as a Project File..reference that .D2V file with your AVISynth script. You must use the
LoadPlugin("mpeg2dec.dll")
command to enable AVISynth to read .D2V files. Your script would look like this:

LoadPlugin("c:\myplugins\mpeg2dec.dll")
Mpeg2Source("c:\mydvd2avifiles\dvd2avi.d2v")

Of course you would need to modify the path for both the .D2V file and the DLL referenced above. Also, be aware that V1.76 (not v1.77) of DVD2AVI is the version you need to use with V2.0 of AVISynth. If you use v1.77, you'll get an mpeg error when attempting to access the D2V file.

You can get version 1.76 of DVD2AVI from the www.doom9.org website if the right version isn't found here in the TOOLS section.

[Dragonsf]

You're quite right about confusing matters.But - as you wrote- I'm getting closer.

My last experiences:

1. Vfapi doesn't like to to vdr files (invalid file type).But CCE can open VFapi files (if I load a mpeg directly to vfapi), but tells me about invalid framesize 768x568 instead of 720x576.
2. I can open frameserved files with DVD2AVI thru AviSynth with any avi program (Mediaplayer/VDub/Tmpgenc/CCE 2.66/GoCCE), but not with CCE 2.62.Always: no valid avi file.

As I'm going to like avisynth more and more (the better I know it), I'd really would like to get this working.IMHO, CCE 2.62 doesnt like the avs extension, but I may be wrong.Any further ideas?

[DJRumpy]

I never tried version 2.62 of AVISynth. 2.50 was too funky. I had a version of 2.64 that wouldn't do multipass (bad patch). I finally settled on a working version of 2.64, and later, onto 2.66. Both of which are stable.

I would suggest you stick with version 2.0 of AVISynth, until 2.5 gets out of beta. If your converting MPEG, I would suggest you use DVD2AVI (v1.76), MPEG2DEC, AVISynth, and CCE. Can you get a different (newer) version of CCE? It's unlikely that the .AVS extension has anything to do with it, as versions before worked, and versions after. It could simply be the patch that was applied. I would work on getting at least version 2.64 or higher. You can purchase the basic package for something like $50.00 US. Definately a sweet deal.

[Dragonsf]

You mean CCE 2.62 (not AviSynth which is 2.0 or 2.5 beta), don't you?
Yes, I have more luck with CCE 2.66, which works as expected.The longer I'm looking at avisynth, the more I get the hang on it.I have the one or other idea, how I really could improve my bad frame filter.Just converting it to avsynth plugin and duplicated the last good frame thus replacing the bad one.
And it's really much faster (than VDub+vfapi).
Thanx for the advice in any case!

[DJRumpy]

lol..yes, I meant CCE at the top of the post. Morning here, and not enough coffee yet.