Try to research your issue before posting, don't be vague. The subreddit is only for support with tech issues. Please include your system specs, such as Windows/Linux/Mac version/build, model numbers, troubleshooting steps, symptoms, etc. Live Chat ~Enter Discord~ Submission Guidelines It is very reliable and I've never seen it lose sync with what files it's using.Check out our Knowledge Base, all guides are compiled by our Trusted Techs. Then before the final output, change the viewer back to optimized/original and the rendered output will use the original resolution files, applying your edits. You cannot even tell you are using proxy except it's a lot faster. You perform the editing tasks exactly the same way. After generating the proxies, just change the viewer to "proxy". You don't have to change file pointers or move folders or keep track of locations. Everything is faster - skimming, editing, effects, etc.
In return you get vastly improved performance. In general they require about 50% more space than the original files, so if your media is 100GB, the proxy files once created will take another 50GB. Proxy files are at 1/2 resolution (1/4 total storage size) but they are in ProRes which is less dense than camera-native format. Thanks! I'm somewhat familiar with the approach but never fully quite grasped the use and effectiveness of proxy files. Is editing the proxy also editing the original media? Wouldn't it take up more space or am I getting that wrong? The 2012 MacBook Pros have USB 3.0 so at least you don't have the problem caused by slow USB 2.0 ports. You could move your media to the Touro drive and see if this helps.
The HGST Touro S 7200 rpm USB 3 drive is quite good for a bus-powered drive but it's not equal to an AC-powered 3.5" external drive. That said, it is good practice to have your media on a different drive than your boot drive. Using proxy media greatly reduces the CPU burden. So you want good I/O performance but if you are already bottlenecked on the CPU then infinitely fast I/O won't help. However editing itself, rendering the timeline (minus effects) and exporting (ie encoding) to a file are typically CPU bound operations. It is generally CPU bound and effects often use the GPU. In most cases editing H264 content (even 4K) is not extremely I/O bound due to the compressed nature. Before final export to a file, change viewer back to "optimized/original", else output will be in proxy resolution
Do not select "optimized", since that will take up too much space in your specific situation. In upper-right corner of viewer, click drop down triangle and select "Proxy". Right-click, select "transcode media", then pick "Create proxy media" This will yield a major editing speed improvement and doesn't cost anything. Since FCPX has seamless, built-in proxy support, your best approach is transcode to proxy on either import or afterward. It's an integrated Intel Graphics card which isn't much, but I hear a lot about external video seems like I could put those funds in getting a solid desktop or laptop, but then I couldn't work with FCPX which leaves me in a rut.ĤK can be challenging to edit on even higher end machines. would that help ease the macbook's strain by editing through the drive?.
#Mid 2012 macbook pro ssd size upgrade#
Been working with a Macbook Pro 2012.while it does a decent job for smaller 4k projects, bigger files will slow the hardware down and sometimes crash.Īll I've done is upgrade my ram from 8 to 16gb.I have an external Touro drive running at 7200rpm but I honestly barely use it.
0 kommentar(er)
