Skip to content
This repository was archived by the owner on Apr 13, 2025. It is now read-only.

Feature/Virtual device support for Midi services #143

Closed
NeoCortex97 opened this issue Nov 30, 2020 · 1 comment · Fixed by #254
Closed

Feature/Virtual device support for Midi services #143

NeoCortex97 opened this issue Nov 30, 2020 · 1 comment · Fixed by #254
Labels
enhancement New feature or request service Requires changes to a service

Comments

@NeoCortex97
Copy link
Contributor

Description

I think the midi service should provide a setting so it can present a virtual input or output.

Virtual Midi ports are not reflected in hardware and are made to allow communication between two midi capable softwares.
I think both inputs and outputs should be supported.

@NeoCortex97 NeoCortex97 added the enhancement New feature or request label Nov 30, 2020
@hlxid hlxid added the service Requires changes to a service label Nov 30, 2020
@carterfyi
Copy link

I may not be understanding your specific feature request, but at first glance this seems duplicative of the existing MIDI service implementation. Virtual midi device instantiation on-the-fly would be pretty heavily OS dependent, and there are existing solutions for this by platform. On Windows, for example, I've used loopMIDI for years, which could create and expose the virtual ports to be used by the nodecg-io MIDI service. Unless there's something I'm missing, it seems this feature might be out of scope for the project?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request service Requires changes to a service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants