Greetings,

Csound's alsa midi support isn't very helpful...  -+rtmidi=asla
doesn't create an alsa client, and so doesn't show up with
 aconnect -oil  and can't be connected to using  aconnect
or disconnected from using  aconnect -d  or  aconnect -x  or
played to with  aplaymidi -p  or  midikbd -o  or  midiedit  or
midifade -o  or connected from more than one source, etc etc.

I know csound can be run initially with a -M999 option, and
its STERR parsed for lines  /^\s*(\d+):\s+(.+)\s+\(ALSA/
, and then re-run with (one of) the desired numbers, but
that's slow and messy.  Csound can be started up connecting
from some hardcoded number but that's very unportable.

It would be more useful, and look less clunky, if csound could
start a proper ALSA client. It's not much code; this example
( see:  http://search.cpan.org/perldoc?MIDI::ALSA ) is in Perl:
  use MIDI::ALSA;
  MIDI::ALSA::client( "csound pid=$$", 1, 1, 0 );
  foreach my $input (@Inputs) {
      MIDI::ALSA::connectfrom( 0, $input )
        or warn(" warning: couldn't connect from $input\n");
  }
  while (1) {
      my @alsaevent = MIDI::ALSA::input();
      do_something( @alsaevent );
  }
The corresponding C routines are in
  http://cpansearch.perl.org/src/PJB/MIDI-ALSA-1.14/ALSA.xs
or within
  http://www.pjb.com.au/comp/lua/midialsa-1.15.tar.gz

I'd like to suggest that  -+rtmidi=alsa  should create a proper
ALSA client.  If that's not possible for backward-compatibility
reasons, I'd like to suggest a new  -+rtmidi=alsaseq  option.

Apologies if it's been raised before and rejected...

Regards,  Peter Billam

http://www.pjb.com.au      pj@pjb.com.au     (03) 6278 9410
"Follow the charge, not the particle."  --  Richard Feynman
 from The Theory of Positrons, Physical Review, 1949

Thanks for the suggestion. We'll look into it.

Victor
On 24 Aug 2012, at 05:08, pj@pjb.com.au wrote:

> Greetings,
> 
> Csound's alsa midi support isn't very helpful...  -+rtmidi=asla
> doesn't create an alsa client, and so doesn't show up with
> aconnect -oil  and can't be connected to using  aconnect
> or disconnected from using  aconnect -d  or  aconnect -x  or
> played to with  aplaymidi -p  or  midikbd -o  or  midiedit  or
> midifade -o  or connected from more than one source, etc etc.
> 
> I know csound can be run initially with a -M999 option, and
> its STERR parsed for lines  /^\s*(\d+):\s+(.+)\s+\(ALSA/
> , and then re-run with (one of) the desired numbers, but
> that's slow and messy.  Csound can be started up connecting
> from some hardcoded number but that's very unportable.
> 
> It would be more useful, and look less clunky, if csound could
> start a proper ALSA client. It's not much code; this example
> ( see:  http://search.cpan.org/perldoc?MIDI::ALSA ) is in Perl:
>  use MIDI::ALSA;
>  MIDI::ALSA::client( "csound pid=$$", 1, 1, 0 );
>  foreach my $input (@Inputs) {
>      MIDI::ALSA::connectfrom( 0, $input )
>        or warn(" warning: couldn't connect from $input\n");
>  }
>  while (1) {
>      my @alsaevent = MIDI::ALSA::input();
>      do_something( @alsaevent );
>  }
> The corresponding C routines are in
>  http://cpansearch.perl.org/src/PJB/MIDI-ALSA-1.14/ALSA.xs
> or within
>  http://www.pjb.com.au/comp/lua/midialsa-1.15.tar.gz
> 
> I'd like to suggest that  -+rtmidi=alsa  should create a proper
> ALSA client.  If that's not possible for backward-compatibility
> reasons, I'd like to suggest a new  -+rtmidi=alsaseq  option.
> 
> Apologies if it's been raised before and rejected...
> 
> Regards,  Peter Billam
> 
> http://www.pjb.com.au      pj@pjb.com.au     (03) 6278 9410
> "Follow the charge, not the particle."  --  Richard Feynman
> from The Theory of Positrons, Physical Review, 1949
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Tito comes to the rescue...
On 24 Aug 2012, at 09:49, Tito Latini wrote:

> It is simple and useful, I think that this evening it will be in git
> (before the freeze) otherwise, if I'll have other problems, it is
> deferred to the next week.
> 
> tito
> 
> On Fri, Aug 24, 2012 at 08:56:36AM +0100, Victor Lazzarini wrote:
>> Thanks for the suggestion. We'll look into it.
>> 
>> Victor
>> On 24 Aug 2012, at 05:08, pj@pjb.com.au wrote:
>> 
>>> Greetings,
>>> 
>>> Csound's alsa midi support isn't very helpful...  -+rtmidi=asla
>>> doesn't create an alsa client, and so doesn't show up with
>>> aconnect -oil  and can't be connected to using  aconnect
>>> or disconnected from using  aconnect -d  or  aconnect -x  or
>>> played to with  aplaymidi -p  or  midikbd -o  or  midiedit  or
>>> midifade -o  or connected from more than one source, etc etc.
>>> 
>>> I know csound can be run initially with a -M999 option, and
>>> its STERR parsed for lines  /^\s*(\d+):\s+(.+)\s+\(ALSA/
>>> , and then re-run with (one of) the desired numbers, but
>>> that's slow and messy.  Csound can be started up connecting
>>> from some hardcoded number but that's very unportable.
>>> 
>>> It would be more useful, and look less clunky, if csound could
>>> start a proper ALSA client. It's not much code; this example
>>> ( see:  http://search.cpan.org/perldoc?MIDI::ALSA ) is in Perl:
>>> use MIDI::ALSA;
>>> MIDI::ALSA::client( "csound pid=$$", 1, 1, 0 );
>>> foreach my $input (@Inputs) {
>>>     MIDI::ALSA::connectfrom( 0, $input )
>>>       or warn(" warning: couldn't connect from $input\n");
>>> }
>>> while (1) {
>>>     my @alsaevent = MIDI::ALSA::input();
>>>     do_something( @alsaevent );
>>> }
>>> The corresponding C routines are in
>>> http://cpansearch.perl.org/src/PJB/MIDI-ALSA-1.14/ALSA.xs
>>> or within
>>> http://www.pjb.com.au/comp/lua/midialsa-1.15.tar.gz
>>> 
>>> I'd like to suggest that  -+rtmidi=alsa  should create a proper
>>> ALSA client.  If that's not possible for backward-compatibility
>>> reasons, I'd like to suggest a new  -+rtmidi=alsaseq  option.
>>> 
>>> Apologies if it's been raised before and rejected...
>>> 
>>> Regards,  Peter Billam
>>> 
>>> http://www.pjb.com.au      pj@pjb.com.au     (03) 6278 9410
>>> "Follow the charge, not the particle."  --  Richard Feynman
>>> from The Theory of Positrons, Physical Review, 1949
>>> 
>>> 
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>> 
>> 
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>> 
>> 
>> 
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

In this case we should wait for your say to freeze the code.
On 24 Aug 2012, at 11:42, Tito Latini wrote:

> I have the 50% of the code but I cannot continue today.
> I'll conclude it during my breaks the next week.
> 
> An example of the interface is
> 
>  csound -+rtmidi=alsaseq -M14,16 -Q128,129
> 
> Read from the clients 14, 16 and write to the clients 128 and 129.
> 
> The default for the client name is "Csound" but it is setable with
> 
>  -+alsaseq_client=[client_name]
> 
> that it is coherent with
> 
>  -+jack_client=[client_name]
> 
> tito
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Agreed -- this seem rather useful.  It will also give time for cossegr to
be written.. (done cossegb now)
==John


> In this case we should wait for your say to freeze the code.
> On 24 Aug 2012, at 11:42, Tito Latini wrote:
>
>> I have the 50% of the code but I cannot continue today.
>> I'll conclude it during my breaks the next week.
>>
>> An example of the interface is
>>
>>  csound -+rtmidi=alsaseq -M14,16 -Q128,129
>>
>> Read from the clients 14, 16 and write to the clients 128 and 129.
>>
>> The default for the client name is "Csound" but it is setable with
>>
>>  -+alsaseq_client=[client_name]
>>
>> that it is coherent with
>>
>>  -+jack_client=[client_name]
>>
>> tito
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>

Many many thanks to Tito.  I have changed the version number to 5.18 and
will be sending the revised Release Notes out very soon.

==John ff

> In git (no documentation).
>
> Memorandum about the syntax of the connections:
>
> -M address_list
> -Q address_list
>
> where:
>
>   address_list ::= address[,address,...]
>
>   address ::= client_number[:port_number]
>   address ::= client_name[:port_number]
>
>   client_number and port_number are integers >= 0
>
>   The default port_number is 0.
>
>   client_name is a string where the first char is not a number
>   (I can change it if it is a limitation)
>
> Example with `CsOptions':
>
> 
> -odac ; etc
> -+rtmidi=alsaseq
> ;; The default name of the client is 'Csound'
> -+alsaseq_client="Csound ALSA Sequencer Test"
> ;; If there are spaces in the name of the client,
> ;; we can put it between the "..."
> -M 20,"USB MIDI Controller:1",128:3,keykit:1
> -Q LinuxSampler,LinuxSampler:1
>
> ;; Also the follow is valid
> ;; -M "20,USB MIDI Controller:1,128:3,keykit:1"
> ;;
> ;; Here is an extreme example that uses the characters ','
> ;; and ':' in the name of the client.
> ;;
> ;;   -M "Uno\,Due\,Tre\:4"
> ;;
> ;; The name of the client is Uno,Due,Tre:4 and the port is 0.
> ;; Idem but the port is 1 (it also works without escape for ':')
> ;;
> ;;   -M "Uno\,Due\,Tre:4:1"
> ;;
> 
>
> tito
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>

has anyone succesfully used the Midi driver Alsasequencer yet?
I'm not sure what arguments to use or how to obtain them.



--
View this message in context: http://csound.1045644.n5.nabble.com/Suggestion-for-rtmidi-alsa-tp5715167p5741333.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

since nobody seems to know, i have done some trial and error -with success!

I have found the right commandline argument for the output of the Alsa
Sequncer Midi driver.
My commandline for midi output should, in my case, read: -+rtmidi=alsaseq
-Q20
The -Q20 spits out the midi data to the hardware output of my soundcard.

~$ aconnect -o
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 20: 'M Audio Delta 1010' [type=kernel]
    0 'M Audio Delta 1010 MIDI'

The output from Csound:
...........
ALSASEQ: opened MIDI output sequencer
ALSASEQ: created output port 'Csound' 130:0
ALSASEQ: connected to 20:0
..............

Then
the commandline for Midi In of the soundcard (playing my midikeyboard):
-+rtmidi=alsaseq -M20
because
~$ aconnect -i
client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 20: 'M Audio Delta 1010' [type=kernel]
    0 'M Audio Delta 1010 MIDI'
client 130: 'Csound' [type=user]
    0 'Csound 

The output from Csound:
...........
ALSASEQ: opened MIDI input sequencer
ALSASEQ: created input port 'Csound' 130:0
ALSASEQ: connected from 20:0
..............

The command line: -+rtmidi=alsaseq -M20 Q20
in my case lets me play the midikeyboard via Csound with a csd, containing
the midiin and midiout opcodes.

cool!



--
View this message in context: http://csound.1045644.n5.nabble.com/Suggestion-for-rtmidi-alsa-tp5715167p5741371.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Great,
Thanks for the explanation and example!
Tarmo

Tarmo, if you find some time for testing if this Midi Sequencer works on your
system too, please do.
Others, of course, are welcome to try too ...
At one point, this has to be a part of the manual and i hate putting too
much garbage in it :)

I don't know much (some, but i'm not an expert) about the inner workings of
Midi. Somewhere i read: "the role of the Midi Sequencer is to deliver events
at the right time (sequence) to the right destination (device)", so it has a
tight performance.
And there are other advantages.
Since 2012 Csound has this Midi Sequencer driver, and the difference between
the Raw Midi driver and the Midi Sequencer driver should become clear in the
manual.





--
View this message in context: http://csound.1045644.n5.nabble.com/Suggestion-for-rtmidi-alsa-tp5715167p5741387.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

yes -
whenever i get lost in a dark forest in any unknown country, i will try 
to call menno, to help me out ...
thanks, menno — can be very useful.
	joachim


Am 06.05.2015 um 08:15 schrieb Tarmo Johannes:
> Great,
> Thanks for the explanation and example!
> Tarmo
>
> 05.05.2015 23:47 kirjutas kuupäeval "Menno Knevel"  >:
>
>     since nobody seems to know, i have done some trial and error -with
>     success!
>
>     I have found the right commandline argument for the output of the Alsa
>     Sequncer Midi driver.
>     My commandline for midi output should, in my case, read:
>     -+rtmidi=alsaseq
>     -Q20
>     The -Q20 spits out the midi data to the hardware output of my soundcard.
>
>     ~$ aconnect -o
>     client 14: 'Midi Through' [type=kernel]
>          0 'Midi Through Port-0'
>     client 20: 'M Audio Delta 1010' [type=kernel]
>          0 'M Audio Delta 1010 MIDI'
>
>     The output from Csound:
>     ...........
>     ALSASEQ: opened MIDI output sequencer
>     ALSASEQ: created output port 'Csound' 130:0
>     ALSASEQ: connected to 20:0
>     ..............
>
>     Then
>     the commandline for Midi In of the soundcard (playing my midikeyboard):
>     -+rtmidi=alsaseq -M20
>     because
>     ~$ aconnect -i
>     client 0: 'System' [type=kernel]
>          0 'Timer           '
>          1 'Announce        '
>     client 14: 'Midi Through' [type=kernel]
>          0 'Midi Through Port-0'
>     client 20: 'M Audio Delta 1010' [type=kernel]
>          0 'M Audio Delta 1010 MIDI'
>     client 130: 'Csound' [type=user]
>          0 'Csound
>
>     The output from Csound:
>     ...........
>     ALSASEQ: opened MIDI input sequencer
>     ALSASEQ: created input port 'Csound' 130:0
>     ALSASEQ: connected from 20:0
>     ..............
>
>     The command line: -+rtmidi=alsaseq -M20 Q20
>     in my case lets me play the midikeyboard via Csound with a csd,
>     containing
>     the midiin and midiout opcodes.
>
>     cool!
>
>
>
>     --
>     View this message in context:
>     http://csound.1045644.n5.nabble.com/Suggestion-for-rtmidi-alsa-tp5715167p5741371.html
>     Sent from the Csound - General mailing list archive at Nabble.com.
>
>     ------------------------------------------------------------------------------
>     One dashboard for servers and applications across Physical-Virtual-Cloud
>     Widest out-of-the-box monitoring support with 50+ applications
>     Performance metrics, stats and reports that give you Actionable Insights
>     Deep dive visibility with transaction tracing using APM Insight.
>     http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>     _______________________________________________
>     Csound-users mailing list
>     Csound-users@lists.sourceforge.net
>     
>     https://lists.sourceforge.net/lists/listinfo/csound-users
>     Send bugs reports to
>     https://github.com/csound/csound/issues
>     Discussions of bugs and features can be posted here
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> _______________________________________________
> Csound-users mailing list
> Csound-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-users
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

as it happens, i live in an unknown country near a dark forest....



--
View this message in context: http://csound.1045644.n5.nabble.com/Suggestion-for-rtmidi-alsa-tp5715167p5741417.html
Sent from the Csound - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here