Currently Being ModeratedFeb 17, 2013 5:22 PM (in response to Michael Grenadier)
Yes, I am putting out support requests. The BMD website shows no trace of any driver downloads anywhere like they used to. My problem seems to have no cause. I used to use BM audio. Then I stopped. Then I started again. And the trouble started.
There is one thing. Mountain Lion is new. I'm very leery of it. I called Apple about Compressor. It was crashing after installing ML.. Apple just told me that FCS is untested with Mountain Lion. Probably will remain so it seems. They do not care about FCS and ML and wll simply tell you there's nothing they can do. But Pro Maintenance Tools fixed it. Thanks to folks in this group.
Just think how different life would be if they weren't always cramming the next best thing down our throat with such a vengeance. I've been using FCP 7 just over 2 years.
Currently Being ModeratedFeb 18, 2013 8:00 AM (in response to Chris Howe)
Did you do a clean install of Mountain Lion and the fcp suite? Really, it's the only way to go. Unfortunately OS upgrades can break things. I gotta admit that I resisted this for years. Jerry Hoffman always said to a complete clean install. After many years successfully editing without doing this, my system finally completely melted down. If you depend on your system to make your livelihood, it's really worth while.
Here's a user tip about best practices for upgrading OS and apps
Currently Being ModeratedFeb 18, 2013 9:58 AM (in response to Michael Grenadier)
No I did not do clean install. It seems a bit scary, but I will give serious consideration. You'd have to reinstall FCS? Couldn't just copy things back? I guess not. Thanks.
Currently Being ModeratedFeb 19, 2013 2:08 PM (in response to Michael Grenadier)
I've got other bugs since Mountain Lion. The following programs either crash, or start after a period of time, except after a reboot, when they work.
Compressor 3.5.3, Disk Utility, Squeeze 8.5 (delayed start). Toast 11. I guess you think the clean install may help?
Currently Being ModeratedFeb 19, 2013 4:52 PM (in response to Chris Howe)
You have to realize you are two (2) OSX generations past the final cut suite's last upgrade ( which was with 10.6.8).
Stuff breaks with the misfit between OS and app. The further you get from the sweet spot, the more unreliable things become.
fwiw, I've kept everything with 10.6.8 and it is a rock solid system. I dread the day when I'll be forced into a current MacPro (if they even make them when I need one ...)
Currently Being ModeratedFeb 19, 2013 4:59 PM (in response to Chris Howe)
as studio x says "maybe." Starting with a clean install is a good place to start, but who the heck knows. but it can't hurt.
I'm also on 10.6.8 on my mac pro and my macbookpro.
Currently Being ModeratedFeb 19, 2013 5:05 PM (in response to Studio X)
For me, Mountain Lion was foisted upon me as Apple and I wrestled with an iphone sync problem in January. I didn't feel good about from the start, and for whatever reason, I think I have more software bugs than anyone. The problem with Toast 11 crashing is new. I'm in contact w/ support. I almost feel like saying "maybe you can't fix it, nothing else is working right". Well actually many things do work, thank God.
Apple tried to get Disk Utility to work three times. The second two times it worked, but only for so long. Compressor 3.5.3 they won't deal with. Squeeze 8.5 is a four minute program start delay and they can't get it resolved. I've gotten used to that one. And as I say Toast 11 updated for Mountain Lion is new.
Currently Being ModeratedFeb 22, 2013 8:50 AM (in response to Studio X)
I found myself in a position yesterday where it was necessary to a regular reinstall. Knock wood, but it seems to have fixed the dropped frames problem. It also seems to have fixed the crashing programs problem. My last fix for Final Cut was to simply turn of the dropped frames warning. Blackmagic gave me several things to try, but ultimately said they thought it came down to the capability of the drives or some hardware issue. They said it was not possible for the Decklink card to cause such a problem.