<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix"> Both raw device access and alsa access are interesting. ALSA is mediated (multiple snaps can get it) and raw device is exclusive. Mark On 27/07/16 11:54, Oliver Grawert wrote: </div> <blockquote cite="mid:1469613261.4310.21.camel@anubis" type="cite"> <pre wrap="">hi, Am Dienstag, den 26.07.2016, 19:46 -0600 schrieb Selene Scriven: </pre> <blockquote type="cite"> <pre wrap="">* Jamie Strandboge <a class="moz-txt-link-rfc2396E" href="mailto:jamie@canonical.com"><jamie@canonical.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">On classic the interface provides access to the user session's pulseaudio. On an all snaps system (eg, Ubuntu Core) pulseaudio doesn't exist on the system and a pulseaudio snap must be installed. Once installed, the interface is available for other snaps to connect. </pre> </blockquote> <pre wrap=""> Any idea if there are plans to allow ALSA access? Several things don't work (or don't work well) with Pulse running, and I find that a few lines in .asoundrc usually make Pulse unnecessary even for basic desktop purposes. </pre> </blockquote> <pre wrap=""> well, you dont really need alsa *access* you can ship the libs and config in your snap (and have full control over your dependencies), what you need is direct device access for that setup ... that way you can also have all realtime love you can imagine without the underlying host system interfering ... so instead of an alsa interface we should have an audio-device interface that you can use more flexible... ciao oli </pre> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> </body> </html>