MacBook Pro late-2013 2.6 Ghz Quad Core i7 The results show that BruceX tests processor power, but also shows that Iris Pro Graphics has some way to go to match a discrete graphics GPU in the new MacBook Pro 15″ with Retina These results include those posted at the FCP.co Forum and from. Your configuration’s BruceX Score is the average export time in seconds. Before timing the next export, restart Final Cut (otherwise the exports speed up each time because X does a little caching renders to save time). If possible do the export at least three times. #Gfxcardstatus v2.2.1 2010 movie#Get your stopwatch ready and time from when you click ‘Save’ until you see the movie open up in QuickTime Player.ġ2. In the Save sheet, choose a name and location for the export – export to your fastest drive connected using your fastest connection.ġ1. Click the ‘Next…’ button in the bottom-right of the dialogue boxġ0. From the ‘When Done’ pop-up menu, choose ‘Open With QuickTime Player’ĩ. In the ‘Video Codec’ section choose a flavour of ‘ProRes’Ĩ. In the dialogue box that appears, click the ‘Settings’ Tabħ. Export the QuickTime movie by choosing “File:Share:Master File…’Ħ. Click the new ‘BruceX Test – 5K ‘ project timeline (this makes the Share command selectable)ĥ. Open the BruceX.fcpbundle library which contains a very short but complex 5K project.Ĥ. In Final Cut Pro, go to ‘Final Cut Pro:Preferences…’ – in the Playback tab make sure ‘Background render’ is off.ģ. Have both QuickTime Player and Final Cut Pro open at the same time.Ģ. …and time the export of a 5K master file from the timeline. To use this, open the Final Cut Pro library at The Bruce X benchmark is based on timing how long a Mac configuration takes to export the project. As it uses many layers of complex content, it requires lots of GPU RAM. It uses standard Final Cut generators, titles and transitions. It creates a very short timeline at a high resolution: 5120 by 2700 (at 23.975 fps). I’ve come up with a test that shows the differences between these GPUs and other Macs… The BruceX benchmarkīruceX is a small Final Cut Pro X XML file that you import into Final Cut Pro. MacBook Pro late-2013 Intel Iris Pro Graphics 1GB 19.2 seconds MacBook Pro late-2013 Discrete GeForce GT 750M 2GB 18.8 seconds It turns out that the test wasn’t tough enough to show a difference between the two GPUs: Over at the the FCP.co forum, qbe asked me to do the ‘Far Far Away’ test on my new late 2013 MacBook Pro 15″ using only the built-in Iris Pro Graphics and also on only the Discrete GeForce GT 750M GPU which I included in my BTO Mac. This test puts enough pressure on main memory and GPU memory to separate older generation Macs from more recent computers. #Gfxcardstatus v2.2.1 2010 1080p#The Intel Iris and Iris Pro are every bit the match or master of discrete NVIDIA Mobile GPUs - at least when it comes to OpenCL acceleration.Īlthough it is great news that integrated GPUs are getting better, many are worried that the MacBook Pros should be avoided until Iris Pro has improved a little more.Ī speed test proposed by FCP.co was to time the render of Final Cut Pro X’s built-in ‘Far Far Away’ title on a 23.975 1080p timeline. In the past we sneered at the integrated GPUs and their puny performance. #Gfxcardstatus v2.2.1 2010 software#Editors want to know if the integrated Intel Iris and Iris Pro Graphics GPUs are powerful enough to run professional software well.Įarly testing shows that Iris Pro graphics are better than many expected. New Mac software is depending more and more on GPU power. To help people work out which Macs work best with Final Cut Pro X, it is useful to refer to a standard speed test.Īll but one of the MacBook Pros with Retina configurations do not have dedicated GPUs. BruceX: Try this new Final Cut Pro X benchmark
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |