-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Software based feedback #27
Comments
Thanks for the feedback. Currently, you should be able to send messages back to the physical device using the MIDI action. However, I am unsure how effective this is as you may have to test MANY different messages until get what you want. And yes, it would be a pain to implement this natively. |
I think we are trying to achieve similar thing, but not sure how to do it. I have just installed the latest 2.0.0. Firstly, thanks for the work, the revised UI is easier to understand. I am trying to have a MIDI keyboard toggle the mute on OBS audio source, the keyboard also accept MIDI command to light up that button. Idea is when I click MUTE on keyboard, the MIDI key press is sent to OBS to toggle the source mute, and MIDI is sent back to MIDI keyboard to light up the button, so as to indicate the source is muted, or turn off when it is not muted.
Question. How can the velocity value be automatically reflecting the status of the source mute? |
Unfortunately, the velocity cannot be changed like that as of right now. But that will be considered in the next update. |
This issue has finally been resolved as of the latest update (v2.1.1). Again, thanks for the feedback! |
Update macOS build scripts * Update buildspec.json to support multiple Qt versions and different requested Qt versions per platform * Add generator command line switch for CMake generator selection * Add automatic multi processing support to GNU Makefile generator * Add skip command line switch to manually speed up consecutive runs * Fix zsh scoping issues * Add support for CMake debug output if debug switch is supplied * Extract pre-built dependencies into more specifically named directory * Update notarization process to use updated xcrun functionality (macOS) * Increase required development version to macOS 11.0 CI: Update Linux build scripts * Adds support for "Aptfile"-based installation of build requirements * Adds support for Qt6 dependencies installed via apt-get cmake: Update plugin helper to support Qt6 and proper macOS targets * Also changes name of packages project file to use lowercase "macos" to avoid issues with case-sensitive file systems. CI: Update Windows build scripts * Add switches to skip dependency download or extraction, and building * Add support for updated buildspec.json * Update Expand-ArchiveExt with most current version from ops-deps * Update Invoke-GitCheckout with most current version from obs-deps * Update Setup-Host to use loop-based processing and support updated buildspec.json format and support skip switches * Update Setup-Obs to use values from buildspec.json file and support skip switches CI: Update Ubuntu image to 22 for clang-format-13 support * buildspec: Update obs-studio to 28.0.0-beta1 tag
When you trigger a command on the MIDI device, the plug-in processes the pre-set actions. Could this also be reversed so that the software can trigger certain things on the MIDI device?
Example: I have a button to mute an audio source. When I toggle the mute status in the software, the MIDI controller still shows its last known setting. Here it would be useful to be able to tell the controller via MIDI command what the actual status in OBS is, so that it also displays the current status of the software correctly.
Example 2: My controller has motorised faders. When I adjust the volume in the software, it would make sense for the controller to automatically move the assigned fader to the corresponding position.
However, it is probably a big effort to implement something like that. Would something like that be possible?
The text was updated successfully, but these errors were encountered: