Bluetooth Gps Output

[Epicuro Kishore]

Im trying to use mt SONY MDR-XB950BT headphones on Ubuntu 16.04 but not having any luck. I've managed to get them connected but it doesn't seem like I can actually listen to music/videos out of them. I tried setting the audio output to the headphones, but sound keeps coming out of the speakers instead. I also installed Pulse Audio Volume Control, but that doesn't seem to make a difference. I briefly managed to get it so that the test sound would play through the headphones, but when I tried to watch an online video, the video wouldn't even play until I changed the sound output device.

To install blueman, open a terminal and type sudo apt-get install blueman. Once it's installed, you can run it by typing blueman or you can search for "bluetooth manager" in the Applications menu. Once blueman is running, you can lock it to the launcher.

Firstly with my UE Boom 2 connected, I went into "Sound Settings" and made sure the output "mode" was set to "Headset Head Unit (HSP/HFP)", NOT "High Fidelity Playback (A2DP Sink)". Making sure it was in the low quality output is the only way I can ensure a successful connection. Then I installed blueman sudo apt-get install blueman and then rebooted.

After that, I clicked on the new bluetooth icon in the menubar provided by blueman and selected "devices". The "UE Boom 2" appears in the window when it's discoverable. Now click "Setup..." at the top of the window. Given the choice of connection, under "Connect to:", I selected "Audio Sink". This took a couple of tries, but it worked eventually.

Once successfully connected, close the setup window and go back to the sound settings. You should now be able to switch the output mode to "High Fidelity Playback (A2DP Sink)" without losing audio. This is now the process I use to start up my UE Boom 2 each time I need to use it.

TLDR: Connect using regular bluetooth, set connection to "On", set the output to "HSP/HSF" in sound settings (make sure that works), set connection to "Off". Then set up the device using blueman, connect it as an "Audio Sink". Now back into sound settings and change the output to "A2DP".

I am using SONY MDR-XZ770BN and I had no problems with Ubuntu 14.04 using the default bluetooth. After installing 16.04 the High Fidelity Playback A2DP Sink was not working. Problem was solved after installing the Blueman manager and selecting the Audio Sink option. Still experiencing some minor issues as sometimes I have to switch off and on the bluetooth before success but it is doing well overall. Try it and maybe it works also for you :)

Blueman: Connected headphones via the 'Audio Sink' option, setting 'Audio Profile' to 'High Fidelity Playback'. Marked the headphones as 'Trusted' in the 'Device' menu (or by right-click context option).

Ubuntu 'Sound Preferences': In the 'Hardware' tab turned off 'Built-in Audio' and set the headphones (same ID as appears in Blueman) to HSP/HFP. In the 'Output' tab selected the headphones (again, same ID as appears in Blueman).

A bit fiddly, but did the job. Turning the 'Built-in Audio' on again once the headphones were connected had no adverse effect on playback, and audio played as normal after the headphones were disconnected. :)

I was on ubuntu 15.04. While on it, i was already having the problem with my Sony MDR-ZX550BN. The problem was sometimes, ubuntu refused to play sound through AD2P.What i ended up usually doing, was un-pairing the device (remove it from the bluetooth devices list), then repairing it. It was working.

Also have Sony MDR-XB950BT. Kubuntu 18.04 LTS.Open System settings > find "Configure the Audio Volume" > select "Advanced" tab.Find "Built-in Audio" > press "Profile:" combobox and select Digital Stereo (HDMI) Output.Worked for me.

As a seasoned DJ from 1973 I agree with DJ Icespic. There are enough bells and whistles in the app to make marking your cue so that you can release real-time while listening to the main live output. The company seems to be on the cutting edge enough to eventually come up with a build in adjustable delay circuit to sync the signals removing the latency and releasing the next mix on the beat.

I know no musical app wants to enable bluetooth audio, because of the high latency and not so good quality... but in some scenarios i would like to use bluetooth audio connection. for instance, i could work with loopy, creating layers of ambient sounds that do not need to be on sync, or be rhythmically accurate.

but there would be many other positive things.

Bluetooth keyboards also work with Loopy to trigger actions, but if you're wanting bluetooth audio, rather than bluetooth control, there are some things that are under development for very low latency, but I don't know of anything that's rolled out yet.

example 1:

one week ago i did a performance in a church, only by recording live and looping some of the sounds produced by small bells or the furnishing. letting them in the background for a cello player to improvise over them. no need at all the sounds to be in sync. i had to move with a cable, it was a pain in the ass. i would have loved a bluetooth audio connection.

example 2:

for a theatrical play i had to record live the voices of the performers, only small sentences, which were looped one over another during a certain amount of time. no need at all of accuracy in the timing. i had to use a very expensive wireless send and receiver. would have loved the bluetooth connection.

example 3:

sometimes in my concerts, before i sit to play my cello, i start creating a layered background of voices, they are just some whispered voices. i like to do it walking among the audience. the voices don't need to be in sync. having in one hand the mic, and in another my idevice, without any cables, would be so cool and practical.

in general, any looping work or musical performance which is intended to be "atmospheric" and not rhythmical, would be perfectly realizable using a bluetooth connection. and it would open new interesting and creative possibilities.

I'm not sure bluetooth audio would be of any use for me because of the latency. Bluetooth midi on the other hand would be a great thing to get working. It already exists as an app (bluemidi) for midi connections between ios device and host computers/daws, but I think it would be cool if I could get midi from one ios device to another through bluetooth. Also it would be great if somebody made a powered usb midi to bluetooth box to send usb midi controller data to ios devices wirelessly. I wonder if there would be latency issues, though. Bit of a threadjack there, sorry...

Bluetooth audio is an absolute necessity for Sound Design when you don't want to use headphones- my iPad 4 had decent enough sound ... But read up on the iPad Air 2's speakers ... They are God awful no matter how many units I swapped out ! Everyone is complaining & they hyped the treble & midrange & the bass is tinny & muddy .... So yes absolutely us Sound Designers REALLY need the Bluetooth support added to Audiobus & there are great bluetooth speakers out there & some synth & effects apps already support it like Waldorf Nave & So many others -- So Please offer us that feature ... Thank you

I believe this issue is that apps allow recording into them can't support Bluetooth output on newer versions of iOS. So Nave can support but Loopy can not. Audiobus can't either. Could be wrong there but I think this is a feature request for Apple, not Audiobus.

Hmm not sure either but I can't think of a reason (then again I'm not a coder) why in Audiobus being the host -can't have the ability regardless of the apps hosted -to output audio over Bluetooth ...would love to hear from the Audiobus developers on this & hell I'd pay as an IAP to be able to do this & OH I havnt noticed any latency at all -but maybe I got lucky with the speaker I use

I don't understand the two posters above who said they wanted Bluetooth output so they wouldn't have to use headphones. Anything that can be done with Bluetooth can also be done with a stereo cable with 1/8" jacks.

I thought it was a matter that if you use BT, you are stuck with BT tx and rx...you couldn't use BT for tx and expect to rx on the mic input, or vice versa. I'm not sure how well BTLE handles audio, from a latency and bandwidth perspective, particularly with tx and rx at the same time. I imagine you could tx BT midi from a controller and send BT audio to reduce the processing, but there still aren't that many controllers available that tx BTLE midi, afaik.

That abandoned feature was really about dynamic outputs (part of the MPD protocol we do not support). For a static setup where you are happy to always output to both Bluetooth and your soundcard then a custom Gstreamer pipeline similar to what is described in ours docs for Icecast should work. Something like the following lets me output to two soundcards so maybe you can adapt that:

Running Mopidy as your user or as the service? If the latter, the service runs as user mopidy which will have no idea about anything in your user .asoundrc file. It also may or may not have access to the bluetooth device. If the former, try pairing up those audioresample elements with an audioconvert element (wild guess).

Hello, I was wondering if it would be too crazy to this same thing but with two bluetooth speakers? This could save me some nasty wiring and saving the expense of an entire rpi for each speaker on my house.

You are great! The solution is also working for me with only a small issue I would like to resolve and I hope you can help me. The jack output and BT are working together as you described above but if I turn off my BT device the other output also falls silent with error in the log:

ERROR GStreamer error: gst-resource-error-quark: Error outputting to audio device. The device has been disconnected. (

ERROR GStreamer error: gst-resource-error-quark: Could not open audio device for playback. (6)

3a8082e126