Csound Csound-dev Csound-tekno Search About

Stable and predictable MIDI connection with ALSA

Date2017-07-13 20:48
FromAnton Kholomiov
SubjectStable and predictable MIDI connection with ALSA
Can you help me?

I use many csound files as MIDI-synthesizers.
I use alsa sequencer midi driver.

Recently I've run into problem with MIDI device IDs.
I've changed the audio card and now it has midi in/outs
So I've got MIDI-keyboard and MIDI-capable audio card.
And when I plug them my PC seems to randomly switch
the identifiers for MIDI devices.

But in Csound I have to specify the precise number.
And sometimes it's not the number that  ALSA gives
to my MIDI-keyboard on the next PC start.
So I have to change the device IDs for all files.

Do you know some trick to connect Csound with
MIDI-keyboard in this case? More reliable way to do it

Thanks!
Anton


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

Date2017-07-13 20:50
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Is it possible for example to connect to device by it's name
instead of id?


2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Can you help me?

I use many csound files as MIDI-synthesizers.
I use alsa sequencer midi driver.

Recently I've run into problem with MIDI device IDs.
I've changed the audio card and now it has midi in/outs
So I've got MIDI-keyboard and MIDI-capable audio card.
And when I plug them my PC seems to randomly switch
the identifiers for MIDI devices.

But in Csound I have to specify the precise number.
And sometimes it's not the number that  ALSA gives
to my MIDI-keyboard on the next PC start.
So I have to change the device IDs for all files.

Do you know some trick to connect Csound with
MIDI-keyboard in this case? More reliable way to do it

Thanks!
Anton



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

Date2017-07-13 21:20
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
Hi Anton,

Off the top of my head I can think of:

* Using JACK for midi?

* Fixing the assignments somehow. If it's USB something like:
http://www.familjenpalo.se/vpo/SoundAndMIDI

* Using raw MIDI instead of alsaseq.

* Calling a (non-portable) bash script with system_i and fixing the
connection with aconnect.

Cheers.


On 13/07/17 16:50, Anton Kholomiov wrote:
> Is it possible for example to connect to device by it's name
> instead of id?
>
>
> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov :
>
>> Can you help me?
>>
>> I use many csound files as MIDI-synthesizers.
>> I use alsa sequencer midi driver.
>>
>> Recently I've run into problem with MIDI device IDs.
>> I've changed the audio card and now it has midi in/outs
>> So I've got MIDI-keyboard and MIDI-capable audio card.
>> And when I plug them my PC seems to randomly switch
>> the identifiers for MIDI devices.
>>
>> But in Csound I have to specify the precise number.
>> And sometimes it's not the number that  ALSA gives
>> to my MIDI-keyboard on the next PC start.
>> So I have to change the device IDs for all files.
>>
>> Do you know some trick to connect Csound with
>> MIDI-keyboard in this case? More reliable way to do it
>>
>> Thanks!
>> Anton
>>
>>
>>
> 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

Date2017-07-13 21:47
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Thanks Guillermo I will investigate the options.

Do you think that JACK for midi is more appropriate?
I have never tried it with Csound

2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Hi Anton,

Off the top of my head I can think of:

* Using JACK for midi?

* Fixing the assignments somehow. If it's USB something like:
http://www.familjenpalo.se/vpo/SoundAndMIDI

* Using raw MIDI instead of alsaseq.

* Calling a (non-portable) bash script with system_i and fixing the
connection with aconnect.

Cheers.


On 13/07/17 16:50, Anton Kholomiov wrote:
> Is it possible for example to connect to device by it's name
> instead of id?
>
>
> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>
>> Can you help me?
>>
>> I use many csound files as MIDI-synthesizers.
>> I use alsa sequencer midi driver.
>>
>> Recently I've run into problem with MIDI device IDs.
>> I've changed the audio card and now it has midi in/outs
>> So I've got MIDI-keyboard and MIDI-capable audio card.
>> And when I plug them my PC seems to randomly switch
>> the identifiers for MIDI devices.
>>
>> But in Csound I have to specify the precise number.
>> And sometimes it's not the number that  ALSA gives
>> to my MIDI-keyboard on the next PC start.
>> So I have to change the device IDs for all files.
>>
>> Do you know some trick to connect Csound with
>> MIDI-keyboard in this case? More reliable way to do it
>>
>> Thanks!
>> Anton
>>
>>
>>
> 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

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

Date2017-07-13 22:00
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
Scratch that. I've tried alsaseq and this one worked for me: csound
-+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
to see if you can find the name of the card.


On 13/07/17 17:47, Anton Kholomiov wrote:
> Thanks Guillermo I will investigate the options.
>
> Do you think that JACK for midi is more appropriate?
> I have never tried it with Csound
>
> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>
>> Hi Anton,
>>
>> Off the top of my head I can think of:
>>
>> * Using JACK for midi?
>>
>> * Fixing the assignments somehow. If it's USB something like:
>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>
>> * Using raw MIDI instead of alsaseq.
>>
>> * Calling a (non-portable) bash script with system_i and fixing the
>> connection with aconnect.
>>
>> Cheers.
>>
>>
>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>> Is it possible for example to connect to device by it's name
>>> instead of id?
>>>
>>>
>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov :
>>>
>>>> Can you help me?
>>>>
>>>> I use many csound files as MIDI-synthesizers.
>>>> I use alsa sequencer midi driver.
>>>>
>>>> Recently I've run into problem with MIDI device IDs.
>>>> I've changed the audio card and now it has midi in/outs
>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>> And when I plug them my PC seems to randomly switch
>>>> the identifiers for MIDI devices.
>>>>
>>>> But in Csound I have to specify the precise number.
>>>> And sometimes it's not the number that  ALSA gives
>>>> to my MIDI-keyboard on the next PC start.
>>>> So I have to change the device IDs for all files.
>>>>
>>>> Do you know some trick to connect Csound with
>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>
>>>> Thanks!
>>>> Anton
>>>>
>>>>
>>>>
>>> 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
>>
> 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

Date2017-07-13 22:02
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Wow! That's exactly what I need!

2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Scratch that. I've tried alsaseq and this one worked for me: csound
-+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
to see if you can find the name of the card.


On 13/07/17 17:47, Anton Kholomiov wrote:
> Thanks Guillermo I will investigate the options.
>
> Do you think that JACK for midi is more appropriate?
> I have never tried it with Csound
>
> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>
>> Hi Anton,
>>
>> Off the top of my head I can think of:
>>
>> * Using JACK for midi?
>>
>> * Fixing the assignments somehow. If it's USB something like:
>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>
>> * Using raw MIDI instead of alsaseq.
>>
>> * Calling a (non-portable) bash script with system_i and fixing the
>> connection with aconnect.
>>
>> Cheers.
>>
>>
>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>> Is it possible for example to connect to device by it's name
>>> instead of id?
>>>
>>>
>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>
>>>> Can you help me?
>>>>
>>>> I use many csound files as MIDI-synthesizers.
>>>> I use alsa sequencer midi driver.
>>>>
>>>> Recently I've run into problem with MIDI device IDs.
>>>> I've changed the audio card and now it has midi in/outs
>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>> And when I plug them my PC seems to randomly switch
>>>> the identifiers for MIDI devices.
>>>>
>>>> But in Csound I have to specify the precise number.
>>>> And sometimes it's not the number that  ALSA gives
>>>> to my MIDI-keyboard on the next PC start.
>>>> So I have to change the device IDs for all files.
>>>>
>>>> Do you know some trick to connect Csound with
>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>
>>>> Thanks!
>>>> Anton
>>>>
>>>>
>>>>
>>> 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
>>
> 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

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

Date2017-07-13 22:02
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Thanks alot!

2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Wow! That's exactly what I need!

2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Scratch that. I've tried alsaseq and this one worked for me: csound
-+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
to see if you can find the name of the card.


On 13/07/17 17:47, Anton Kholomiov wrote:
> Thanks Guillermo I will investigate the options.
>
> Do you think that JACK for midi is more appropriate?
> I have never tried it with Csound
>
> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>
>> Hi Anton,
>>
>> Off the top of my head I can think of:
>>
>> * Using JACK for midi?
>>
>> * Fixing the assignments somehow. If it's USB something like:
>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>
>> * Using raw MIDI instead of alsaseq.
>>
>> * Calling a (non-portable) bash script with system_i and fixing the
>> connection with aconnect.
>>
>> Cheers.
>>
>>
>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>> Is it possible for example to connect to device by it's name
>>> instead of id?
>>>
>>>
>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>
>>>> Can you help me?
>>>>
>>>> I use many csound files as MIDI-synthesizers.
>>>> I use alsa sequencer midi driver.
>>>>
>>>> Recently I've run into problem with MIDI device IDs.
>>>> I've changed the audio card and now it has midi in/outs
>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>> And when I plug them my PC seems to randomly switch
>>>> the identifiers for MIDI devices.
>>>>
>>>> But in Csound I have to specify the precise number.
>>>> And sometimes it's not the number that  ALSA gives
>>>> to my MIDI-keyboard on the next PC start.
>>>> So I have to change the device IDs for all files.
>>>>
>>>> Do you know some trick to connect Csound with
>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>
>>>> Thanks!
>>>> Anton
>>>>
>>>>
>>>>
>>> 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
>>
> 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


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

Date2017-07-13 22:13
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
Sure. Cheers!


On 13/07/17 18:02, Anton Kholomiov wrote:
> Thanks alot!
>
> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>
>> Wow! That's exactly what I need!
>>
>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
>>
>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
>>> to see if you can find the name of the card.
>>>
>>>
>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>> Thanks Guillermo I will investigate the options.
>>>>
>>>> Do you think that JACK for midi is more appropriate?
>>>> I have never tried it with Csound
>>>>
>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>>>>
>>>>> Hi Anton,
>>>>>
>>>>> Off the top of my head I can think of:
>>>>>
>>>>> * Using JACK for midi?
>>>>>
>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>
>>>>> * Using raw MIDI instead of alsaseq.
>>>>>
>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>> connection with aconnect.
>>>>>
>>>>> Cheers.
>>>>>
>>>>>
>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>> Is it possible for example to connect to device by it's name
>>>>>> instead of id?
>>>>>>
>>>>>>
>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov >>> :
>>>>>>> Can you help me?
>>>>>>>
>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>> I use alsa sequencer midi driver.
>>>>>>>
>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>> the identifiers for MIDI devices.
>>>>>>>
>>>>>>> But in Csound I have to specify the precise number.
>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>> So I have to change the device IDs for all files.
>>>>>>>
>>>>>>> Do you know some trick to connect Csound with
>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>
>>>>>>> Thanks!
>>>>>>> Anton
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>>
>>
> 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

Date2017-07-13 22:14
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Alas it's not working for me. I've tried

-M'UMX 250'

And it says

ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)

2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Thanks alot!

2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Wow! That's exactly what I need!

2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Scratch that. I've tried alsaseq and this one worked for me: csound
-+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
to see if you can find the name of the card.


On 13/07/17 17:47, Anton Kholomiov wrote:
> Thanks Guillermo I will investigate the options.
>
> Do you think that JACK for midi is more appropriate?
> I have never tried it with Csound
>
> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>
>> Hi Anton,
>>
>> Off the top of my head I can think of:
>>
>> * Using JACK for midi?
>>
>> * Fixing the assignments somehow. If it's USB something like:
>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>
>> * Using raw MIDI instead of alsaseq.
>>
>> * Calling a (non-portable) bash script with system_i and fixing the
>> connection with aconnect.
>>
>> Cheers.
>>
>>
>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>> Is it possible for example to connect to device by it's name
>>> instead of id?
>>>
>>>
>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>
>>>> Can you help me?
>>>>
>>>> I use many csound files as MIDI-synthesizers.
>>>> I use alsa sequencer midi driver.
>>>>
>>>> Recently I've run into problem with MIDI device IDs.
>>>> I've changed the audio card and now it has midi in/outs
>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>> And when I plug them my PC seems to randomly switch
>>>> the identifiers for MIDI devices.
>>>>
>>>> But in Csound I have to specify the precise number.
>>>> And sometimes it's not the number that  ALSA gives
>>>> to my MIDI-keyboard on the next PC start.
>>>> So I have to change the device IDs for all files.
>>>>
>>>> Do you know some trick to connect Csound with
>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>
>>>> Thanks!
>>>> Anton
>>>>
>>>>
>>>>
>>> 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
>>
> 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



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

Date2017-07-13 22:14
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
It's on my list as follows

client 32: 'UMX 250' [type=kernel,card=4]
    0 'UMX 250 MIDI 1  '
    Connecting To: 128:0[real:0], 130:0
    Connected From: 128:0

2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Alas it's not working for me. I've tried

-M'UMX 250'

And it says

ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)

2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Thanks alot!

2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Wow! That's exactly what I need!

2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Scratch that. I've tried alsaseq and this one worked for me: csound
-+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
to see if you can find the name of the card.


On 13/07/17 17:47, Anton Kholomiov wrote:
> Thanks Guillermo I will investigate the options.
>
> Do you think that JACK for midi is more appropriate?
> I have never tried it with Csound
>
> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>
>> Hi Anton,
>>
>> Off the top of my head I can think of:
>>
>> * Using JACK for midi?
>>
>> * Fixing the assignments somehow. If it's USB something like:
>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>
>> * Using raw MIDI instead of alsaseq.
>>
>> * Calling a (non-portable) bash script with system_i and fixing the
>> connection with aconnect.
>>
>> Cheers.
>>
>>
>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>> Is it possible for example to connect to device by it's name
>>> instead of id?
>>>
>>>
>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>
>>>> Can you help me?
>>>>
>>>> I use many csound files as MIDI-synthesizers.
>>>> I use alsa sequencer midi driver.
>>>>
>>>> Recently I've run into problem with MIDI device IDs.
>>>> I've changed the audio card and now it has midi in/outs
>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>> And when I plug them my PC seems to randomly switch
>>>> the identifiers for MIDI devices.
>>>>
>>>> But in Csound I have to specify the precise number.
>>>> And sometimes it's not the number that  ALSA gives
>>>> to my MIDI-keyboard on the next PC start.
>>>> So I have to change the device IDs for all files.
>>>>
>>>> Do you know some trick to connect Csound with
>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>
>>>> Thanks!
>>>> Anton
>>>>
>>>>
>>>>
>>> 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
>>
> 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




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

Date2017-07-13 22:25
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:

client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
    0 'Scarlett 2i4 USB MIDI 1'
    Connecting To: 128:0[real:0]
    Connected From: 128:0

I can't imagine why it would work for me, but not for you. My libasound2
version is 1.1.3-5.


On 13/07/17 18:14, Anton Kholomiov wrote:
> It's on my list as follows
>
> client 32: 'UMX 250' [type=kernel,card=4]
>     0 'UMX 250 MIDI 1  '
>     Connecting To: 128:0[real:0], 130:0
>     Connected From: 128:0
>
> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov :
>
>> Alas it's not working for me. I've tried
>>
>> -M'UMX 250'
>>
>> And it says
>>
>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)
>>
>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>
>>> Thanks alot!
>>>
>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>>
>>>> Wow! That's exactly what I need!
>>>>
>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
>>>>
>>>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
>>>>> to see if you can find the name of the card.
>>>>>
>>>>>
>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>
>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>> I have never tried it with Csound
>>>>>>
>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>>>>>>
>>>>>>> Hi Anton,
>>>>>>>
>>>>>>> Off the top of my head I can think of:
>>>>>>>
>>>>>>> * Using JACK for midi?
>>>>>>>
>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>
>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>
>>>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>>>> connection with aconnect.
>>>>>>>
>>>>>>> Cheers.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>> instead of id?
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>> Can you help me?
>>>>>>>>>
>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>
>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>
>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>
>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>> Anton
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> 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
>>>>>>>
>>>>>> 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
>>>>>
>>>>
> 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

Date2017-07-13 22:34
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
I'm using Csound 6.09. Not sure on the version of libasound2

2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:

client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
    0 'Scarlett 2i4 USB MIDI 1'
    Connecting To: 128:0[real:0]
    Connected From: 128:0

I can't imagine why it would work for me, but not for you. My libasound2
version is 1.1.3-5.


On 13/07/17 18:14, Anton Kholomiov wrote:
> It's on my list as follows
>
> client 32: 'UMX 250' [type=kernel,card=4]
>     0 'UMX 250 MIDI 1  '
>     Connecting To: 128:0[real:0], 130:0
>     Connected From: 128:0
>
> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>
>> Alas it's not working for me. I've tried
>>
>> -M'UMX 250'
>>
>> And it says
>>
>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)
>>
>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>
>>> Thanks alot!
>>>
>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>
>>>> Wow! That's exactly what I need!
>>>>
>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>
>>>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect -l"
>>>>> to see if you can find the name of the card.
>>>>>
>>>>>
>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>
>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>> I have never tried it with Csound
>>>>>>
>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>
>>>>>>> Hi Anton,
>>>>>>>
>>>>>>> Off the top of my head I can think of:
>>>>>>>
>>>>>>> * Using JACK for midi?
>>>>>>>
>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>
>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>
>>>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>>>> connection with aconnect.
>>>>>>>
>>>>>>> Cheers.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>> instead of id?
>>>>>>>>
>>>>>>>>
>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>> Can you help me?
>>>>>>>>>
>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>
>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>
>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>
>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>> Anton
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> 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
>>>>>>>
>>>>>> 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
>>>>>
>>>>
> 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

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

Date2017-07-13 22:49
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
apt-cache show libasound2 | grep Version

Although I doubt that's what's happening. Maybe you could try connecting
first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
-M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
check if the connection is made.


On 13/07/17 18:34, Anton Kholomiov wrote:
> I'm using Csound 6.09. Not sure on the version of libasound2
>
> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
>
>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>
>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>     0 'Scarlett 2i4 USB MIDI 1'
>>     Connecting To: 128:0[real:0]
>>     Connected From: 128:0
>>
>> I can't imagine why it would work for me, but not for you. My libasound2
>> version is 1.1.3-5.
>>
>>
>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>> It's on my list as follows
>>>
>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>     0 'UMX 250 MIDI 1  '
>>>     Connecting To: 128:0[real:0], 130:0
>>>     Connected From: 128:0
>>>
>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov :
>>>
>>>> Alas it's not working for me. I've tried
>>>>
>>>> -M'UMX 250'
>>>>
>>>> And it says
>>>>
>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)
>>>>
>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>>>
>>>>> Thanks alot!
>>>>>
>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>>>>
>>>>>> Wow! That's exactly what I need!
>>>>>>
>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
>>>>>>
>>>>>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect
>> -l"
>>>>>>> to see if you can find the name of the card.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>
>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>> I have never tried it with Csound
>>>>>>>>
>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>>>>>>>>
>>>>>>>>> Hi Anton,
>>>>>>>>>
>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>
>>>>>>>>> * Using JACK for midi?
>>>>>>>>>
>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>
>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>
>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>>>>>> connection with aconnect.
>>>>>>>>>
>>>>>>>>> Cheers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>> instead of id?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>> Can you help me?
>>>>>>>>>>>
>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>
>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>
>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>
>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>> Anton
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>> 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
>>>>>>>
>>> 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
>>
> 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

Date2017-07-13 22:50
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
if aconnect can't do it, it's alsaseq and your card. Otherwise it is
probably Csound.


On 13/07/17 18:49, Guillermo Senna wrote:
> apt-cache show libasound2 | grep Version
>
> Although I doubt that's what's happening. Maybe you could try connecting
> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> check if the connection is made.
>
>
> On 13/07/17 18:34, Anton Kholomiov wrote:
>> I'm using Csound 6.09. Not sure on the version of libasound2
>>
>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
>>
>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>
>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>     Connecting To: 128:0[real:0]
>>>     Connected From: 128:0
>>>
>>> I can't imagine why it would work for me, but not for you. My libasound2
>>> version is 1.1.3-5.
>>>
>>>
>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>> It's on my list as follows
>>>>
>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>     0 'UMX 250 MIDI 1  '
>>>>     Connecting To: 128:0[real:0], 130:0
>>>>     Connected From: 128:0
>>>>
>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov :
>>>>
>>>>> Alas it's not working for me. I've tried
>>>>>
>>>>> -M'UMX 250'
>>>>>
>>>>> And it says
>>>>>
>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)
>>>>>
>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>>>>
>>>>>> Thanks alot!
>>>>>>
>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov :
>>>>>>
>>>>>>> Wow! That's exactly what I need!
>>>>>>>
>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
>>>>>>>
>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect
>>> -l"
>>>>>>>> to see if you can find the name of the card.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>
>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>> I have never tried it with Csound
>>>>>>>>>
>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>>>>>>>>>
>>>>>>>>>> Hi Anton,
>>>>>>>>>>
>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>
>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>
>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>
>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>
>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>>>>>>> connection with aconnect.
>>>>>>>>>>
>>>>>>>>>> Cheers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>> instead of id?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>
>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>
>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>
>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>
>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>> Anton
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>
>>>> 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
>>>
>> 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

Date2017-07-14 01:08
FromForrest Curo
SubjectRe: Stable and predictable MIDI connection with ALSA
I think that alsa is not always consistent with how it assigns midi ports after reboot.

On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
if aconnect can't do it, it's alsaseq and your card. Otherwise it is
probably Csound.


On 13/07/17 18:49, Guillermo Senna wrote:
> apt-cache show libasound2 | grep Version
>
> Although I doubt that's what's happening. Maybe you could try connecting
> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> check if the connection is made.
>
>
> On 13/07/17 18:34, Anton Kholomiov wrote:
>> I'm using Csound 6.09. Not sure on the version of libasound2
>>
>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>
>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>
>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>     Connecting To: 128:0[real:0]
>>>     Connected From: 128:0
>>>
>>> I can't imagine why it would work for me, but not for you. My libasound2
>>> version is 1.1.3-5.
>>>
>>>
>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>> It's on my list as follows
>>>>
>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>     0 'UMX 250 MIDI 1  '
>>>>     Connecting To: 128:0[real:0], 130:0
>>>>     Connected From: 128:0
>>>>
>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>>
>>>>> Alas it's not working for me. I've tried
>>>>>
>>>>> -M'UMX 250'
>>>>>
>>>>> And it says
>>>>>
>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)
>>>>>
>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>>>
>>>>>> Thanks alot!
>>>>>>
>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>>>>
>>>>>>> Wow! That's exactly what I need!
>>>>>>>
>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>
>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me: csound
>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of "aconnect
>>> -l"
>>>>>>>> to see if you can find the name of the card.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>
>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>> I have never tried it with Csound
>>>>>>>>>
>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Hi Anton,
>>>>>>>>>>
>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>
>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>
>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>
>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>
>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing the
>>>>>>>>>> connection with aconnect.
>>>>>>>>>>
>>>>>>>>>> Cheers.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>> instead of id?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>
>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>
>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>
>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>
>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>> Anton
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>
>>>> 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
>>>
>> 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

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

Date2017-07-14 03:16
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
That's correct. But we were trying to make the connection by name.


On 13/07/17 21:08, Forrest Curo wrote:
> I think that alsa is not always consistent with how it assigns midi ports
> after reboot.
>
> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna  wrote:
>
>> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
>> probably Csound.
>>
>>
>> On 13/07/17 18:49, Guillermo Senna wrote:
>>> apt-cache show libasound2 | grep Version
>>>
>>> Although I doubt that's what's happening. Maybe you could try connecting
>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>> check if the connection is made.
>>>
>>>
>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>
>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
>>>>
>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>>>
>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>     Connecting To: 128:0[real:0]
>>>>>     Connected From: 128:0
>>>>>
>>>>> I can't imagine why it would work for me, but not for you. My
>> libasound2
>>>>> version is 1.1.3-5.
>>>>>
>>>>>
>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>> It's on my list as follows
>>>>>>
>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>     Connected From: 128:0
>>>>>>
>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov >> :
>>>>>>> Alas it's not working for me. I've tried
>>>>>>>
>>>>>>> -M'UMX 250'
>>>>>>>
>>>>>>> And it says
>>>>>>>
>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>> permitted)
>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov >> :
>>>>>>>> Thanks alot!
>>>>>>>>
>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>> anton.kholomiov@gmail.com>:
>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
>>>>>>>>>
>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
>> csound
>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>> "aconnect
>>>>> -l"
>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>
>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
>>>>>>>>>>>
>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>
>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>
>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>
>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>
>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>
>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
>> the
>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>
> 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

Date2017-07-14 09:31
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Although I doubt that's what's happening. Maybe you could try connecting
first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
-M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
check if the connection is made.

This recipe works!

Maybe I need to update Csound to the very latest version... to work it directly
But atleast I have some predictable way to to it now.

 

2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
That's correct. But we were trying to make the connection by name.


On 13/07/17 21:08, Forrest Curo wrote:
> I think that alsa is not always consistent with how it assigns midi ports
> after reboot.
>
> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
>
>> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
>> probably Csound.
>>
>>
>> On 13/07/17 18:49, Guillermo Senna wrote:
>>> apt-cache show libasound2 | grep Version
>>>
>>> Although I doubt that's what's happening. Maybe you could try connecting
>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>> check if the connection is made.
>>>
>>>
>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>
>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>
>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>>>
>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>     Connecting To: 128:0[real:0]
>>>>>     Connected From: 128:0
>>>>>
>>>>> I can't imagine why it would work for me, but not for you. My
>> libasound2
>>>>> version is 1.1.3-5.
>>>>>
>>>>>
>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>> It's on my list as follows
>>>>>>
>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>     Connected From: 128:0
>>>>>>
>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>> Alas it's not working for me. I've tried
>>>>>>>
>>>>>>> -M'UMX 250'
>>>>>>>
>>>>>>> And it says
>>>>>>>
>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>> permitted)
>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>>> Thanks alot!
>>>>>>>>
>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>> anton.kholomiov@gmail.com>:
>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
>> csound
>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>> "aconnect
>>>>> -l"
>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>
>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>
>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>
>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>
>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>
>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>
>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
>> the
>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>
> 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

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

Date2017-07-14 10:49
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
I think it's have to do with interpretation of unary quotes ' ' on my system 
Unfortunately when I try to automize your solution whenever I try to
execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language

I get error on

invalid sender address 'UMX

But with plain integers it works

aconnect 28 129

2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Although I doubt that's what's happening. Maybe you could try connecting
first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
-M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
check if the connection is made.

This recipe works!

Maybe I need to update Csound to the very latest version... to work it directly
But atleast I have some predictable way to to it now.

 

2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
That's correct. But we were trying to make the connection by name.


On 13/07/17 21:08, Forrest Curo wrote:
> I think that alsa is not always consistent with how it assigns midi ports
> after reboot.
>
> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
>
>> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
>> probably Csound.
>>
>>
>> On 13/07/17 18:49, Guillermo Senna wrote:
>>> apt-cache show libasound2 | grep Version
>>>
>>> Although I doubt that's what's happening. Maybe you could try connecting
>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>> check if the connection is made.
>>>
>>>
>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>
>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>
>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>>>
>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>     Connecting To: 128:0[real:0]
>>>>>     Connected From: 128:0
>>>>>
>>>>> I can't imagine why it would work for me, but not for you. My
>> libasound2
>>>>> version is 1.1.3-5.
>>>>>
>>>>>
>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>> It's on my list as follows
>>>>>>
>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>     Connected From: 128:0
>>>>>>
>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>> Alas it's not working for me. I've tried
>>>>>>>
>>>>>>> -M'UMX 250'
>>>>>>>
>>>>>>> And it says
>>>>>>>
>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>> permitted)
>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>>> Thanks alot!
>>>>>>>>
>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>> anton.kholomiov@gmail.com>:
>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
>> csound
>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>> "aconnect
>>>>> -l"
>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>
>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>
>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>
>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>
>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>
>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>
>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
>> the
>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>
> 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


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

Date2017-07-14 11:10
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
but I don't have the way to automate this process..

2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
I think it's have to do with interpretation of unary quotes ' ' on my system 
Unfortunately when I try to automize your solution whenever I try to
execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language

I get error on

invalid sender address 'UMX

But with plain integers it works

aconnect 28 129

2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Although I doubt that's what's happening. Maybe you could try connecting
first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
-M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
check if the connection is made.

This recipe works!

Maybe I need to update Csound to the very latest version... to work it directly
But atleast I have some predictable way to to it now.

 

2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
That's correct. But we were trying to make the connection by name.


On 13/07/17 21:08, Forrest Curo wrote:
> I think that alsa is not always consistent with how it assigns midi ports
> after reboot.
>
> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
>
>> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
>> probably Csound.
>>
>>
>> On 13/07/17 18:49, Guillermo Senna wrote:
>>> apt-cache show libasound2 | grep Version
>>>
>>> Although I doubt that's what's happening. Maybe you could try connecting
>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>> check if the connection is made.
>>>
>>>
>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>
>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>
>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
>>>>>
>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>     Connecting To: 128:0[real:0]
>>>>>     Connected From: 128:0
>>>>>
>>>>> I can't imagine why it would work for me, but not for you. My
>> libasound2
>>>>> version is 1.1.3-5.
>>>>>
>>>>>
>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>> It's on my list as follows
>>>>>>
>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>     Connected From: 128:0
>>>>>>
>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>> Alas it's not working for me. I've tried
>>>>>>>
>>>>>>> -M'UMX 250'
>>>>>>>
>>>>>>> And it says
>>>>>>>
>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>> permitted)
>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>> :
>>>>>>>> Thanks alot!
>>>>>>>>
>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>> anton.kholomiov@gmail.com>:
>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
>> csound
>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>> "aconnect
>>>>> -l"
>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>
>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>
>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>
>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>
>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>
>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>
>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
>> the
>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>> Is it possible for example to connect to device by it's name
>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>
> 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



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

Date2017-07-14 11:14
FromVictor Lazzarini
SubjectRe: Stable and predictable MIDI connection with ALSA
did you try this script?

#!/usr/sh
csound … & aconnect ‘UMX 250’ ‘Csound’


========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 14 Jul 2017, at 11:10, Anton Kholomiov  wrote:
> 
> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> but I don't have the way to automate this process..
> 
> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov :
> I think it's have to do with interpretation of unary quotes ' ' on my system  
> Unfortunately when I try to automize your solution whenever I try to
> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
> 
> I get error on 
> 
> invalid sender address 'UMX
> 
> But with plain integers it works
> 
> aconnect 28 129
> 
> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov :
> Although I doubt that's what's happening. Maybe you could try connecting
> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> check if the connection is made.
> 
> This recipe works!
> 
> Maybe I need to update Csound to the very latest version... to work it directly
> But atleast I have some predictable way to to it now.
> 
>  
> 
> 2017-07-14 5:16 GMT+03:00 Guillermo Senna :
> That's correct. But we were trying to make the connection by name.
> 
> 
> On 13/07/17 21:08, Forrest Curo wrote:
> > I think that alsa is not always consistent with how it assigns midi ports
> > after reboot.
> >
> > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna  wrote:
> >
> >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> >> probably Csound.
> >>
> >>
> >> On 13/07/17 18:49, Guillermo Senna wrote:
> >>> apt-cache show libasound2 | grep Version
> >>>
> >>> Although I doubt that's what's happening. Maybe you could try connecting
> >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> >>> check if the connection is made.
> >>>
> >>>
> >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> >>>>
> >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
> >>>>
> >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> >>>>>
> >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> >>>>>     Connecting To: 128:0[real:0]
> >>>>>     Connected From: 128:0
> >>>>>
> >>>>> I can't imagine why it would work for me, but not for you. My
> >> libasound2
> >>>>> version is 1.1.3-5.
> >>>>>
> >>>>>
> >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> >>>>>> It's on my list as follows
> >>>>>>
> >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> >>>>>>     0 'UMX 250 MIDI 1  '
> >>>>>>     Connecting To: 128:0[real:0], 130:0
> >>>>>>     Connected From: 128:0
> >>>>>>
> >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov  >>> :
> >>>>>>> Alas it's not working for me. I've tried
> >>>>>>>
> >>>>>>> -M'UMX 250'
> >>>>>>>
> >>>>>>> And it says
> >>>>>>>
> >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> >> permitted)
> >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov  >>> :
> >>>>>>>> Thanks alot!
> >>>>>>>>
> >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> >> anton.kholomiov@gmail.com>:
> >>>>>>>>> Wow! That's exactly what I need!
> >>>>>>>>>
> >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
> >>>>>>>>>
> >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> >> csound
> >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> >> "aconnect
> >>>>> -l"
> >>>>>>>>>> to see if you can find the name of the card.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> >>>>>>>>>>>
> >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> >>>>>>>>>>> I have never tried it with Csound
> >>>>>>>>>>>
> >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi Anton,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Off the top of my head I can think of:
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using JACK for midi?
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> >> the
> >>>>>>>>>>>> connection with aconnect.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> >>>>>>>>>>>>> instead of id?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> >>>>>>>>>> anton.kholomiov@gmail.com>:
> >>>>>>>>>>>>>> Can you help me?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> >>>>>>>>>>>>>> the identifiers for MIDI devices.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>> Anton
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>> 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
> >>>>>>>>>>>>
> >>>>>>>>>>> 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
> >>>>>>>>>>
> >>>>>> 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
> >>>>>
> >>>> 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
> >>
> > 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
> 
> 
> 
> 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

Date2017-07-14 11:23
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
It gives the same error:

> sh 00-dream-pad.sh
invalid sender address ‘UMX
... csound output...


Script content:

#!/usr/sh
csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’


2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
did you try this script?

#!/usr/sh
csound … & aconnect ‘UMX 250’ ‘Csound’


========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
>
> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> but I don't have the way to automate this process..
>
> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> I think it's have to do with interpretation of unary quotes ' ' on my system
> Unfortunately when I try to automize your solution whenever I try to
> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
>
> I get error on
>
> invalid sender address 'UMX
>
> But with plain integers it works
>
> aconnect 28 129
>
> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> Although I doubt that's what's happening. Maybe you could try connecting
> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> check if the connection is made.
>
> This recipe works!
>
> Maybe I need to update Csound to the very latest version... to work it directly
> But atleast I have some predictable way to to it now.
>
>
>
> 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> That's correct. But we were trying to make the connection by name.
>
>
> On 13/07/17 21:08, Forrest Curo wrote:
> > I think that alsa is not always consistent with how it assigns midi ports
> > after reboot.
> >
> > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
> >
> >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> >> probably Csound.
> >>
> >>
> >> On 13/07/17 18:49, Guillermo Senna wrote:
> >>> apt-cache show libasound2 | grep Version
> >>>
> >>> Although I doubt that's what's happening. Maybe you could try connecting
> >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> >>> check if the connection is made.
> >>>
> >>>
> >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> >>>>
> >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>
> >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> >>>>>
> >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> >>>>>     Connecting To: 128:0[real:0]
> >>>>>     Connected From: 128:0
> >>>>>
> >>>>> I can't imagine why it would work for me, but not for you. My
> >> libasound2
> >>>>> version is 1.1.3-5.
> >>>>>
> >>>>>
> >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> >>>>>> It's on my list as follows
> >>>>>>
> >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> >>>>>>     0 'UMX 250 MIDI 1  '
> >>>>>>     Connecting To: 128:0[real:0], 130:0
> >>>>>>     Connected From: 128:0
> >>>>>>
> >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> >>> :
> >>>>>>> Alas it's not working for me. I've tried
> >>>>>>>
> >>>>>>> -M'UMX 250'
> >>>>>>>
> >>>>>>> And it says
> >>>>>>>
> >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> >> permitted)
> >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> >>> :
> >>>>>>>> Thanks alot!
> >>>>>>>>
> >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> >> anton.kholomiov@gmail.com>:
> >>>>>>>>> Wow! That's exactly what I need!
> >>>>>>>>>
> >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>>>>>>
> >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> >> csound
> >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> >> "aconnect
> >>>>> -l"
> >>>>>>>>>> to see if you can find the name of the card.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> >>>>>>>>>>>
> >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> >>>>>>>>>>> I have never tried it with Csound
> >>>>>>>>>>>
> >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi Anton,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Off the top of my head I can think of:
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using JACK for midi?
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> >> the
> >>>>>>>>>>>> connection with aconnect.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> >>>>>>>>>>>>> instead of id?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> >>>>>>>>>> anton.kholomiov@gmail.com>:
> >>>>>>>>>>>>>> Can you help me?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> >>>>>>>>>>>>>> the identifiers for MIDI devices.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>> Anton
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>> 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
> >>>>>>>>>>>>
> >>>>>>>>>>> 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
> >>>>>>>>>>
> >>>>>> 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
> >>>>>
> >>>> 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
> >>
> > 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
>
>
>
> 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

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

Date2017-07-14 11:27
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
That's the strange why something that works when I type it doesn't work when I execute
it from script. I think it's not the question for the list.

I think it's some thing to do with the OS which is Arch.
I've tried it recently and regret my choice.
But right now I'm to lazy to switch so I'm trying to make use of it.

2017-07-14 13:23 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
It gives the same error:

> sh 00-dream-pad.sh
invalid sender address ‘UMX
... csound output...


Script content:

#!/usr/sh
csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’


2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
did you try this script?

#!/usr/sh
csound … & aconnect ‘UMX 250’ ‘Csound’


========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
>
> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> but I don't have the way to automate this process..
>
> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> I think it's have to do with interpretation of unary quotes ' ' on my system
> Unfortunately when I try to automize your solution whenever I try to
> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
>
> I get error on
>
> invalid sender address 'UMX
>
> But with plain integers it works
>
> aconnect 28 129
>
> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> Although I doubt that's what's happening. Maybe you could try connecting
> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> check if the connection is made.
>
> This recipe works!
>
> Maybe I need to update Csound to the very latest version... to work it directly
> But atleast I have some predictable way to to it now.
>
>
>
> 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> That's correct. But we were trying to make the connection by name.
>
>
> On 13/07/17 21:08, Forrest Curo wrote:
> > I think that alsa is not always consistent with how it assigns midi ports
> > after reboot.
> >
> > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
> >
> >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> >> probably Csound.
> >>
> >>
> >> On 13/07/17 18:49, Guillermo Senna wrote:
> >>> apt-cache show libasound2 | grep Version
> >>>
> >>> Although I doubt that's what's happening. Maybe you could try connecting
> >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> >>> check if the connection is made.
> >>>
> >>>
> >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> >>>>
> >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>
> >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> >>>>>
> >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> >>>>>     Connecting To: 128:0[real:0]
> >>>>>     Connected From: 128:0
> >>>>>
> >>>>> I can't imagine why it would work for me, but not for you. My
> >> libasound2
> >>>>> version is 1.1.3-5.
> >>>>>
> >>>>>
> >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> >>>>>> It's on my list as follows
> >>>>>>
> >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> >>>>>>     0 'UMX 250 MIDI 1  '
> >>>>>>     Connecting To: 128:0[real:0], 130:0
> >>>>>>     Connected From: 128:0
> >>>>>>
> >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> >>> :
> >>>>>>> Alas it's not working for me. I've tried
> >>>>>>>
> >>>>>>> -M'UMX 250'
> >>>>>>>
> >>>>>>> And it says
> >>>>>>>
> >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> >> permitted)
> >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> >>> :
> >>>>>>>> Thanks alot!
> >>>>>>>>
> >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> >> anton.kholomiov@gmail.com>:
> >>>>>>>>> Wow! That's exactly what I need!
> >>>>>>>>>
> >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>>>>>>
> >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> >> csound
> >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> >> "aconnect
> >>>>> -l"
> >>>>>>>>>> to see if you can find the name of the card.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> >>>>>>>>>>>
> >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> >>>>>>>>>>> I have never tried it with Csound
> >>>>>>>>>>>
> >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi Anton,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Off the top of my head I can think of:
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using JACK for midi?
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> >>>>>>>>>>>>
> >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> >> the
> >>>>>>>>>>>> connection with aconnect.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Cheers.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> >>>>>>>>>>>>> instead of id?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> >>>>>>>>>> anton.kholomiov@gmail.com>:
> >>>>>>>>>>>>>> Can you help me?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> >>>>>>>>>>>>>> the identifiers for MIDI devices.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>> Anton
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>> 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
> >>>>>>>>>>>>
> >>>>>>>>>>> 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
> >>>>>>>>>>
> >>>>>> 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
> >>>>>
> >>>> 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
> >>
> > 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
>
>
>
> 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


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

Date2017-07-14 11:32
FromVictor Lazzarini
SubjectRe: Stable and predictable MIDI connection with ALSA
I think it might be because the script runs it immediately after starting Csound. Maybe Csound has not
opened alsaseq in time. You can try adding a sleep:

csound … &
sleep 1
aconnect …



========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 14 Jul 2017, at 11:27, Anton Kholomiov  wrote:
> 
> That's the strange why something that works when I type it doesn't work when I execute
> it from script. I think it's not the question for the list.
> 
> I think it's some thing to do with the OS which is Arch.
> I've tried it recently and regret my choice.
> But right now I'm to lazy to switch so I'm trying to make use of it.
> 
> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov :
> It gives the same error:
> 
> > sh 00-dream-pad.sh 
> invalid sender address ‘UMX
> ... csound output...
> 
> 
> Script content:
> 
> #!/usr/sh
> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
> 
> 
> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini :
> did you try this script?
> 
> #!/usr/sh
> csound … & aconnect ‘UMX 250’ ‘Csound’
> 
> 
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 14 Jul 2017, at 11:10, Anton Kholomiov  wrote:
> >
> > If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> > but I don't have the way to automate this process..
> >
> > 2017-07-14 12:49 GMT+03:00 Anton Kholomiov :
> > I think it's have to do with interpretation of unary quotes ' ' on my system
> > Unfortunately when I try to automize your solution whenever I try to
> > execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
> >
> > I get error on
> >
> > invalid sender address 'UMX
> >
> > But with plain integers it works
> >
> > aconnect 28 129
> >
> > 2017-07-14 11:31 GMT+03:00 Anton Kholomiov :
> > Although I doubt that's what's happening. Maybe you could try connecting
> > first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > check if the connection is made.
> >
> > This recipe works!
> >
> > Maybe I need to update Csound to the very latest version... to work it directly
> > But atleast I have some predictable way to to it now.
> >
> >
> >
> > 2017-07-14 5:16 GMT+03:00 Guillermo Senna :
> > That's correct. But we were trying to make the connection by name.
> >
> >
> > On 13/07/17 21:08, Forrest Curo wrote:
> > > I think that alsa is not always consistent with how it assigns midi ports
> > > after reboot.
> > >
> > > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna  wrote:
> > >
> > >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> > >> probably Csound.
> > >>
> > >>
> > >> On 13/07/17 18:49, Guillermo Senna wrote:
> > >>> apt-cache show libasound2 | grep Version
> > >>>
> > >>> Although I doubt that's what's happening. Maybe you could try connecting
> > >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > >>> check if the connection is made.
> > >>>
> > >>>
> > >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> > >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> > >>>>
> > >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
> > >>>>
> > >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> > >>>>>
> > >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> > >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> > >>>>>     Connecting To: 128:0[real:0]
> > >>>>>     Connected From: 128:0
> > >>>>>
> > >>>>> I can't imagine why it would work for me, but not for you. My
> > >> libasound2
> > >>>>> version is 1.1.3-5.
> > >>>>>
> > >>>>>
> > >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> > >>>>>> It's on my list as follows
> > >>>>>>
> > >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> > >>>>>>     0 'UMX 250 MIDI 1  '
> > >>>>>>     Connecting To: 128:0[real:0], 130:0
> > >>>>>>     Connected From: 128:0
> > >>>>>>
> > >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov  > >>> :
> > >>>>>>> Alas it's not working for me. I've tried
> > >>>>>>>
> > >>>>>>> -M'UMX 250'
> > >>>>>>>
> > >>>>>>> And it says
> > >>>>>>>
> > >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> > >> permitted)
> > >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov  > >>> :
> > >>>>>>>> Thanks alot!
> > >>>>>>>>
> > >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> > >> anton.kholomiov@gmail.com>:
> > >>>>>>>>> Wow! That's exactly what I need!
> > >>>>>>>>>
> > >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna :
> > >>>>>>>>>
> > >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> > >> csound
> > >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> > >> "aconnect
> > >>>>> -l"
> > >>>>>>>>>> to see if you can find the name of the card.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> > >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> > >>>>>>>>>>> I have never tried it with Csound
> > >>>>>>>>>>>
> > >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna :
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Hi Anton,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Off the top of my head I can think of:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using JACK for midi?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> > >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> > >> the
> > >>>>>>>>>>>> connection with aconnect.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> > >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> > >>>>>>>>>>>>> instead of id?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> > >>>>>>>>>> anton.kholomiov@gmail.com>:
> > >>>>>>>>>>>>>> Can you help me?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> > >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> > >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> > >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> > >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> > >>>>>>>>>>>>>> the identifiers for MIDI devices.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> > >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> > >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> > >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> > >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Thanks!
> > >>>>>>>>>>>>>> Anton
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>> 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
> > >>>>>>>>>>>>
> > >>>>>>>>>>> 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
> > >>>>>>>>>>
> > >>>>>> 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
> > >>>>>
> > >>>> 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
> > >>
> > > 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
> >
> >
> >
> > 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
> 
> 
> 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

Date2017-07-14 11:37
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
I've make it work by creating a script connect_umx_csound
that just connects the Csound:

#!/usr/bin/sh
aconnect 'UMX 250' 'Csound'

And then I can run it programmatically after start of the csd and it gives no errors,

phew...

That's really strange. 



2017-07-14 13:32 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
I think it might be because the script runs it immediately after starting Csound. Maybe Csound has not
opened alsaseq in time. You can try adding a sleep:

csound … &
sleep 1
aconnect …



========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 14 Jul 2017, at 11:27, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
>
> That's the strange why something that works when I type it doesn't work when I execute
> it from script. I think it's not the question for the list.
>
> I think it's some thing to do with the OS which is Arch.
> I've tried it recently and regret my choice.
> But right now I'm to lazy to switch so I'm trying to make use of it.
>
> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> It gives the same error:
>
> > sh 00-dream-pad.sh
> invalid sender address ‘UMX
> ... csound output...
>
>
> Script content:
>
> #!/usr/sh
> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
>
>
> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
> did you try this script?
>
> #!/usr/sh
> csound … & aconnect ‘UMX 250’ ‘Csound’
>
>
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
> > On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
> >
> > If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> > but I don't have the way to automate this process..
> >
> > 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> > I think it's have to do with interpretation of unary quotes ' ' on my system
> > Unfortunately when I try to automize your solution whenever I try to
> > execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
> >
> > I get error on
> >
> > invalid sender address 'UMX
> >
> > But with plain integers it works
> >
> > aconnect 28 129
> >
> > 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> > Although I doubt that's what's happening. Maybe you could try connecting
> > first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > check if the connection is made.
> >
> > This recipe works!
> >
> > Maybe I need to update Csound to the very latest version... to work it directly
> > But atleast I have some predictable way to to it now.
> >
> >
> >
> > 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > That's correct. But we were trying to make the connection by name.
> >
> >
> > On 13/07/17 21:08, Forrest Curo wrote:
> > > I think that alsa is not always consistent with how it assigns midi ports
> > > after reboot.
> > >
> > > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
> > >
> > >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> > >> probably Csound.
> > >>
> > >>
> > >> On 13/07/17 18:49, Guillermo Senna wrote:
> > >>> apt-cache show libasound2 | grep Version
> > >>>
> > >>> Although I doubt that's what's happening. Maybe you could try connecting
> > >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > >>> check if the connection is made.
> > >>>
> > >>>
> > >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> > >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> > >>>>
> > >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>
> > >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> > >>>>>
> > >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> > >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> > >>>>>     Connecting To: 128:0[real:0]
> > >>>>>     Connected From: 128:0
> > >>>>>
> > >>>>> I can't imagine why it would work for me, but not for you. My
> > >> libasound2
> > >>>>> version is 1.1.3-5.
> > >>>>>
> > >>>>>
> > >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> > >>>>>> It's on my list as follows
> > >>>>>>
> > >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> > >>>>>>     0 'UMX 250 MIDI 1  '
> > >>>>>>     Connecting To: 128:0[real:0], 130:0
> > >>>>>>     Connected From: 128:0
> > >>>>>>
> > >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> > >>> :
> > >>>>>>> Alas it's not working for me. I've tried
> > >>>>>>>
> > >>>>>>> -M'UMX 250'
> > >>>>>>>
> > >>>>>>> And it says
> > >>>>>>>
> > >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> > >> permitted)
> > >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> > >>> :
> > >>>>>>>> Thanks alot!
> > >>>>>>>>
> > >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> > >> anton.kholomiov@gmail.com>:
> > >>>>>>>>> Wow! That's exactly what I need!
> > >>>>>>>>>
> > >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>>>>>>
> > >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> > >> csound
> > >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> > >> "aconnect
> > >>>>> -l"
> > >>>>>>>>>> to see if you can find the name of the card.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> > >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> > >>>>>>>>>>> I have never tried it with Csound
> > >>>>>>>>>>>
> > >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Hi Anton,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Off the top of my head I can think of:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using JACK for midi?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> > >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> > >> the
> > >>>>>>>>>>>> connection with aconnect.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> > >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> > >>>>>>>>>>>>> instead of id?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> > >>>>>>>>>> anton.kholomiov@gmail.com>:
> > >>>>>>>>>>>>>> Can you help me?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> > >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> > >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> > >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> > >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> > >>>>>>>>>>>>>> the identifiers for MIDI devices.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> > >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> > >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> > >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> > >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Thanks!
> > >>>>>>>>>>>>>> Anton
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>> 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
> > >>>>>>>>>>>>
> > >>>>>>>>>>> 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
> > >>>>>>>>>>
> > >>>>>> 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
> > >>>>>
> > >>>> 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
> > >>
> > > 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
> >
> >
> >
> > 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
>
>
> 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

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

Date2017-07-14 11:48
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Thanks Victor for the hint with the script!
I think I can also put in the script the jack connection commands.
That way I can get reliable jack connections without ladish sessions.

2017-07-14 13:37 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
I've make it work by creating a script connect_umx_csound
that just connects the Csound:

#!/usr/bin/sh
aconnect 'UMX 250' 'Csound'

And then I can run it programmatically after start of the csd and it gives no errors,

phew...

That's really strange. 



2017-07-14 13:32 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
I think it might be because the script runs it immediately after starting Csound. Maybe Csound has not
opened alsaseq in time. You can try adding a sleep:

csound … &
sleep 1
aconnect …



========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 14 Jul 2017, at 11:27, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
>
> That's the strange why something that works when I type it doesn't work when I execute
> it from script. I think it's not the question for the list.
>
> I think it's some thing to do with the OS which is Arch.
> I've tried it recently and regret my choice.
> But right now I'm to lazy to switch so I'm trying to make use of it.
>
> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> It gives the same error:
>
> > sh 00-dream-pad.sh
> invalid sender address ‘UMX
> ... csound output...
>
>
> Script content:
>
> #!/usr/sh
> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
>
>
> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
> did you try this script?
>
> #!/usr/sh
> csound … & aconnect ‘UMX 250’ ‘Csound’
>
>
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
> > On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com> wrote:
> >
> > If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
> > but I don't have the way to automate this process..
> >
> > 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> > I think it's have to do with interpretation of unary quotes ' ' on my system
> > Unfortunately when I try to automize your solution whenever I try to
> > execute the line: "aconnect 'UMX 250' 'Csound'" from some programming language
> >
> > I get error on
> >
> > invalid sender address 'UMX
> >
> > But with plain integers it works
> >
> > aconnect 28 129
> >
> > 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
> > Although I doubt that's what's happening. Maybe you could try connecting
> > first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > check if the connection is made.
> >
> > This recipe works!
> >
> > Maybe I need to update Csound to the very latest version... to work it directly
> > But atleast I have some predictable way to to it now.
> >
> >
> >
> > 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > That's correct. But we were trying to make the connection by name.
> >
> >
> > On 13/07/17 21:08, Forrest Curo wrote:
> > > I think that alsa is not always consistent with how it assigns midi ports
> > > after reboot.
> > >
> > > On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com> wrote:
> > >
> > >> if aconnect can't do it, it's alsaseq and your card. Otherwise it is
> > >> probably Csound.
> > >>
> > >>
> > >> On 13/07/17 18:49, Guillermo Senna wrote:
> > >>> apt-cache show libasound2 | grep Version
> > >>>
> > >>> Although I doubt that's what's happening. Maybe you could try connecting
> > >>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
> > >>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
> > >>> check if the connection is made.
> > >>>
> > >>>
> > >>> On 13/07/17 18:34, Anton Kholomiov wrote:
> > >>>> I'm using Csound 6.09. Not sure on the version of libasound2
> > >>>>
> > >>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>
> > >>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l says:
> > >>>>>
> > >>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
> > >>>>>     0 'Scarlett 2i4 USB MIDI 1'
> > >>>>>     Connecting To: 128:0[real:0]
> > >>>>>     Connected From: 128:0
> > >>>>>
> > >>>>> I can't imagine why it would work for me, but not for you. My
> > >> libasound2
> > >>>>> version is 1.1.3-5.
> > >>>>>
> > >>>>>
> > >>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
> > >>>>>> It's on my list as follows
> > >>>>>>
> > >>>>>> client 32: 'UMX 250' [type=kernel,card=4]
> > >>>>>>     0 'UMX 250 MIDI 1  '
> > >>>>>>     Connecting To: 128:0[real:0], 130:0
> > >>>>>>     Connected From: 128:0
> > >>>>>>
> > >>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> > >>> :
> > >>>>>>> Alas it's not working for me. I've tried
> > >>>>>>>
> > >>>>>>> -M'UMX 250'
> > >>>>>>>
> > >>>>>>> And it says
> > >>>>>>>
> > >>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
> > >> permitted)
> > >>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
> > >>> :
> > >>>>>>>> Thanks alot!
> > >>>>>>>>
> > >>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
> > >> anton.kholomiov@gmail.com>:
> > >>>>>>>>> Wow! That's exactly what I need!
> > >>>>>>>>>
> > >>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>>>>>>
> > >>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for me:
> > >> csound
> > >>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
> > >> "aconnect
> > >>>>> -l"
> > >>>>>>>>>> to see if you can find the name of the card.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
> > >>>>>>>>>>> Thanks Guillermo I will investigate the options.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Do you think that JACK for midi is more appropriate?
> > >>>>>>>>>>> I have never tried it with Csound
> > >>>>>>>>>>>
> > >>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> Hi Anton,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Off the top of my head I can think of:
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using JACK for midi?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something like:
> > >>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and fixing
> > >> the
> > >>>>>>>>>>>> connection with aconnect.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Cheers.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
> > >>>>>>>>>>>>> Is it possible for example to connect to device by it's name
> > >>>>>>>>>>>>> instead of id?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
> > >>>>>>>>>> anton.kholomiov@gmail.com>:
> > >>>>>>>>>>>>>> Can you help me?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
> > >>>>>>>>>>>>>> I use alsa sequencer midi driver.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
> > >>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
> > >>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
> > >>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
> > >>>>>>>>>>>>>> the identifiers for MIDI devices.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> But in Csound I have to specify the precise number.
> > >>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
> > >>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
> > >>>>>>>>>>>>>> So I have to change the device IDs for all files.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Do you know some trick to connect Csound with
> > >>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Thanks!
> > >>>>>>>>>>>>>> Anton
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>> 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
> > >>>>>>>>>>>>
> > >>>>>>>>>>> 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
> > >>>>>>>>>>
> > >>>>>> 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
> > >>>>>
> > >>>> 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
> > >>
> > > 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
> >
> >
> >
> > 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
>
>
> 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


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

Date2017-07-14 13:26
FromGuillermo Senna
SubjectRe: Stable and predictable MIDI connection with ALSA
Just for the record, Anton, could you try running Csound with the
following options? All of these work for me.

csound -+rtmidi=alsaseq -M"UMX 250"

csound -+rtmidi=alsaseq -M"UMX\ 250"

csound -+rtmidi=alsaseq -MUMX\ 250

We obviously weren't reading the error message correctly. It is clear
that the problem (as usual) was the quotes and then the space between
UMX and 250:

ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)



On 14/07/17 07:48, Anton Kholomiov wrote:
> Thanks Victor for the hint with the script!
> I think I can also put in the script the jack connection commands.
> That way I can get reliable jack connections without ladish sessions.
>
> 2017-07-14 13:37 GMT+03:00 Anton Kholomiov :
>
>> I've make it work by creating a script connect_umx_csound
>> that just connects the Csound:
>>
>> #!/usr/bin/sh
>> aconnect 'UMX 250' 'Csound'
>>
>> And then I can run it programmatically after start of the csd and it gives
>> no errors,
>>
>> phew...
>>
>> That's really strange.
>>
>>
>>
>> 2017-07-14 13:32 GMT+03:00 Victor Lazzarini :
>>
>>> I think it might be because the script runs it immediately after starting
>>> Csound. Maybe Csound has not
>>> opened alsaseq in time. You can try adding a sleep:
>>>
>>> csound … &
>>> sleep 1
>>> aconnect …
>>>
>>>
>>>
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 14 Jul 2017, at 11:27, Anton Kholomiov 
>>> wrote:
>>>> That's the strange why something that works when I type it doesn't work
>>> when I execute
>>>> it from script. I think it's not the question for the list.
>>>>
>>>> I think it's some thing to do with the OS which is Arch.
>>>> I've tried it recently and regret my choice.
>>>> But right now I'm to lazy to switch so I'm trying to make use of it.
>>>>
>>>> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov :
>>>> It gives the same error:
>>>>
>>>>> sh 00-dream-pad.sh
>>>> invalid sender address ‘UMX
>>>> ... csound output...
>>>>
>>>>
>>>> Script content:
>>>>
>>>> #!/usr/sh
>>>> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini :
>>>> did you try this script?
>>>>
>>>> #!/usr/sh
>>>> csound … & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 14 Jul 2017, at 11:10, Anton Kholomiov 
>>> wrote:
>>>>> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
>>>>> but I don't have the way to automate this process..
>>>>>
>>>>> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov >>> :
>>>>> I think it's have to do with interpretation of unary quotes ' ' on my
>>> system
>>>>> Unfortunately when I try to automize your solution whenever I try to
>>>>> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming
>>> language
>>>>> I get error on
>>>>>
>>>>> invalid sender address 'UMX
>>>>>
>>>>> But with plain integers it works
>>>>>
>>>>> aconnect 28 129
>>>>>
>>>>> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov >>> :
>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>>>> check if the connection is made.
>>>>>
>>>>> This recipe works!
>>>>>
>>>>> Maybe I need to update Csound to the very latest version... to work
>>> it directly
>>>>> But atleast I have some predictable way to to it now.
>>>>>
>>>>>
>>>>>
>>>>> 2017-07-14 5:16 GMT+03:00 Guillermo Senna :
>>>>> That's correct. But we were trying to make the connection by name.
>>>>>
>>>>>
>>>>> On 13/07/17 21:08, Forrest Curo wrote:
>>>>>> I think that alsa is not always consistent with how it assigns midi
>>> ports
>>>>>> after reboot.
>>>>>>
>>>>>> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna 
>>> wrote:
>>>>>>> if aconnect can't do it, it's alsaseq and your card. Otherwise it
>>> is
>>>>>>> probably Csound.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 18:49, Guillermo Senna wrote:
>>>>>>>> apt-cache show libasound2 | grep Version
>>>>>>>>
>>>>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>>>>> first to the Midi Through port (in my case, csound
>>> -+rtmidi=alsaseq
>>>>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'.
>>> Then
>>>>>>>> check if the connection is made.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>>>>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna :
>>>>>>>>>
>>>>>>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l
>>> says:
>>>>>>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>>>>>>     Connecting To: 128:0[real:0]
>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>
>>>>>>>>>> I can't imagine why it would work for me, but not for you. My
>>>>>>> libasound2
>>>>>>>>>> version is 1.1.3-5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>>>>>>> It's on my list as follows
>>>>>>>>>>>
>>>>>>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>> Alas it's not working for me. I've tried
>>>>>>>>>>>>
>>>>>>>>>>>> -M'UMX 250'
>>>>>>>>>>>>
>>>>>>>>>>>> And it says
>>>>>>>>>>>>
>>>>>>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>>>>>>> permitted)
>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>>> Thanks alot!
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna >>> :
>>>>>>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for
>>> me:
>>>>>>> csound
>>>>>>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>>>>>>> "aconnect
>>>>>>>>>> -l"
>>>>>>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <
>>> gsenna@gmail.com>:
>>>>>>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something
>>> like:
>>>>>>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and
>>> fixing
>>>>>>> the
>>>>>>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>>>> Is it possible for example to connect to device by it's
>>> name
>>>>>>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> 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
>>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> 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
>>>>
>>>>
>>>> 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
>>>
>>
> 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

Date2017-07-14 13:55
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
Ok, finally

This way it works:

-+rtmidi=alsaseq --midi-device="UMX 250"

BUT:

This way

--midi-device="UMX 250"  -+rtmidi=alsaseq

It says:

Unknown RawMidi UMX 250

I think it's not good when the order of flags matter.



2017-07-14 15:26 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Just for the record, Anton, could you try running Csound with the
following options? All of these work for me.

csound -+rtmidi=alsaseq -M"UMX 250"

csound -+rtmidi=alsaseq -M"UMX\ 250"

csound -+rtmidi=alsaseq -MUMX\ 250

We obviously weren't reading the error message correctly. It is clear
that the problem (as usual) was the quotes and then the space between
UMX and 250:

ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)



On 14/07/17 07:48, Anton Kholomiov wrote:
> Thanks Victor for the hint with the script!
> I think I can also put in the script the jack connection commands.
> That way I can get reliable jack connections without ladish sessions.
>
> 2017-07-14 13:37 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>
>> I've make it work by creating a script connect_umx_csound
>> that just connects the Csound:
>>
>> #!/usr/bin/sh
>> aconnect 'UMX 250' 'Csound'
>>
>> And then I can run it programmatically after start of the csd and it gives
>> no errors,
>>
>> phew...
>>
>> That's really strange.
>>
>>
>>
>> 2017-07-14 13:32 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
>>
>>> I think it might be because the script runs it immediately after starting
>>> Csound. Maybe Csound has not
>>> opened alsaseq in time. You can try adding a sleep:
>>>
>>> csound … &
>>> sleep 1
>>> aconnect …
>>>
>>>
>>>
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 14 Jul 2017, at 11:27, Anton Kholomiov <anton.kholomiov@gmail.com>
>>> wrote:
>>>> That's the strange why something that works when I type it doesn't work
>>> when I execute
>>>> it from script. I think it's not the question for the list.
>>>>
>>>> I think it's some thing to do with the OS which is Arch.
>>>> I've tried it recently and regret my choice.
>>>> But right now I'm to lazy to switch so I'm trying to make use of it.
>>>>
>>>> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>> It gives the same error:
>>>>
>>>>> sh 00-dream-pad.sh
>>>> invalid sender address ‘UMX
>>>> ... csound output...
>>>>
>>>>
>>>> Script content:
>>>>
>>>> #!/usr/sh
>>>> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
>>>> did you try this script?
>>>>
>>>> #!/usr/sh
>>>> csound … & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com>
>>> wrote:
>>>>> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
>>>>> but I don't have the way to automate this process..
>>>>>
>>>>> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>>> :
>>>>> I think it's have to do with interpretation of unary quotes ' ' on my
>>> system
>>>>> Unfortunately when I try to automize your solution whenever I try to
>>>>> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming
>>> language
>>>>> I get error on
>>>>>
>>>>> invalid sender address 'UMX
>>>>>
>>>>> But with plain integers it works
>>>>>
>>>>> aconnect 28 129
>>>>>
>>>>> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>>> :
>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>>>> check if the connection is made.
>>>>>
>>>>> This recipe works!
>>>>>
>>>>> Maybe I need to update Csound to the very latest version... to work
>>> it directly
>>>>> But atleast I have some predictable way to to it now.
>>>>>
>>>>>
>>>>>
>>>>> 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>> That's correct. But we were trying to make the connection by name.
>>>>>
>>>>>
>>>>> On 13/07/17 21:08, Forrest Curo wrote:
>>>>>> I think that alsa is not always consistent with how it assigns midi
>>> ports
>>>>>> after reboot.
>>>>>>
>>>>>> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com>
>>> wrote:
>>>>>>> if aconnect can't do it, it's alsaseq and your card. Otherwise it
>>> is
>>>>>>> probably Csound.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 18:49, Guillermo Senna wrote:
>>>>>>>> apt-cache show libasound2 | grep Version
>>>>>>>>
>>>>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>>>>> first to the Midi Through port (in my case, csound
>>> -+rtmidi=alsaseq
>>>>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'.
>>> Then
>>>>>>>> check if the connection is made.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>>>>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l
>>> says:
>>>>>>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>>>>>>     Connecting To: 128:0[real:0]
>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>
>>>>>>>>>> I can't imagine why it would work for me, but not for you. My
>>>>>>> libasound2
>>>>>>>>>> version is 1.1.3-5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>>>>>>> It's on my list as follows
>>>>>>>>>>>
>>>>>>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>> Alas it's not working for me. I've tried
>>>>>>>>>>>>
>>>>>>>>>>>> -M'UMX 250'
>>>>>>>>>>>>
>>>>>>>>>>>> And it says
>>>>>>>>>>>>
>>>>>>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>>>>>>> permitted)
>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>>> Thanks alot!
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com
>>>> :
>>>>>>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for
>>> me:
>>>>>>> csound
>>>>>>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>>>>>>> "aconnect
>>>>>>>>>> -l"
>>>>>>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <
>>> gsenna@gmail.com>:
>>>>>>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something
>>> like:
>>>>>>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and
>>> fixing
>>>>>>> the
>>>>>>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>>>> Is it possible for example to connect to device by it's
>>> name
>>>>>>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> 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
>>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> 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
>>>>
>>>>
>>>> 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
>>>
>>
> 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

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

Date2017-07-14 13:57
FromAnton Kholomiov
SubjectRe: Stable and predictable MIDI connection with ALSA
With the latest Csound. It was just announced

2017-07-14 15:55 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
Ok, finally

This way it works:

-+rtmidi=alsaseq --midi-device="UMX 250"

BUT:

This way

--midi-device="UMX 250"  -+rtmidi=alsaseq

It says:

Unknown RawMidi UMX 250

I think it's not good when the order of flags matter.



2017-07-14 15:26 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
Just for the record, Anton, could you try running Csound with the
following options? All of these work for me.

csound -+rtmidi=alsaseq -M"UMX 250"

csound -+rtmidi=alsaseq -M"UMX\ 250"

csound -+rtmidi=alsaseq -MUMX\ 250

We obviously weren't reading the error message correctly. It is clear
that the problem (as usual) was the quotes and then the space between
UMX and 250:

ALSASEQ: connection failed from 'UMX, port 0 (Operation not permitted)



On 14/07/17 07:48, Anton Kholomiov wrote:
> Thanks Victor for the hint with the script!
> I think I can also put in the script the jack connection commands.
> That way I can get reliable jack connections without ladish sessions.
>
> 2017-07-14 13:37 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>
>> I've make it work by creating a script connect_umx_csound
>> that just connects the Csound:
>>
>> #!/usr/bin/sh
>> aconnect 'UMX 250' 'Csound'
>>
>> And then I can run it programmatically after start of the csd and it gives
>> no errors,
>>
>> phew...
>>
>> That's really strange.
>>
>>
>>
>> 2017-07-14 13:32 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
>>
>>> I think it might be because the script runs it immediately after starting
>>> Csound. Maybe Csound has not
>>> opened alsaseq in time. You can try adding a sleep:
>>>
>>> csound … &
>>> sleep 1
>>> aconnect …
>>>
>>>
>>>
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 14 Jul 2017, at 11:27, Anton Kholomiov <anton.kholomiov@gmail.com>
>>> wrote:
>>>> That's the strange why something that works when I type it doesn't work
>>> when I execute
>>>> it from script. I think it's not the question for the list.
>>>>
>>>> I think it's some thing to do with the OS which is Arch.
>>>> I've tried it recently and regret my choice.
>>>> But right now I'm to lazy to switch so I'm trying to make use of it.
>>>>
>>>> 2017-07-14 13:23 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com>:
>>>> It gives the same error:
>>>>
>>>>> sh 00-dream-pad.sh
>>>> invalid sender address ‘UMX
>>>> ... csound output...
>>>>
>>>>
>>>> Script content:
>>>>
>>>> #!/usr/sh
>>>> csound 00-dream-pad.csd & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> 2017-07-14 13:14 GMT+03:00 Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
>>>> did you try this script?
>>>>
>>>> #!/usr/sh
>>>> csound … & aconnect ‘UMX 250’ ‘Csound’
>>>>
>>>>
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 14 Jul 2017, at 11:10, Anton Kholomiov <anton.kholomiov@gmail.com>
>>> wrote:
>>>>> If I type it by hand it works on terminal: aconnect 'UMX 250' 'Csound'
>>>>> but I don't have the way to automate this process..
>>>>>
>>>>> 2017-07-14 12:49 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>>> :
>>>>> I think it's have to do with interpretation of unary quotes ' ' on my
>>> system
>>>>> Unfortunately when I try to automize your solution whenever I try to
>>>>> execute the line: "aconnect 'UMX 250' 'Csound'" from some programming
>>> language
>>>>> I get error on
>>>>>
>>>>> invalid sender address 'UMX
>>>>>
>>>>> But with plain integers it works
>>>>>
>>>>> aconnect 28 129
>>>>>
>>>>> 2017-07-14 11:31 GMT+03:00 Anton Kholomiov <anton.kholomiov@gmail.com
>>>> :
>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>> first to the Midi Through port (in my case, csound -+rtmidi=alsaseq
>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'. Then
>>>>> check if the connection is made.
>>>>>
>>>>> This recipe works!
>>>>>
>>>>> Maybe I need to update Csound to the very latest version... to work
>>> it directly
>>>>> But atleast I have some predictable way to to it now.
>>>>>
>>>>>
>>>>>
>>>>> 2017-07-14 5:16 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>> That's correct. But we were trying to make the connection by name.
>>>>>
>>>>>
>>>>> On 13/07/17 21:08, Forrest Curo wrote:
>>>>>> I think that alsa is not always consistent with how it assigns midi
>>> ports
>>>>>> after reboot.
>>>>>>
>>>>>> On Thu, Jul 13, 2017 at 2:50 PM, Guillermo Senna <gsenna@gmail.com>
>>> wrote:
>>>>>>> if aconnect can't do it, it's alsaseq and your card. Otherwise it
>>> is
>>>>>>> probably Csound.
>>>>>>>
>>>>>>>
>>>>>>> On 13/07/17 18:49, Guillermo Senna wrote:
>>>>>>>> apt-cache show libasound2 | grep Version
>>>>>>>>
>>>>>>>> Although I doubt that's what's happening. Maybe you could try
>>> connecting
>>>>>>>> first to the Midi Through port (in my case, csound
>>> -+rtmidi=alsaseq
>>>>>>>> -M14) and later in another terminal: aconnect 'UMX 250' 'Csound'.
>>> Then
>>>>>>>> check if the connection is made.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 13/07/17 18:34, Anton Kholomiov wrote:
>>>>>>>>> I'm using Csound 6.09. Not sure on the version of libasound2
>>>>>>>>>
>>>>>>>>> 2017-07-14 0:25 GMT+03:00 Guillermo Senna <gsenna@gmail.com>:
>>>>>>>>>
>>>>>>>>>> Latest Csound? I'm using Ubuntu Studio 17.04. My aconnect -l
>>> says:
>>>>>>>>>> client 28: 'Scarlett 2i4 USB' [type=kernel,card=3]
>>>>>>>>>>     0 'Scarlett 2i4 USB MIDI 1'
>>>>>>>>>>     Connecting To: 128:0[real:0]
>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>
>>>>>>>>>> I can't imagine why it would work for me, but not for you. My
>>>>>>> libasound2
>>>>>>>>>> version is 1.1.3-5.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 13/07/17 18:14, Anton Kholomiov wrote:
>>>>>>>>>>> It's on my list as follows
>>>>>>>>>>>
>>>>>>>>>>> client 32: 'UMX 250' [type=kernel,card=4]
>>>>>>>>>>>     0 'UMX 250 MIDI 1  '
>>>>>>>>>>>     Connecting To: 128:0[real:0], 130:0
>>>>>>>>>>>     Connected From: 128:0
>>>>>>>>>>>
>>>>>>>>>>> 2017-07-14 0:14 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>> Alas it's not working for me. I've tried
>>>>>>>>>>>>
>>>>>>>>>>>> -M'UMX 250'
>>>>>>>>>>>>
>>>>>>>>>>>> And it says
>>>>>>>>>>>>
>>>>>>>>>>>> ALSASEQ: connection failed from 'UMX, port 0 (Operation not
>>>>>>> permitted)
>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>> anton.kholomiov@gmail.com
>>>>>>>> :
>>>>>>>>>>>>> Thanks alot!
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2017-07-14 0:02 GMT+03:00 Anton Kholomiov <
>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>> Wow! That's exactly what I need!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2017-07-14 0:00 GMT+03:00 Guillermo Senna <gsenna@gmail.com
>>>> :
>>>>>>>>>>>>>>> Scratch that. I've tried alsaseq and this one worked for
>>> me:
>>>>>>> csound
>>>>>>>>>>>>>>> -+rtmidi=alsaseq -M'Scarlett 2i4 USB'. Check the output of
>>>>>>> "aconnect
>>>>>>>>>> -l"
>>>>>>>>>>>>>>> to see if you can find the name of the card.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 13/07/17 17:47, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>> Thanks Guillermo I will investigate the options.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do you think that JACK for midi is more appropriate?
>>>>>>>>>>>>>>>> I have never tried it with Csound
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2017-07-13 23:20 GMT+03:00 Guillermo Senna <
>>> gsenna@gmail.com>:
>>>>>>>>>>>>>>>>> Hi Anton,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Off the top of my head I can think of:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using JACK for midi?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Fixing the assignments somehow. If it's USB something
>>> like:
>>>>>>>>>>>>>>>>> http://www.familjenpalo.se/vpo/SoundAndMIDI
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Using raw MIDI instead of alsaseq.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> * Calling a (non-portable) bash script with system_i and
>>> fixing
>>>>>>> the
>>>>>>>>>>>>>>>>> connection with aconnect.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Cheers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 13/07/17 16:50, Anton Kholomiov wrote:
>>>>>>>>>>>>>>>>>> Is it possible for example to connect to device by it's
>>> name
>>>>>>>>>>>>>>>>>> instead of id?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2017-07-13 22:48 GMT+03:00 Anton Kholomiov <
>>>>>>>>>>>>>>> anton.kholomiov@gmail.com>:
>>>>>>>>>>>>>>>>>>> Can you help me?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I use many csound files as MIDI-synthesizers.
>>>>>>>>>>>>>>>>>>> I use alsa sequencer midi driver.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Recently I've run into problem with MIDI device IDs.
>>>>>>>>>>>>>>>>>>> I've changed the audio card and now it has midi in/outs
>>>>>>>>>>>>>>>>>>> So I've got MIDI-keyboard and MIDI-capable audio card.
>>>>>>>>>>>>>>>>>>> And when I plug them my PC seems to randomly switch
>>>>>>>>>>>>>>>>>>> the identifiers for MIDI devices.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> But in Csound I have to specify the precise number.
>>>>>>>>>>>>>>>>>>> And sometimes it's not the number that  ALSA gives
>>>>>>>>>>>>>>>>>>> to my MIDI-keyboard on the next PC start.
>>>>>>>>>>>>>>>>>>> So I have to change the device IDs for all files.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Do you know some trick to connect Csound with
>>>>>>>>>>>>>>>>>>> MIDI-keyboard in this case? More reliable way to do it
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>>> Anton
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> 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
>>>>>>>
>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> 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
>>>>
>>>>
>>>> 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
>>>
>>
> 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


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