OMTPlugin 1.0.0.13

[omtdev]

omtdev submitted a new resource:

OMTPlugin - Open Media Transport protocol plugin for Audio/Video over LAN

Send and receive high quality audio/video between OBS and other OMT compatible devices over a local network!

For more information about Open Media Transport in general, see the README here: https://github.com/openmediatransport/

OMT Source​

Receive audio/video from OMT sources on the network.

Supports HDR workflows using the Color Space dropdown in the OMT Source properties.

OMT Output​

Send audio/video from the main OBS output.

This...

Read more about this resource...

 

[阿斯顿]

OBS 31.1.2 crashes immediately upon launch.

 

[omtdev]

We cannot replicate this issue, so there appears to be a problem with that particular computer or the settings being used.
Are you able to test on another machine?

 

[KattPhloxworthy]

Hello!

Was just testing out the plugin for my own workflow. I had a couple of questions:

I tend to use 59.94fps (keeps with NTSC/ATSC standards) internally as well as on-stream as opposed to a full 60fps. Does this cause any issues? It seems to work, but it could be smoother. I could set up a secondary profile set to 60fps on the three systems I was testing on, which are part of my production setup, but this is a lower-priority item presently.

Additionally, the plugin seems to work well with a need I have for the BGRA colorspace. I am a VTuber which makes it ideal for me to send a stream with an alpha channel to another computer for integration into my stream.

Finally, I found out how to properly get this plugin working in the C:\ProgramData\obs-studio\plugins hierarchy. I needed to make sure the plugin directory was correctly named and it shows up. However, it will not send any stream out. I have not yet tried to see if it can receive in this way. Any plans to get this working this way?

Thanks for any information you might have!

--Katt. =^.^=

 

[阿斯顿]

We cannot replicate this issue, so there appears to be a problem with that particular computer or the settings being used.
Are you able to test on another machine?

另外一台机器也出现了同样的问题

 

[omtdev]

Hello!

Was just testing out the plugin for my own workflow. I had a couple of questions:

I tend to use 59.94fps (keeps with NTSC/ATSC standards) internally as well as on-stream as opposed to a full 60fps. Does this cause any issues? It seems to work, but it could be smoother. I could set up a secondary profile set to 60fps on the three systems I was testing on, which are part of my production setup, but this is a lower-priority item presently.

Additionally, the plugin seems to work well with a need I have for the BGRA colorspace. I am a VTuber which makes it ideal for me to send a stream with an alpha channel to another computer for integration into my stream.

Finally, I found out how to properly get this plugin working in the C:\ProgramData\obs-studio\plugins hierarchy. I needed to make sure the plugin directory was correctly named and it shows up. However, it will not send any stream out. I have not yet tried to see if it can receive in this way. Any plans to get this working this way?

Thanks for any information you might have!

--Cat. =^.^=

OMT supports any frame rate, essentially it just passes frames from one end to the other without changing the original timing at all. It is essentially up to the app (in this case OBS) to synchronise those frames if required.

Currently omtplugin has a dependency on libvmx.dll and looks for that within the program files instead of programdata.
However, this should be an easy fix in the next update to search both locations for the library.

Thanks for your feedback!

 

[bOMBA]

Warning! Installing OMTPlugin blocks some OBS 32.0.0 settings (the program apparently thinks it's recording).
(OBS 32.0.0, plugin version 1.0.0.12, Windows 10).
Disabling the plugin in the plugin manager solves the problem (but disables OMT).

 

[bOMBA]

Deactivating output in OMT Output Settings also solves the problem (but disables OMT).

 

[KattPhloxworthy]

Warning! Installing OMTPlugin blocks some OBS 32.0.0 settings (the program apparently thinks it's recording).
(OBS 32.0.0, plugin version 1.0.0.12, Windows 10).
Disabling the plugin in the plugin manager solves the problem (but disables OMT).

Tried on OBS Studio 32.0.1 and Windows 11 Pro 23H2. While I can select a source stream, e.g. my Gaming or VTuber machines to send to a source on my Studio machine. The interface and ability to find the senders (which I have turned on in both cases), but I can't connect and move data from either machine.

If you need any manner of assistance, please let me know.

--Katt. =^.^=

 

[omtdev]

Warning! Installing OMTPlugin blocks some OBS 32.0.0 settings (the program apparently thinks it's recording).
(OBS 32.0.0, plugin version 1.0.0.12, Windows 10).
Disabling the plugin in the plugin manager solves the problem (but disables OMT).

Please be advised this is normal behavior and expected in OBS.
When you use any plugins that have an output of some kind active (OMT or NDI for example) , OBS will temporarily disable some settings automatically.

You will need to turn off the OMT output temporarily while making those changes and then turn it back on again.

This is controlled by OBS and not a problem with this plugin.

 

[omtdev]

Tried on OBS Studio 32.0.1 and Windows 11 Pro 23H2. While I can select a source stream, e.g. my Gaming or VTuber machines to send to a source on my Studio machine. The interface and ability to find the senders (which I have turned on in both cases), but I can't connect and move data from either machine.

If you need any manner of assistance, please let me know.

--Katt. =^.^=

This is usually a firewall issue. Need to make sure OBS and any apps using OMT are added as a firewall exception in Windows. This is needed even if OBS is successfully able to access the internet, as the firewall rules only apply to connecting between sources on a local network.

Search for Add an app to windows firewall in start menu, then click Change Settings and make sure all OBS options in list are ticked.

 

[KattPhloxworthy]

This is usually a firewall issue. Need to make sure OBS and any apps using OMT are added as a firewall exception in Windows. This is needed even if OBS is successfully able to access the internet, as the firewall rules only apply to connecting between sources on a local network.

Search for Add an app to windows firewall in start menu, then click Change Settings and make sure all OBS options in list are ticked.

As it turns out, the firewall was never the problem but something entirely different. I realized i had forgotten something in my most recent test. It actually failed the same way under 31.1.2, something I actually alluded to in my first report.

The real problem was that in one of my installs, I had the plugin and DLL in an alternate location, C:\ProgramData\obs-studio\plugins, in this case, those files would live off that path in the path omtplugin\64bit. The plugin would load, but for whatever reason, the rest of the plugin behind the UI wouldn't work. I had forgotten that the files have to, have to, be in C:\Program Files\obs-studio\obs-plugins\64bit (if the OBS Studio tree is rooted in C:\Program Files; adjust to suit installation).

Once the files are in the location within the OBS Studio installation tree, it works fine. I never had to make changes to my Windows Firewall. Furthermore, it's actually far better-behaved under OBS Studio 32.0.1 than under 31.1.2.

--Katt. =^.^=

P.S. I would like to see it in the C:\ProgramData\obs-plugins tree because when OBS Studio is uninstalled via a system install procedure, it deletes everything under the installation tree, regardless of how it was installed. I mean EVERYTHING. Anything in C:\ProgramData\obs-studio is completely left alone. Plus placing files in there does not require elevated privileges, which C:\ProgramFiles requires.

 

[omtdev]

As it turns out, the firewall was never the problem but something entirely different. I realized i had forgotten something in my most recent test. It actually failed the same way under 31.1.2, something I actually alluded to in my first report.

The real problem was that in one of my installs, I had the plugin and DLL in an alternate location, C:\ProgramData\obs-studio\plugins, in this case, those files would live off that path in the path omtplugin\64bit. The plugin would load, but for whatever reason, the rest of the plugin behind the UI wouldn't work. I had forgotten that the files have to, have to, be in C:\Program Files\obs-studio\obs-plugins\64bit (if the OBS Studio tree is rooted in C:\Program Files; adjust to suit installation).

Once the files are in the location within the OBS Studio installation tree, it works fine. I never had to make changes to my Windows Firewall. Furthermore, it's actually far better-behaved under OBS Studio 32.0.1 than under 31.1.2.

--Katt. =^.^=

P.S. I would like to see it in the C:\ProgramData\obs-plugins tree because when OBS Studio is uninstalled via a system install procedure, it deletes everything under the installation tree, regardless of how it was installed. I mean EVERYTHING. Anything in C:\ProgramData\obs-studio is completely left alone. Plus placing files in there does not require elevated privileges, which C:\ProgramFiles requires.

Thanks for tracking that down. I have released an update that will allow the plugin to work in both locations and also updated the readme to specify ProgramData as the recommended location moving forward.

Release Open Media Transport (OMT) Plugin · openmediatransport/omtplugin

This is the official Windows and Mac binaries release for the Open Media Transport (OMT) plugin for OBS. This plugin adds a Source and an Output to OBS to support the OMT Protocol. For more informa...

github.com

 

[omtdev]

omtdev updated OMTPlugin with a new update entry:

OMTPlugin v1.0.0.13

This updates the plugin to support placing the files in the ProgramData location on Windows.
This should be C:\ProgramData\obs-studio\plugins\omtplugin\bin\64bit where C: is the drive Windows was installed to.

Read the rest of this update entry...

 

[KattPhloxworthy]

Thanks for tracking that down. I have released an update that will allow the plugin to work in both locations and also updated the readme to specify ProgramData as the recommended location moving forward.

Release Open Media Transport (OMT) Plugin · openmediatransport/omtplugin

This is the official Windows and Mac binaries release for the Open Media Transport (OMT) plugin for OBS. This plugin adds a Source and an Output to OBS to support the OMT Protocol. For more informa...

github.com

Looks good on this side! I even have things set up so I can go between technologies without too much effort.

I want do a full-system test to see how well I can do an entire stream with the four PCs I used video-over-LAN on to see how well it works.

--Katt. =^.^=

 

[KattPhloxworthy]

Looks good on this side! I even have things set up so I can go between technologies without too much effort.

I want do a full-system test to see how well I can do an entire stream with the four PCs I used video-over-LAN on to see how well it works.

--Katt. =^.^=

As promised, I've done a stream which features not just one instance of OMT, but three. One for my VTuber (which shows my using a transparent stream with BGRA), one for the game I'm playing, and the one to the machine that's sending the resulting composited stream to encoder, the output heading to Twitch and YouTube (the latter two using NV12). It seems to have handled it pretty well overall.

--Katt. =^.^=