Home of the Squeezebox™ & Transporter® network music players.
Page 12 of 14 FirstFirst ... 21011121314 LastLast
Results 111 to 120 of 138
  1. #111
    Junior Member
    Join Date
    Jun 2020
    Posts
    3

    Issue with specific speaker

    Hi all,

    First of all, thanks for the hard work on PCP 6, so much improvments since the previous versions.
    I've just a question for the community. I'm using PCP 6.1 with the bluetooth version v0011.
    I can add 2 speakers to the bluetooth layer, no issue with that.
    I'm just wondering why I cannot add a specific speaker... it's a kooduu one... Each time I try to add it to the bluetooth configuration I just have a message telling the operation failed and the device will be removed.

    The most weird is that this speaker is working with my phone, and even was working with the version 5.x of picoreplayer.

    Does any of you have a tip to wee where I can look on specific log or whatever that can improve the situation?

    Thanks.
    Last edited by tekman54190; 2020-06-26 at 05:25.

  2. #112
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,185
    There are some devices that seem not to work with the automated pairing. You can try to manually do it from an ssh session

    1. Start SSH session
    2. type "bluetoothctl"
    3. type "scan on"
    4. When you see your device, type "scan off"
    5. Then get the mac address of the device. The format is xx:xx:xx:xx:xx:xx
    6. type "pair xx:xx:xx:xx:xx:xx"
    7. Hopefully the device pairs.....follow any prompts you see.
    8. If pairing works, type "trust xx:xx:xx:xx:xx:xx"
    9. type "quit"
    10. Then go to the pCP bluetooth web page, and you should see the device, make and changes you need....then press save. Press save, even if you don't make a change.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #113
    Junior Member
    Join Date
    Jun 2020
    Posts
    3
    Quote Originally Posted by paul- View Post
    There are some devices that seem not to work with the automated pairing. You can try to manually do it from an ssh session

    1. Start SSH session
    2. type "bluetoothctl"
    3. type "scan on"
    4. When you see your device, type "scan off"
    5. Then get the mac address of the device. The format is xx:xx:xx:xx:xx:xx
    6. type "pair xx:xx:xx:xx:xx:xx"
    7. Hopefully the device pairs.....follow any prompts you see.
    8. If pairing works, type "trust xx:xx:xx:xx:xx:xx"
    9. type "quit"
    10. Then go to the pCP bluetooth web page, and you should see the device, make and changes you need....then press save. Press save, even if you don't make a change.

    Many thanks !! I think the issue was a pin asked by the speaker... once I accepted the pin code... it worked.

    Very efficient troubleshooting

    I'm just wondering now why the speaker is not reconnecting automatically to PcP...
    Last edited by tekman54190; 2020-06-26 at 08:46.

  4. #114
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,185
    Quote Originally Posted by tekman54190 View Post
    Many thanks !! I think the issue was a pin asked by the speaker... once I accepted the pin code... it worked.

    Very efficient troubleshooting

    I'm just wondering now why the speaker is not reconnecting automatically to PcP...
    Bluetooth is set for pin less pairing, and most devices honor that, but some don't
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  5. #115
    Junior Member
    Join Date
    Jun 2020
    Posts
    3
    Ok but it was working with version 5.x this is weird

  6. #116
    Junior Member
    Join Date
    Aug 2017
    Posts
    14

    Two piCoreplayer(s), same sw versions, different DACs, bluetooth on one does not work

    Hi all, wish to thank all the developers for the wonderful work they're doing on piCorePlayer: such an integrated system ready to run on Raspberry is a dream come true for anyone willing to experiment a little with the verious options.

    I am also here to seek help for a couple of players I just updated/installed and not working properly in a few features.
    The main non working feature is the bluetooth in one of the players.
    In the updated player that I going to call "basement" the sw versions are as it follows:

    basement | piCorePlayer v6.1.0 | www v0009 | linux 4.19.122-pcpCore_v7 | piCore v10.3pCP | Squeezelite v1.9.7-1256-pCP

    This is from the bottom line in the web configuration page. On this player bluetooth work flawlessly and plays anything I play on the smartphone, including system sounds like notifications and the like.

    On another player that I am going to call "bedroom" and I have installed from scratch and report this versions:

    bedroom | piCorePlayer v6.1.0 | www v0009 | linux 4.19.122-pcpCore_v7 | piCore v10.3pCP | Squeezelite v1.9.7-1256-pCP

    bluetooth starts fine, pairs fine with a smartphone, but no sound comes out of the DAC, nor from the integrated Raspberry audio jack, when I play anything on the smartphone.

    Here is the bluetooth log from the non-working bedroom player:

    Code:
    pCP Bluetooth extension build:0011
    Starting BT Controller
    bcm43xx_init
    Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
    Set BDADDR UART: b8:27:eb:d6:78:4d
    Set Controller UART speed to 3000000 bit/s
    Device setup complete
    RPi Bluetooth Hardware Address: B8:27:EB:D6:78:4D
    Starting pCP BT Pairing Agent
    BT Controller Ready
    01-01 01:00 CET INFO     ------------Starting pCP BT Speaker Daemon v6.0.0.0010------------
    01-01 01:00 CET INFO     Resetting asound.conf.
    01-01 01:00 CET INFO        Removing bt_ from asound.conf
    01-01 01:00 CET INFO     Current contents of /usr/local/etc/pcp/pcp-bt.conf.
    01-01 01:00 CET INFO        BC:A5:8B:E6:17:C6#texarkana#10000#2
    01-01 01:00 CET INFO        D8:50:E6:08:D4:30#ME173X#10000#2
    01-01 01:00 CET DEBUG    PCM Devices found dbus.Dictionary({}, signature=dbus.Signature('oa{sv}'))
    01-01 01:00 CET INFO     Starting connection signal handlers.
    06-29 18:58 CEST INFO     ---- Caught Connect signal ----
    06-29 18:58 CEST DEBUG    /org/bluealsa/hci0/dev_BC_A5_8B_E6_17_C6/a2dpsnk/source
    06-29 18:58 CEST DEBUG       HCI:hci0
    06-29 18:58 CEST INFO        MAC:BC:A5:8B:E6:17:C6
    06-29 18:58 CEST INFO        TRANSPORT:a2dpsnk
    06-29 18:58 CEST DEBUG       pCP OUTPUT="hw:CARD=D10,DEV=0"
    06-29 18:58 CEST DEBUG       pCP ALSAVOLUME=""
    06-29 18:58 CEST DEBUG       pCP Card Conf:"USB.conf"
    06-29 18:58 CEST INFO        Starting player:"texarkana" bluetooth, alsa device:"hw:CARD=D10,DEV=0", volume:"".
    06-29 19:00 CEST INFO     ---- Caught Disconnect signal ----
    06-29 19:00 CEST DEBUG       HCI:hci0
    06-29 19:00 CEST INFO        MAC:BC:A5:8B:E6:17:C6
    06-29 19:00 CEST INFO        TRANSPORT:a2dpsnk
    06-29 19:00 CEST INFO        Stopping playback from texarkana
    texarkana is a Samsung A6+ smartphone that I connected to both basement and bedroom player, but working only on the basement player, while on the bedroom player I posted the log from, produces no sound whatsoever.

    Anyone can help with this issue?

    Thanx in advance.
    Paolo

  7. #117
    Junior Member
    Join Date
    Aug 2017
    Posts
    14

    How to store alsamixer gain?

    Hi all,
    I am having an issue with an external USB DAC gain in piCorePlayer after updating to 6.x.x version.
    When I try to use the "Card Control" button on the Squeezelite page i get a warning that it can't be used to control a USB DAC:

    • Sorry, you cannot control a USB DAC from this page.
    • Login via ssh.
    • Use 'alsamixer' to change the ALSA output level.
    • Save mixer settings by using Save button below.


    So I follow the suggested procedure and use alsamixer to bring the DAC volume up to 100% (it it set to 39 when I start alsamixer).

    The issue is that, although I "Save ALSA mixer settings to make them available after a reboot." as suggested on the web interface after exiting alsamixer in the ssh connection to the player, after reboot the volume reverts back to the 39 value every time.

    I also tried to use "alsactl store", after having switched to root with "sudo su" to avoid the "alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists" message from alsactl, since the file is owned by root, but it does not improve the situation.

    Can anyone help with this issue?

    TIA.

    Paolo

  8. #118
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,839
    hi psychokiller,

    Unfortunately I don't have USB DACs other than a $5 USB Headphone amp, so my experience is limited to that.

    Code:
    $ alsamixer
    $ sudo alsactl store
    
    # Check ALSAlevelout="Custom" has been set in your pcp.cfg file.
    $ grep ALSAlevelout < /usr/local/etc/pcp/pcp.cfg
    
    $ pcp bu
    regards
    Greg

  9. #119
    Junior Member
    Join Date
    Aug 2017
    Posts
    14

    How to store alsamixer gain?

    Quote Originally Posted by Greg Erskine View Post
    hi psychokiller,

    Unfortunately I don't have USB DACs other than a $5 USB Headphone amp, so my experience is limited to that.

    Code:
    $ alsamixer
    $ sudo alsactl store
    
    # Check ALSAlevelout="Custom" has been set in your pcp.cfg file.
    $ grep ALSAlevelout < /usr/local/etc/pcp/pcp.cfg
    
    $ pcp bu
    regards
    Greg
    Hi Greg, thanx for your help.

    ALSAlevelout is set to "Custom" but unfortunately executing those commands does not solve my issue: alsamixer setting does not seem to survive a couple of reboots and volume goes down to 39 again. Strangely it seems to survive a single reboot, but not twice.

    Paolo.

  10. #120
    Junior Member
    Join Date
    Jul 2020
    Posts
    3

    RPI4 misses Bluetooth output device in the list

    Hi all,
    I love this project.
    Fresh installed and updated piCorePlayer 6.1.0

    I have seen the light (heard som music through my headphones), but I cannot get a Bluetooth speaker in the works.
    I'm missing a Bluetooth Device in the list of devices.

    It seems that my pcp_bt.log contains a link or image so it is forwarded in my next post.


    What am I missing?
    Best Regards
    -Z

Posting Permissions

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