Resource icon

obs-midi-mg 3.1.5

Go to download
Overview Updates (26) Reviews (12) History Discussion
Hi, I have a problem. I have binding collections that I only use with the midi device "icon istage v2.01" but when I close and reopen obs studio my binding collections have another device assigned "nanoKONTROL2.1 SLIDER/KNOB"
1717851704419.png


1717851773486.png


This "nanoKONTROL2.1 SLIDER/KNOB" yes or yes I must have it connected to the PC, but I am not interested in using it with "obs-midi-mg"

I just want to use "icon istage v2.01" with "obs-midi-mg"

So, I have to enter each binding to set the correct device. I have more than 100 bindings. Every time I open obs studio I have to change it manually, it's very annoying.

Would there be any possibility of being able to eliminate from "obs-midi-mg" the midi devices that I do not want to use with the plugin? or is there a way to default the midi "icon istage v2.01" . Or put the midi that I want as the first option... because as another midi device appears first, the device changes in all the binding collections.

Please I need your help @nhielost I'm going crazy to solve it

thank you
 
@nhielost Is there any possibility to choose in this instance for the entire collection to use the selected midi device instead of choosing one by one in each binding

1717851973795.png
 
How to automatically change the LED between preview and program on me when I use the transition keys? I don't see a function or something that allows me to do it. I am using my VMIX Mini Switcher controller
 
Please help with the problem, plugin cacthes the button signal, but does not perform the action

- YouTube

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
youtu.be youtu.be

- YouTube

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
www.youtube.com www.youtube.com
 
josiealexdaisy said:
Amazing update! So much more convenient and intuitive.

I'm still have issues targeting which setting in the custom filter settings I want to map. It could be user error, but nothing is popping up prompting me to select a setting. I am on Macos and Obs Midi 3.0 Beta 2.
Click to expand...
Following up, I haven't found a fix to this. I love this plugin and want to keep using it and really want to find a solution! None of the varibles or options of filter settings are showing up when assigning an action.
 
Hi, I can't get the OBS slider up and down in OBS. I have the nanocontrol studio. He does react to it, but he just jumps down. but no ongoing regulation. Buttons are working. I have OBS plugin version 3.0.3 LG
 
I have just added the Atium Vertical plugin for OBS so I can stream horizontally and vertically at the same time. Currently I have my horizontal scenes MIDI mapped to an Akai MPK Mini keyboard using OBS MIDI-MG. Everything works flawlessly.

I want to mirror exactly my horizontal scenes and transitions in my vertical stream. Linking the horizontal and vertical scenes in OBS allows me to switch scenes using my current MIDI bindings (set up for horizontal scenes). The only thing I can't figure out is how to do the same for my transitions (Fade, move, etc). Right now, the horizontal and vertical transitions are separate and I am unsure of how to link them together. End result: I should be able to control both orientations simultaneously.

Please advise. Thanks.
 
Last edited:
Feature request:
I hope to map the midi data to a group source element display switch, which can realize the mapping of a specific value to a fixed beginning + index to locate the target element and then display it. In the current 3.0.3 version, the source display and hiding can only be targeted at 1 source object. If you want to implement the switch of a group of sources, you have to create this function repeatedly.
 
Hey there, thanks for this amazing plugin, it helps a lot. This enables me to use my Launchpad Mini to control OBS.

But a problem I keep running into is, sometimes the plugin will 'forget' my MIDI device and act like it's an entirely new device. Whenever this happens, I have to manually edit every binding to point to the "new" MIDI device. For example, I had all my bindings set to device "6- Launchpad Mini" but now it's displaying as "3- Launchpad Mini" and I had to change them all manually. Bit of a pain in the ass when it keeps happening. Can anyone suggest how I might be able to keep this from happening, or is this an issue with the plugin?
 
Yes I had such issue too. And some others. I document hoping it will help improving:
Issue 1: The device is seen as a new device. My explanation is: I changed the USB where the midi device was first plugged in. Actually it is loupedeck Live plugged into the LENOVO laptop with OBS (preparing a broadcast.) I did quit OBS/turned off the computer (probably hibernate), then plugged diffently: to a DELL screen featuring an usb hub and turned on again. The loupedeck appeared in the MIDI Devices list with different name (such as "Loupedeck Live - 2" or -3). I suppose this is due to the USB architecture/path
Issue 2: sometimes the MIDI device does not operates. It is seen "Disconnected" and I can reconnect in frame "Midi Devices" (look at Input Status / Output Status. if disconnected: click to reactivate (otherwise this is another issue).
issue 3: Sometimes the "action" has changed. This can be checked by selecting the binding in "Binding Collection", then select one binding in first column then look at the red frame:Category/Action/etc). May be this is due to some re-arrangement in the Scene or Sources...?
I dont blame the author since this plugin is great improvement over previous attempts (thanks !). I just wish some fix will come... (thanks again!)
 
Last edited:
I recently installed obs-midi-mg (v3.0.3), which seems to be extremely nice... however, so far I failed to have it receive the MIDI message sent by my controller. I did connect my device and the MIDI capabilities seems to be fine (I'm not sure what that should mean though). I read the whole HELP page (which is very impressive as well btw) I'm positive that the device does send messages. I run OBS-studio 30.0.2.1 on ubuntu 24.10.
1727451959448.png
1727453162916.png

I might be missing something completely obvious... so any help will be greatly appreciated!
 
Update from my previous post: with version v2.3.0, the MIDI messages are received properly on my machine.
 
LHR said:
I recently installed obs-midi-mg (v3.0.3), which seems to be extremely nice... however, so far I failed to have it receive the MIDI message sent by my controller. I did connect my device and the MIDI capabilities seems to be fine (I'm not sure what that should mean though). I read the whole HELP page (which is very impressive as well btw) I'm positive that the device does send messages. I run OBS-studio 30.0.2.1 on ubuntu 24.10.
View attachment 108138
From what I see, I would ask:
1/ did you press some key on your midi device, while being in the configuration displayed in your above picture. "Listening ...Continuously" is activated so pressing a button on your "Launch control XL" should change some values, specially "Note #". Does this work ?
2/ Indeed you need to define an action in the red frame next the green one on the picture.
Click to expand...
 
Sophilautia said:
Hey there, thanks for this amazing plugin, it helps a lot. This enables me to use my Launchpad Mini to control OBS.

But a problem I keep running into is, sometimes the plugin will 'forget' my MIDI device and act like it's an entirely new device. Whenever this happens, I have to manually edit every binding to point to the "new" MIDI device. For example, I had all my bindings set to device "6- Launchpad Mini" but now it's displaying as "3- Launchpad Mini" and I had to change them all manually. Bit of a pain in the ass when it keeps happening. Can anyone suggest how I might be able to keep this from happening, or is this an issue with the plugin?
Click to expand...
Did you solve the issue ? For example did you try different usb entry in you PC ? I planned to try this myself but i am a quite lazy...
 
Thank you for the answer. I did press some keys as it was listening. Finally I went back to version 3.0.3 and hack this a bit by transferring the MIDI messages on 'Midi Through Port-0' this now works like a charm. However I notice a bug, which causes OBS to crash immediatly. It seems to happens when reusing (ie copying) a given media (in my instance a video). Every thing is fine until you choose in the red area "Category> Video Sources". Then OBS crashes. I launche OBS from a terminal to get log and here it what it gives:
> obs: symbol lookup error: /usr//lib/x86_64-linux-gnu/obs-plugins/obs-midi-mg.so: undefined symbol: obs_sceneitem_get_info2
 
Still couldn't get it to start on Debian 12

Code: 
debug: Found portal inhibitor
debug: Attempted path: share/obs/obs-studio/locale/en-US.ini
debug: Attempted path: /usr/share/obs/obs-studio/locale/en-US.ini
debug: Attempted path: share/obs/obs-studio/locale.ini
debug: Attempted path: /usr/share/obs/obs-studio/locale.ini
debug: Attempted path: share/obs/obs-studio/locale/en-GB.ini
debug: Attempted path: /usr/share/obs/obs-studio/locale/en-GB.ini
info: Using preferred locale 'en-GB'
debug: Attempted path: share/obs/obs-studio/themes/Dark.qss
debug: Attempted path: /usr/share/obs/obs-studio/themes/Dark.qss
info: Using EGL/X11
info: CPU Name: AMD Ryzen 5 3600 6-Core Processor
info: CPU Speed: 4158.316MHz
info: Physical Cores: 6, Logical Cores: 12
info: Physical Memory: 31996MB Total, 10474MB Free
info: Kernel Version: Linux 6.1.0-26-amd64
info: Distribution: "Debian GNU/Linux" "12"
info: Session Type: x11
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1
info: Qt Version: 5.15.8 (runtime), 5.15.8 (compiled)
info: Portable mode: false
QMetaObject::connectSlotsByName: No matching signal for on_tbar_position_valueChanged(int)
info: OBS 29.0.2.1-1+b1 (linux)
info: ---------------------------------
info: ---------------------------------
info: audio settings reset:
    samples per sec: 48000
    speakers:        2
    max buffering:   21 milliseconds
    buffering type:  fixed
info: ---------------------------------
info: Initializing OpenGL...
info: Enabling fixed audio buffering, total audio buffering is now 21 milliseconds
info: Loading up OpenGL on adapter NVIDIA Corporation NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
info: OpenGL loaded successfully, version 3.3.0 NVIDIA 535.183.01, shading language 3.30 NVIDIA via Cg compiler
info: ---------------------------------
info: video settings reset:
    base resolution:   1920x1080
    output resolution: 1920x1080
    downscale filter:  Bicubic
    fps:               60/1
    format:            NV12
    YUV mode:          Rec. 709/Partial
info: NV12 texture support not available
info: P010 texture support not available
info: Audio monitoring device:
    name: Default
    id: default
info: ---------------------------------
warning: Failed to load 'en-US' text for module: 'decklink-captions.so'
warning: Failed to load 'en-US' text for module: 'decklink-output-ui.so'
info: Decklink API Compiled version 11.6
info: Decklink API Installed version 12.8.1
warning: Failed to load 'en-GB' text for module: 'frontend-tools.so'
warning: Failed to load 'en-GB' text for module: 'linux-alsa.so'
warning: Failed to load 'en-GB' text for module: 'linux-capture.so'
warning: Failed to load 'en-GB' text for module: 'linux-jack.so'
warning: Failed to load 'en-GB' text for module: 'linux-pipewire.so'
info: [pipewire] No captures available
warning: Failed to load 'en-GB' text for module: 'linux-pulseaudio.so'
info: [obs-browser]: Version 2.19.0
info: [obs-browser]: CEF Version 103.0.5060.134 (runtime), 103.0.0-5060-shared-textures_143.2591+g4204d54+chromium-103.0.5060.134 (compiled)
info: NVENC supported
error: VAAPI: Failed to initialize display in vaapi_device_h264_supported
info: FFmpeg VAAPI H264 encoding not supported
warning: Failed to load 'en-GB' text for module: 'obs-midi-mg.so'
info: [obs-midi-mg] Loading plugin (v3.0.3)...
info: [obs-midi-mg] [Configuration] Initializing MIDI...
info: [obs-midi-mg] [MIDI] Device <Midi Through Port-0> detected.
info: [obs-midi-mg] [MIDI] Device <Scarlett 18i8 USB MIDI 1> detected.
info: [obs-midi-mg] [MIDI] Device <VI49 VI49 In> detected.
info: [obs-midi-mg] [MIDI] Device <VI49 EDITOR In> detected.
info: [obs-midi-mg] [Configuration] MIDI initialized.
info: [obs-midi-mg] [Configuration] Loading configuration...
info: [obs-midi-mg] [Configuration] Configuration file not found. Loading new configuration data...
info: [obs-midi-mg] [Configuration] Configuration file data loaded. Extracting...
info: [obs-midi-mg] [Configuration] Configuration loading complete.
Segmentation fault (core dumped)
 
Not sure what I'm doing wrong.

I've tried to install this plugin both with the installer - obs-midi-mg-3.0.3-windows-x64-Installer.exe and manually from zip file obs-midi-mg-3.0.3-windows-x64, but the plugin isn't loading. It doesn't appear under Tools, and in the log file that it says, "Module '../../obs-plugins/64bit/obs-midi-mg.dll' not loaded".

New install OBS Studio 30.0.2
Windows 10 x64

I have restarted OBS and my computer multiple times, but still isn't loading. I'm new to OBS and this is the first plugin I've tried to add. Have I overlooked something?
 
Last edited:
I am trying to receive MIDI inputs from another program that sends them on the same PC, but I'm only seeing "restricted device" under "MIDI Devices".

Is there a way to do this?
 
You must log in or register to reply here.
Back
Top