Let me put it another way. What I/O device does Avid work with? Is there one?

andrebetz:

Let me put it another way. What I/O device does Avid work with? Is there one?

As far as I'm aware, AJA + Mac Studio systems do not face issues. 

If users are facing issues with AJA and Mac Studios, they should create cases, and I will personally endorse/forward that to our development team. 

On Macs (except for Mac Studios) and PCs, any I/O device compatible with Avid's Open IO architecture will work:

- Blackmagic

- Aja

- Bluefish 444

- Motu

- Neutex

Wrong. It drops to black quite often. There are zero 100% working options for IO 2022 and 2023.

Hi Philip,

AJA + MC on M1/M2 does not work.  There is constant video stuttering.  Some kind of frame buffer problem.  There have been countless discussions of it here, Marianna has acknowledged  it and Avid bug ID MCDEV17407 is the reference I was given.

If there is a solution, we are all waiting eagerly, as working with the Blackmagic is also causing a lot of trouble, though at least it does play frames in order.

Literallly the only version that functions normally is 2021.12.8 and AJA 16.2.2. Any version of MC after that causes issues with AJA and BMD.

kkordisch:

This all started back in 2022 versions and even in some 2021 versions on apple silicon. So what you are saying is Avid hasn't reached out to these IO companies for almost 2 years to fix this? Am I hearing that correctly? I just want to make sure that is what I am hearing because that is what it sounds like. 

No, that is not correct. We meet regularly with engineers at AJA, BMD, Apple, etc, etc. We have strong partnerships with all of them. This particular series of issues has been a series of fixes throughout that entire time. In many cases, a fix would get iomplemented, but then changes get made outside of our control, so new fixes needed to be made.

rockpaperscissors:

Hi Philip,

 

AJA + MC on M1/M2 does not work.  There is constant video stuttering.  Some kind of frame buffer problem.  There have been countless discussions of it here, Marianna has acknowledged  it and Avid bug ID MCDEV17407 is the reference I was given.

 

If there is a solution, we are all waiting eagerly, as working with the Blackmagic is also causing a lot of trouble, though at least it does play frames in order.

Apologies, I haven't been on the forum as much as I used to be...

I have looked into MCDEV-17407, but found MCCET-5232: Video flicker stutter when playing AJA Io4KPlus on Apple Silicon M1 Ultra 

Which appears to match what you describe. That is an Avid bug... the more cases we have of that issue, the more pressure there will be to resolve it. 

Great! Then why isn't this fixed? It has been over a year at least. Why have I been told the fix for the BMD is in final testing for 2 months. Why is there zero transparency except for these vague replies that do nothing but make people even more upset?

Somebody should make a twitter account like the Abe Vigoda status one for Media Composer and Apple silicon "Is IO working on apple silicon?" like this with daily updates.  https://twitter.com/AbeVigodaUpdate

When I talked to AJA about these issues, after being told by Avid that these issues were on AJA, they specifically told me this was an Avid issue.

Hi Philip,

I appreciate your acknowledging that we are not making this up.

The fact that zero AJA devices that can be purchased work with any version of MC that can be used on any Mac that can be bought shouldn't be waiting for a critical mass of complaints.  It should be a house-on-fire emergency.

It is currently a system requirement for MC on Mac to be running on discontinued, unsupportable hardware.

M1 Max on a MacBook Pro 

Philip Kapadia:

andrebetz:

Let me put it another way. What I/O device does Avid work with? Is there one?

As far as I'm aware, AJA + Mac Studio systems do not face issues.

Philip Kapadia:

I have looked into MCDEV-17407, but found MCCET-5232: Video flicker stutter when playing AJA Io4KPlus on Apple Silicon M1 Ultra

kkordisch:

Great! Then why isn't this fixed? It has been over a year at least. Why have I been told the fix for the BMD is in final testing for 2 months. Why is there zero transparency except for these vague replies that do nothing but make people even more upset?

Here lies the problem. Even if any individual Product manager, engineer, customer advocate or forum moderator honestly, to the best of his/her knowledge, replies to the questions asked by one or more customers in these (or other) forums, a lack of internal communication and/or coherent communication to the customer base is exposed. 

The end users and resellers are obviously not in a position to judge individual Avid employees. And these forums are obviously also not the place to engage in discussion regarding any individuals. Neither are users or resellers always able to determine if it is Avid's, Apple's, Microsoft's, Aja's, BMD's, etc.. fault. And while determining blame for (Avid) developers might sometimes be difficult and publicly sharing it not helpful in inter-company relations, the current state of communication regarding the long standing (= over a year imho) issues regarding Titler+, open I/O on Mac, Dynamic relink and Media indexer in Mediacentral, Flex licensing, etc... is not sustainable. 

Customers need commitments on when product design and bugs are going to be 99,999% ready for production to make investment decisions on hardware and software. We need to be able to rely on the Avid certified/supported configurations being tested extensively including I/O of the main manufacturers for the Media composer systems. If that requires cross company commitments... So be it.

If Aja, BMD and Avid can't keep up with the changes in Apple hardware... be honest about it!

kkordisch:

My contact at blackmagic has not heard anything about this.

It would be far fetched to assume that everyone at BMD is privy to the work being done with just one of their 3rd party venders. Avid is in constant communication with our dedicated contacts at BMD. The Media Composer team meets regularly with them in a constant pipeline of communication.

Understood. In the meantime, I have forwarded this thread and the emails that I have saying a fix was in final testing from 2 months ago, to them so that they can confirm and give me a better update because all I have gotten from Avid is "next week" since August. You were on the emails. I will try to update everybody with a real, non vague, answer here when I can.

Same.

We're definitely trying to be as open and clear as possible about this, but admittedly, Avid, BMD, Apple, etc, have all found this issue to be quite ellusive and confusing. It took quite a while and a lot of back-and-forth communications between all of us before any of the engineers in all companies began to finally get triage results and understand what the work load would entail. 

We're so very close to a conclusion. The final leg of the race involves sending lots of things back and forth to all companies involved vor validation and final testing, which might show that it's fixed or it might reveal more work to be done. Plus, with macOS Sonoma now thrown into the mix, it might put a few things back to square one. Hopefully not. 

But I'll trust the engineers to sort that out. In the meantime, I thank you for your patience. As a 30-year editor myself, I understand the frustration as well as your need to be vocal so that you can get things moving forward for the editors you represent.