David Powell
Forum Replies Created
-
I use “export media” from PP and then “queue” to send it to AME for export.
-
I’m going to have to completely disagree with Bill on this. Remapping your keyboard has nothing to do with thinking like an Avid Editor. Apple keyboard layout was never fantastic. F9 and F10 for a repeatable function like overwrite and insert? Pleeez! Many of the Apple commands are laid out for mnemonic memory (“C” for Connect, “T” for Trim”) and have nothing to do with actual muscle function. Avid layout is not that way, but still Avid editors (like myself) remap their Avid keyboards as well as it is not perfect. I’ve been using FCX every day for the last 3 years. I learned their keyboard first, and it’s not great for me. One of the great things about Apples design is how deep the keyboard customization is compared to the competition. And Avid and FCX function surprisingly similar modally which makes it easier to bring the commands from Avid to FCX than it would be to Premiere, which has that worse command execution of all the NLE’s imo, though it’s been improving.
-
Will rolling back to an old driver affect my user saved layouts at all?
-
Its not just MXF files. Its everything else as well. Even Prores Proxy. The worst is fast forwarding a clip in a bin. Instant crash.
-
What am I doing wrong? I have a nearly identical setup 24 gigs of ram and Premiere 2015 crashes every 5 minutes. It’s horrible. Any time I ff on the source side it crashes using prores proxy! I guess I’ll post in the PP forums but UI response and stability has been a nightmare! I agree with all the feature requests though and would add
* Duplicate Frames Detection
*Roll Previous/Next Edit To Playhead -
Keywording is quick in FCPX but the downside is when you have to matchframe back to a clip. Its really a burden in FCPX. Theres no relation to the clips that are in the bin from which it came. It opens at event level VERY slowly and half the time you cant even see the clip. May not be a big deal to you. It is to me. Just something to consider.
-
Mauricio ,
No I can’t. I mark up the sequence while I’m creating a live cut (which is why Adobe’s targeting problem hurts me) and then I make a smaller highlight from those selects. Also, all my projects are multicam. FCPX does not properly cut multicam nests back into sequences. That was a major problem when I first tried to cut from a nest the I/O points are way off (and even the camera if I remember correctly). Stacking timelines is truly the most superior way to do this.
So X would have to fix the multi-cam nest problem inherit the marker markers to the nest, at least from the top most video connected. As of now I have to copy and paste which is a pain. -
Its extremely annoying that I can’t do it in X. Avid allows source side sequence loading in the monitor which inherit the markers. So functionally you can do the same thing, though its not a stack. As of CC 2014, the marker targeting or lack thereof wasted too much time to make the pancake function a net gain for me. Or at least if felt that way.
-
Does it allow for multiple timelines to be opened at once?
-
I’ve cut a lot of footage with FS100 on my 2011 imac. Generally 3-6 cameras. It works great. As far as money is concerned, that depends on how much you’re getting it for. You’ll get more milage out of an i7 than an i5. With 16 gigs of ram, you’ll be good. As it happens I have such an imac for sale if you’re intersted 😉 Its got 2gig vram which is maxed out for that year.