Activity › Forums › Creative Community Conversations › Feature request
-
Feature request
Posted by David Mathis on February 4, 2016 at 8:03 pmI am hoping this one gets implemented, wanting to see native support for Cinema Raw DNG files. I doubt Send To Motion will ever rise out of the deep blue see.
Camera Operator | Editor | PA
FCP X, Motion, Compressor, Resolve Studio, Photoshop
Blackmagic Design Cimea Camera, Bolex H16, Kodak Super 8Paul Golden replied 10 years, 5 months ago 6 Members · 11 Replies -
11 Replies
-
Noah Kadner
February 4, 2016 at 8:17 pmI’d be surprised to see native CinemaDNG ever either as it’s barely implemented in Adobe’s own NLE. Problem is it’s basically terrible for playing back at full speed in decent performance because it’s a massive sequence of images vs. a continuous video stream. Better workflow is proxy it for FCPX and then grade to DNG in Resolve.
Noah
FCPWORKS – FCPX Workflow
FCP eXchange – FCPX Workshops -
Erik Lindahl
February 4, 2016 at 8:43 pmThe only request for FCPX I’ve had since day one is zero lag playback over video I/O. In it’s current state I can’t see anyone editing in FCPX in other ways than with-out video I/O.
With lag I mean the time from you push play or stop and until the app responds. It’s embarrassingly poor now, given I haven’t tested the latest FCPX with 10.11.3 – it seems BMD has stability issue there anyways so I’m not sure it’s the best platform anyway.
-
Bret Williams
February 4, 2016 at 9:06 pmReally? FCP 7 was the same way. Certainly not that big of a deal to me. I use BMD ultrastudio express. Performance is same with or without.
-
Shawn Miller
February 4, 2016 at 9:21 pm[Noah Kadner] “problem is it’s basically terrible for playing back at full speed in decent performance because it’s a massive sequence of images vs. a continuous video stream.”
Image sequences can playback in real time as easily as any “container format”. The problem with CinemaDNG files from the Blackmagic cameras is that they’re 12bit, 3:1 or 4:1 compressed raw files. Depending on the frame size and frame rate, you’ll need between 95Mbps and 220Mbps per stream to get real time playback in an NLE (IIRC). I’m sure someone will correct me if I’m wrong.
Shawn
-
Noah Kadner
February 4, 2016 at 9:34 pm -
Erik Lindahl
February 4, 2016 at 10:07 pmNope. FCP7 was instant play / stop on a decent system. Crap realtime FX but super low latency editing. Premiere Pro of later versions are also instant. FCPX is not.
-
Erik Lindahl
February 4, 2016 at 10:10 pmEven “official” systems at IBC at the AJA and BMD booth suffer from the latency / lag issue. I don’t understand how people aren’t bothered by it. Last year an AJA engineer said “we’ve heard that from user, we’re aware of the issue” and then mumbled something about Apple.
Premiere Pro had the same issue – worse even – in the CS5, 5.5 and maybe 6 days, but not anymore.
-
Noah Kadner
February 4, 2016 at 10:13 pmYep- exactly my point explained in detail.
Noah
FCPWORKS – FCPX Workflow
FCP eXchange – FCPX Workshops -
Shawn Miller
February 4, 2016 at 11:39 pm[Noah Kadner] “Yep- exactly my point explained in detail.”
I get that your point was about having a workaround for working with CinemaDNG… but you also said that playback performance suffers because of media type (massive numbers of images vs a video stream). Should it not be pointed out if that’s incorrect?
Shawn
-
Noah Kadner
February 5, 2016 at 1:00 am
Reply to this Discussion! Login or Sign Up