Announce: piCorePlayer 8.0.0

[Labarum]

I notice that when setting USB output to a DAC there are a number of options. Why is that? Isn't the USB transfer a standard protocol? Why is it not "one for all"?

If I am not using a named DAC I presume I just use the generic option. What might I expect to hear if I experiment with the others?

[Greg Erskine]

The "Output setting" is really just passing the card name and dev number to an ALSA plugin in the ALSA configuration.

If the "Output setting" is blank, ALSA will use a default config, probably the hw: plugin, with CARD=0 and DEV=0. In your case, if your USB DAC is sitting on CARD 0 it might just work (or output to Headphones?).

I think the hw plugin connects to the hardware with little ALSA processing.

I also think the number of ALSA options is defined by the manufacturers driver.

[Labarum]

The "Output setting" is really just passing the card name and dev number to an ALSA plugin in the ALSA configuration . . .

Thanks Greg, but that will need a good deal of unpacking to make sense to me. I know that ALSA is the heart of the Linux audio engine.

[denmla]

You still need to watch your distance too. The RPI bluetooth transmitter is not the strongest. What I might recommend would be to start an ssh shell. Use ps to find the bluealsa process. And kill it. Disconnect your headphones first.

The run bluealsa from command line, and you will see all kinds of debug info.

$ sudo /usr/local/bin/bluealsa --profile=a2dp-source --profile=a2dp-sink --profile=hsp-ag --profile=hfp-ag --aac-afterburner

Once running, connect your headphones, and start playing music. And then just watch for any debug info that might occur when you hear your hiccup in audio. (Please note for others reading this message a month or so from today(2/7/2022) I will be upgrading blueasla soon and that will change the commandline used.

First of all, thank you for the support and for the suggestions. Wanted to provide some feedback and maybe help out someone else having similar issue. I had audio stutter when streaming radio, using tidal/spotify or playing local tracks. I did not find errors with the above commands, but it is definitely related to the quality of the Bluetooth signal (or better to say not the strongest bluetooth transmitter). Although it is below 10m distance from the bluetooth receiver, I've moved RPI4 closer and stutter was mostly gone (so thanks about that tip Paul).

After that I've bought an external dongle (first one I've found in nearby store, it was gembird bt500 mini bluetooth 4.0 dongle). But I was not successful in getting this to work, as it turned out cambridge silicon radio chip used in this usb dongle is a fake chinese copy. I've tried to patch the OS, but was unsuccessful as this is beyond my knowledge of linux. Anyway, I've managed to return this one to the store and bought a new one (TP-link UB400 nano) and I can confirm this one works out of the box. So anyone having issues with RPI4 bluetooth and needs a small low power dongle, this one is working (you cannot believe how hard is to find online info which one is working good).

That being said, stutter is almost all gone. I still have stutter when streaming radio stations (I'm trying to figure out what is the cause, because it is not the same with all stations), but tidal and spotify are working fine. So if someone is having bluetooth issues, 99% it is related to the bluetooth quality....as everything is working as expected.

[jbraveman]

Picoreplayer 8.00 confusing players

I’ve noticed a problem that just cropped up. I’m running picoreplayer 8.00 and lms 8.2.0 (windows). Two of my players are being confused by LMS. They switch back and forth on the sever. Music will play but then stops after a song. One of the players is remote and the other is located on my home network. I’ve attached a short video of the behavior I’m not sure how to troubleshoot.

I have a fresh install of 8.00 on "picoreplayer WO" device and 8.1 on "picoreplayer LR". I renamed the LR player to living room and it still causes the same behavior. I have multiple other boxes with various versions picoreplayer on them and have not had a similar problem. I can definitely keep one of them off since I wouldn't ever use them both at the same time. I'm just curious if anyone knows why I would be having this issue.

https://www.dropbox.com/s/cyxmj7qo0e81p0u/IMG_6137.MOV?dl=0

Thanks

[Howard Passman]

Remote control through AudioLab M-DAC+

I use a AudioLab M-DAC+ and the included remote control controls some of the players functions. Can someone tell me how basically that works so I can ask a question in the correct forum.

Obviously somehow through the USB interface.

Thanks,

Howard

[cburbs]

I noticed with HDMI power set to off on a few of my Pi's it is still on if I do the following.....

sudo tvservice -s


state 0x40000 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced

Why is that and can I fix it?

The above is on a:
Raspberry Pi Model B+ (B PLUS) 512MB Computer Board
piCorePlayer v8.1.0 | www v00017 | linux 5.10.77-pcpCore (32) | piCore v13.1 | Squeezelite v1.9.9-1391-pCP


Same on this device...
Raspberry Pi 3 Model B Motherboard
piCorePlayer v8.1.0 | www v00017 | linux 5.10.77-pcpCore-v7 (32) | piCore v13.1 | Squeezelite v1.9.9-1391-pCP

[Jaca]

Hi, I've added IR sensor for remote operation and it works fine, but was wondering if there is an option in PcP to have audible remote "clicks"? I don't have screen on rpi3 so it would be handy to hear if remote signal was registered. Thanks

[Greg Erskine]

I’ve noticed a problem that just cropped up. I’m running picoreplayer 8.00 and lms 8.2.0 (windows). Two of my players are being confused by LMS. They switch back and forth on the sever. Music will play but then stops after a song. One of the players is remote and the other is located on my home network. I’ve attached a short video of the behavior I’m not sure how to troubleshoot.

I have a fresh install of 8.00 on "picoreplayer WO" device and 8.1 on "picoreplayer LR". I renamed the LR player to living room and it still causes the same behavior. I have multiple other boxes with various versions picoreplayer on them and have not had a similar problem. I can definitely keep one of them off since I wouldn't ever use them both at the same time. I'm just curious if anyone knows why I would be having this issue.

https://www.dropbox.com/s/cyxmj7qo0e81p0u/IMG_6137.MOV?dl=0

Thanks

Just to let you know I am not ignoring you, I have read this post a couple of times and unfortunately can't offer any help as I don't use remote players.

[Greg Erskine]

I use a AudioLab M-DAC+ and the included remote control controls some of the players functions. Can someone tell me how basically that works so I can ask a question in the correct forum.

Obviously somehow through the USB interface.

Thanks,

Howard

I have a Topping E30 with a remote, but once the E30 is setup I don't need the remote. Is it the same for the AudioLab M-DAC+?

I do use a SB remote to control squeezelite on pCP.

[Greg Erskine]

Hi, I've added IR sensor for remote operation and it works fine, but was wondering if there is an option in PcP to have audible remote "clicks"? I don't have screen on rpi3 so it would be handy to hear if remote signal was registered. Thanks

There is no pCP option.

Where is the click coming from?

Not all RPi's have built-in audio and none has a built-in speaker.

On the SB controller it actually has a additional mono DAC which I assume is only for the clicks but I think you can only hear the clicks if you have headphones connected. ALSA configuration is also required to handle output to 2 DACs. So it has been done before and someone could work out how it was done.

I have thought about it before, but IMHO it is one of those things that requires a lot of effort with little payback.

[cburbs]

I’ve noticed a problem that just cropped up. I’m running picoreplayer 8.00 and lms 8.2.0 (windows). Two of my players are being confused by LMS. They switch back and forth on the sever. Music will play but then stops after a song. One of the players is remote and the other is located on my home network. I’ve attached a short video of the behavior I’m not sure how to troubleshoot.

I have a fresh install of 8.00 on "picoreplayer WO" device and 8.1 on "picoreplayer LR". I renamed the LR player to living room and it still causes the same behavior. I have multiple other boxes with various versions picoreplayer on them and have not had a similar problem. I can definitely keep one of them off since I wouldn't ever use them both at the same time. I'm just curious if anyone knows why I would be having this issue.

https://www.dropbox.com/s/cyxmj7qo0e81p0u/IMG_6137.MOV?dl=0

Thanks

I am not sure if mine is the same but I have seen mine where one of my players will just disappear from LMS all together. All mine are on my home network. I still can access the picoreplayer it just goes in and out of LMS players. Usually I just restart LMS along with all 4 of my picore players and things seem to go back to normal.

A remote player could be more difficult to troubleshoot as there are alot more variables involved.

Have you tried restarting from scratch on the one on the home network to see if that resolves the problem?

[Jaca]

There is no pCP option.

Where is the click coming from?

Not all RPi's have built-in audio and none has a built-in speaker.

On the SB controller it actually has a additional mono DAC which I assume is only for the clicks but I think you can only hear the clicks if you have headphones connected. ALSA configuration is also required to handle output to 2 DACs. So it has been done before and someone could work out how it was done.

I have thought about it before, but IMHO it is one of those things that requires a lot of effort with little payback.

Ohh OK thanks, yeah I just though maybe I did miss this option in settings somewhere.
I had in mind it would work like SB Touch "remote navigation sounds/clicks" so just from main/std outputs
I have hifiberry dac+pro hat so from that in my case but I guess generally from primary sound source..

I naively assume it would be case of:
if there is IR /licrc command /signal or smth then play sound(wav or mp3 of click etc) .. But like I said its navie assumption as I got no idea how things works ubderhood and if its anything more complicated then I completely agree it's not point spending time on this as its little payback indeed thanks

[indigo]

Hi, I've a RPI with piCorePlayer server and I need to have a push button to shut it down since I cannot connect to it with a PC.
I've seen that in pCP tweaks page there is the option to configure a GPIO to have a clean shutdown, and I've seen that I need to install this " shutdown-monitor.tcz" extension
What next ? I'm a linux newbie, is there any step by step guide to have a working shutdown button ?

[Grumpy Bob]

Hi, I've a RPI with piCorePlayer server and I need to have a push button to shut it down since I cannot connect to it with a PC.
I've seen that in pCP tweaks page there is the option to configure a GPIO to have a clean shutdown, and I've seen that I need to install this " shutdown-monitor.tcz" extension
What next ? I'm a linux newbie, is there any step by step guide to have a working shutdown button ?

I use these - https://shop.pimoroni.com/products/o...nt=41102600138 either with its built-in switch or by wiring a separate momentary switch to it.

Robert