wtf? cce is slow like tmpeng too?

[Aznboi_nz]

I use to use tmpgenc for encoding svcd's mpeg2 and I found it really slow, so today I decided to use cce and see if it was faster since everyone say it is, anyways i started encoding and the speed is 0.50.

I assume this is fps, why the heck is it so slow?

Im on winxp, p3 733, 356 ram

[Aznboi_nz]

anyone? im using pretty much the exact same hardware as the one used in the comparison section and he is able to manage and get 7fps speed where as i can only get 0.5

[adam]

That is not fps that is % real time. 1=real time so you are going half real time which means that 1 hr of video would take 2 hrs to encode. I'm not sure how fast you should be running on that hardware, but this may be about right. This should still be significantly faster than TMPGenc on your system.

I run an AMD 1.333 and when making SVCDS (480x480) I go about 1.8, which is almost double time.

[bunyip]

0.50 would be about right for a P3-733.
On an Athlon 1100, without filtering, using an uncompressed source you can get upto 0.90 (1hr 10min for 1hr video).
However if the source is compressed and you need to apply filters this rate can drop as low as 0.30 (3hr 20min for 1hr vid).

[Aznboi_nz]

im pretty new to using cce, is there a guide out there that shows u how to use avisynth with cce? also ur time is that constant or variable bitrate?

Also can someone tell me the difference between 1 pass vbr and multi-pass vbr and the difference quality wise?

[Aznboi_nz]

also when doing 1 pass vbr I am unable to choose an average bitrate, how am I suppose to control the outcome file size?

[antjmon03]

Aznboi_nz, from all of my experiences cce has never been slower than tmpgenc (or even close). First of all make sure that you dont have alot of background programs running b/c cce will hog alot of your resources. I have a question, what are encoding the in cce itself? Did you drag and drop the orginal? Are you frameserving? Are you using avisynth? I would recommend using avisynth (unless your source is already in the resolution that you want and the way you want it then just do the file itself). Fitcd is a program that will help in writing those tedious scripts in avisynth.


To answer your other questions, in 1pass vbr the only way to control your output quality and size is to use whats called the quantization factor (that Q digit before your settings) and of course the bitrates themselves. The lower the number, the higher the quality and output size. Vice Versa. To be honest with you, it would be a waste of cce's power to not use its multipassing capabilities. The difference between 1pass and 2pass is just as the name implies. W/one pass cce goes through the movie once and approximates where to use high/low bitrates. This is successful in creating a vbr file, but it is VERY rough around the edges. With each pass the program will go back over the source file to compare that respective passes result with the one(s) before it, thus "ironing out the wrinkles". It may decide on the 3rd pass that a certain scene would look best if more bitrate were allocated to it. It may also conclude that another scene wouldnt lose any quality if the bitrate was taken down some. To find a guide on cce on here look here https://www.videohelp.com/newbie and scroll down to CCE 2.5.

Here are some elementary settings that you can use to play around with, by all means tweak them to your own liking.

Video Files (Checked) ES
Video Information (Required to be checked for multipass)
Audio UNcheck (encode audio with another program)

Multipass VBR (3Passes) MPEG-2 Avg. 1600, Min 300, Max 2100
Click Quality Settings, Image Priority (7), UNcheck anti-noise

The rest you can just play with. Keep in mind that the more passes you have the longer it will take. But in the long run it is WELL worth an extra hour or so.

[Aznboi_nz]

ok thanks alot guys, using avisynth did speed it up alot, speed went up to 0.668. It took 2hours and 30mins for the encoding but then took another 8 hours for the "transcoding" which is still faster than tmpgenc. Wondering what time it takes for guys? (total time)

[digitalmaster]

That is strange. Using AviSynth should slow it way down. Frameserving like that should always slow down an encoding program.

[digitalmaster]

Also, the latest 2.67 demo of CCE, shows they have even increased the speed more. I was able to do a 1 hour 40 minute movie in 45 minutes on a 2.4 Ghz PC. Amazing. I guess that is why it costs 2,000 dollars.

[Aznboi_nz]

^^ really? I read heaps of threads and it says frameserving with avisynth is faster than virtualdub

[adam]

Yes frameserving with avisynth can be much faster than with virtual dub because it supports YUV content, which means you avoid the conversion to RGB that you have to do with Vdub. On my machine this speeds things up by about %30.

I think maybe he meant its slower as opposed to not frameserving at all, but unless you dealing with dv or avi than this is not possible, and actually avisynth hardly adds any additional encoding time at all.