obs-midi-mg 3.1.5

[l1i1l]

Hello,

Can you provide the whole crash report? There is not enough information here for me to diagnose any issues.
Additionally, I would appreciate it if you provided your configuration file as well. (I assume your log file remains the same when the crash occurs?)

Also, for the zip archive, the directory to put the files has changed from previous versions. Those files can no longer be included with the native OBS Studio files, and must be placed in the %PROGRAMDATA%\obs-studio\plugins directory for the plugin to run. (The installer does all of this for you!)

I am sorry this is happening for you, and I hope it can be resolved soon.

Hello! Don't worry, no problem (except for problems with the plugin ))) )

In order.

I don't use the installer for two reasons: 1) I prefer manual installation so I can see what I'm doing, and 2) in this case your .exe-file is not digitally signed, which my security system objects to.

I repeat once again, the structure of your folders does not correspond to what I see and use in OBS. If I create this “plugins” folder manually and place the “obs-midi-mg” folder from your archive in it, the plugin is not available.

That's why I'm placing your files within the standard OBS folders configuration for plugins:

%PROGRAMDATA%\obs-studio\data\obs-plugins

— a named plugin folder with its additional folders/files (locale, etc.).

%PROGRAMDATA%\obs-studio\obs-plugins\64bit

— 64-bit dll and pdb files.

Just in case, I tried, as I already said, the path you indicated and other options — in all these cases, your plugin turns out to be simply not available for use, which is confirmed by the information in the OBS plugin manager. The only time your plugin shows up in the plugin manager as available and can be activated is when I host your files using these two folders:

%PROGRAMDATA%\obs-studio\data\obs-plugins
%PROGRAMDATA%\obs-studio\obs-plugins\64bit

???

 

[nhielost]

Hello! Don't worry, no problem (except for problems with the plugin ))) )

In order.

I don't use the installer for two reasons: 1) I prefer manual installation so I can see what I'm doing, and 2) in this case your .exe-file is not digitally signed, which my security system objects to.

I repeat once again, the structure of your folders does not correspond to what I see and use in OBS. If I create this “plugins” folder manually and place the “obs-midi-mg” folder from your archive in it, the plugin is not available.

That's why I'm placing your files within the standard OBS folders configuration for plugins:

%PROGRAMDATA%\obs-studio\data\obs-plugins

— a named plugin folder with its additional folders/files (locale, etc.).

%PROGRAMDATA%\obs-studio\obs-plugins\64bit

— 64-bit dll and pdb files.

Just in case, I tried, as I already said, the path you indicated and other options — in all these cases, your plugin turns out to be simply not available for use, which is confirmed by the information in the OBS plugin manager. The only time your plugin shows up in the plugin manager as available and can be activated is when I host your files using these two folders:

%PROGRAMDATA%\obs-studio\data\obs-plugins
%PROGRAMDATA%\obs-studio\obs-plugins\64bit

???

Hello again,

So I think you are unaware what the difference is between %PROGRAMDATA% and the program files directories. The directory you are copying the installation files into is the program files directory, which is where OBS Studio is installed - typically this is in the C:\Program Files directory. %PROGRAMDATA% is a different directory entirely, and it is typically located in the hidden C:\ProgramData directory. New OBS Studio versions will look for plugin files in the %PROGRAMDATA%\obs-studio\plugins directory, not the C:\Program Files\obs-studio\plugins directory. Try placing the plugin installation files there - just copy and paste the obs-midi-mg folder into the C:\ProgramData\obs-studio\plugins directory, and the plugin should appear as normal.

As for your other crash, I still need your entire crash report as well as your configuration file. Configurations can be found at the path indicated in the log file.

I appreciate the feedback, and I hope these issues can be resolved.

 

[sharemess]

hello,
im using the plugin on OBS 32.0.4, im facing some issues that has been really bothering me.

Issue 1/2: OBS Will crash when using the midi controller to configure an trigger seems at random, cant really say what causes it.

Issue 2/2: i personally use a DDJ-400 as my midi controller, sometimes the plugin will not respond to it and will require me going on the trigger, and without changing the input just editing and confirming it will work again, although not the end of the world ive found me doing this multiple times and since i use a lot of buttons it takes a while to go on each input and just confirm it again.

why im posting this?, i think its not a plugin bug and me being very dummy, so i wanted to confirm if its a know thing or i have been doing something wrong, but as anyway, thanks for the incredible plugin, its absurdly usefuly, the only thing i need now is to trigger windows hotkeys with it, but thats on me

 

[Meltopia]

I use a Novation LaunchPad Pro, its works fine,
but i missed in Midi to switch pictures on and off,
or i have not found the right buttons.
I will also use this in Advanced Scene Switcher,
for the LED'd to switch on and off.
Can anyone help me.
Thank you.

If you're on windows, you could try midi command studio, it's still being tested but the test program can still be joined.

 

[Meltopia]

hello,
im using the plugin on OBS 32.0.4, im facing some issues that has been really bothering me.

Issue 1/2: OBS Will crash when using the midi controller to configure an trigger seems at random, cant really say what causes it.

Issue 2/2: i personally use a DDJ-400 as my midi controller, sometimes the plugin will not respond to it and will require me going on the trigger, and without changing the input just editing and confirming it will work again, although not the end of the world ive found me doing this multiple times and since i use a lot of buttons it takes a while to go on each input and just confirm it again.

why im posting this?, i think its not a plugin bug and me being very dummy, so i wanted to confirm if its a know thing or i have been doing something wrong, but as anyway, thanks for the incredible plugin, its absurdly usefuly, the only thing i need now is to trigger windows hotkeys with it, but thats on me

you could try midi command studio, it's still being tested but you can join the test program and get a free licence

 

[nhielost]

nhielost updated obs-midi-mg with a new update entry:

obs-midi-mg v3.1.3

obs-midi-mg v3.1.3 is now available.​

This is a bugfix release.

Bug Fixes:​

• Windows Installers will now properly uninstall plugins created before version 3.1.0
• Copying Messages and Actions no longer causes unintended behavior or crashing
• Copying Messages and Actions now tries to maintain as many similar Field values as possible
• Scene Items Actions will no longer remove sources with no video
• Scene Items Actions will now emit...

Read the rest of this update entry...

 

[dj divz]

There needs to be a proper midi controller plugin that works. its been forever we had one,.

 

[dj divz]

the new plugin update has no info on programing it to your controller. smh

 

[AntonArtsev]

Hi nhielost,

First of all, thank you for this amazing plugin! I've successfully set up buttons for scene switching, quick transitions (Fade/Cut via hotkeys), and everything works perfectly.

However, I'm unable to get the T-Bar fader control working. Here's my setup:

- OBS Studio 32.0.4
- macOS Sequoia 15.5 (Apple M4 Max)
- obs-midi-mg 3.1.3
- MIDI device: iPhone via USB running MIDI Studio Pro app
- Fader sends Control Change, Channel 12, CC #53, values 0–127 (confirmed working in Logic Pro)

The problem: I cannot configure the Position field in the "Set Transition Bar (Studio Mode)" action to respond dynamically to the fader.

What I've tried:
1. In the Action panel, clicking the field name "Position" (label) — no response
2. Switching between all modes (=, MIDI, grid) in the right panel
3. Setting Reference Field to "Value" — gives error: "The selected reference field must also depend on incoming values. This binding will not execute until a valid reference field is selected."
4. Directly editing the JSON config file with various 'state' values (0, 1, 2) for the position field — state:2 caused OBS to crash

In the OBS log I can see:
[obs-midi-mg] [Actions] FAILED: A transition bar distance could not be selected. Check the Position field and try again.

The MIDI signal is received correctly (confirmed by the Listening mode in the plugin). The issue seems to be specifically with linking the Position field to incoming MIDI values.

Could you please advise on the correct way to configure a fader for T-Bar control in version 3.1.3? Is there a specific workflow or a known issue with this feature?

Thank you!

 

[nhielost]

Hi nhielost,

First of all, thank you for this amazing plugin! I've successfully set up buttons for scene switching, quick transitions (Fade/Cut via hotkeys), and everything works perfectly.

However, I'm unable to get the T-Bar fader control working. Here's my setup:

- OBS Studio 32.0.4
- macOS Sequoia 15.5 (Apple M4 Max)
- obs-midi-mg 3.1.3
- MIDI device: iPhone via USB running MIDI Studio Pro app
- Fader sends Control Change, Channel 12, CC #53, values 0–127 (confirmed working in Logic Pro)

The problem: I cannot configure the Position field in the "Set Transition Bar (Studio Mode)" action to respond dynamically to the fader.

What I've tried:
1. In the Action panel, clicking the field name "Position" (label) — no response
2. Switching between all modes (=, MIDI, grid) in the right panel
3. Setting Reference Field to "Value" — gives error: "The selected reference field must also depend on incoming values. This binding will not execute until a valid reference field is selected."
4. Directly editing the JSON config file with various 'state' values (0, 1, 2) for the position field — state:2 caused OBS to crash

In the OBS log I can see:
[obs-midi-mg] [Actions] FAILED: A transition bar distance could not be selected. Check the Position field and try again.

The MIDI signal is received correctly (confirmed by the Listening mode in the plugin). The issue seems to be specifically with linking the Position field to incoming MIDI values.

Could you please advise on the correct way to configure a fader for T-Bar control in version 3.1.3? Is there a specific workflow or a known issue with this feature?

Thank you!

Hello, and thank you for your feedback!

From what I have found, the only thing I can think of that seems to be amiss here is that in the Message section of your Binding, the Value Field is not set to Range mode (the three slider looking button). You tried setting the Action's Position Field to that same mode, and it returned a message saying that the reference field did not depend on incoming values. This means the Value Field in the Message was not set to that mode. The error message that you see in the log is the plugin compensating for this by not executing the Action at all.

Try it out with both the Message's Value and the Action's Position set to Range mode and let me know how it works out.

I appreciate your message - it helps out more than you think!

 

[AntonArtsev]

Hi nhielost,


Thank you for your response! I tried your suggestion — set both the Message Value field AND the Action Position field to Range mode (three sliders button) with Reference Field set to "Value". Min: 0, Max: 127 for Message, Min: 0, Max: 100 for Position.


Unfortunately, the T-Bar still does not respond to the fader. The Action panel still shows a red border around Position.


Could you please show a screenshot or video of the correct configuration? I want to make sure I'm not missing something obvious.


Thank you again for your help!

Hello, and thank you for your feedback!

From what I have found, the only thing I can think of that seems to be amiss here is that in the Message section of your Binding, the Value Field is not set to Range mode (the three slider looking button). You tried setting the Action's Position Field to that same mode, and it returned a message saying that the reference field did not depend on incoming values. This means the Value Field in the Message was not set to that mode. The error message that you see in the log is the plugin compensating for this by not executing the Action at all.

Try it out with both the Message's Value and the Action's Position set to Range mode and let me know how it works out.

I appreciate your message - it helps out more than you think!

Hi nhielost,


Thank you for your response! I tried your suggestion — set both the Message Value field AND the Action Position field to Range mode (three sliders button) with Reference Field set to "Value". Min: 0, Max: 127 for Message, Min: 0, Max: 100 for Position.


Unfortunately, the T-Bar still does not respond to the fader. The Action panel still shows a red border around Position.


Could you please show a screenshot or video of the correct configuration? I want to make sure I'm not missing something obvious.


Thank you again for your help!

 

[nhielost]

Hi nhielost,


Thank you for your response! I tried your suggestion — set both the Message Value field AND the Action Position field to Range mode (three sliders button) with Reference Field set to "Value". Min: 0, Max: 127 for Message, Min: 0, Max: 100 for Position.


Unfortunately, the T-Bar still does not respond to the fader. The Action panel still shows a red border around Position.


Could you please show a screenshot or video of the correct configuration? I want to make sure I'm not missing something obvious.


Thank you again for your help!

Hi nhielost,


Thank you for your response! I tried your suggestion — set both the Message Value field AND the Action Position field to Range mode (three sliders button) with Reference Field set to "Value". Min: 0, Max: 127 for Message, Min: 0, Max: 100 for Position.


Unfortunately, the T-Bar still does not respond to the fader. The Action panel still shows a red border around Position.


Could you please show a screenshot or video of the correct configuration? I want to make sure I'm not missing something obvious.


Thank you again for your help!

This is an example of what your Binding should look like based on what you have described. This was tested and working in the latest version of the plugin. Let me know if you have any questions.

 

[nhielost]

nhielost updated obs-midi-mg with a new update entry:

obs-midi-mg v3.1.4

obs-midi-mg v3.1.4 is now available.​

This is a bugfix release.

Bug Fixes:​

• More Bindings can now be executed at once (limit increased from <1000 to >1m)
• Output Sources Events now produce correct values when using reference Fields
• Custom actions now use the appropriate values when loaded in for the first time
• Custom actions now correctly use the most current source settings
• Scene Items > Scale actions will no longer crash when...

Read the rest of this update entry...

 

[AntonArtsev]

Hi nhielost,

It works!!! Thank you so much for your help and for the screenshots — they made all the difference. The key was the Maximum Position value of 1024, which we would never have guessed on our own.

The T-Bar now responds to the fader and scenes transition smoothly. This is exactly what I needed!

Thank you for this amazing plugin and for taking the time to help. Really appreciate it!

 

[Mitchtsg_93]

Hello! I am successfully getting my Razer stream controller X to trigger OBS scene switching, but I am having issues getting my scenes switches to trigger a USB MIDI device.
Mostly, I am struggling to see an output at all.
I am temporarily using BOME to see MIDI messages to test, and I have set up a BOME virtual port, where I have assigned the output to ON and made sure I have the scenes binded to that output but I can;t seem to get a read on any MIDI message leaving OBS or the plug in.

 

[sky7176]

I'm trying to configure a slider on my SMC-Mixer to control the audio levels of the sources.
I can't seem to figure out what I'm doing wrong, but I can't control the volume.I managed to set the mute controls, but I just can't adjust the level.
I tried the MidiControl program, and with that I can control the audio level.
OBS version 32.0.4
Plug-in version 3.1.4.
I even tried uninstalling everything, deleting the configuration file, and starting from scratch, but nothing worked.
I couldn't get the slider to work.
I'm attaching the two configuration screenshots.

Many thanks
Giuseppe

 

[sky7176]

I'm trying to configure a slider on my SMC-Mixer to control the audio levels of the sources.
I can't seem to figure out what I'm doing wrong, but I can't control the volume.I managed to set the mute controls, but I just can't adjust the level.
I tried the MidiControl program, and with that I can control the audio level.
OBS version 32.0.4
Plug-in version 3.1.4.
I even tried uninstalling everything, deleting the configuration file, and starting from scratch, but nothing worked.
I couldn't get the slider to work.
I'm attaching the two configuration screenshots.

Many thanks
Giuseppe

I realized I was wrong, now I can control the volume slider.

 

[sky7176]

A question about the T-Bar: why does the "Hold Time" parameter exist?

I set a slider to control the T-Bar, but the Hold Time parameter switches the source after n milliseconds.

I'd like to leave the bar at halfway, just to create a source overlay. How can I do that?

 

[nhielost]

A question about the T-Bar: why does the "Hold Time" parameter exist?

I set a slider to control the T-Bar, but the Hold Time parameter switches the source after n milliseconds.

I'd like to leave the bar at halfway, just to create a source overlay. How can I do that?

Hello, and thanks for posting feedback!

The "Hold Time" exists because of a limitation with older versions of OBS Studio. The T-Bar used to only work programmatically if it was "released" - as if the mouse had let go of it physically. This has since changed it seems, and the plugin has not been updated to accommodate that. A fix is coming soon.

 

[sky7176]

Hello, and thanks for posting feedback!

The "Hold Time" exists because of a limitation with older versions of OBS Studio. The T-Bar used to only work programmatically if it was "released" - as if the mouse had let go of it physically. This has since changed it seems, and the plugin has not been updated to accommodate that. A fix is coming soon.

Thanks for the reply.
I'm waiting for the plugin change. If you need a test user, I'll be happy to help.
Giuseppe