[Alsa-user] ALSA PCM plugin lifetime
Hi all, I have a system setup where I need a post-processing ALSA PCM plugin. But how is the lifetime managed by the ALSA server? Will the plugin only be instantiated whilst there is an audio stream running? Is it possible to setup an ALSA configuration that keeps the PCM plugin instantiated, whether or not there is any audio running? (there will be an external application that communicates with the plugin through unix sockets) Regards /Robert The information in this email (including any attachments) may contain confidential and/or proprietary material. Any review, retransmission or use of this information by persons or entities other than the intended, authorized recipient is prohibited. If you received this email in error, please notify the sender and delete the material. For information regarding how Dirac handles personal data, please visit https://www.dirac.com/privacy-policy. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] RME HDSPe AIO + RME AO4S 192 AIO
Ralph, the AO4S expansion card for HDSPe AIO also works well, adds 4 monophonic outputs that become 2 stereo and does it totally independently of the main AIO card. It has an analog section and a DAC dedicated only to you and its outputs so the quility is at the top. What I don't understand is how to save HDSPMixer settings. I tried to adjust the volumes of the channels, one of the presets flashes, I press the button of the desired preset, for example 1, they all flash, I press save and he blocks the flashing preset. It seems done but when I restart the machine after turning it off, at the next restart the preset returns to the origin and has not saved anything. I also tried through a drop-down menu but nothing does not save. Why? Do you have any idea? ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Android Pixel C in MIDI mode not creating a alsa seq port
Stefan Sauer wrote: > If I use my pixel c tablet, the alsa device is recognized (it shows > up in /proc/asound/ and also creates a midi0 entry) Does it show up in the output of "amidi -l"? Is the ID 5209 or 520a? Your logs show both. Regards, Clemens ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Android Pixel C in MIDI mode not creating a alsa seq port
On 18.05.20 17:25, Clemens Ladisch via Alsa-user wrote: > Stefan Sauer wrote: >> If I use my pixel c tablet, the alsa device is recognized (it shows >> up in /proc/asound/ and also creates a midi0 entry) > Does it show up in the output of "amidi -l"? > > Is the ID 5209 or 520a? Your logs show both. idProduct=5209 is the Pixel C as a midi device, 520a is when it connects as MTP. $ amidi -l Dir Device Name $ If I do the same with the Pixel 3: $ amidi -l Dir Device Name IO hw:1,0,0 Pixel 3 MIDI 1 $ I hope it is just some udev rule mismatch, but I don't find any file containing those ids. Stefan > > > Regards, > Clemens > > > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] RME HDSPe AIO + RME AO4S 192 AIO
Hi Maurizio, thank you for reporting back. Take a look at the attached pic. You only made step 1, but you need to do step 2 and step 3, too. CCing, since the attached png might not make it through the mailing list. Regards, Ralf ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] RME HDSPe AIO + RME AO4S 192 AIO
On Mon, 18 May 2020 18:30:08 +0200, Ralf Mardorf wrote: >Take a look at the attached pic. You only made step 1, but you need to >do step 2 and step 3, too. It seems you made step 1 and step 2, but you are missing step 3, "Make current file default". If you already made step 2, you don't need to do the settings again, just open the file and then choose "Make current file default". ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Out AO4S 192 AIO
Hi Ralph, yes I was missing the third part in fact you are absolutely right. I did step 3 and already saved 2 presets thank you very much. I wanted to ask you for more information then if possible, I have 2 more outputs from the expansion card that I have just installed, the AO4S-192-AIO, which however I can't activate. I can't get anything out. The outputs of the card are 4 monophinic that are used to make 2 stereo outputs and while the output 3 and the output 4 of the card, I am currently using them successfully and I managed to direct them to channel 19 and channel 20 of the mixer, the outputs 1 and 2 of the card which should go to channel 17 and 18 of the mixer, I can't address them. I put 1-2 AN then analog outputs in the drop-down menu, I also put 3-4, 5-6 I tried them all but I couldn't. Can you tell me where I'm wrong? Thanks ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Out AO4S 192 AIO
On Mon, 2020-05-18 at 19:54 +0200, Maurizio M wrote: > Hi Ralph, yes I was missing the third part in fact you are absolutely > right. I did step 3 and already saved 2 presets thank you very much. I > wanted to ask you for more information then if possible, I have 2 more > outputs from the expansion card that I have just installed, the > AO4S-192-AIO, which however I can't activate. I can't get anything out. > The outputs of the card are 4 monophinic that are used to make 2 stereo > outputs and while the output 3 and the output 4 of the card, I am > currently using them successfully and I managed to direct them to > channel 19 and channel 20 of the mixer, the outputs 1 and 2 of the card > which should go to channel 17 and 18 of the mixer, I can't address them. > I put 1-2 AN then analog outputs in the drop-down menu, I also put 3-4, > 5-6 I tried them all but I couldn't. Can you tell me where I'm wrong? Thanks Sorry, I can't help with this. To ensure that you understand how hdspmixer works, I recommend to temporarily install Windows and TotalMix. Maybe a dated version of TotalMix. When I installed Windows and TotalMix around 9 years ago, TotalMix was already more advanced than hdspmixer, but there was no real difference related to the GUI's routing principle. The latest version of TotalMix might be completely different. I don't know. However, I know how to use an aged version of TotalMix and seemingly/likely how to use hdspmixer, too, but never got all available IOs working on Linux. For some reason the card also doesn't work, when trying to use Ardour with plain ALSA instead of jackd. I guess the driver is fishy, or some ALSA config was and still is missing on my machines. Some people claimed, the driver does work for the HDSPe AIO without issues, too. ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Android Pixel C in MIDI mode not creating a alsa seq port
Stefan Sauer wrote: > idProduct=5209 is the Pixel C as a midi device, 520a is when it connects > as MTP. Your lsusb output showed 520a. Was it supposed to be in MIDI mode at that time? Please show the output of "lsusb -d 18d1:5209 -v". Regards, Clemens ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user