Activity › Forums › Creative Community Conversations › Adobe pro video apps now support ProRes on Windows
-
Adobe pro video apps now support ProRes on Windows
Walter Soyka replied 7 years, 6 months ago 12 Members · 19 Replies
-
Andrew Kimery
December 11, 2018 at 4:56 pmThe Internet is abuzz! On Twitter I’m seeing everything from Apple did this so it can showoff how much faster it’s upcoming MacPro will be at encoding ProRes than any Windows machine to Apple is doing this to keep ProRes alive because it’s about to start EOLing all creative apps.
The best part about the Internet is that everyone has a voice. The worst part about the Internet is that everyone has a voice. lol
-Andrew
-
Brooks Tomlinson
December 11, 2018 at 5:00 pm[Walter Soyka] “ready to jump to Windows”
Yep, well our colorist is. We deliver our broadcast commercials 100% in prores. All of our deliverly specs are prores. We live in a pro-res world. Currently we us the Pablo Rio for color, but now it makes a Resolve station a lot more tempting. Not having to have two computers for prores, just fire up encoder is way better.
I currently am a flame Op, so I am stuck on mac, because linux is well… linux…. I would be a happy person if flame came to windows.
Walter, how do you feel about Apple droping Cinform?
Brooks Tomlinson
“I dream in 32bit float” -
Oliver Peters
December 11, 2018 at 5:14 pm[Brooks Tomlinson] “Currently we us the Pablo Rio for color, but now it makes a Resolve station a lot more tempting. Not having to have two computers for prores, just fire up encoder is way better.”
Hmm… Of course, speaking with my colorist’s hat on, I would say, stick with Rio. ☺
– Oliver
Oliver Peters – oliverpeters.com
-
Greg Janza
December 11, 2018 at 9:57 pmThe industry is oftentimes intractable when it comes to delivery specs and so this development is a big leap forward towards simplicity in post.
Tallmanproductions.net | Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
Adobe CC 2019 13.0 | Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 x 2 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with Resilio -
Michael Gissing
December 12, 2018 at 3:36 amI’m waiting to see if Resolve on Win will also have ProRes encoding. Fusion (paid) does. I don’t use Adobe so this doesn’t change things for me, but I’m still pushing away from quicktime and ProRes in favour of the DNxHR family in an mxf wrapper. I know ProRes can be in an mxf now but ProRes remains a proprietary codec rather than an open codec like DNx. I note that many broadcasters world wide are dropping ProRes as a requirement and it is mostly an option.
I was disappointed that BM dropped DNx not long ago from the Ursa cameras. Once BRAW is available for the whole Ursa Mini family I will be dropping ProRes completely.
-
Craig Seeman
December 12, 2018 at 10:48 am[David Cherniack] “Well BRAW is an acquisition codec like ProresRaw only tied (so far, and probably indefinitely) to BM cameras. Not being a delivery codec like Prores, I don’t see how it might factor in A’s decision to license Prores to Adobe.
“
Because, as you see here on this on other forums, there’s a general residence to trust Apple’s proprietary codecs. It may well factor into the business decision a camera manufacturer may make in their decisions to license codecs.
BRaw is being made freely available. ProRes Raw is not. Industry players (both manufacturers, developers, end users) may make decision on paying an “Apple Tax” (licensing) especially when there are alternatives.We’ll never know for sure but I can’t help but think BRaw, announced shortly after Apple’s ProRes Raw, the (short term) ATMOS deal along with implementation by DJI, may have resulted in Apple rethinking its approach to codec license if its goals standardization based on market share.
-
David Cherniack
December 12, 2018 at 10:51 am[Michael Gissing] “I note that many broadcasters world wide are dropping ProRes as a requirement and it is mostly an option.”
Quite possibly this is one of the reasons for Apple to release its codec to Adobe…to grab some cash before it becomes less valuable over the next few years. Of all the existing mezzanine, archival, and delivery codecs, the generally superior Cineform stands the best chance going forward because it’s non-proprietary. As a producer it’s a no-brainer for quality and once broadcast and streaming services technocrats realize they won’t be fired for accepting it the world will be a better place.
David
https://AllinOneFilms.com -
Shawn Miller
December 12, 2018 at 4:57 pm[Michael Gissing] “I was disappointed that BM dropped DNx not long ago from the Ursa cameras. Once BRAW is available for the whole Ursa Mini family I will be dropping ProRes completely.”
Same here, I’m still not happy that BMD dropped support for DNx (on the UM4.6), and I’m keeping my fingers crossed that it will get BRAW. But I’m really curious to see how wide the support for .braw will be… and if it will be supported by FCPX at all… I’m not holding my breath on that, but I’m willing to be pleasantly surprised.
Shawn
-
Walter Soyka
December 12, 2018 at 5:55 pm[Brooks Tomlinson] “I currently am a flame Op, so I am stuck on mac, because linux is well… linux…. I would be a happy person if flame came to windows. “
From your lips to Montreal’s ears.
[Brooks Tomlinson] “Walter, how do you feel about Apple droping Cinform?”
I think Apple was right to drop the 32-bit QuickTime library. It’s long past time. What I would have liked to have seen was third-party codec support in AVFoundation, like we used to have in QuickTime via components, so a user could install a system-wide CineForm plugin and have all video applications be able to understand CineForm MOVs.
I liked having video decode available at the system level. I think it’s a major step backwards that each application must now feature its own direct support for different video formats.
1) Incompatibility has resurfaced. Some apps will simply never support some formats because the developers can’t or won’t address them. It’s like the platform wars of the 1980s and 1990s all over again.
2) It’s a big waste of development resources. Each developer has to write their own support, and that takes time away from their core application development.
3) Having so many different implementations is a potential minefield of subtle differences. I understand that Apple is pretty strict about their ProRes implementations (which is good), but I know correctly managing DHxHD and DNxHR data/video levels and color shifts are a constant headache across applications.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn]
Reply to this Discussion! Login or Sign Up