-
Another Media Performance Warning…
I recently bought a new high speed RAID array from OWC, with 7200 RPM drives. I used Media Manager to migrate my projects to it. Now I’m getting a message I’ve never got before. Anyone seen this, and know whether it’s worth worrying about? Given that I did use media manager to get the projects to the new drive in the first place, not sure why it would give me this warning. The drives are plenty fast. The media all plays just fine. I did review the other Media Performance Warning posts from earlier, but they didn’t totally match up.
Alf
-
8 Replies
-
I have seen it Alf, but I ignored it.
If I’m correct, it was flashing that sign at files captured in a previous version of FCP, a previous version of the OS, or a previous version of QT. Any of those sound logical?
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comPOST-PRODUCTION WITHOUT THE USUAL INSANITY ™
A forum host of Creative COW’s Business & Marketing and Apple Final Cut Pro forums. Formerly host of the Apple Final Cut Basics, Indie Film & Documentary, and Film History & Appreciations forums.
-
Hi Alf,
Same than David, I always have been ignoring those messages and never had any issue.
I think that “Media not optimized for FC” warning is related with the issues explained on this article:
https://library.creativecow.net/articles/lyon_matt/
rafael -
Thanks for the thoughts, I’ll check out the article later in the evening…Only thing I can think of is that I added some stills I needed recently, but as you can see from the error message, it was a huge pile of files that had never given me problems in 10 months of editing, rediting etc. Only thread here is that I used MM to migrate them all to the external OWC drive. Must be something that FCP didn’t like. Maybe I’ll try posting on Apple’s support site and see what I get, or even send an email to Larry Jordan, who doesn’t seem to frequent the boards but has just about as encyclopedic a background as anyone.
Bottom line, like you both said, there was no problem with anything, so I’m ignoring it until I can’t. It may have something to do with shifting RT settings to do multiclip in another FCP project. It shouldn’t follow to another open project sequence, but who knows. At least by posting it with the screen shot, I hope to save someone else a bit of persperation when they come looking for an answer in the future. New drives, new problems…
I do wish there was an easy way to migrate everything FCP from one drive to another without going project by project. Just repoint scratch drives etc and let them rebuild over night… Or is there some tool to do that? I’ll re-ask in another post.
Alf
-
Thanks for linking to my article, Rafael, but I don’t remember seeing that particular warning when I was troubleshooting those particular issues.
I have definitely experienced the “media not optimized” warning in other situations though. But like David, I just ignored it. Last time I saw it was with some media I converted using MPEG Streamclip. I’m really not sure what causes it … my WAG was something to do with the order the bytes are written on disk?
Matt Lyon
Editor
Toronto -
[Matt Lyon] ” have definitely experienced the “media not optimized” warning in other situations though. But like David, I just ignored it. Last time I saw it was with some media I converted using MPEG Streamclip. I’m really not sure what causes it … my WAG was something to do with the order the bytes are written on disk?”
Hi Matt,
Perhaps I’ve been misleaded relating both issues by the fact that In the screen grab that Alf posted, the files seems to be all Audio files (.mov).
Your article has been the only interesting research on a FC bug in a long time, and cleared an issue that was causing many troubles.
The kind of issues that seems that Apple seems prefer to ignore.
Cheers,
rafael -
[Rafael Amador] “The kind of issues that seems that Apple seems prefer to ignore.”
I don’t know what goes on inside Apple HQ, but it seems to me like this is really just a matter of economics. At FCP’s price point, Apple makes money by selling upgrades and new versions of the software. There are no mega-buck support contracts to rely on. Selling new software requires new features. So that’s where the programming resources get assigned.
I’m speculating here, but It could also be that this issue is so ingrained in the current architecture of the product, that fixing it would require more effort then Apple judges it to be worth.
I’m hoping the 64 bit version of FCP, when it materializes, tackles the fundamental issues that create these problems in the first place.
Matt Lyon
Editor
Toronto -
[Matt Lyon] ” Selling new software requires new features.”
You are right. and the only thing we’ve got with FC 7, was the new Prores flavors. BTW, the most interesting one (444) not fully developed and functional.
Waiting for “The Awesome” one 🙂
rafael -
Raphael, the clips that are MOV aren’t audio, their video. whenever I convert a clip in L&T I end up with MOV files. That’s how they are stored. I do shoot with both a 7D and a Panny HMC150. The 7D creates “native” mov files, but they are not drop in compatable with FCP. I run them through depressor first.
When I go to my “capture scratch” files, all my video and audio clips are mov, not just audio.
Alf
Reply to this Discussion! Login or Sign Up