Fri Jan 11, 2013 12:24 am
Xtreemtec,
I've posted loads of ranting on this issue, if you like that kind of thing, over on the ATEMUser.com both in the developer sub-forum and amongst the normal topics, so I won't go into too much detail here.
But the Short version:
In versions of firmware 1.0->2.7.2 there was a fully functional public and published API/SDK (i.e. all key /transition settings, media control, crosspoints, multi-viewer control absolutely everything on the mixer ), was controllable from 3rd party integration solutions. In 2.8 that control was reduced to just the program/preset bus and the ability to trigger Auto Transitions and Fade to Black.
Effectively they removed 90% of the functionality if you were driving your mixer from your in-house systems, or slaving the mixer from a big production switcher for just a small part of your product.
There are incomplete workarounds to this problem, but I think it's pretty bad that they removed all this functionality from people who bought the mixer, in the first place specifically because this functionality existed.
My warranty ran out, whilst I've been waiting for them to put the SDK back to a usable standard, which is something they promised to do "within a couple of versions" around January 2012.
So basically I've had zero firmware updates between buying my mixer and the warranty expiring. I know they updates have existed, I've tested them. But just like 3.2 & 3.3 wasn't relevant to anyone requiring 60Hz, and 3.4 is irrelevant to users requiring the down-converter. The following versions have been irrelevant to me: 2.8, 3.0, 3.0.1, 3.1, 3.1.1, 3.2, 3.3, 3.4.
Sorry if this means I'm sometimes sarcastic on these forums. By those 348 days have made me believe BMD don't really prioritise updates based on customer request, but in order to make new sales, and I'm yet to see any evidence to contradict this theory.
Cheers
John