Hi All,

I'm a bit behind on some emails, but I thought this one was worth
discussing.  Just some random thoughts, but what if we had a virtual
device layer?  The current system reads/writes values to a single IO
target. Instead, we could add an additional layer where a user can
read/write to virtual devices, and IO can be setup to read/write to
various targets.  (Somewhat similar to JACK...)

We don't have a system for dealing with multiple devices, but it might
be interesting if the user could design a project to work with
"8-Channel output" as a device as well as "2-Channel input". If the
user writes their project using those devices, Csound could, upon
initialization, look to see if the system has those devices defined.
For example, a user might define these in a .csound.json file or
something like that.  (Imagine also having active virtual devices,
say, defining an 8-channel output device that uses code to process
8-channels into 2-channel binaural...). Granted, users might already
be using something like Jack for this?

I think the above for audio would also work for MIDI (and again, would
replicate some of the functionality of JACK, though would open up
multiple MIDI devices in Csound).

That all said, there's some internals that would need changing, and
things that are hard-coded now would become default behavior that
could be overridden in a new system.

Anyways, some thoughts about it all.  One thing I'd mention here is
that users who are developers can, at this time, avail themselves of
implementing the above behavior using the API by using channels for
input/output for both audio and control signals, and the event-related
functions for dealing with MIDI. Users can design CSD projects that do
work across systems by depending on channels instead of direct
hardware. I think that's good for developers, but it is not a feature
that's built into Csound nor available to the lay user.

steven


On Sun, Jan 22, 2017 at 3:18 PM, Dr. Richard Boulanger
 wrote:
> What we are saying is that we are happy with the current functionality,
> but... if the MIDI controller or MIDI keyboard hardware is removed or
> swapped or accidentally comes loose during a performance, then you are sunk
> because the only way to reconnect is to stop the render and then start the
> .csd again, usually (but not always appropriate musically) from the
> beginning.  Or not restart at all and just power through without your Csound
> support or processing.
>
> It would be nice
>
> On Sun, Jan 22, 2017 at 1:36 PM Anton Kholomiov 
> wrote:
>>
>> I think it would be great addition to csound functionality, bu Ipropose it
>> as a workaraound. You don't need software. probably you already code in some
>> lang that is specific to the mobile platform and I assume that it gives you
>> some ways to handle the midi. Though Csound code becomes clumsy when you
>> have to encode midi messages with notes
>>
>> 2017-01-22 21:21 GMT+03:00 Bernt Isak Wærstad :
>>>
>>> It's a possible solution, but requires knowledge of how to use the API
>>> and forces you to use other software in addition to Csound, so I still think
>>> it makes sense to have the functionality in core Csound.
>>>
>>>
>>>
>>> On 22 January 2017 at 16:58, Anton Kholomiov 
>>> wrote:
>>>>
>>>> One way to avid this problem is to handle the midi outside of Csound and
>>>> send the midi messages over API
>>>>
>>>> 2017-01-22 0:56 GMT+03:00 Dr. Richard Boulanger
>>>> :
>>>>>
>>>>> Steven, Victor, John,
>>>>>
>>>>> You might remember when Bernt and Alex were making a request about
>>>>> Csound knowing when a controller was "disconnected" in mid performance?
>>>>>
>>>>> The problem is that when a controller is disconnected (accidentally or
>>>>> intentionally - you might be swapping in a different one), one is required
>>>>> to restart Csound in order for it to be recognized.
>>>>>
>>>>> Bernt and Alex were reporting this problem for the Pi.
>>>>> This is the case on the iPad and iPhone too..
>>>>> - the MIDI hardware needs to be installed before starting the app in
>>>>> order for it to be recognized.
>>>>>
>>>>> Is there a way for Csound to notice a controller when it is plugged
>>>>> into a port and update the list of controllers at that time (using a
>>>>> callback?).  And, remembering the previously selected device - so that if it
>>>>> was accidentally knocked/pulled out
>>>>> it would choose the same device when it was plugged back in?
>>>>>
>>>>> -dB
>>>>>
>>>>> --
>>>>> _____________________________________________
>>>>> Dr. Richard Boulanger
>>>>> Professor of Electronic Production and Design
>>>>> Professional Writing and Music Technology Division
>>>>> Berklee College of Music
>>>>> ______________________________________________
>>>>> President of Boulanger Labs - http://boulangerlabs.com
>>>>> Author & Editor of The Csound Book -
>>>>> http://mitpress.mit.edu/books/csound-book
>>>>> Author & Editor of The Audio Programming Book -
>>>>> http://mitpress.mit.edu/books/audio-programming-book
>>>>> ______________________________________________
>>>>> about: http://www.boulangerlabs.com/about/richardboulanger/
>>>>> about:
>>>>> http://www.csounds.com/community/developers/dr-richard-boulanger/
>>>>> music:
>>>>> http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/
>>>>> ______________________________________________
>>>>> email: rboulanger@berklee.edu
>>>>> facebook: https://www.facebook.com/richard.boulanger.58
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Csound mailing list
>>>>>
>>>>> Csound@listserv.heanet.ie
>>>>>
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>
>>>>> Send bugs reports to
>>>>>
>>>>> https://github.com/csound/csound/issues
>>>>>
>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>
>>>>
>>>>
>>>> Csound mailing list
>>>>
>>>> Csound@listserv.heanet.ie
>>>>
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>
>>>> Send bugs reports to
>>>>
>>>> https://github.com/csound/csound/issues
>>>>
>>>> Discussions of bugs and features can be posted here
>>>>
>>>
>>>
>>>
>>> --
>>> Mvh.
>>>
>>> Bernt Isak Wærstad
>>>
>>>
>>>
>>>
>>>
>>>
>>> Csound mailing list
>>>
>>> Csound@listserv.heanet.ie
>>>
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>
>>> Send bugs reports to
>>>
>>> https://github.com/csound/csound/issues
>>>
>>> Discussions of bugs and features can be posted here
>>>
>>
>>
>>
>> Csound mailing list
>>
>> Csound@listserv.heanet.ie
>>
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>
>> Send bugs reports to
>>
>> https://github.com/csound/csound/issues
>>
>> Discussions of bugs and features can be posted here
>>
> --
> Sent from Gmail Mobile
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here