-
FCP7 and Retina MacBook Pros
Hi All
Having posed the question myself on WWDC day, I’ve been curious ever since ordering my rMBP how it would behave and look with good ol’ FCP7. After receiving mine yesterday, I’ve finally had a chance to find out. I also tried a little ‘unauthorised’ testing on the full 2880×1800 resolution, courtesy of the ‘Change Resolution’ app from Wineskin – find it via this link:
For info, I have the 2.6Mhz 15″ rMBP with 512Gb flash drive. The MBP came with 10.7.4. As is common with new Apple computers, YOU CANNOT DOWNGRADE the OS, even one percentage build.
The short version: FCP7 looks fine on this new machine. As a former owner of a 17″ MBP with a 1920×1200 display, I have mostly been using it at the ‘more space’ resolution offered in the new display controls (which annoyingly you can’t enable in the menu bar any more) which gives this ‘effective’ resolution. Although not native to the display, you cannot see ‘scaling’ common with using lower-than-native resolutions.
It’s clear that the text in FCP7 is not ‘retina’ – nor I am sure will it ever be. But it is as clear and readable as it ever was, at least to my eye. Although a smaller screen than the old high-res 17″, I find this size more than useable, as the display is so sharp.
CAVEATS: I’ve seen two problems so far. 1) FCP7 crashed at one point. I have been unable to repeat it, but it was also before I updated to 7.0.3 (the original install was 7.0 from the disks and I got impatient!) so may be related to this. Problem 2) is more of an issue: FCP7 DOES NOT LIKE RESOLUTION CHANGES.
As you will note above, I have installed a small app to change resolutions on the MBP. I assume (as it seems to have no lasting effect and is easily undone in prefs) that this is not causing the problem – but I first noticed this bug when using the unsupported 2880×1800 resolution and then changing back to ‘official’ resolutions – however, it does appear the bug appears even when you change between supported official resolutions as well. It happens EVERY time.
Essentially, the Canvas stops playing video, and flickers between a few current frames – irrespective of where you are on the timeline. I’ve seen similar issues in FCP7 before that appear to be caused by external video cards – but I currently have nothing installed on the system (I’ll be testing it with an MXO2 soon).
The bug can only be corrected by shutting down FCP7 and restarting it. Of course, this is not a problem if you open FCP7 and stay in the same resolution – as most will. I was changing res so I could compare them – hardly standard practice. It remains to be seen if this bug will be fixed by an OSX update – which seems possible given the newness of the rMBP – or whether it will never be solved for FCP software that will never see another update. It’s not a deal breaker for me, unless it turns out to be symptomatic of larger issues – especially with the use of video devices.
As a matter of preference, I found the ‘true retina’ setting of 1440×900 too small for me – as I said I’m used to bigger resolutions on 17″ MBPs and 27″ iMacs (and cinema displays), but either of the ‘more space’ settings were fine for general use in FCP7 – the ‘two up’ window layout in 1920×1200 mode gives video windows of HD material at 49% scale.
Now for the fun bit (assuming you are still reading) – I also used the above hack to run FCP7 at 2880×1800. Although this crashed once at this res running 7.0.0, otherwise it seemed useable. Hopefully I can embed a screenshot below at full size. By creating a ‘retina’ layout, with a smaller viewer and big canvas, and setting the text size to ‘large’ in the browser (and larger sized timeline) I was able to have a 100% HD (1920×1080 prores) canvas in FCP7! As someone who mostly uses shortcuts in FCP7, I found this surprisingly useable, although the buttons were predictably tiny!
I’d add that the canvas in FCP7 doesn’t (as far as I know) show full resolution in the Canvas – I believe it’s half res. In addition, the footage I have is 1080i, so shows interlacing. I couldn’t honestly say it looked super sharp (as the viewer does in FCPX), although it looked very nice. In addition, there was quite a bit of ‘tearing’ in moving video, where the screen struggled to refresh this monster resolution.
I will try to take a comparison shot of the canvas in FCP7 and X to see how the retina-ready FCPX compares in 100% playback. Incidentally, I think anyone using FCPX will be very pleased with the retina MBP….
Now for some screenshots:
First up (because I know you want it) here’s the slightly absurd 2880×1800 FCP7 workspace:
Now, here’s the same project at 1920×1200 resolution. I left the text size the same in FCP7 so you could see the difference in scale at play here:
Finally, here’s FCP7 running at ‘retina’ 1440×900:
I think it’s clear if you compare the menu bar to the app that there is no ‘pixel doubling’ going on in the text. I’ve also set the text scaling in the browser to the small size – otherwise if I’d left it, it would have been huge. Perfectly usable, but if anything the larger GUI text looks worse at this lower resolution. I think that’s because your eye gets so used to the pin sharp elements in retina apps so quickly. There really is no going back from the retina display. It’s a shame FCP7 will never be optimised for it – I expect to be using it for at least another 12 months.
I’ll be carrying on testing FCP7 with my MXO2 (via thunderbolt) and the rMBP to make sure it’s stable for an upcoming job. I’ll report back if I have any major problems.
I’ll also be installing CS6 this evening – keen to see how it looks before its retina update – but having seen FCP7 I’m not too bothered.
Let me know if I can answer any specific queries – I’ll see what I can do.
Ben
Edit Out Ltd
—————————-
FCP Editor/Trainer/System Consultant
EVS/VT Supervisor for live broadcast
RED camera transfer/post
Independent Director/Producerhttps://www.blackmagic-design.com/community/communitydetails/?UserStoryId=8757


