Need help from CCE expert.

[2pac]

I just started using CCE v2.50, my problem is the speed is really slow (0.29)when I encode to a 480x480 resolution from a 40 minute, 352x288 .avi. But when I encode without resizing, the speed is fast around (.500-600). I tried every frameserving method that there is, and still didn't do any good. What could be causing the speed to decrease so much?

[homerpez]

It's probably due... to the resize.

I am fairly sure any frameserve process will also slow it down (as the filters are processed before CCE sees the video).

On mine, it does slow down in frameserving, but only to about .47 or .5 rate. Even so, you can do 3 passes in this time, compared to TMPGEnc doing 2 in the same amount of time.

[2pac]

I even tried making the fake VFAPI and AVIsynth .avs method too, but it's still the same thing. I'm not even doing 3-pass either, just 2-passes.

[Truman]

It doesn't matter if you do a 2pass or 3pass encode.
It slows down, as homerpez said, due to the resize filter.
Different resize filters end in different speed. Different frameserve methods end in different speed too.
For example, if you use Vdub to resize and frameserve, "nearest neighbor" is faster than "bicubic resize".
Resizing with AVIutl or TMPG should be faster than Vdub at all.
Every use of filters will slow down the encoding process.
0.290 vs. 0.500-0.600 seems to be normal.
You may try different methods and compare speed and quality. Report your results here please.
I use always Vdub to frameserve avis to CCE. Yes, it is quite slow, but I like the VirtualDub filters and I love to work with a GUI. AVIsynth is a bit more complicated in that case.
For DVD to (S)VCD conversions I resize and frameserve with AVIsynthMMX / MPEG2DEC to CCE. Definitly the best and fastest frameserve method, if your source is MPEG-2.

[2pac]

well, I've tried every method there is... still gettin' speeds around 0.025-0.031

[Truman]

wow, you meant 0.029 instead of 0.29???
Do you use any other filters beside the resize filter?

[Vejita-sama]

First question, why are you resising the avi? 352x288 (PAL) is the standard VCD resolution. And blowing that up to 480x480 isn't going to improve the the picture quaility, it should hurt it.

What filter are you using to resize? I would try making the following avs file:

================================
AVISource("d:\capture.avi&quot
BilinearResize (480,480)
================================

Save this is notepad as xxx.avs, open the avs file in CCE and encode it, and tell us what you get. I'm recommend bilinear or bicubic because you're blowing up the picture.

[2pac]

Ok, I tried it... it didn't work at all!
The only filter I use is resizing & changing the frame rate from 12fps to 29fps. The reason why I need to resize to 480x480 is cuZ I want the SVCD format, NOT VCD. Earlier today I tried to encode without resizing, the speed was around 0.500-0.600 (pretty fast), after the encoding, I burned it on a CD, played it on my DVD player and now I see a blue CINEMA CRAFT encoder logo on the bottom of the screen. I thought I had the full version since I have the patch for it and it didn't say it was a DEMO.

[homerpez]

If you're only going for a 2-pass... and your source video appears to be crap (pocket webcam)?... why not just use TMPGEnc?

Just make yourself a project, save and run under "batch encode". Bet PATIENT.

Also, you never mentioned the system you're running? What processor speed? What RAM? I think anything with CCE (or any other encoder) depends heavily on CPU resources and speed.

Just to make you aware, though... this is a normal drop in speed... any filtering you do whatsoever, will show itself in a speed slowdown.

You'd be amazed at this effect using TMPGEnc. Try an IVTC filter during the encode process sometime! It adds about another length of the movie on my system, PER FILTER.

Patience...

[2pac]

I have a slow PC (crap), IntelCeleron 600mhz with only 64MB of RAM, LOL.

[dec0n]

When converting a DVD source to SVCD,
I got sick of the Vdub frame server really slowing CCE, so I tried converting a .tpr project file with VFAPI (after just resizing the output in TMPGEnc), and just straight importing the psuedo .avi into CCE, this was alot faster (about 6 hours faster) but obviously not as good as the Vdub resize filter.

I'm using a PAL source, has anyone else tried this, & could anyone tell me if this is a bad way of doing things?

Thanks Gusto

[Truman]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-09-13 00:24:14, 2pac wrote:
Ok, I tried it... it didn't work at all!
The only filter I use is resizing & changing the frame rate from 12fps to 29fps. The reason why I need to resize to 480x480 is cuZ I want the SVCD format, NOT VCD. Earlier today I tried to encode without resizing, the speed was around 0.500-0.600 (pretty fast), after the encoding, I burned it on a CD, played it on my DVD player and now I see a blue CINEMA CRAFT encoder logo on the bottom of the screen. I thought I had the full version since I have the patch for it and it didn't say it was a DEMO.
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>
As homerpez said, this is a normal drop in speed!
You blow up the frames and you add 17 frames / sec. Think about it. I believe you should make a VCD here. You can not expect SVCD quality with that source.

[Truman]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-09-13 01:16:24, dec0n wrote:
When converting a DVD source to SVCD,
I got sick of the Vdub frame server really slowing CCE, so I tried converting a .tpr project file with VFAPI (after just resizing the output in TMPGEnc), and just straight importing the psuedo .avi into CCE, this was alot faster (about 6 hours faster) but obviously not as good as the Vdub resize filter.

I'm using a PAL source, has anyone else tried this, & could anyone tell me if this is a bad way of doing things?

Thanks Gusto
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>
The method you mentioned is used by many people and I think, it's a good way.
Personally I prefer VirtualDub/AVIsynth's bicubic resize, but there is only a slight difference and taste is subjectiv anyway.
Especially if you use cce sp 2.62 there is no other option than this TMPG method.
ebaldino has a frameserve method using Vdub and AVIsynth, but I believe this will slow down the speed even more. Have a look at his reply.
btw, you are talking about dvd2svcd conversion. Try AVIsynth/MPEG2DEC.

<font size=-1>[ This Message was edited by: Truman on 2001-09-13 05:28:09 ]</font>

[2pac]

I guess I'll have to make xVCDs instead and up the bitrates. All of the movies that I have are all from p2p file-sharing programs. Most the movies downloaded from them are either 352x240 or 352x288 with 12fps.

[smchgait]

Hi,

i am using CCE 2.5 SP. It is very important to
have a lot of RAM. 256 MB are the minimum size.
The bigger your RAM the faster CCE will become. 2 PAC, how much
RAM does your PC have?
Resizing costs a lot of speed if you do a 4 pass.
I always
create a resized AVI file with VD (save as segmented
AVI) and frameserve the segmented AVI via AVIsynth
to CCE. On my PIII 667 (384MB RAM) I get 0.450 realtime.
It is a big difference if your AVI output is in RGB or YUV2.
YUV2 saves a lot of CPU time as RGB has to be converted to YUV2.
On my AMD 1200 (512 MB RAM)I get between 0.750 and 1.100 realtime. I am using DVD2avi 1.76 and AVISYNTH that supports YUV2 and MPEG2DEC. I get those speeds without!!!
creating a resized AVI file.
I use the following script.

LoadPlugin("c:\temp\Mpeg2dec\MPEG2DEC.DLL&quot
mpeg2source("D:\abc.d2v&quot
ResizeBicubic(480,576)

[2pac]

smchgait,

Like I posted earlier before on this topic... I have only 64 megabyte of RAM. And I have tried all kinds of frameserving methods, including segmented files, vfapi files, project files, etc.

[Truman]

According to the cce manual 128 MB RAM is required (256 recommended). SDRAM is quite cheap these days, you should consider to buy some more. Some people reported a better performance with 128MB RAM compared to 64 MB RAM.

[2pac]

Thanks for all the recommendations and replys everybody. And maybe I'll upgrade the processor too.

[smchgait]

On my PIII 667 with 128 MB RAM I got speeds of
0.067 in CCE
and heavy HD activity.
Then I uppgraded to 384 MB CL2 133 MHZ RAM and now I
am getting speeds of
0.450
with the same settings.
This says all.

[zereack]

sorry i just cant resist.

Dual 1G althlon , 1G ddr 266hmz ram , 75G 7200 ibm dma-100 HD

cce runs at 1.234 for me

<font size=-1>[ This Message was edited by: zereack on 2001-10-03 18:17:53 ]</font>

[Truman]

Yes you have a long one...
Encoding speed depends on source, avi or frameserved files, it depends on output resolution and every use of filters will also slow down the process.
So your reply is quite useless.

[Raider]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-09-13 01:16:24, dec0n wrote:
When converting a DVD source to SVCD,
I got sick of the Vdub frame server really slowing CCE, so I tried converting a .tpr project file with VFAPI (after just resizing the output in TMPGEnc), and just straight importing the psuedo .avi into CCE, this was alot faster (about 6 hours faster) but obviously not as good as the Vdub resize filter.

I'm using a PAL source, has anyone else tried this, & could anyone tell me if this is a bad way of doing things?

Thanks Gusto
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>


does this work with cce sp2.5?
as vdub takes ages when frameserving
I loaded the dv2 file and wav files into tmpeng, then saved as .tpr file, converted with vfapi, and then tried to load into cce, and got an error saying unable to open file, file is corrupt or unrecognised format.
thanks for any help
Raider.

[Raider]

ok, sorted it, hadn't uninstalled vdub handler.......doh!!.

Now running converted .tpr files ok in CCE, but getting speeds of 0.243. Is this about right for a PIII 733HZ, 256 RAM, with 20gb. Encoding cbr at the moment.
Seems slow??
Raider

[Truman]

No, it isn't too slow. If I use this way, output resolution 480x576, resize 16:9->4:3, I get speed of 0.43 with an Athlon 1.2G.

[Raider]

Thanks Truman,
Nice to be reassured. First time I've used this method with 480x576, and the quality is excellent with cce.Resulting file was to big though (cbr@ 2500) gave a 1.88gb mpa.So I'll have to play a bit.
Would like to have a go with avisynth, but when I load a .avs I get a file duration of only 10 secs. and we all know what that means.....

thanks again
Raider.

[Truman]

If you like smaller filesizes with similiar quality, use the VBR multipass encode mode. Which error message did you got from Avisynth? Either Avisynth isn't installed properly or the script is wrong.