3Play 440 and 4800 will have NDI support in a little while, can't say just when yet, but I'm hoping for by NAB if all goes well. This may not be quite what you're hoping for though; we're not adding support for NDI inputs for 3Play - the primary need seems to be NDI output (A and B).
3Play 440 and 4800 will have NDI support in a little while, can't say just when yet, but I'm hoping for by NAB if all goes well. This may not be quite what you're hoping for though; we're not adding support for NDI inputs for 3Play - the primary need seems to be NDI output (A and B).
Perhaps there was some misunderstanding. At present, at least, NDI in to 3Play is limited to the DSK layers. They could be cameras, but these cannot serve as primary replay sources.
Perhaps there was some misunderstanding. At present, at least, NDI in to 3Play is limited to the DSK layers. They could be cameras, but these cannot serve as primary replay sources.
Essentially, it's because various products spring from sometimes similar but not identical code branches, and the architecture can be different enough to make wedging some new feature in rather more daunting. Too, the standard resource burden on a 3Play tends to be somewhat more demanding. I don't want to speculate, so speaking of present possibilities, one wanting to use NDI would need to first supply video over NDI, which would allow one to route and use it as pleased on NDI enabled systems, but convert it back at some point upstream of 3Play's primary inputs. I realize that's not as convenient as we would all like.I'd hate to have to run fiber everywhere, so could you maybe explain why this limitation exists?
Essentially, it's because various products spring from sometimes similar but not identical code branches, and the architecture can be different enough to make wedging some new feature in rather more daunting. Too, the standard resource burden on a 3Play tends to be somewhat more demanding. I don't want to speculate, so speaking of present possibilities, one wanting to use NDI would need to first supply video over NDI, which would allow one to route and use it as pleased on NDI enabled systems, but convert it back at some point upstream of 3Play's primary inputs. I realize that's not as convenient as we would all like.
Any hope that this feature will change so cameras can be primary replay sources over NDI? We really want to use NDI to transport cameras to our Tricaster, but if we can't use it with a 3Play, I'm reluctant to go that route. I'd hate to have to run fiber everywhere, so could you maybe explain why this limitation exists?
I assume the TriCaster and 3Play are not near each other because you mentioned fiber?
Pardon my lack of research if this has been discussed or documented, but will a 3Play 425 output to a TriCaster 460 with the new Advanced Edition over the network? Or does this not work because of the NDI implementation? I haven't been able to test it yet.
Brian
nope. you will need to use hard inputs or roll back to AE V1
nope. you will need to use hard inputs or roll back to AE V1