CCE 2.5 vs 2.67

[pchan]

I would like to know what are the features available in CCE 2.67 that are not in CCE 2.5 ? Thanks.

[freelock7]

CCE 2.5 don't support .avs file.
That's the GREAT difference!

[tedkunich]

Originally posted by freelock7
CCE 2.5 don't support .avs file.
That's the GREAT difference!

@freelock7
Know your FACTS before you speak! CCE 2.5 will most certainly work with Avisynth. There are some issues dealing with audio (with viable workarounds), but that is nothing to base a claim like yours.

@pchan
I'm not sure if there are any significant "feature" differences between the two - I do know that the trial version of 2.67 no longer supports .ecl files, but there is a wook around for that (search for eclcce.exe) There are also some reported speed differences between the versions depending on your processor. Read the guides (there are version for 2.5 and 2.6x) and they will cover the differences in sufficient detail.



T

[hendrix]

2.67 has more video modes, also has 3:2 pulldown detection (although using pulldown.exe is better), you can specify absolute frames or smpte frames when inserting Iframes...there may be more that i missed and it supports avisynth as well as 2.50

[Fr4nz]

CCE 2.50 works well with avs files. And works well with the audio workaround too.

The main difference between 2.50 and 2.6x is that the 2.50 is optimized for Athlons while 2.6x are faster on Pentium 4.

[tedkunich]

Originally posted by Fr4nz
CCE 2.50 works well with avs files. And works well with the audio workaround too.

The main difference between 2.50 and 2.6x is that the 2.50 is optimized for Athlons while 2.6x are faster on Pentium 4.

Funny, than on my 3200 AthlonXP, I get a 1.7 encode speed for a full D1 resolution with version 2.67, while with version 2.5 I get less than 1.5. same settings, same source.....

T

[freelock7]

CCE2.5 don't support Avs file

It means that CEE 2.5 don't recognize directly avs file but it is right that CCE 2.5 can be used with Avisynth and Avs file through the <READAVS> patch in the VFAPI directory.
But CCE2.67 is really faster than 2.5 (more buggy).

[adam]

Readavs? Isn't that for loading avisynth scripts into TMPGenc? This is definitely not necessary for CCE. I don't even know what VFAPI would have to do with it. 2.5 accepts avs files fine without having to install anything else or frameserve through VFAPI.

CCE 2.5 is indeed alot faster on my Athlon setup then later versions. Its close, but I actually prefer the quality of 2.5 over later versions too. It certainly has less options and filters, but its still a viable choice. Personally, I think its still the best version of CCE available, especially if you have an Athlon chip. Talking to various people, it seems that many still use 2.5.

[br408408]

CCE 2.5 will load an avs without Readavs or any other patch for that matter...and I have used it for 3 years or more...I think I would know. I don't know where all this mis-information is comming from...this is how rumors start. Also, I doubt it was made for Athlons...probably more like P3's... although it is the fastest version for them. And lastly, to my eyes, it (2.5) give the best picture quality, and I use it on my P4 even though 2.67 runs a little faster. Hey, 2.5 runs at over 3.0 RT on my P4...that fast enough for me.


PS
I must add that I don't use CCE for the sound. Plus, CCE sound is not very good anyway, and there are so many other high quality ways to encode sound....

[freelock7]

CCE 2.5 read avs file

Strange!
I have 2.5.01 SP and it supports only .mov, .avi and .dv file!

[robot1]

Originally posted by freelock7
Strange!
I have 2.5.01 SP and it supports only .mov, .avi and .dv file! Select "All files (*.*)" and try loading .avs
It works.

[adam]

Or you can just drag and drop. There is also a patch that makes .avs one of the default file extensions.

[freelock7]

I read this thread (by RB):
"For AVISynth 2.08 and 2.5.x, create a text file in your AVISynth Plugins directory (usually the 'Plugins' directory in the AVISynth installation directory) named AddAudio.avsi, then paste the following into the file
function AddAudio(clip v1) {
v2 = Blankclip()
v1 = AudioDub(v1,v2)
return v1
Add the line
code:AddAudio
at the end of your script.


Alternatively, make sure that in the currently active CCE-SP 2.50 template (see "Template" menu item), the "Audio File" option is not checked before loading an AVS file into CCE. In that case you don't need the fake audio trick.

Well, now that you did that you can load the Script into CCE-SP 2.50 but it may still crash when you start encoding. This will happen on AMD Athlon "Thunderbird" CPUs because CCE-SP 2.50 uses SSE commands to process audio. SSE is not supported by the Thunderbird line of CPUs, that takes at least an Athlon XP. You'll have to uncheck the "Audio File" option in Encode Settings, process audio in another program and later multiplex it with the CCE encoded video file (which is recommended anyway because CCE's audio encoder is generally not considered to be top of the line)."
But still fail.
No matter. I'm using CCE2.67 and It works very well.
----------------------
AthlonXP2200
WinXPPro
Avisynth255

[br408408]

If CCE 2.67 works well, and you are happy with it, then that's all that matters. All CCE products are good encoders :)

[Matthew]

avs support only went out the window for 2.62/2.64, it's for those versions that the vfapi workaround is required. Except if I recall correctly avs support was reinstated in at least one late build of 2.64.

[pchan]

Thank you everybody from taking time and share your knowledge on CCE. I am using Premiere 6.5 and Videoserver to frameserve to CCE2.5. Since the audio is not so good for 2.5, is the sound for 2.67 better ?

[hendrix]

dont use CCE for sound, use it only for video - just use Premiere for audio