Ryan Patch
Forum Replies Created
-
I am hitting this issue today HARD CORE. Making editing impossible.
Anyone have any ideas?
-
Preferences> Media, to be specific.
You should be able to delete media files without damaging your system, however. That is a strange occurrance.
-
Same problem here. It appears that they simply aren’t cached, which is frustrating.
-
They are not defaulted to mapped, but are mappable… I have them mapped to the 1-0 keys like AVID too! So good…
Search for “toggle”.
-
Yes, all very true.
One workflow that hits both strengths would be to edit nativity with Premiere, and then only transcode the material you need to correct. You could do this either by using the project manager to consolidate media you need, or use the “Send to speedgrade” command do get DPXs made. I was told that you can actually “Send to speedgrade”, let Adobe do all of the rendering for you, then from speedgrade, save an XML and open that in resolve. Haven’t gotten this to work yet, though.
Ryan
-
If the H.264 plays back well on your computer, there is NO REASON to transcode to another format. Working with the original media is always best. You will not “gain” any color depth or anything by transcoding to a 10-bit format or anything – your colors are limited to what you captured. Adobe will work with them in a high-bit-depth, but transcoding will only add time and disk space.
-
CS6 is more stable than FCP 7 for long-form stuff (assuming you have a GPU-enabled computer). Not as stable as Avid.
I would definitely try it!
-
Agreed, this is rediculious. The limitations of XML output with merged clips mean that if you were to edit a feature film with dual system sound that you wanted to color on ANY platform other than Speedgrade… you are up a creek.
Not really a professional post-production workflow mindset.
Adobe hasn’t seemed to break out of a single-seat, single-user, start-to-finish mindset yet. I hope they realize that’s what killed FCX and will be working to resolve it soon.
-
Never got to the bottom of this. Still an issue. I find that it happens more when you have more tracks going on, or more plugins activated, but can still happen with just one or two simple files playing. Dealing with this all over the place today.
I am usually editing some sort of H.264 footage as well. Don’t have enough examples of non h.264 stuff to know if that’s the problem.
Definitely something that needs a fix.
-
Try deleting your .cfa files for the media in question, and then don’t mess with the project until they are done re-conforming.