NDI Auto Shot Creation
A good friend of mine uses Wirecast and Skype as part of a weekly live show. He uses auto live to activate shots, which works for his workflow... MOSTLY. The place where it doesn't work is Skype call-in guests that are unexpected.
For REGULAR guests, he gets them to connect to Skype BEFORE the show. He then creates the NDI shot for that guest, has it in his document and the world is good. However, he sometimes has competitions or "viewer visits" where someone joins the show that is not as planned and scripted.
What would be helpful is a configuration item where newly discovered NDI sources are auto created in a specific layer within Wirecast. That way, he can get his guest to call into Skype - and the shot magically appears ready for use.
This would greatly assist his workflow, and allow more seamless production for his show.
Greg Kuhnert said:
What would be helpful is a configuration item where newly discovered NDI sources are auto created in a specific layer within Wirecast.
Do explain how you'd like this to work. I can see the convenience yet I can see many ways this could go wrong. Explaining how it would work would help the developers understand how to prevent potential problems something like this might result in.Reply
Do explain how you'd like this to work. I can see the convenience yet I can see many ways this could go wrong. Explaining how it would work would help the developers understand how to prevent potential problems something like this might result in.
From a UI perspective, a new config element that is a pull down menu - that allows selection of the new default layer for newly discovered NDI sources. Allows selection on 1 2 3 4 5 or none
From a process perspective, if the config item is not set to NONE, whenever Wirecast discovers a new NDI source that is not already in the Media asset manager, add it to asset manager - and create a new shot on the configured layer with the NDI source as the only element fully zoomed to fit the whole screen.
Optional extra: A checkbox / toggle in the main UI to enable / disable this feature. That might be useful, but it might also add clutter to the main screen. I'll let others decide on that one.
Greg Kuhnert Would adding and dropping callers during a show create a problem? Would the NDI identification work reliably or when caller 1 drops and 5 is added would there be reliable NDI metadata to see it as 5 or would it replace 1 which might not be what you want. And, due to potential discovery time you'd have to make sure the new guest waited to make sure the source is "discovered" and added in Wirecast.Reply
CraigS Each source from Skype has a new identifier. so there is no problem with 1 drop and another added. Thats all good.
Looking at discovery time, that should also be a non issue. I will assume that Wirecast is polling the mDNS libraries provided by the operating system. If that is correct, they maintain last modified time. Polling that metadata frequently would be a low impact / low load request. Whenever a change is discovered, it could populate up to the assets and to a new shot automatically.