David Cherniack
Forum Replies Created
-
[Michael Aranyshev] “Adobe Premiere though finally having an almost complete editing toolset doesn’t give you access to this toolset from keyboard.”
Good Grief! As someone who’s complained for a few years about functions you couldn’t assign to a key I can report that in CS5.5 there are very few things you can’t configure the keyboard setup to do. What are you missing?
David
AllinOneFilms.com -
Be sure to import your native EX clips in through the Media Browser. It takes care of all spanned clips. I just copy the entire directory structure into a dated folder on my array, then point the media browser to it and drag all my clips into a folder in my project panel.
David
AllinOneFilms.com -
Right now the only way that you can employ a control surface in mixing is to OMF output to a DAW that supports it.
David
AllinOneFilms.com -
[Chris Kenny] ” If Apple releases an API to access sequence data, and it works reasonably, I suspect I could implement EDL exporting well enough for our internal needs in just a few hours.”
Now while I agree with the first part of the sentence, the “few hours” strikes me as unbridled optimism 🙂
But I was refering to IO drivers and keyframeable plugins….if keyframable is going to be at all possible – hard to see how it couldn’t factor into their plans if they see it as a pro app. But is there a place for that in the present interface or will it need something that’s not yet apparent?
David
AllinOneFilms.com -
I use the GTX 470 in Premiere these days. It’s great and hardly pops 30% useage when stacking half a dozen CUDA effects on any HD nmaterial. The only time I wish I had more vidram (1.3GB) is when working with CUDA on 5k stills series. (Premiere handles source at up to 11k though you’d need a monster amount of vidram to preview it, let alone the raid speed to push it through).
Check out the performance of the machine at work. I have no doubt that Apple can bring it up to speed if it’s a bit tardy in this first release, which I sort of expect because it is a first release.
Honestly, as an ‘outsider’ I did expect more of the missing features to be present. I’m rather dumfounded in the choices they did make, in the inflexibility of the interface and like everyone else here I’m rather stunned at the pulling of FCS from the market. If I was a user, with my present needs, I’d feel just as upset as many here. But if Apple realy wants to make it a pro app it may take much longer than just a few months that many here are hoping..more like a year or two would be my guess, because it’s quite clear they’ll be relying on 3rd parties to do the grunt work, and they’re not nearly as well capitalized as Apple.
David
AllinOneFilms.com -
Actually I’ve just had this experince outputting 23.98 in a Matrox 59.97df timeline. The great news is that 3:2 pulldown is added automatically by the Matrox drivers to HD-SDI. There is a bit of glitch in CS5.5 where 23.98 is directly output as 29.97NDF. The workaround is to render out the 23.98 timeline to an intermediate code, import it, and interpret it as 24. Then when it’s dropped into a 59.97DF timeline it will play out at the right DF duration.
David
AllinOneFilms.com -
[Chris Kenny] “Have you used the app? On decent hardware most things play back just fine before they render.”
Just curious…what doesn’t play back just fine so far?
David
AllinOneFilms.com -
[John Pale] “DNX HD play out in realtime through a Kona or BMD”
I use Matrox and AVCIntra when I need a space-efficient codec but the Mercury Playback Engine should treat them just like any other codec – add CUDA effects and play back in real time out HD-SDI.
David
AllinOneFilms.com -
[John Pale] “That’s insane. Not only does it require massive amounts of storage, the drives must be extremely fast and expensive. Broadcasters generally do not work with uncompressed HD. Its all Pro Res or Avid DNX HD. This is the main reason why those codecs were developed.”
At modern raid speeds and capacities it’s hardly insane. I used to do it all the time if I needed the extra quality for effects work. But you can capture to DnxHD in Premiere, and to Prores if you have FCP installed.
David
AllinOneFilms.com -
[Chris Kenny] “[David Cherniack] “I’m a little perplexed why they background render everything to Prores for performance if the playback engine is that good. ”
Faster exporting, for one thing. If everything’s rendered already then when you go to export (if you’re using ‘current settings’), it basically happens at the speed of a file copy.”
But Chris, by “better performance” I think they mean playback. And it indicates to me that they still may have some optimizing to do on their playback engine.
As far as exporting in Premiere you can always turn on Use Previews if you so desire or not, if you want to render to a higher bit depth than the previews. I see no advantage to FCP-X in this respect.
[Chris Kenny] “OpenCL wasn’t really a viable option when Adobe wrote the Mercury engine. It’s a nice example of how “more modern” actually translates into material benefits. (Though of course it wouldn’t be impossible for Adobe to add OpenCL support now. Their engine is new enough that I’d guess it has a fairly clean, modular architecture.)”
You’re coorect that OpenCL was not quite ready when they wrote their CUDA engine but I’ve been told privately (long before OpenCL was known to be in Apple’s plans) that OpenCL was not quite as efficient as CUDA in their internal testing. Personally. though I expect to see it as a playback option in some future release, if only to accommodate those with ATI GPUs.
David
AllinOneFilms.com