View Full Version : CS5.5 Compatable??


Pages : 1 [2]

David Newman
June 27th, 2011, 05:10 PM
Did you uninstall first? If you did, you should not be seeing a performance hit, and should contact support for help.

Jay West
June 27th, 2011, 07:06 PM
I'm seeing some performance issues with CS5.5 but, in my case, they do not seem to be caused by Cineform.

I'm seeing a puzzling mix of some things seemingly running faster than before while others -- particularly timeline playback in multi-cam edits --- exhibit unrpredictable hiccups and pauses even with timeline playback of MPE-enabled transitions. The annoying thing is that sometimes there are pauses and halts and sometimes MPE transitions hiccup and judder as they play, and sometimes these problems disappear.

I note that I installed the latest Neo beta (build 327, I think.) That certainly fixed the problem of audio reconforming but did not fix the intermittent glitches and halts with timeline playback from multi-cam timelines.

The reason I think this is not a Cineform problem is I got the same issues when testing in a new project using the base AVCHD files rather than using the Cineform conversions. In my case, I suspect the issue is either my video card (I'm using an old GTX260 with DDR 3 RAM which may be too slow for mutlicamming in CS 5.5 on my system) or it might be an interaction with the CS5.5 drivers for the Matrox MXO2 Mini (the Matrox info indcates that some users may experience problems like these.) Maybe a combination of both.

As Ben noted in his case, I am considering switching back, for the time being, to PPro CS5.03 and also going back to the previous drivers for the Matrox Mini. When I can get time to do this --- which is when I get the pending couple of 5.5 projects completed --- I'll report back if if the latest Neo Beta has any untoward effects in CS5 on my system. (Doubt that it will, but it is worth checking out.)

Which leads me to ask Ben if he swtiched back to CS5.03 and is having performance issues with b.327 or if the problem is confined to PPro CS 5.5 on his system?

Julian Frost
June 30th, 2011, 05:47 PM
Reference my Green Screen multi-camera window when using CF AVI and Premier Pro CS 5.5, I just got notified by an Adobe employee (on their forums), that Adobe is working with Cineform to find a solution to this problem.

Hopefully a fix will be coming soon.

Ben Winter
July 1st, 2011, 12:43 AM
Which leads me to ask Ben if he swtiched back to CS5.03 and is having performance issues with b.327 or if the problem is confined to PPro CS 5.5 on his system?

It is purely a Cineform issue for me, CS5.0.4 and CS5.5 display virtually the same performance, it's the change from Neo4K to the new Neo that reduces performance for me. I haven't tried a full uninstall before a new install yet as David suggested, as I need to finish up my current projects before I go messing about risking a change from a configuration that works.

Jay West
July 18th, 2011, 02:23 PM
The constant re-conforming bug has turned again. It went away for a couple of weeks after I installed the recent beta. It has now turned up again to periodically stop playback in CS 5.5 until it finishes reconforming and re-re-conconforming and re-re-re-conforming. I have had to switch off "write xmp id" again.

Julian Frost
August 2nd, 2011, 09:44 AM
Cineform Folks...

Any updates on these issues?

Zac Lam, over on the Adobe forums, told me over a month ago, that the multi-camera "green window" problem was not an Adobe issue, but Adobe and Cineform were actively working together on a solution.

There have been no updates to the Adobe software in quite some time, and no updates to Neo either.

Julian Frost
August 21st, 2011, 11:42 AM
I'm pleased to report that my multi-camera problem (the multi-cam window going green when hardware Mercury acceleration was switched on in Premier, and Cineform files were on the timeline) has been fixed in the latest beta release of Neo. Apparently, according to Adobe, the problem wasn't in their code, as initially reported by Cineform. Thanks to Cineform for addressing the issue.

I haven't checked the other issues listed in this thread.