OMT (Open Media Transport) src/sink plugin

Plugin and library development
1

Hi all

I’m developing a src/sink plugin for OMT (see https://openmediatransport.com) that is a open source video transport on gigabit networks. Very similar to NDI.

I already have a first POC of a omtsrc working.

OMT libraries handle compression/decompression of vmx codec internally (vmx codec recentrly open sourced under mit license by VMIX folks).

As I’m new as a gstreamer developer, let me ask you wether its ok to leave it as it is (codec handling inside src/sink) or its better to take out omtsrc vmx codec management, so it can be used also in non omt pipelines.

I’m considering to leave it inside, to have it running earlier and then try to break this encapsulation and have separate omtsrc/sink and vmxenc/dec.

What are your thoughts?

TIA

2

It depends on how the OMT SDK works but keeping it internal is not necessarily a problem. The NDI source/sink does it internally because that’s how the SDK works (and you can only do it separately if you pay for the SDK).