Derek Andonian
Forum Replies Created
-
Derek Andonian
May 4, 2012 at 11:57 pm in reply to: Sony XD-Cam .MOV’s Don’t Play Nice in Premiere Pro…?Chris Borjis “could be your ram…you’ve got the bare minimum.”
Adding more ram isn’t going to help much though, until you upgrade to 6. 4 is still 32 bit, and can only use 4 gigs.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
Derek Andonian
May 3, 2012 at 5:15 am in reply to: Thank you Apple – and don’t change course. PleaseCarsten Orlt A lot of discussion here is also about native format support. I understand if you have fast turnarounds you like the fact that nothing needs to be transcoded initially (eventually it will). When you work for month on a single project I couldn’t care less about a few nights the computer humming away to get footage transcoded. Again exactly what FCPx does best. Ingest fast to get going and transcode in background. So mercury engine is cool but not necessary.
The Mercury Engine isn’t what allows Premiere to edit natively. Premiere has had native support for DVCProHD since CS3. The purpose of the Mercury Engine is to accelerate playback performance- which does improve playback of highly-compressed footage, but also allows for things like real-time chroma keying, which are pretty useful.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
When I saw the title of this post, I immediately saw an image in my mind of a bunch of dudes with red skin tinkering with an HP tower. 🙂
But seriously though, that sounds really cool. It sounds a lot more appealing than the iMac Pro that Apple wants us to use…
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
Derek Andonian
May 3, 2012 at 3:28 am in reply to: Thank you Apple – and don’t change course. PleaseApple should have continued developing the track-based FCPX shown in that image that was floating around before, then added a magnetic timeline “mode” on top of it. Then people could work whicever way they prefer and ease into the new way of thinking.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
“Some of the Apple product managers wanted to charge a premium for Final Cut Studio with Color vs. Final Cut Studio without Color. Names such as Final Cut Studio Platinum or Final Cut Studio Extended Edition were bandied about”
I wonder if this is how the “Final Cut Extreme” rumors got started…
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
Bill Davis I’m betting in 5 years we’ll all look back and see that whatever the editing landscape looks like, it looks a hell of a lot more like X than it does like X’s competitors.
Then why is Apple putting the source monitor back in?
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
WOW! I bet you could do some serious 4K editing with that thing…
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
Thomas Frank Three minutes is too long good we didn’t go to Premiere!
I should’ve been more clear on that. I didn’t mean just the import- I was factoring in the time it took me to create the screenshot in Photoshop and upload it. The actual importing as a sequence took about 15 seconds. And it worked beautifully.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
Leo Hans I had send a bug feedback to Apple regarding layered PSD file importing.
In less than three hours I got an e-mail from an Apple employee asking me to send him the PSD file.
As a Premiere Pro user, this does NOT sound encouraging to me…
This took me less than three minutes.
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.” -
John Heagy Don’t expect Apple to “make it pro” if you don’t list what you want.
But the thing about that is, it was ALREADY PRO before Apple butchered it…
______________________________________________
“THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.”
