RFC: MIDI Support

[danielbuechele]

I am curious to hear your feedback on this idea. In many cases atemOSC is used together with Osculator to map MIDI signals to OSC messages.

Should we support MIDI messages out of the box? We could have a list of actions, which you can learn MIDI nodes for.

[XENONChromatic]

Thats something that I find intriguing. I regularly use both OSC and Midi, and in some cases wind up having to bridge one to the other. My perspective is always that its better to have more comm protocol options than less.

One other fear I have right now is the current dearth of simple midi patchbay apps for MacOS. Midi Patchbay development ceased years ago, and is 32 bit, so will stop working in the next OS update. Midi Pipe is great, but development has also dropped off. The developer is supposedly updating it for future MacOS versions, but there is very little communication there, and its just one dude I believe, and closed source. I guess what I'd really love is a FOSS Midi and OSC routing app. Even if it didnt do any complex transforms like MidiPipe and OSCulator.

[SteffeyDev]

Like @carbon43 mentioned, I think it would be more valuable to create a standalone app that is good at converting MIDI to OSC but has a lower learning curve than OSCulator. While integrating MIDI sounds like a good idea at first, I think it would slow down development (every time I make a change I would then have to program for and test the midi), as well as make the app unnecessarily complex for people who don’t want MIDI.

That being said, I am also a huge fan of apps as having one dedicated purpose, one thing it is very good at doing, so I’m already a bit biased by that philosophy. Just my thoughts :)

[Paradox32]

I’m all for this idea. I currently run a live production switcher and to use my midi controllers I have to run AtemOSC and OSCulator and then I also have a Steam Deck Controller that has its own software and an app called Companion to adapt it to the switcher also. So 4 pieces of software to convert over 2 hardware devices to OSC commands to the switcher. Whew.

[officialmattsnyder]

Would 100% use on a weekly basis

[JamesFrank2525]

That would be totally awesome and save us all so much pain with OSCulator configuration.

[bqiu86]

Yes, please! I want to use midi controller to control ATEM mini!

[KevinvOosterhout]

Yes please :)

[ruebyi]

It would be great to have the midi support!
I‘m using an c touch mini to control my Atem mini with a bar

[pedroitan]

Definetely!

[bischofftep]

Most definitely. I use a Korg nanoKontrol2 and being able to map this to audio mix, etc. would be extremely useful!

[nick-shaw]

While it is appealing to only have to run one background app instead of two, I fear this might change atemOSC from the simple clean app that it currently is into something rather cluttered.

Also there are some relatively complex operation I do with OSCulator which I would need to be able to replicate in atemOSC in order to make OSCulator redundant. For example, I have the master fader on my X-Touch Mini acting as a transition bar for the ATEM Mini, I need two instances of the mapping, with opposite directions, which have to toggle enabling of each time I press the auto-take button.

That said, if atemOSC could implement a more powerful approach to this, with status-aware mathematical operations being applied to mappings (allowing things like linear fader position being mapped to logarithmic gain) that would be fantastic. OSCulator appears to be EOL, so we won't get any new functionality there.

[ruebyi]

@nick-shaw Could you please help be with this?

I have the master fader on my X-Touch Mini acting as a transition bar for the ATEM Mini, I need two instances of the mapping, with opposite directions, which have to toggle enabling of each time I press the auto-take button.

I'm trying to figure this out for almost 2 Weeks and are very frustrated...

Sorry for answering in this thread, but I don't know how to contact you in any other way