Tom Sefton
Forum Replies Created
-
I know it will take a long time – but the RAW settings are the same in AME and FCPX. AME is encoding the files way faster. Like I said, a full 40 minute segment is being exported in less than an hour in AME, in FCPX a minute of r3d is taking 10 mins……
I can’t get the files into resolve due to the complicated multicam edits. Hey ho – just looks like a long night watching render bars!
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
This is correct regarding the missing red controls in FCPX. Just one thing to note that Premiere CC can do – you can adjust all of the settings that are available in RedCine X, and export a look that you can apply to all clips on a timeline or in a folder. FCPX still has relatively limited controls for raw red files.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Another post from Tim that keeps you totally engrossed until the end. Bravo.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Just a muse on the cost of entry point – could it be that the lower cost of equipment is actually hurting startup businesses more than helping them because they don’t start to budget for the absolute minimum that a day of filming or editing would cost? If you’ve dropped £100k on cameras, lenses, edit equipment etc, would it protect your investment more by charging a fair amount or turning work down? Is it easier to shoot and edit for £200 per day if you have only invested £5k on all the equipment you own?
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
look, robin. I’ve worked in fcpx with this workload for 6 months. Ive exported over 8000 files from fcpx with this project alone. I’ve tried and tested with the proxy workflow and the optimise option. I beta tested the last version of fcpx and was sent beta drivers from red to test with it. I work in premiere and fcpx and avid on a daily basis and each one suits a different job. More and more fcpx is getting into our studio workflow because it is quick and efficient and good at what it does. I love the program and it has literally saved us thousands of pounds in wasted studio time after an aborted attempt to use resolve to edit the same project. It couldn’t cope and had massive issues with audio. X came to the rescue and we haven’t looked back.
However, with high res raw footage it just hasn’t performed as well for us as premiere has. It slows down. The beachball appears after a while of working. Inspector windows and multicam windows and waveform windows need closing down to get optimum performance that you just don’t need to do in premiere. However, it is still brilliant. You might not want to believe me, I really don’t care. It’s just been our experience on a very intensive and long lasting project that we are still getting through. And you haven’t understood my point that 40hrs of r3d data PER WEEK will create at least half again of proxy footage, which has cost implications for ongoing workflows that aren’t easy to sustain.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
I understand that the workflow I’m showing as an example is an extreme one. However, the project I’m working on has 20hrs of footage for each camera with a 2 camera shoot. My figures were slightly off….by half. So I’m actually bringing in 40hrs of footage. This is happening 2 times a month. With space for backups I’m processing 8TB of data each week. To render out proxies or optimise would almost double this amount.
I also note that you have said you haven’t used premiere in 2 years and you base a lot of your comments on what you have read on reduser. Trust me, if you populate a timeline with 4,5 or 6K material in premiere, it doesn’t get sluggish and it doesn’t slow down with huge projects. The interface is smooth for editing and shuttling around clips. In fcpx it isn’t.
6K would usually require proxies, but for this particular project which is a mix of 6,5 and 4K r3d files, it isn’t an option to spend 5 nights doing proxy exports before starting to edit with almost double the amount of rushes. Who has 32TB of data storage free all the time?
It wasn’t long ago that people were getting abuse on this forum for saying they hadn’t used fcpx but were basing their scepticism on what they had read on the Internet.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
I’m basing my comparison on editing the r3d files. Not proxy’s or optimised media. With the r3d files at 4k and above premiere cc has a much faster and smoother interface, but isn’t as quick at rendering.
I’m doing a project at the moment with over 20hrs of footage per week where there simply isn’t the time or storage space available to duplicate to ProRes LT or similar and have been testing for a long time between programs. FCPX is faster with organising clips, syncing and exporting, but Adobe is better with the speed of interface. At ProRes there isn’t much difference between them, but raw shows up some ram leaks.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Great comparison.
It baffles me that we still have nowhere even close to realtime playback in Ae for some things that seem very simple. Even dropping resolution to 1/2 or even 1/4 often doesn’t change things enough to make it useful.
A basic keying job today in 1080p ProRes was taking me between 8-13 minutes to render out for sections that were between 15s and 1m long. Effects used were keylight, selective colour, and colour correction. I’m not saying keying is simple but the amount of time it was taking me to do ram previews and renders on a new Mac Pro system with max ram and d700s was crazy.
I really should give motion a lot more time and effort to learn.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
I get that bill, and the increase in performance for 1080p projects on MacBook Pro and iMac is v exciting. It would be really great if there was some indication that a new Mac Pro is due to be released and take advantage of this new coding though, as many production houses like ours are hanging on to see if another is coming to help speed up workflow of high res, raw projects. The only thing I know from current experience is that editing r3d based projects in 4, 5 and 6K is sluggish on fcpx and fast on premiere cc. I wish it wasn’t so because the more I use fcpx, the more I love it.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
It still is an issue if you are working with high resolution raw footage, even with a high spec Mac pro. Unfortunately, premiere cc is hands down miles faster at doing this when you drop your working resolution to 1/4. The timeline doesn’t slow down, you don’t occasionally lose waveforms on your clips and you don’t get the beach ball every time you need to keyframe something. For one massive project we are working in fcpx with this kind of footage and it works, just with these performance glitches. It’s come a very, very long way but for speed of interface it still has ground to make.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk