On Mon, 23 Mar 2015 09:06:01 +0100 Clemens Ladisch <cladisch@xxxxxxxxxxxxxx> wrote: > Dmitri Seletski wrote: > > It came to my attention, that I can start process and pass some > > variable to ALSA upon execution, so it may change PCM for example. > > > > I took information from here: > > > > http://blog.vrplumber.com/b/2012/03/23/control-default-alsa-device/ > > > > I tried it and it worked. However, it didn't work as expected for > > me. I was able to see rate is changing if I used various PCM with > > variable. So this part worked. > > > > I was able to check with /proc/asound/card0/pcm0p/sub0/hw_params > > file, it showed correct rate when I was using different PCM's. > > > > However, it seems that something happened to dmix, > > Some processes failed with "device busy" message, devices, who used > > default rate settings, to which I did not change rate with shell > > variable. > > This is probably because those processes ignore the "default" device > and got directly to some "hw" device. > > > My question, is, is there any user documentation to those three > > lines: @func getenv > > vars [ DISPLAY_ALSA_DEVICE ] > > default front > > Not really. > > > I want to know if function in question can be used in non !default > > device? > > Yes. > > > Regards, > Clemens Thanks! ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
