Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 8 FirstFirst 12345 ... LastLast
Results 21 to 30 of 78
  1. #21
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,719
    hi cpd73,

    Unfortunately I don't have any blue tooth devices. Hopefully one of the other guys will jump in.

    But I was working on something else recently on a 512MB RPi and I just about ran out of RAM. Weird things started happening.

    regards
    Greg

  2. #22
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,328
    I test bluetooth on a ZeroW all the time. But I'm using the onboard Bluetooth and wifi. What USB stick are you trying?

    The problem stems from Bluetooth are very close to the same frequencies. When you use the onboard Wifi and Bluetooth the chipset does broadcast sharing, meaning it does wifi traffic, and then does bluetooth, alternating back and forth. Since you are using different devices, they don't know they need to live together, what you can try is to put the bluetooth stick on an extension cable to get it away from the ZeroW. Also, make sure you have disabled the onboard bluetooth.
    Last edited by paul-; 2019-06-14 at 14:35.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #23
    Quote Originally Posted by cpd73 View Post
    Does this work with a PiZeroW and a USB bluetooth dongle? Because I'm really struggling to get this to work. I have pcp 5.0.0 installed (clean install), configured pcp for a bluetooth speaker. I can see the speaker/pcp in LMS, and can play music for about 1 minute. After that the audio gets very jittery, and after a few seconds just stops. If I'm ssh'ed into pcp at the time, then the connection is painstakingly slow. I guess something is hogging the CPU, but top updates so badly its hard to tell. During initial playback, squeezelite is only consuming 5-10% CPU.

    Am I doing something wrong? Or does USB bluetooth + inbuilt WiFi on a PiZeroW just not work?
    As I write, I'm listening to music via a PiZeroW and a pair of Bowers & Wilkins PX bluetooth headphones and the built-in bluetooth - this is the same PiZero I mentioned earlier in this thread. I did an in situ update to PcP 5.0 a few days ago and it's behaving perfectly. I am connected to the server by WiFi.

    I haven't tried a clean install of 5.0.0, but given my experience with the 4.1.0 clean install, I'd be reluctant.

    Robert

    Edit: I always use the standard PcP, not the experimental real-time kernel version.
    Last edited by Grumpy Bob; 2019-06-14 at 23:00. Reason: more info
    Home: Raspberry Pi 3/piCoreplayer/LMS7.9.2 with files on QNAP TS-251A
    Touch > DacMagic 100 > Naim Audio Nait 3 > Mission 752 (plus Rega Planar 3 > Rega Fono Mini; Naim CD3)
    PiCorePlayer(Pi2) with IQAudIO DAC+>Sennheisers
    2 x Squeezebox Radios, 1 X Squeezebox 3 (retired), spare Pi2/piCorePlayer
    Office: LMS7.9.2 running on WiFi MyPassport drive > piCorePlayer(PiB)/HiFiBerryDAC > Amptastic Amplifier
    SqueezePad, iPeng as controllers

    last.fm/user/GrumpyBob

  4. #24
    Senior Member
    Join Date
    Mar 2017
    Posts
    1,123
    Quote Originally Posted by paul- View Post
    I test bluetooth on a ZeroW all the time. But I'm using the onboard Bluetooth and wifi.
    I cannot get this combination to work. Using onboard Bluetooth and wifi; played for about 2 minutes, player went missing from LMS but continued to play for another 30 seconds before stopping. After a further 30 seconds, playback restarted, and player re-appeared in LMS. Whilst music stopped/not in LMS, top did not show high CPU but it also seemed to get stuck displaying only 2 or 3 processes. Played next song to completion, then did not play next. ssh session unresponsive. After a few minutes I could play another track, but ssh again was unresponsive.

    Quote Originally Posted by paul- View Post
    What USB stick are you trying?
    Just a cheap belkin dongle

    Quote Originally Posted by paul- View Post
    The problem stems from Bluetooth are very close to the same frequencies. When you use the onboard Wifi and Bluetooth the chipset does broadcast sharing, meaning it does wifi traffic, and then does bluetooth, alternating back and forth. Since you are using different devices, they don't know they need to live together, what you can try is to put the bluetooth stick on an extension cable to get it away from the ZeroW. Also, make sure you have disabled the onboard bluetooth.
    That seems to have done the trick. I've placed the dongle on a 1m extension cable, and its up to its 5th track with no dropouts.

    Thanks for your help.

  5. #25
    Senior Member
    Join Date
    Jun 2017
    Posts
    118
    Quote Originally Posted by cpd73 View Post
    (Originally Posted by paul-: I test bluetooth on a ZeroW all the time. But I'm using the onboard Bluetooth and wifi.)

    I cannot get this combination to work. Using onboard Bluetooth and wifi; played for about 2 minutes, player went missing from LMS but continued to play for another 30 seconds before stopping....
    It's interesting that you had problems with this combination on 5.0.0 that are similar (but not quite identical) to the issues I had with the same combination on pcp 4.0.0 and 4.1.0, Bob had issues with 4.1.0, but not 4.0.0, and an in situ update to 4.1.0 worked for him, and it's still working after an in situ update to 5.0.0. In my case, it was a clean install of 5.0.0 that made this combination work.

    Obviously, that are a lot of variables at play here, and many of them are not under the control of the pcp team. Manufacturing tolerances on the Zero W, perhaps?
    LMS (recent) running on Debian X86_64; 5 Squeezelite players (3 in PiCorePlayer), 3 players connected via Airplay Bridge
    1 Squeezebox Radio (upgraded UE Smart Radio) now mostly retired

  6. #26
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,328
    I would guess that channel selection/distance to WAP/enclosure/other wifi traffic has more to do with it.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  7. #27
    Senior Member
    Join Date
    Jun 2017
    Posts
    118
    Quote Originally Posted by paul- View Post
    I would guess that channel selection/distance to WAP/enclosure/other wifi traffic has more to do with it.
    That makes sense, and is bound to be better than my uneducated guess. Just FWIW, my setup -- the one that's working with 5.0.0, but had issues with 4.0.0 and 4.1.0 -- uses channel 6 to connect to an access point about ten feet (approx. 3 meters) away, with a wall between. Distance to the speaker is about 4 feet, slightly more than 1 meter. Two other players, both using the Airplay bridge) are connected to the access point, but nothing else.

    The Zero W is in the "official case": https://www.amazon.com/dp/B06XD18H6K..._w7sbDb0JHA009

    The access point is a "mini travel router": https://www.amazon.com/dp/B01K6MHRJI..._xetbDbH5HQY7T
    LMS (recent) running on Debian X86_64; 5 Squeezelite players (3 in PiCorePlayer), 3 players connected via Airplay Bridge
    1 Squeezebox Radio (upgraded UE Smart Radio) now mostly retired

  8. #28
    Senior Member
    Join Date
    Mar 2017
    Posts
    1,123

    Speaker does not reconnect?

    Whilst I've managed to get the speaker to connect and play, it does not always seem to reconnect when connection is lost. If i power off the speaker, LMS still seems to think something is playing - shouldn't the squeezelite instance be stopped? When I power the speaker back on it does not always reconnect - there is no connection beep, and no music is played. Is this a known issue? Or something strange with my setup?

    What I'd ideally like is to leave my PiZeroW always switched on, and just turn the bluetooth speaker on when required. Then the music should continue from where it switched off. Is this possible with pCP? I have a python script that I tested on my main (non-pCP) Pi (where LMS is located) that will start squeezelite when a speaker is connected, and stop it when it disconnects - but this requires python and dbus (which I don't think are on pCP?). However, I can't use this as my main Pi is too far away from where I wish to use the bluetooth speaker. So, I was hoping that pCP could do something similar.

  9. #29
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,328
    Quote Originally Posted by cpd73 View Post
    What I'd ideally like is to leave my PiZeroW always switched on, and just turn the bluetooth speaker on when required.
    I’ve not had luck doing this, as it normally causes BT to not allow new connections

    Then the music should continue from where it switched off. Is this possible with pCP? I have a python script that I tested on my main (non-pCP) Pi (where LMS is located) that will start squeezelite when a speaker is connected, and stop it when it disconnects - but this requires python and dbus (which I don't think are on pCP?). However, I can't use this as my main Pi is too far away from where I wish to use the bluetooth speaker. So, I was hoping that pCP could do something similar.
    Not using python, but am using dbus and scripts, but generally this is how it works. When squeezelite is disconnected for a while, LMS will not automatically restart either.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  10. #30
    Senior Member
    Join Date
    Mar 2017
    Posts
    1,123
    Quote Originally Posted by paul- View Post
    Iĺve not had luck doing this, as it normally causes BT to not allow new connections
    Ah, OK. Guess I'll try installing plain Raspbian on the Pi, and use my script.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •