Home of the Squeezebox™ & Transporter® network music players.
Page 33 of 38 FirstFirst ... 233132333435 ... LastLast
Results 321 to 330 of 379
  1. #321
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,110
    The Pi3B+ is only Bluetooth 4.2. I would suspect that it is backwards compatible, but there is nothing in their manual that says that.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  2. #322
    Senior Member carsten_h's Avatar
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    615
    Quote Originally Posted by paul- View Post
    The Pi3B+ is only Bluetooth 4.2. I would suspect that it is backwards compatible, but there is nothing in their manual that says that.
    I asked them and yes, the headphone is backwards compatible. I didn't expect that they answer so fast, it took only 8 minutes. But maybe it's because they are only 23km away. :-)
    Pi4 4GB piCorePlayer with LMS and Squeezelite for USB inside an Argon One case
    Pi3B+ (7" Display, Hifiberry DAC+ Pro) piCorePlayer with Squeezlite/Jivelite for Hifiberry and Bluetooth headphone inside a SmartiPi touch case
    Two Airport Express
    Ikea Symfonisk

  3. #323
    Junior Member
    Join Date
    Dec 2020
    Posts
    10
    sorry for bothering you again, but is there anything new about being able to control bluetooth squeezelite instance with the IR remote or any other way except web interface?

  4. #324
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,110
    With the latest build, it will add the IR options from the squeezelite page to the bluetooth command line. I'm just not sure if you can have 2 squeezelite sessions running at the same time.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  5. #325
    Junior Member
    Join Date
    Dec 2020
    Posts
    10
    Oh, thanx Paul. But since I'm not very good at understanding, I would be grateful if you would tell me exactly what should I do to try, please.

  6. #326
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,110
    If you have a working IR setup with a squeezelite wired dac, then the bluetooth session will use the same IR commands. As for setting up IR from scratch with squeezelite, I've not done that. But it should be nothing more than setting up LIRC and then telling squeezelite where to find the configuration file.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  7. #327
    Junior Member
    Join Date
    Dec 2020
    Posts
    10
    Thank you, but unfortunately this does not work for me.
    I'v got a working IR setup with a squeezelite with dac or simply analog audio out.
    For bluetooth headphones squeezelite IR not react (no matter if main squeezelite is on or off)
    Only when I try to synchronize main squeezelite with bluetooth instance then IR working simultanetly, but then there are lot of strange sound drops or clics and i think that this is not acceptable.
    Regards,
    Ejdzi

  8. #328
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,110
    CAn you post your bluetooth log?
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  9. #329
    Junior Member
    Join Date
    Dec 2020
    Posts
    10
    Code:
    pCP Bluetooth extension build:0015
    Starting BT Controller
    bcm43xx_init
    Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
    Set BDADDR UART: b8:27:eb:87:4b:60
    Set Controller UART speed to 3000000 bit/s
    Device setup complete
    Waiting for bluetooth controller.Ready
    RPi Bluetooth Hardware Address: B8:27:EB:87:4B:60
    Starting pCP BT Pairing Agent
    BT Controller Ready
    01-16 17:49 CET INFO     ------------Starting pCP BT Speaker Daemon v7.0.0.0015------------
    01-16 17:49 CET INFO     Resetting asound.conf.
    01-16 17:49 CET INFO        Removing bt_ from asound.conf
    01-16 17:49 CET INFO     Current contents of /usr/local/etc/pcp/pcp-bt.conf.
    01-16 17:49 CET INFO        20:09:11:27:11:13#T Monitor#1000#1
    01-16 17:49 CET DEBUG    PCM Devices found dbus.Dictionary({}, signature=dbus.Signature('oa{sv}'))
    01-16 17:49 CET INFO     Starting connection signal handlers.
    01-16 17:51 CET INFO     ---- Caught Connect signal ----
    01-16 17:51 CET DEBUG    /org/bluealsa/hci0/dev_20_09_11_27_11_13/hfpag/sink
    01-16 17:51 CET DEBUG       HCI:hci0
    01-16 17:51 CET INFO        MAC:20:09:11:27:11:13
    01-16 17:51 CET INFO        TRANSPORT:hfpag
    01-16 17:51 CET INFO        Starting a2dp background monitor.
    01-16 17:51 CET INFO     ---- Caught Connect signal ----
    01-16 17:51 CET DEBUG    /org/bluealsa/hci0/dev_20_09_11_27_11_13/hfpag/source
    01-16 17:51 CET DEBUG       HCI:hci0
    01-16 17:51 CET INFO        MAC:20:09:11:27:11:13
    01-16 17:51 CET INFO        TRANSPORT:hfpag
    01-16 17:51 CET INFO     ---- Caught Connect signal ----
    01-16 17:51 CET DEBUG    /org/bluealsa/hci0/dev_20_09_11_27_11_13/a2dpsrc/sink
    01-16 17:51 CET DEBUG       HCI:hci0
    01-16 17:51 CET INFO        MAC:20:09:11:27:11:13
    01-16 17:51 CET INFO        TRANSPORT:a2dpsrc
    01-16 17:51 CET INFO        Connected T Monitor
    01-16 17:51 CET DEBUG       pCP OUTPUT="hw:CARD=Headphones,DEV=0"
    01-16 17:51 CET DEBUG       LMS server IP:""
    01-16 17:51 CET DEBUG       pCP ALSAVOLUME=""
    01-16 17:51 CET DEBUG       pCP Card Conf:"Analog.conf"
    01-16 17:51 CET INFO        Starting squeezelite with output device: bt_T_Monitor
    01-16 17:51 CET INFO        Device: dev_20_09_11_27_11_13, connected normally. Monitor exiting.
    01-16 17:51 CET INFO        Checking for squeezelite pid:10804
    01-16 17:51 CET INFO        Player Connected to LMS at: 192.168.0.20:9000
    01-16 17:51 CET INFO        Sending Play command for T Monitor to LMS at 192.168.0.20
    01-16 17:51 CET DEBUG       /usr/bin/wget -T 5 -q -O- --post-data='{"id":1,"method":"slim.request","params":[ "T Monitor", [ "play" ]]}' --header 'Content-Type: application/json' http://192.168.0.20:9000/jsonrpc.js
    01-16 17:51 CET DEBUG       Command returned 0

  10. #330

    cannot pair ?

    Hello

    I just finalized to upgrade to last PCP 7, last LMS, jivelite,...etc... All is working perfect, thanks to the developpers

    As I changed my smartphone from IOS =>Android Galaxy, no Airplay possible anymore.
    I wanted to use bluetooth to allow Android mobile to send music to PCP/LMS

    I insert a BT dongle laying around, install the libraries, apply last patches. It seems to be properly detected. But impossible to pair with my galaxy. This stupid phone asked for a PIN. I tried 0000 or 1234 without success

    same behavior with my laptop windows 10

    I tried with another BT dongle... I see my Samsung during the scan, but it does not appear in droplist. And from samsung, same effect, pairing error

    any idea to debug ?

    Thomas

    pCP Bluetooth extension build:0015
    Starting BT Controller
    Waiting for bluetooth controller.Ready
    USB Bluetooth Hardware Address: 00:15:83:15:A2:2C
    Starting pCP BT Pairing Agent
    Powering on the BT controller
    Success.
    01-30 12:41 CET INFO ------------Starting pCP BT Speaker Daemon v7.0.0.0015------------
    01-30 12:41 CET INFO Resetting asound.conf.
    01-30 12:41 CET INFO Removing bt_ from asound.conf
    01-30 12:41 CET INFO Config file: /usr/local/etc/pcp/pcp-bt.conf is not found. Make sure to pair devices.
    01-30 12:41 CET DEBUG PCM Devices found dbus.Dictionary({}, signature=dbus.Signature('oa{sv}'))
    01-30 12:41 CET INFO Starting connection signal handlers.
    Last edited by tparvais; 2021-01-30 at 05:48.

Posting Permissions

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