You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
VSTs typically process or output midi, one of the tutorials mentions it but not in full. A nice part of having some VSTs and often their key feature is the ability to automate some controls using midi messages.
This is potentially extremely useful for live streaming purposes, any VST for example that allows automation of a gain control*, or any other processing effect that maybe an audio processional would be familiar with.
A sort've hackish way around this is to have a VST host within this VST host with a plugin which gives the user the option to pick a midi hardware device as it's source...it's not pretty. Most of any VST plugin assumes that midi is being provided via hardware, not that it needs to provide it and just eyeballing a few VST hosts midi support is pretty much always included.
Another interesting idea may be to pass along any captured midi control codes and treating them as OBS hotkeys*...which would just naturally over time extend creative control over OBS features as more plugins add hotkey support...
I've already found examples of people using the WebSockets API w/ a bit of powershell and .NET to do this in a round about way on Windows. It seems like people'd probably like this feature, especially since it'd make it nice to do scene selections, or fire off animations, etc...
VSTs typically process or output midi, one of the tutorials mentions it but not in full. A nice part of having some VSTs and often their key feature is the ability to automate some controls using midi messages.
This is potentially extremely useful for live streaming purposes, any VST for example that allows automation of a gain control*, or any other processing effect that maybe an audio processional would be familiar with.
A sort've hackish way around this is to have a VST host within this VST host with a plugin which gives the user the option to pick a midi hardware device as it's source...it's not pretty. Most of any VST plugin assumes that midi is being provided via hardware, not that it needs to provide it and just eyeballing a few VST hosts midi support is pretty much always included.
Another interesting idea may be to pass along any captured midi control codes and treating them as OBS hotkeys*...which would just naturally over time extend creative control over OBS features as more plugins add hotkey support...
I've already found examples of people using the WebSockets API w/ a bit of powershell and .NET to do this in a round about way on Windows. It seems like people'd probably like this feature, especially since it'd make it nice to do scene selections, or fire off animations, etc...
Little busy myself but*
http://www.music.mcgill.ca/~gary/rtmidi/
may be useful along w/ this:
http://teragonaudio.com/article/How-to-make-your-own-VST-host.html#sending_midi_messages
This would mean that somewhere there needs to be a midi device selection in some part of the filters GUI
The text was updated successfully, but these errors were encountered: