Tom_Bassford wrote:Nobody from BMD has (afaik) ever mentioned that this issue will be fixed in the next or any future firmware.
BMD tend not to promise functions / fixes preferring to roll out the changes and then see if anyone notices.
A pretty poor approach imho.
Tom. You did indeed miss some of the posts from BMD about this. Here is a link to one specifically speaking to this being fixed.
Joshua Helling wrote:Also as an FYI we are working on adding official support for 1080i60 into the ATEM line. Previously it was not officially supported or tested, but it did work. When we released 3.2 this function broke (again since we weren't testing it we didn't know). But we are now working on supporting it officially. But the converters will get you there as well, and I would imagine that 50i would work too, though you might have to manually "list the modes" to select it in a PAL region.
viewtopic.php?f=4&t=419&p=3533&hilit=1080i60#p3533That was just ONE of the posts by BMD. There are others.
Of course right after my reply on that thread Joshua came back with a posty basically saying... no gurantees on when this will be implemented... while in other posts it was given this was a very high priority.
Joshua Helling wrote:I only know that we are actively working on it.
So that means it could be in the next release, or if the changes for the next release were already too close to release it may be in the one following. Of course, that being said...as always with adding features, it's entirely possible that things could take us longer than we expect and it might get pushed out.
So... what that really means is i'm not exactly sure when, but we do see it as an important issue.