#apertus IRC Channel Logs

morning folks!

hi Bertl!, available?

hi supragya

it's holiday today, so i'm at home and tomorrow in home office

working on emulation myself!

do you plan on sending meta using Gbe for video streams Bertl ?

and how will interframe markers look like on high speed channel?

suppose it is just RAW12 that comes out

but in case we decide to go with 'just' 12bit words, then we have to reserve one or two for marking

what if some bits get lost (is that even a possibility) ?

and dont't forget about possible header

we need some secondary control channel, so the recording app gets a signal that new data will start to arrive

would it be hard to induce a header such as (marker bits| sequenceID bits) before frame data

so that we can correlate which meta is for which frame?

something like this has to happen, probably time codes are a better 'id' though

Also, for the recorder end, should I expect camera to provide me with structured meta? or should I expect it to provide me with a simple register dump for sensor/lens controller

In general I think there are a number of options and it would be way better to 'design' data/metadata coherence independant of file formats and data streams

IMHO some kind of camera identifier (users choice) and a time code would be appropriate

regarding the USB3 interface, it would make sense to send metadata over the USB3 link instead of a GbE side channel, but in the beginning we won't be able to do that easily

Bertl, that also my idea, to send the separate, later to concatenate by using some frame id

danieel, and what are the licensing options?

"GigE Vision is not an open protocol, and as such a special license is required to develop GigE camera drivers."

Kjetil, and if 14 other standards are proprietary, what should be done then?

make a 15th and make it proprietary

Objection.

Good Afternoon Everyone!