Forum Replies Created
-
Last night I did a quick stress test with FCP 7 encoded XDCAM HD and working with that format on a mac version of PProCS5. Although the XDCAM mov files work pretty well in FCP on a MBP laptop, using the same clips in PPro has very poor performance. I converted some of the media to ProRes HQ and PPro ate it up. Multicam editing like a breeze.
The bitrate and HDD is not the problem, it’s the XDCAM format that FCP makes that is not decompressing in PPro clean enough to get performance. I would say, as this is not an open codec, whereas ProRes is available outside of FCP for decoding, the crunching on the CPU is enormous.
PPro was much better at the multiclip editing using thr ProRes media versions than FCP 7 and the XDCAM mov files as it kept crashing in multiclip editing.
The difference when using the “open” codec was amazing! Boo to apple for being so “closed”. At least sell the codecs via iTunes.
– Jon
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Short answer. No.
Keep in mind HDD should maintain 20% free space to run efficiently. 80gig from 1000gig is not healthy.
What system ate you using, PPro version, HDD setup, project and media and export properties. Did u change the preset?
– Jon
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Great to hear. Sometimes it’s a small oversight that needs correcting.
That time difference is pretty huge. Can you post your system and project specs so others can compare in building a similar machine.
Cheers. Jon
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Run the updates. Help>updates
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
The GTX470 is only supported from the 5,0,2 update,
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Take a look under the opacity property for the clip. You can use screen cmpositing. I think that’s what you are after. 😉
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Please do use the original recording data, access it via the Media Browser Panel not traditional import.
Be sure to have it on a drive that can play back at high speeds for the multicam, and if need be lessen the resolution in the source monitor as I think that affects the Multicam Window.
– Jon Barrie
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Hi Charles,
There is no “secret” but the setting for importing image sequences is in the preferences. It will most likely be set to 29.97fps by default as it is a US based company and that is the frame rate their.
CS5 is a little more intelligent in that is knows from which country you set at installation which settings to work with as default.
This may not be the case for importing image sequences, but it is on their radar to get more intuitive workflows for PAL based countries, it’s just got to rise in the ranks of importance.
Hope the Preferences gets you importing properly again. Let us know if it works out. Others could find it useful to know a solution.
If you have imported many image sequences you can select them all collectively and make the frame rate change to one and all with adopt the change. It is a little faster than one by one 🙂
– Jon Barrie
ANZ Adobe Ambasssador
Freelance Video Editor
Youtube Tutorialist/EducatorJon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Jon Barrie
November 17, 2010 at 1:20 am in reply to: Strange Playback problem with a particular sequenceStart a new Project and import the troubled one.
You may need to also clean the media cache from the Preferences. And restart PPro.
Then allow all the media indexing and conforming to take place before you start editing.
Let us know if the this works out for you as others may come across this same issue and would like to confirm the solution.
– Jon Barrie
Adobe Ambassador
Freelance EditorJon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter -
Sounds like it could be a graphics card driver issue.
Did it work before and recently stopped or has it always had this issue?
What kind of video card and driver version are you working with?
– Jon
Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter