[Craig Seeman]

I also experienced the issue with the Flow transition.
It seems intermittent. Sometimes removing and reapplying appears to improved it’s behavior.
I contacted Apple FCPX Support.
They asked for and I sent them my system profile and a short screen capture showing Flow behaving as a Dissolve.
Late 2013 6 Core Mac Pro with dual AMD Firepro 500.

[Craig Seeman]

So their site now has iZotope 6.
Plugin Pack 5 to 6 upgrade $49
Upgrade from Standard 5 to 6 $149

[Craig Seeman]

First make sure you are using Blackmagic driver 10.8.6 which is the current version.
Then check in Blackmagic Media Express to see if you get audio from the camera. It’s quite possible audio is not being sent through HDMI but checking in Media Express could confirm that.
If there’s no audio in Media Express you may need to see if there’s a camera setting that enables that.
If there is no way to send audio over HDMI than you will need an external audio source (mic) to send to Wirecast separately.

[Craig Seeman]

I don’t see it mentioned but the Audio FX icons have changed.

[Craig Seeman]

[Shaune Fradley] “After some trial and error I’ve managed to get everything working in FCP 10.3.2 apart from the dereverb filter.”

Meaning workarounds I’m sure. BTW you’d think they’d have tutorials for such given that they sell a plugin pack. Several plugins in the pack suffer from the issue of tail audio being cut off.

[Craig Seeman]

[Robin S. Kurz] “Imagine having just that, the realtime transcription, in X. Seriously. ????”

Perhaps this is the “testing grounds” for them to implement in FCPX at a later date… in some ways like iMovie had elements that later appeared in FCPX in a much more advanced version. One can hope.

[Craig Seeman]

[Robin S. Kurz] “I can hook a Tbo3 RAID up to a Tbo1 machine if I like. “

Sure but then you’re not getting TB3 speeds. Maybe I wasn’t clear on that point.

[Craig Seeman]

Rereading does bring something of the Apple Mac ecosystem to mind that isn’t mentioned directly (and rarely mentioned in the forum I think), the relationship of the sales of one Mac to another for a user.

My guess is that many (most?) Mac Pro users also own another Mac. Likely that’s a MacBook Pro for portable use. I imagine some own MacMinis as desktop for lighter use in the home. I wonder how many MacPro users also have iMacs. In my own case I have a few generations of Mac Pros, MacBook Pros’ MacMinis but no iMacs. I don’t know what the norm is though.

One thing a multi mac user runs into is peripheral compatibility across Macs. One might have accumulated several TB2 peripherals to use interchangeably between Macs. If one busy a new MBP with TB3 you can certainly adapt your TB2 peripherals. If you buy peripherals to take advantage of TB3 it’s pretty much an island though.

I’m wonder if they considered how the stagnation of the MacPro had a ripple effect on whether to upgrade other Macs. I certainly think it would impact peripheral makers if people are reluctant to buy the latest (TB3) peripherals since they lack the interchangeability until the user can replace Macs with newer models using the same technology.

Even though the Mac Pro makes up single digits it may impact the uptake of TB3 which is why a more “professional” iMac is that much more important. But for those who’d prefer a Mac Pro there’s less incentive to move to TB3 (upgrade other computers) until a TB3 Mac Pro comes to market.

[Craig Seeman]

I just don’t think ECC RAM would be enough performance incentive much as you describe, given the variety of workflows.

In fact I do wish Apple would take advantage of Xeon’s multiprocessor support. I wouldn’t expect it in an iMac though but it was one of the disappointments with the Mac Pro. I’d like to see that change.

It’ll be interesting when people test the Xeon vs Kaby Lake Quad i7 as they’ll probably release one as well.

[Craig Seeman]

That’s a big concern of mine and it would negate an important asset that the iMac has in workflow dependent on fast H.264 delivery. I did hear that the next generation Xeons may support hardware accelerated decode/encode of H.264 but not sure if that’s what they’re aiming for here. The odd thing is otherwise I don’t see any significant advantage to using Xeon over i7. There has to be another piece to the puzzle.