Hi Ralf,
i think this solved the problem - thanks!
>I suspect that you device sometimes is hw:0 and sometimes hw:1
>To /etc/modprobe.d/alsa-base.conf add
> # ALSA module ordering
> options snd slots=snd_ice1712
>then it always will be hw:0 and I suspect the MIDI port always will be 16.
On Thu, May 7, 2015 at 6:09 PM, <alsa-user-requ...@lists.sourceforge.net>
wrote:
> Send Alsa-user mailing list submissions to
> alsa-user@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/alsa-user
> or, via email, send a message with subject or body 'help' to
> alsa-user-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> alsa-user-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Alsa-user digest..."
>
>
> Today's Topics:
>
> 1. assign Midi port client number (Menno Knevel)
> 2. Re: assign Midi port client number (Ralf Mardorf)
> 3. Sending all audio over socket (Guru Prasad)
> 4. Re: Sending all audio over socket (Guru Prasad)
> 5. Re: Sending all audio over socket (Guru Prasad)
> 6. How to report bugs? (Todd Dailey)
> 7. Re: How to report bugs? (Clemens Ladisch)
> 8. Re: Sending all audio over socket (Sergei Steshenko)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 6 May 2015 20:23:44 +0200
> From: Menno Knevel <magkne...@gmail.com>
> Subject: [Alsa-user] assign Midi port client number
> To: alsa-user@lists.sourceforge.net
> Message-ID:
> <CAEV_10hu7Yn5VAUy3m4q=
> vbmoymucmqhzsuzdgeuqt6enqu...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> When i use aconnect -i -o, sometimes my soundcard has Midi port 20, after a
> reboot it becomes Midi port 16
>
> client 0: 'System' [type=kernel]
> 0 'Timer '
> 1 'Announce '
> client 14: 'Midi Through' [type=kernel]
> 0 'Midi Through Port-0'
> client 16: 'M Audio Delta 1010' [type=kernel]
> 0 'M Audio Delta 1010 MIDI'
>
> Is there a way to assign my M Audio Delta 1010 midi port to a fixed number,
> for example 20?
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Wed, 6 May 2015 21:03:50 +0200
> From: Ralf Mardorf <ralf.mard...@alice-dsl.net>
> Subject: Re: [Alsa-user] assign Midi port client number
> To: alsa-user@lists.sourceforge.net
> Message-ID: <20150506210350.705d3b8f@archlinux>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 6 May 2015 20:23:44 +0200, Menno Knevel wrote:
> >Is there a way to assign my M Audio Delta 1010 midi port to a fixed
> >number, for example 20?
>
> I suspect that you device sometimes is hw:0 and sometimes hw:1
> To /etc/modprobe.d/alsa-base.conf add
>
> # ALSA module ordering
> options snd slots=snd_ice1712
>
> then it always will be hw:0 and I suspect the MIDI port always will be
> 16.
>
> My set up does look like this and the order for MIDI is always the same:
>
> [rocketmouse@archlinux ~]$ cat /etc/modprobe.d/alsa-base.conf
> # ALSA module ordering
> options snd slots=snd_hdspm,snd_ice1712,snd_ice1712
>
> [rocketmouse@archlinux ~]$ aconnect -i
> client 0: 'System' [type=kernel]
> 0 'Timer '
> 1 'Announce '
> client 14: 'Midi Through' [type=kernel]
> 0 'Midi Through Port-0'
> client 16: 'RME AIO_579bcc' [type=kernel]
> 0 'HDSPMx579bcc MIDI 1'
> client 20: 'TerraTec EWX24/96' [type=kernel]
> 0 'TerraTec EWX24/96 MIDI'
> client 24: 'TerraTec EWX24/96' [type=kernel]
> 0 'TerraTec EWX24/96 MIDI'
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 6 May 2015 19:45:02 -0400
> From: Guru Prasad <gurup...@buffalo.edu>
> Subject: [Alsa-user] Sending all audio over socket
> To: alsa-user@lists.sourceforge.net
> Message-ID:
> <CAMefCkAZSigFfYLBqH0ake84J73knbvZKtFOAdOd=
> awyxxw...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> I'm trying to write an application that can hook into ALSA and receive
> all audio and send it across the network. I realize that JACK and
> Pulse are probably better suited for implementing this, but I would
> like to be able to run this on most Linux machines including
> smartphones(hopefully).
>
> Currently, with .asoundrc, I've had limited success with the pcm file
> plugin.
> However, given my lack of knowledge, I've only been able to write this
> to a file (instead of a pipe/socket) which starts using a lot of disk
> space.
>
> Is there a programmatic way of adding a hook to ALSA at run-time to
> capture and forward all audio?
>
> Thanks
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 6 May 2015 23:23:53 -0400
> From: Guru Prasad <gurup...@buffalo.edu>
> Subject: Re: [Alsa-user] Sending all audio over socket
> To: Sergei Steshenko <steshenko_ser...@list.ru>,
> alsa-user@lists.sourceforge.net
> Message-ID:
> <CAMefCkCxhD+bnJEe4kWph5H7mc8LFwWXeUGbOmm9hjyf=
> cq...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Could you give me an example of how I can ask the PCM file plugin to
> write to a named pipe?
> Should i create this manually or can I somehow do this via the PCM
> file plugin itself by using the '|' character?
>
> Also, don't named pipes block until there is a reader? Given that I've
> only been able to do this via .asoundrc (and not via the
> snd_pcm_file_open), I'm not sure how the blocking behaviour would
> interact with ALSA. Would only my file plugin PCM definition block
> while others continue?
>
> Regardless, thank you for the suggestion. I will try this out meanwhile.
>
> Regards
> Guru
>
> On Wed, May 6, 2015 at 10:41 PM, Sergei Steshenko
> <steshenko_ser...@list.ru> wrote:
> > "I've only been able to write this to a file (instead of a pipe/socket)"
> -
> > have you tried named pipe ?
> >
> > It looks like a file, and behave like a pipe.
> >
> > --Sergei.
> >
> >
> > ?????, 6 ??? 2015, 19:45 -04:00 ?? Guru Prasad <gurup...@buffalo.edu>:
> >
> > Hi,
> >
> > I'm trying to write an application that can hook into ALSA and receive
> > all audio and send it across the network. I realize that JACK and
> > Pulse are probably better suited for implementing this, but I would
> > like to be able to run this on most Linux machines including
> > smartphones(hopefully).
> >
> > Currently, with .asoundrc, I've had limited success with the pcm file
> > plugin.
> > However, given my lack of knowledge, I've only been able to write this
> > to a file (instead of a pipe/socket) which starts using a lot of disk
> > space.
> >
> > Is there a programmatic way of adding a hook to ALSA at run-time to
> > capture and forward all audio?
> >
> > Thanks
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > _______________________________________________
> > Alsa-user mailing list
> > Alsa-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
> >
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 7 May 2015 08:25:33 -0400
> From: Guru Prasad <gurup...@buffalo.edu>
> Subject: Re: [Alsa-user] Sending all audio over socket
> To: Anders Genell <anders.gen...@gmail.com>,
> alsa-user@lists.sourceforge.net
> Message-ID:
> <CAMefCkCQ=
> kqmtdy6f0edb1o8c98i4bm47hbocrl9fivsife...@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I had some luck with the named pipe setup. I was able to set up
> .asoundrc to write to a named pipe in /tmp and then send this data
> over a socket and play it on another machine.
> However, all (audio) applications freeze until my program (which reads
> from the pipe) begins to run. This is expected behaviour of named
> pipes.
>
> I believe I can solve this by modifying the PCM 'default' dynamically.
> That way, I can modify the PCM at the start of my program to use my
> custom .asoundrc.
> Is it possible to:
> 1) Modify PCM 'default' on the fly?
> 2) Re-initialize ALSA with a new .asoundrc without
> rebooting/restarting the desktop manager?
>
>
> @Anders:
> I tried that approach already with no luck. For some reason when I
> include snd-aloop to my modules, aplay -L does not show any of the
> loopback devices.
>
>
> On Thu, May 7, 2015 at 3:01 AM, Anders Genell <anders.gen...@gmail.com>
> wrote:
> >
> >> 7 maj 2015 kl. 05:23 skrev Guru Prasad <gurup...@buffalo.edu>:
> >>
> >> Could you give me an example of how I can ask the PCM file plugin to
> >> write to a named pipe?
> >> Should i create this manually or can I somehow do this via the PCM
> >> file plugin itself by using the '|' character?
> >>
> >> Also, don't named pipes block until there is a reader? Given that I've
> >> only been able to do this via .asoundrc (and not via the
> >> snd_pcm_file_open), I'm not sure how the blocking behaviour would
> >> interact with ALSA. Would only my file plugin PCM definition block
> >> while others continue?
> >>
> >> Regardless, thank you for the suggestion. I will try this out meanwhile.
> >>
> >> Regards
> >> Guru
> >
> > Maybe this could be a starting point?
> >
> > http://plasmasturm.org/log/soundserverhack/
> >
> > Regards,
> > /Anders
> >
> >
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 07 May 2015 09:15:27 -0400
> From: Todd Dailey <t...@todddailey.ca>
> Subject: [Alsa-user] How to report bugs?
> To: alsa-user@lists.sourceforge.net
> Message-ID: <554b656f.40...@todddailey.ca>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> How to report bugs when https://bugtrack.alsa-project.org/alsa-bug does
> not work?
>
> --
> TD
> t...@todddailey.ca
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 07 May 2015 15:58:25 +0200
> From: Clemens Ladisch <cladi...@googlemail.com>
> Subject: Re: [Alsa-user] How to report bugs?
> To: Todd Dailey <t...@todddailey.ca>, alsa-user@lists.sourceforge.net
> Message-ID: <554b6f81.5090...@googlemail.com>
> Content-Type: text/plain; charset=us-ascii
>
> Todd Dailey wrote:
> > How to report bugs when https://bugtrack.alsa-project.org/alsa-bug does
> > not work?
>
> For driver bugs, use the kernel bugzilla: https://bugzilla.kernel.org/
> For other bugs, send a mail to the alsa-devel list.
>
>
> Regards,
> Clemens
>
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 07 May 2015 19:06:34 +0300
> From: Sergei Steshenko <steshenko_ser...@list.ru>
> Subject: Re: [Alsa-user] Sending all audio over socket
> To: Guru Prasad <gurup...@buffalo.edu>
> Cc: alsa-user@lists.sourceforge.net
> Message-ID: <1431014794.196857...@f402.i.mail.ru>
> Content-Type: text/plain; charset="utf-8"
>
> "
> However, all (audio) applications freeze until my program (which reads
> from the pipe) begins to run. This is expected behaviour of named
> pipes.
>
> I believe I can solve this by modifying the PCM 'default' dynamically.
> "
>
> - well, to me it sounds like your "overall" application should be a
> multi-threaded one - one of the threads reads audio stream, waiting for
> data as necessary (you call it "freeze") while other threads check the
> status of the audio reading thread.
>
> ...
>
> Your whole IPC, including over the network part, can be implemented (or,
> say, prototyped) using a scripting language and utilities like 'cat',
> 'netcat' - the latter for the networking part.
>
> Regards,
> ? Sergei.
>
>
> ???????, 7 ??? 2015, 8:25 -04:00 ?? Guru Prasad <gurup...@buffalo.edu>:
> >I had some luck with the named pipe setup. I was able to set up
> >.asoundrc to write to a named pipe in /tmp and then send this data
> >over a socket and play it on another machine.
> >However, all (audio) applications freeze until my program (which reads
> >from the pipe) begins to run. This is expected behaviour of named
> >pipes.
> >
> >I believe I can solve this by modifying the PCM 'default' dynamically.
> >That way, I can modify the PCM at the start of my program to use my
> >custom .asoundrc.
> >Is it possible to:
> >????1) Modify PCM 'default' on the fly?
> >????2) Re-initialize ALSA with a new .asoundrc without
> >rebooting/restarting the desktop manager?
> >
> >
> >@Anders:
> >I tried that approach already with no luck. For some reason when I
> >include snd-aloop to my modules, aplay -L does not show any of the
> >loopback devices.
> >
> >
> >On Thu, May 7, 2015 at 3:01 AM, Anders Genell < anders.gen...@gmail.com
> > wrote:
> >>
> >>> 7 maj 2015 kl. 05:23 skrev Guru Prasad < gurup...@buffalo.edu >:
> >>>
> >>> Could you give me an example of how I can ask the PCM file plugin to
> >>> write to a named pipe?
> >>> Should i create this manually or can I somehow do this via the PCM
> >>> file plugin itself by using the '|' character?
> >>>
> >>> Also, don't named pipes block until there is a reader? Given that I've
> >>> only been able to do this via .asoundrc (and not via the
> >>> snd_pcm_file_open), I'm not sure how the blocking behaviour would
> >>> interact with ALSA. Would only my file plugin PCM definition block
> >>> while others continue?
> >>>
> >>> Regardless, thank you for the suggestion. I will try this out
> meanwhile.
> >>>
> >>> Regards
> >>> Guru
> >>
> >> Maybe this could be a starting point?
> >>
> >> http://plasmasturm.org/log/soundserverhack/
> >>
> >> Regards,
> >> /Anders
> >>
> >>
> >
>
> >------------------------------------------------------------------------------
> >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
> >_______________________________________________
> >Alsa-user mailing list
> >Alsa-user@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/alsa-user
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> 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
>
> ------------------------------
>
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>
>
> End of Alsa-user Digest, Vol 109, Issue 4
> *****************************************
>
------------------------------------------------------------------------------
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
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
