chichian
commented
5 years ago Hi David,
Sorry we have not responded to you sooner. I just did some quick fixes for cvOSCcv, but did not work on any new features. Real life has kept me busy, but I think j4s0n is open to allowing a back-channel. I'm not sure when we will get to it though.
So for the back-channel, you would like to display a single multi-line message like the latest message or have a buffer of messages (like the last N messages or characters)? If it is per channel, then I would probably limit it to the latest message (and hopefully a small message).
Hi,
I started using your awesome cvOSCcv module after I was pointed to it on in the VCV community. I'm using it to send data back and forth to some generative music Python scripts which I use to play around with ideas I find hard to do with plugins, especially stuff around scales and harmony. Everything works really well so far.
What would greatly improve the module for me (but maybe I'm exotic here) is a back-channel, where the module would receive a string message via OSC (which exists, afaik) and simply displays it as a (multi-line) label or on a little "screen". The simplest way would be a single dedicated "message channel". This would allow me to display some status data about the script I'm running, which has console output but no UI. Say I use CV to set a scale, I currently have no way of seeing which scale it is other than switching to the console. For me, such a label would be much more useful than the little scopes per channel. One label per output channel would also be cool, just to show a parameter value as interpreted by the script.
The second thing that would be cool (but less so than the back channel) would be the ability to send the value of several CV ins as a vector valued message.
Best, and thanks for this great module! David