<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Route all Pi audio to bluetooth speaker</title><link>https://community.element14.com/products/raspberry-pi/f/forum/38623/route-all-pi-audio-to-bluetooth-speaker</link><description>Can someone share their experience on how to route all audio available from the Raspbian GUI to a bluetooth speaker? After establishing a bluetooth connection to a speaker, I can use the audio menu to select the bluetooth device and play audio through</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><lastBuildDate>Sun, 08 Sep 2019 19:59:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://community.element14.com/products/raspberry-pi/f/forum/38623/route-all-pi-audio-to-bluetooth-speaker" /><item><title>RE: Route all Pi audio to bluetooth speaker</title><link>https://community.element14.com/thread/140847?ContentTypeID=1</link><pubDate>Sun, 08 Sep 2019 19:59:11 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:32d7bdf9-d2b9-475a-958e-61b46593781c</guid><dc:creator>clem57</dc:creator><description>&lt;p style="margin:0;"&gt;In Linux, a dot before the name implies normal ls command will not show the file. It is like the hidden attribute in Windows.&lt;/p&gt;&lt;p style="margin:0;"&gt;Glad you found it works now,&lt;/p&gt;&lt;p style="margin:0;"&gt;Clem&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Route all Pi audio to bluetooth speaker</title><link>https://community.element14.com/thread/140835?ContentTypeID=1</link><pubDate>Sun, 08 Sep 2019 18:47:44 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:37818260-e717-4054-a14f-ff328b25ba53</guid><dc:creator>colporteur</dc:creator><description>&lt;p style="margin:0;"&gt;The link provided insight into turning of the onboard audio card. The information in the link was stale dated but the configuration changes looked familiar.&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;The following change:&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;pre class="jive-pre"&gt;disable audio support /boot/config.txt &lt;br /&gt;# Enable audio (loads snd_bcm2835) &lt;br /&gt;#dtparam=audio=on &amp;lt;--- inserted the octothorpe and perform a reboot. &lt;/pre&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;Before making this change you will notice a /proc/asound directory. After the change and reboot the directory is not created (i.e. no sound card).&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;I then configured the bluetooth device (i.e. speaker) using bluetoothctl&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;I was then going to make the following entry&lt;/p&gt;&lt;p style="margin:0;"&gt;/home/pi/.asoundrc &amp;lt;---yes there is a period in front of the filename.&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;pcm.!default {&lt;/p&gt;&lt;p style="margin:0;"&gt;type plug&lt;/p&gt;&lt;p style="margin:0;"&gt;slave.pcm {&lt;/p&gt;&lt;p style="margin:0;"&gt;type bluealsa&lt;/p&gt;&lt;p style="margin:0;"&gt;device &amp;quot;C2:E4:94:97:66:A8&amp;quot;&lt;/p&gt;&lt;p style="margin:0;"&gt;profile &amp;quot;a2dp&amp;quot;&lt;/p&gt;&lt;p style="margin:0;"&gt;}&lt;/p&gt;&lt;p style="margin:0;"&gt;}&lt;/p&gt;&lt;p style="margin:0;"&gt;ctl.!default {&lt;/p&gt;&lt;p style="margin:0;"&gt;type bluealsa&lt;/p&gt;&lt;p style="margin:0;"&gt;}&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;but discovered on a reboot after configuring bluetooth the contents were automatically created. The contents for this file I discovered in a post &lt;a class="jive-link-external-small" href="https://www.raspberrypi.org/forums/viewtopic.php?t=231281" rel="nofollow ugc noopener" target="_blank" title="https://www.raspberrypi.org/forums/viewtopic.php?t=231281"&gt;https://www.raspberrypi.org/forums/viewtopic.php?t=231281&lt;/a&gt;&amp;nbsp;&amp;nbsp; on the raspberrypi forum.&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;I did notice if this file had a syntax errors (i.e. device &amp;quot;bluealsa:HCI=hci0,DEV=C2:E4:94:97:66:A8&amp;quot;) applications errored out and the file contained some hardware entries. Not sure how this developed. &lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;With this configuration in place I have all audio from the browser (i.e. youtube video) doesn&amp;#39;t go out the HDMI but the rather the bluetooth speaker. Exactly what I was looking for. I suspect not having audio hardware on bootup removed any confusion to what the ALSA was required to do. Since no other audio support exists other than bluetooth it configured without a hitch.&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;I appreciate the links to resources. It definitely provided the impetus to uncover the solution. A fresh pair of eyes made the difference.&lt;/p&gt;&lt;p style="margin:0;padding:0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="margin:0;"&gt;Sean &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Route all Pi audio to bluetooth speaker</title><link>https://community.element14.com/thread/140802?ContentTypeID=1</link><pubDate>Sun, 08 Sep 2019 01:40:39 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:b7b31eb9-952d-40a1-850a-9c4d2586cbee</guid><dc:creator>clem57</dc:creator><description>&lt;p style="margin:0;"&gt;I think your answer is to send the sound to pulse instead of ALSA. Then the destination is much simpler. Look at &lt;a class="jive-link-external-small" href="https://opensource.com/article/17/1/linux-plays-sound" rel="nofollow ugc noopener" target="_blank" title="https://opensource.com/article/17/1/linux-plays-sound"&gt;https://opensource.com/article/17/1/linux-plays-sound&lt;/a&gt; . For a Windows perceptive this article maybe better &lt;a class="jive-link-external-small" href="https://www.learndigitalaudio.com/how-linux-audio-works-vs-windows-audio-2017" rel="nofollow ugc noopener" target="_blank" title="https://www.learndigitalaudio.com/how-linux-audio-works-vs-windows-audio-2017"&gt;https://www.learndigitalaudio.com/how-linux-audio-works-vs-windows-audio-2017&lt;/a&gt; &lt;/p&gt;&lt;p style="margin:0;"&gt;Hope this helps you.&lt;/p&gt;&lt;p style="margin:0;"&gt;Clem&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Route all Pi audio to bluetooth speaker</title><link>https://community.element14.com/thread/140798?ContentTypeID=1</link><pubDate>Sat, 07 Sep 2019 22:06:01 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:87b52cd9-ec55-4212-bd46-07f33a932e28</guid><dc:creator>clem57</dc:creator><description>&lt;p style="margin:0;"&gt;I do not have the answer, but I can point you in a direction that will help. In this &lt;a class="jive-link-external-small" href="https://plugable.com/2014/11/06/how-to-switch-to-usb-audio-on-raspberry-pi/" rel="nofollow ugc noopener" target="_blank"&gt;link,&lt;/a&gt; you will find how to realign the default sound. It may be adapted to your situation.&lt;/p&gt;&lt;p style="margin:0;"&gt;Clem&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>