[Craig Seeman]

More reports

[Craig Seeman]

[Michael Kellam] “Does this sound like a workable workflow?”

Absolutely.

[Michael Kellam] “I am concerned about whether Wirecast and the Macbook pro can handle 2-3 HDMI cameras “

That depends on the CPU resources and the settings you use. I’ve done two HDMI sources streaming to one destination all at 720p on a 2013 15″ MBP.

[Michael Kellam] “(I have 2 Thunderbolt inputs and wasn’t sure if it would work to get a Thunderbolt adapter with multiple HDMI ports or if I needed another device.”

Two Blackmagic Ultrastudio Mini Recorders for HDMI to Thunderbolt. For the third, a Magewell HDMI to USB3 device should work. Get appropriate compatible adaptor cables from Apple.

[Craig Seeman]

[Joe Marler] “For anything above single users, I don’t see an immediate near-term move from FCPX to Resolve or other NLEs based solely on presence or absence of BRAW support.”

Arguably such facilities or workgroups are editing in FCPX but grading in Resolve. Unless they have physical infrastructure tied to collaborative workflow (another area Resolve had been focusing on), ending the round trip and possible collaborative improvements certainly may be a very strong motivator if this comes along with the move to BRAW.

[Joe Marler] “Blackmagic is developing Resolve very rapidly and BRAW is proliferating rapidly. The glacial development pace of FCPX has got to improve.
“

Yet another reason why a facility may consider moving.

[Joe Marler] “I don’t think groups were abandoning Avid for Resolve due to lack of BRAW support,”

I’m not sure if the few ProRes RAW users felt locked into FCPX but they can certainly consider moving to PremierPro and Avid.

Unless a facility was entirely FCPX based rather than a mixed environment, these moves away from FCPX are probably easier then in the days were NLE moves meant major workflow and possible infrastructure changes.

[Craig Seeman]

[Joe Marler] “IOW if FCPX supports BRAW that will help Blackmagic more than Apple is helped by Resolve supporting ProRes RAW. “

Apple sells hardware as well. Macs. Given the popularity of BMD cameras, it’s for FCPX users to move to Resolve and easy for Resolve users to leave Apple for Windows and NVIDIA GPUs.

If BMD cameras weren’t so popular it might not be an issue but my gut tells me that BMD may be selling more cameras than ATMOS selling their ProResRAW enabled Recorder/Monitors to those who use it for ProRes RAW recording.

Of course it’s just as easy to move to PremierePro and Media Composer for BRAW and STILL have ProRes RAW capability and move to Windows as well.

There is only ONE “major” NLE the REQUIRES using a Mac and it is only the ONLY “major” NLE that doesn’t support BRAW.

Apple isn’t really in hardball position because the movement is from FCPX to Resolve (my guess) as people buy BMD cameras and the movement can easily include PremierePro and Media Composer additionally.

Apple gains nothing by excluding BRAW support and increases the possibility of the move to Windows as editors move to other Mac NLEs with BRAW and then have the opportunity to easily move to Windows when it comes time to make new purchases.

[Craig Seeman]

The lack of BRAW support in FCPX continues to get more depressing while Resolve continues to innovate in many areas as an NLE (except tracks). That the BMPCC 6K only uses 6K with BRAW exacerbates the disparity. I think a lot hinges on the next FCPX version release.

[Craig Seeman]

One possibility is in Fxfactory Sheffield Artitude
https://fxfactory.com/info/artitude/

[Craig Seeman]

[Oliver Peters] “And BTW – Apple should have been involved with this :(“

Could it be that Filmic Pro is not Apple specific? It runs on Android as well. They’re not Apple-specific.
Dec 2015
https://www.filmicpro.com/2015/12/24/filmic-pro-now-available-on-android/

[Craig Seeman]

If you go to the linked page and look under Previous Versions on the top it’ll go back to 6.4.3. The current version is 7.0.11

[Craig Seeman]

As I said in my post

And the new MacPro certainly has reasonable connectivity, much more so than a MBP.

MBP is designed for portability and one might not be carrying around a bunch of legacy drives.
I’d rather carry my USB-C SSD drive.

[Craig Seeman]

[Andy Field] “sadly i (and i would guest most of us) have a bucket load of regular old drives with client projects to constantly update.”

Do you still expect Macs to include Firewire or SCSI? At what point can old technology go away? At what point to the find keeping such ports impacts overall hardware development when all that’s needed is an adaptor. What about new purchasers who don’t need all the legacy? At what point do you migrate stuff on older drives as needed.

I use a “drive dock” and put “raw” drives in it and copy over things as needed.

For older drives in cases, I’ve occasionally pulled them apart so I don’t have to deal with a bunch of older technology and just work with my drive dock.

It’s actually very easy to connect anything from Firewire to flavors of USB to Thunderbolt but I really don’t need a mess of cables when I go somewhere as I don’t carry old enclosed drives with me.

And the new MacPro certainly has reasonable connectivity, much more so than a MBP.