View Full Version : New versions posted for all PC and Mac CineForm tools


David Newman
June 12th, 2009, 07:47 PM
Read all the details here:
Cineform Tech Blog Blog Archive CineForm Product Updates (http://techblog.cineform.com/?p=548)

More Speed, more quality, more features and bug fixes. The usual stuff worth getting.

Robert Young
June 13th, 2009, 02:10 AM
Shazam!!
The new PHD v 4.0.5 has fixed some big problems for me.
CS4 CFHD video playback is now smooth & normal looking (as in CS3/PHD3)
Plus I was getting a severe audio glitch from EX1 converted footage that is now gone.
Is that a light at the end of the tunnel that I'm seeing????
I think I can actually start editing with this rig now.
Congratulations to you and your team, David & Jay.
Ahaaaa... nothing like the bleeding edge.

Steve Henry
June 13th, 2009, 03:22 AM
How come the last two updates of Neoscene MAC say version 1.0.5.9 in About in my system? I installed the 1.0.6.11 tonight from your site and it was still 1.0.5.9. Thanks.

Stephen Armour
June 13th, 2009, 08:54 AM
...Ahaaaa... nothing like the bleeding edge.

Robert, we need hero kinds! Keep up your good medical work, it looks like the patient (pun) will walk again...

(okay, you inspired me...I'll download it too...)

Andy Urtusuastegui
June 13th, 2009, 01:46 PM
Yep, 4.05 has fixed the last few bugs I needed to start using ver 4! Cineform AVI export no longer deinterlaces, playback is good in CS4 etc.

So after owning Premiere CS4 for over 6 months, I can ditch CS3 and fully edit in CS4.

I bought my NeoHD upgrade last night!

Good going David, Tim, Jake and the rest of the team. Keep up the good work.

Ray Parkes
June 13th, 2009, 04:51 PM
412 still doesn't install filters and transitions on either of my sytems.

Ray Parkes
June 13th, 2009, 05:43 PM
412 still doesn't install filters and transitions on either of my sytems.

The filters are there they are just in the wrong place. They install into Adobe/Common/CS4 but for some reason they only work when in the MediaCore folder inside CS4.

David Newman
June 13th, 2009, 07:55 PM
Where are ALL your Premiere PRo folders? Exact paths please.

Robert Young
June 13th, 2009, 10:46 PM
Hmmm... My CF 32 bit filters & transitions show up in Pro CS4, and are usable, tho they give a red render line.
However, I can't find any "Mediacore" folder under Program Files (x86). Adobe> PProCS4, or Common Files> Adobe. I remember there was a Mediacore folder on my old CS3 system
Now my CF filter/transition files are installed in Program Files (x86)> Adobe> PProCS4> Plug ins> en_US.
Is this as it should be, or am I missing something??

Gil Reitsma
June 13th, 2009, 11:14 PM
Hi Guys

I want to try using CS4, but the video transitions don't show on the list. I have been using CS3.

How do I get them to appear?

Thanks

Gil

Gary Brun
June 14th, 2009, 02:33 AM
For some reason mine were installed into C:\Program Files (x86)\Adobe\Adobe Premiere Pro CS4\Plug-ins/en_GB/cineform.
Ive never seen the GB directory before.
Anyway I moved the the cineform directory to en_US and everything worked for me.

Roger Averdahl
June 14th, 2009, 07:22 AM
More Speed, more quality, more features and bug fixes. The usual stuff worth getting.
I did downloaded a trial of Neo Scene and noticed that the audio drops here and there and noticed that if i render out the audio to a new .wav file everything is ok in that file. Then i noticed that the decoding of CF files seems to be really bad optimized. On my dual Intel Xeon E5450's (eight cores) machine all cores peg at around 90% - 97% while playing back the Timeline. It seems that the audio drops is there because it takes to much raw power to decode the files. See attached image.

So, should playing back the Timeline in Premiere Pro CS4.1 make all cores to peg at around 88% - 97% when playing back CF files?

Source footage CineForm AVI File, 1080i, High Quality, I-Frames Only, 25fps, UFF.

I use:
Premiere Pro CS4.1
NeoScene-1.3.2.117
Windows Vista Ultimate 64-bit
16GB RAM
2 x Intel Xeon E5450 (3.0GHz)

David Newman
June 14th, 2009, 10:04 AM
For some reason mine were installed into C:\Program Files (x86)\Adobe\Adobe Premiere Pro CS4\Plug-ins/en_GB/cineform.
Ive never seen the GB directory before.
Anyway I moved the the cineform directory to en_US and everything worked for me.

Well that sucks. Adobe is so messed up. All the non-English users said it didn't install in the last few builds, so we read the default language path and install there -- the fixes Japanese and Italian users, etc, but breaks british english. I give up (not totally), the Adobe registry is complete trash.

David Newman
June 14th, 2009, 10:26 AM
I did downloaded a trial of Neo Scene and noticed that the audio drops here and there and noticed that if i render out the audio to a new .wav file everything is ok in that file. Then i noticed that the decoding of CF files seems to be really bad optimized. On my dual Intel Xeon E5450's (eight cores) machine all cores peg at around 90% - 97% while playing back the Timeline. It seems that the audio drops is there because it takes to much raw power to decode the files. See attached image.

So, should playing back the Timeline in Premiere Pro CS4.1 make all cores to peg at around 88% - 97% when playing back CF files?

Source footage CineForm AVI File, 1080i, High Quality, I-Frames Only, 25fps, UFF.

I use:
Premiere Pro CS4.1
NeoScene-1.3.2.117
Windows Vista Ultimate 64-bit
16GB RAM
2 x Intel Xeon E5450 (3.0GHz)

Well that is weird, as Adobe rarely lets us get 50% of the CPU. Using all cores is a good sign of optimization, as it means well threaded, however playback shouldn't require that. Please file a trouble ticket, yet's see if support can work that one out.

Roger Averdahl
June 14th, 2009, 10:56 AM
...Using all cores is a good sign of optimization, as it means well threaded, however playback shouldn't require that.
Correct, thats how i should have phrased it. :)

I'll file TT tomorrow.

Andy Urtusuastegui
June 14th, 2009, 12:14 PM
Roger, similar % of usage on my machine also. I have Vista x64 SP2, Quad Core 2.83ghz.
CS4 4.1

I am getting in 92% range when viewing in high quality playback and 75% range if previewed in Draft mode

Roger Averdahl
June 14th, 2009, 12:32 PM
Roger, similar % of usage on my machine also. I have Vista x64 SP2, Quad Core 2.83ghz.
CS4 4.1

I am getting in 92% range when viewing in high quality playback and 75% range if previewed in Draft mode
O.k, then i am not alone with this issue. I see the same issue on my old laptop as well.

I updated the graphic card driver and that helped a bit, but not much. It is ImporterProcessServer.exe that uses all that power when i playback the footage. This Process belongs to Pr CS4.

Ray Parkes
June 14th, 2009, 04:42 PM
Where are ALL your Premiere PRo folders? Exact paths please.

CS4 was a standard install on a clean version of Vista x64 to the Program Files (x86) on the C drive.

full file path Adobe/Common/Plug-ins/CS4

Ray Parkes
June 14th, 2009, 05:26 PM
CS4 was a standard install on a clean version of Vista x64 to the Program Files (x86) on the C drive.

full file path Adobe/Common/Plug-ins/CS4
I am somewhat remote on a satelite link and keep loosing your server. I had not finished this responce when this last happened.

The full Premier path is Vista/Program Files (x86)/Adobe/Adobe Premier Pro CS4

I notice that CF filters installed in Adobe Premier Pro CS4/Plug-ins/common and also put a Cineform folder into the Adobe/Common/Plug-ins/CS4.
The files all have the same date so I presume they all installed at the same time.

They work when moved down one level to Adobe/Common/Plug-ins/CS4/Mediacore

David Newman
June 14th, 2009, 05:53 PM
Is the Vista part of "Vista/Program Files (x86)/Adobe/Adobe Premier Pro CS4" really in your path. Please should the full path including the drive letter, as that path looks weird.

Ray Parkes
June 14th, 2009, 06:38 PM
Is the Vista part of "Vista/Program Files (x86)/Adobe/Adobe Premier Pro CS4" really in your path. Please should the full path including the drive letter, as that path looks weird.
Vista is the C drive that machine is dual boot and I tend to use the labels and ignore the letters. It should be:

C/Program Files (x86)/Adobe/Adobe Premier Pro CS4

Gary Brun
June 14th, 2009, 11:12 PM
I am getting ImporterProcessServer.exe crashes quite regulary and it blames the cineform dll. :-)

Roger Averdahl
June 15th, 2009, 04:15 AM
Please file a trouble ticket, yet's see if support can work that one out.
I tried, but it requires a serial number and i have a trial verison of Neo Scene.

However, playback 1920x1080 CFHD footage in Pr CS4.1 and take a look at the CPU usage and how much of that CPU usage ImporterProcessServer.exe uses. I see the same issue on any CFHD 1920x1080 Timeline and/or directly in the Source which rule out any mismatch between media and Timeline.

Dual Intel Xeon E5450, 3.0 GHz
16 GB FBDIMM RAM
ASUS Nvidia 9800 GT
Dedicated video drives with lots of space
Windows Vista Ultimate 64-bit

Stephen Armour
June 15th, 2009, 07:06 AM
Hmmm... My CF 32 bit filters & transitions show up in Pro CS4, and are usable, tho they give a red render line.
However, I can't find any "Mediacore" folder under Program Files (x86). Adobe> PProCS4, or Common Files> Adobe. I remember there was a Mediacore folder on my old CS3 system
Now my CF filter/transition files are installed in Program Files (x86)> Adobe> PProCS4> Plug ins> en_US.
Is this as it should be, or am I missing something??

Hey Islandman, how's the bleeding edge? You back to CS3 for serious work? Just wondering if the bloodpressure level in the Islands is going up again...or if your CS4 projects are actually limping forward? (come on, admit it, that CS3 workstation behind you is still doing the real work)

No, that is not snickers in the background...I really feel for you...

I guess Adobe is getting like MS with their version numbers: "anything odd is good, even is not".

Maybe CS5 will chase the 4 blues away...if there's any blood left in us. Maybe we'll get lucky and Google will come up with a cloud computing editor to take on Adobe...snick snick...

Gary Brun
June 15th, 2009, 10:11 AM
At the moment I feel like Adobe has their head in the clouds and I have a fully fledged "cloud editor".

Adam Gold
June 15th, 2009, 11:19 AM
I guess Adobe is getting like MS with their version numbers: "anything odd is good, even is not". ...
I still remember all the screaming about how crappy CS3 was compared to PPro2. So a bit of revisionist history here, I think...

Robert Young
June 15th, 2009, 12:00 PM
Hey Islandman, how's the bleeding edge? You back to CS3 for serious work? Just wondering if the bloodpressure level in the Islands is going up again...or if your CS4 projects are actually limping forward?

Stephen:
I am actually moving along rather smartly on a 30 min program (200-300 clips in the bins) using PHD4/CS4/Firstlight. It's all running pretty smooth. The power of i7/ Vista 64/ Big RAM is very impressive and I do like PPro CS4. So far, no lock ups, crashes, etc. Occasional minor previewing problems due to lack of CF RT playback, but no big deal so far. I'm encouraged!!
And...duh...I did finally find my Mediacore folder- everything seems to have installed in the right folders.
I'm finding Firstlight to be both terrific and convenient as a basic CC/Clip Tweaking device.
Bottom line: right this minute, CF/CS4 seems to be working better than CF/CS3 does on the old XP/Quad system.
We may finally be coming down the home stretch on all of this.

Stephen Armour
June 15th, 2009, 05:36 PM
Well, smack my mouth! That's the best news I've heard all day! And yes, I confess, now that I remember back Adam...CS3 was crap city in the beginning. Maybe there is hope for CS4 after all?

I'll have to turn my chair around and go back to bleeding with CS4 on another workstation for a while, and see if you guys are telling me the truth...ha!

I sure hope so, we've got lots of work ahead and we need all the POWER we can get.

Keep bleeding! Keep bleeding! We need the fixes and you guys have got my attention now...

Simon Zimmer
June 15th, 2009, 05:40 PM
Interesting because I always liked CS3. I started out with PP2 also. CS4 is the FIRST TIME that Adobe reminded me of Microsoft which is not good.

But looks like Cineform is fixing all the Adobe errors which is great to hear.

Simon

Dmitry Yun
June 15th, 2009, 08:02 PM
Booya...fixed :)

Lauri Kettunen
June 16th, 2009, 08:58 AM
Does anybody get the Cineform presets with this latest version of Prospect 4K when opening a new project in Premiere Pro CS 4.1 under Windows XP64?

David Newman
June 16th, 2009, 09:14 AM
There are no presets yet in CS4, we will put that in the update log when they are ready.

Lauri Kettunen
June 16th, 2009, 09:48 AM
There are no presets yet in CS4, we will put that in the update log when they are ready.

David, Thanks for confirming this. Was not able to find this information anywhere. Though, probably it is somewhere.

Andy Urtusuastegui
June 16th, 2009, 03:33 PM
Roger, you can infact submit a but report with a trial version. Just put TRIAL in the serial number field.

Roger Averdahl
June 17th, 2009, 09:37 AM
Roger, you can infact submit a but report with a trial version. Just put TRIAL in the serial number field.
O.k, good to know! :)

I did however unistall the trial yesterday since it is impossible to try it properly. No RT playback, it uses *more* CPU power to playback the files than it takes to render them out from Adobe Media Encoder (it should be the opposite), 8-bit CFHD files makes Pr CS4.1 freeze everytime i import or try to use one...