Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

FCP X - FORCE QUIT MESSAGES

I'm extremely afraid of messing with the Redrocket FW since many have reported dead cards after upgrading FW. This will of course be a roll back but who knows what might happen ;-)
The little interest in this bugis also a small sign that not many people is using FCPX and Redrocket workflow yet. Personally I like working in FCPX more and more and think others will too if they only give it a chanse..
So was I. This Rocket has already been replaced once from Firmware Upgrade Death. Thankfully it survived both the downgrade and the re-upgrade.

I too was surprised to run into such a significant bug when using (what seems like) a common workflow.
 
I've got the same problem as you on FCPX with the redrocket.
Would you give me a link to download the correct firmware and how to do this ?
Because I search in Red web's download history for redrocket and find nothing.
Thanks.
 
Resurrecting this topic, ran into a weird issue with a ROCKET and FCPX 10.0.8 on Mac Pro 10.7.5.

Playback using Full in FCPX results in choppy motion.

The ROCKET is up date with firmware 1.1.16.11.
 
Tested the new REDROCKET firmware 1.1.17.3 with FCPX today and am sad to report that the memory leak is still there :-(
God knows if this is a RED or Apple bug but I don't think it will ever be fixed as this probably is the last FW upgrade for the current REDROCKET and Apple don't seem to get their shit together on many things...
 
I'm still battling the memory leak problem. Any updates or solutions out there?

Working in FCPX on a MacBook Pro Retina with 16GB of RAM. Using an mLink R Thunderbolt box for my Red Rocket 1.1.17.3.
 
Back
Top