Clearly - and yes, as I wrote above, virtually the same end-result is possible already. Given the time and effort it would take, I'm just asking whether there's some real-world benefit to this that we've overlooked. It may simply be that our friend is fulfilling a promise to pass a customer request along.I think what they are looking for it an 'Empty' input, even if teh DSK get triggered nothing will be displayed.
you cant accidently put something in the keyer without going into the DSK menu.I have used the method suggested (setting to an empty buffer or input) and have been bit when eventually something gets put into that buffer or worse it has a drop shadow applied which effectively puts up a black frame over the whole image. A empty/none would be a nice, cant accidentally put something in there selection.
The advice I was refering to was: As mentioned, this can be done by choosing a Buffer that has no content loaded into it.you cant accidently put something in the keyer without going into the DSK menu.
if using the CS Surface, you can lock the Keyer Delegate buttons so you do not select a source via the Key Row.
Since I moved to a TC2 I have started to use input 32 and I hope I will never get there.Not to ignore the suggestion, but just as additional workarounds:
Again, I can see the point of the suggestion, just mentioning a few ways to avoid the problem right now. (I can think of some other, more sophisticated approaches, but they'd be more trouble to explain to a customer.)
- I often use an unused (high number) video input for this purpose (rather than a buffer)
- Or you could use a buffer that has a fully transparent graphic in it.