search

CESNET / UltraGrid

UltraGrid low-latency audio and video network transmission system
http://www.ultragrid.cz
Other
489 stars 55 forks source link

VANC processing #315

Closed TheSashmo closed 1 year ago

TheSashmo commented 1 year ago

How does UG handle VANC in the source SDI?

MartinPulec commented 1 year ago

It doesn't do this in any way. What exactly would you like to transmit? Something specific or rather something like arbitrary VANC data?

TheSashmo commented 1 year ago

I was just curious, when the source SDI has VANC and if its processed in any way, like captions, or any SMPTE VANC Data.

IMG_0868

MartinPulec commented 1 year ago

I understand - as I've written, it has not been handled in any way so far. Not because it were not possible but because it wasn't requested.

TheSashmo commented 1 year ago

I don't think its needed, but its more nice feature to have to be able to pass the VANC data in through the pipeline. Like Timecode being a main one!

MartinPulec commented 1 year ago

I basically agree that it may be useful in general and I think that we may add a support in feature.

But I'd perhaps wait for an appropriate use case to see, what is supposed to be transmitted. Because depending on the actual type of data there are 2 ways how it can be handled - either it can be transmitted as a opaque uninterpreted data. But there are data that may be useful to handle more sensibly - of course audio, but I suppose also colorspace metadata; maybe even captions?

TheSashmo commented 1 year ago

Well, I suggest that starting with captions and timecode.

608 and 708 captions are commonly needed as part of a SDI video transmit path. I have hardware that can generate and analyze if you would like to get access to test and validate.

Timecode would be the very next important factor. When doing a multiple camera transmit from a site, being able to carry the timecode from the source site to the end production and being able to sync all the SDI together would be a great option.