Tom Sefton
Forum Replies Created
-
No – the problems we saw occurred long before we started the vfx shots.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Interesting.
We only used it in audition from memory, but we used dynamic link to get the comp from premiere into audition and then exported a finished 5.1 wav from audition.
I’ll remember that though – thanks for the tip.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
To be honest, the only plugins that were used for this project were lumetri- which is now part of adobe’s stock plugins, and then izotope RX6 in audition.
Yes – I can believe that tech support for everyone isn’t great, but in the past I’ve had such good experiences from fcpx that I’ve been spoilt. A couple of times I’ve had days and days shaved off a workflow from advice on here, and another time I’ve ended up speaking to someone from Apple.
I’m sure there are ways to optimise premiere and I’m happy to take advice on how we could improve our experiences.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
The project was a series of short films for a public body which we filmed at 8K and 6K on the Red epic-w and epic dragon. We also had 2k proxy files from the camera which we started the edit with, whilst also mixing some footage on the timeline to get an idea of what we could reframe with the added resolution. We also had various music files and external audio to sync.
All the footage was stored on gtech studio xl raids that had plenty of space, and we were editing on Mac Pro 2013s – either 6 or 8 core with 32 or 64GB of ram and max GPU.
The first problem we encountered was a complete slowdown in performance when importing new assets – even jpeg or tiff files caused a beachball which lasted for 10 minutes. Each time the project was opened it took around 25 minutes to organise the media and assets, during which time performance was very sluggish and impossible to work with.
This was when tech support from Adobe suggested we reduce the size of the library which was impossible if we wanted to deliver from the 8K raw files. So if we wanted to carry on we had to work from only 2K proxies from the camera – not a huge problem to get the cut signed off but still – added a large layer of complexity to what should have been simple workflow as we had to use resolve to finish.
The major issue was that when we tried to export an assembly edit from the timeline to help us start vfx for some of the scenes, Adobe media encoder encountered hard crashes when exporting. Not just software hangs, entire system crashes that happened occasionally. This could have been the 8K raw files, but the crashes were occurring at random places during the export which meant we couldn’t narrow down the problem, and because the project wouldn’t import new assets without hours of beachballs due to its size, we couldn’t use Redcine x or resolve to create 4K final assets to work from.
So all in all we found it hard to move forwards and couldn’t believe that the advice from Adobe tech support was to edit short sequences separately, export and then relink on a longer timeline. Fcpx has handled projects 3-4 times as large as this in the past so we didn’t have the best introduction back to premiere. I’d never rule out using it again but it just hasnt been as easy or to be honest, as fun as it is working in fcpx.
That said, the ease of integration between after effects and audition for a 5.1 sound mix was fantastic and I doubt that we could have delivered some of the motion tracking and compositing scenes as quickly and efficiently with fcpx, but I’d love to be shown how! If we could optimise our systems to work faster and better with Adobe I would really appreciate the advice on how to do this – without going anywhere near a platform switch argument.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Went back to dip our toes in the premiere water for a project recently and had some major issues with import, export and performance. Tried the Adobe forums, the premiere forums on the Cow and got no answers. Adobe tech support was woeful – was even told that a 2TB library of rushes was too large and to reduce it down because premiere wouldn’t support it, or we could edit half the sequence in each project and join them together at the end. I’ve really not experienced good tech support for premiere pro.
The main thing that was impressive was the speed and efficiency of dynamic link.
Back to fcpx!
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
-
I’d say that marbles were lost quite some time ago.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
I’m seeing this issue at random on a Mac Pro when rendering r3d to either h264 or prores. There initially was some correlation with the render hitting 8K footage from an epic-w but the last couple of times it’s been at random.
Complete system crash, system report says kernel panic.
Interestingly, rendering the same footage in either redcineX or fcpx doesn’t cause a system crash.
Footage stored on gtech studio xl via thunderbolt 2, and can be outputting to desktop or raid for crash to happen. Running latest OS. Tonnes of space on raid and desktop. Latest version of media encoder and premiere.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Same as Neil, all files on a gtech studio xl raid at raid 5 and half full, with performance still up to 1000mb/s for read speeds
I’ve tried cleaning the cache but this hasn’t helped. That’s 2 projects now that are virtually lost as importing new files (even MP3 files of less than 5Mb) sends the Mac unresponsive.
The exact same setup was used to edit longform projects in fcpx over over 8TB in assets and had no issues?
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
Max ram upgrade – I reckon to jump from 32 to 128GB it will be $1600
Max GPU upgrade – this will be a modest increase, more like $3-400 extra for the top of the range model
Max ssd – jeez, this is going to be silly money, but who needs a 4TB single ssd drive with the mass market saturation of removable ssd drives, raids and 10GE NAS raids…?The processor is the big jump – the current Mac Pro had a jump from 4 to 12 core that went from around $3500 to nearly $6800 with nothing else added. I reckon this will push the top end processor into the realms of a $2000 upgrade.
So a 5K edit station with thunderbolt 3 and 10Ge, with a monitor, at least 500GB SSD, 128GB ram, 8GB GPU and an 18 core processor – the sweet spot for most people lusting after one… I reckon $9200 inc taxes.
Which is a lot. But, find a hp or dell with the same specs AND a 5K monitor included and what does that cost?
Really, what does it cost?
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk