How to support multiple devices? about miditoobs HOT 13 CLOSED

Can't promise any timeline, this might take months to be published, but spoiler:

from miditoobs.

Implemented with d1a646b

from miditoobs.

So the most basic way to do this, is to just have 2 Instances running with different config files. Because of how it loads the config, if you have 2 different folders each with the setup, main and the config file, you can have multiple instances running that do different stuff.
As for native integration this is something i could add without a lot of work.

from miditoobs.

Any expected changes ?

A lot of underlying code was changed, a lot of bugs fixed and there were some breaking changes in 4.5. that i don't want to invest the time into when i don't what will break with 4.6. And i want to maybe add the new requests that come with 4.5 and 4.6.

from miditoobs.

bump Just as a Plus 1 for this feature to be added

from miditoobs.

@gbraad i hope the requirements.txt works as intended. Maybe when you do your testing you can test that too and let me know.

from miditoobs.

Sounds good. Will use the suggested workaround for the moment. Creative symlinking can solve this...

from miditoobs.

One of the easier fixes would be to make

and

to allow a configurable config.json to be loaded (and possible endpoint values). At the moment, the MidiHandler uses default parameter values. This way, alhough not super elegant yet, it is possible to run multiple instances of the script for each configured device. WDYT? Note: however does not enforce a single device entry in the configuration file.

from miditoobs.

I'll be doing some maintenance work when obs-websocket 4.6 is released. I will have a deeper look in how i can implement that.
With multiple input devices there would need to be a flag for every command to which controller it belongs.
I will leave this open for now. Feel free do add some more ideas or even send a pull request. You seem to be a much better programmer then me. Everything on my Github is just stuff i hacked together mostly for myself.

from miditoobs.

to which controller it belongs

I also concluded this. I'll hack up a simple workaround for the moment and try to push a PR

when obs-websocket 4.6 is released

Any expected changes ?

better programmer then me

Nonsense! Same here for a lot of stuff as I just do not have the time. Wish I could spend more on OSC and Midi stuff.

from miditoobs.

As a temporary workaround I override the config.json based on the argument value. This way not much needed to be modified:

gbraad@8415293#diff-5bc02cefb3ea9e27f1a6776eabd1935dR26

and:

gbraad@8415293#diff-2eeaed663bd0d25b7e608891384b7298R11

Note: the rest of this commit deals with convering from dos line endings to unix... else the top sh-bang #! does not work.

from miditoobs.

With 4.6.0 out now and the 4.6.1 hotfix after my bugreport i hope to start working on this in the near future.

from miditoobs.

@lebaston100 thanks. will test soon. Also good to see the requirements.txt doing there now ;-)

from miditoobs.