-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Feature - Adding independent access from&to Midi ports in plug-ins. #1248
Comments
This would be cool, and it can be done. But it would require a bit of rewriting for the MIDI handling. I'll see if I can make some time for this next release, since I do like the idea. |
It would be really cool to see this in the near future! In fact, this is the only thing that stops me from completing the project, since plugdata is the link between my daw and the hardware) |
@KPY7030P just use a separate RTP-MIDI daemon and route both your DAW and Plugdata Standalone through there? Kicking this ticket is not going to make any specialized features happen faster, though. |
@dromer Using a separate RTPMIDI is not a problem, which is why I wrote that this is more my fantasy than something similar to a request. |
Hi |
Currently, most DAWs do not sufficiently support MIDI protocols and cannot send some signals to external devices. Also, large developers do not always and do not really listen to the opinion of users, for this reason, requests remain unsatisfied for many years.
PlugData (plugins) as a development and experimentation environment can extend the possibilities of any host and as I think it is part of the overall logic and philosophy of the project.
At the moment there are only three ways for a plugin to interact with the environment :
1. host > plugin
2. plugin > host
3. host > plugin > host.
Thus the PlugData behavior is completely dependent on the DAW and cannot reveal all its possibilities.
What can be done?
I suggest adding support for external devices to PlugData (plugins), just as it is currently implemented in the standalone version.
1. host > plugin
2. plugin > host
3. host > plugin > host
+
4. host > plugin > outMIDI
5. plugin > outMIDI
6. inMIDI > plugin > host
7. inMIDI > plugin
8. inMIDI > plugin > outMIDI
And multiple variations such as "host > plugin > outMIDI + host". This is achieved already inside the patch by duplicating and customizing inMIDI and outMIDI.
What will this do?
Is it possible to realize this?
At the moment there are several projects based on JUCE that have both standalone versions and plugins. These projects have an implementation of sending and receiving MIDI signals from external devices in both implementations (standalone and plugins):
Element:https://github.com/kushview/element
Architect: https://www.loomer.co.uk/architect.html
CtrlR: https://github.com/RomanKubiak/ctrlr
The text was updated successfully, but these errors were encountered: