Hello!
Does anyone here know if the Raspberry Pi 3 B+ can connect to a
Bluetooth headphone with Bluetooth 5 (Sennheiser 458BT)?
Or is this only possible with an external Bluetooth adapter?
pi4 4gb picoreplayer with lms and squeezelite for usb inside an argon
one case
pi3b+ (7\" display, hifib
TomS wrote:
> I have successfully got it (pCP 7.0) running on a rPi 3b (64-bit).
> Right now playing out of the rPi headphone jack into an amp, but will
> likely add a hifiberry dac.
I had problems with pCP 7.0b6 on my Raspberry Pi 3 B+ and Hifiberry DAC+
Pro with the 64bit version. There are
Hi shunte88,
just tested the new version concerning the "powersave". Same behaviour
as in my last post '#206'
(https://forums.slimdevices.com/showthread.php?111790-ANNOUNCE-LMS-Monitor-2020&p=1004081&viewfull=1#post1004081).
Aki
ralphy wrote:
> Using an ALSA output prefix other than hw: with the -o option "hides"
> some or all of the physical capabilities of the audio hardware from
> squeezelite behind the ALSA subsystems.
Sorry, why if i press the "restart" button in the web interface
squeezelite start (the icon becom
corrobor wrote:
> Sorry, why if i press the "restart" button in the web interface
> squeezelite start (the icon become green) and instead if i do this
> command in SSH Shell "/usr/local/bin/squeezelite -n "Stereo" -o
> hw:CARD=R20,DEV=0 -a 80:4::1:" the icon Is Red ?
pCP calls
sudo /usr/local/e
Paul Webster wrote:
> pCP calls
> sudo /usr/local/etc/init.d/squeezelite status
> which looks for a pid file and then checks to see if the listed process
> is running
>
> So if you called
> sudo /usr/local/etc/init.d/squeezelite restart
> or
> sudo /usr/local/etc/init.d/squeezelite start
> rath
Man in a van wrote:
> things to try
>
> does the usb input stay alive in Amp standby ?
>
> Check if you can defeat the auto-off inactivity timer
>
> Check / change the usb class
>
> If you have an old pi, install pCP on that and see if the external usb
> power will power the pi
I solved:
1
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'
(https://www.paypal.com/cgi-bin/webscr?cmd
carsten_h wrote:
> I had problems with pCP 7.0b6 on my Raspberry Pi 3 B+ and Hifiberry DAC+
> Pro with the 64bit version. There are dropouts in the sound at random
> places. When I used a Bluetooth headphone that didn't happen. After
> changing to the 32bit version everything is fine!
Well, I r
TomS wrote:
> Well, I reflashed to 32-bit, no change. Restarted LMS, no change.
>
> I also have a piZero that I got running, it shows the same behavior (the
> music control buttons the pCP web interface do not work). Since these
> buttons work for others, I am led to believe something about m
slartibartfast wrote:
> I assume you are trying to control the piCorePlayer from the web page
> for that device. I just tried those controls for the first time and they
> work for me.
>
> Sent from my Pixel 3a using Tapatalk
Thanks for confirming it works (for you). Not so important it works,
paul- wrote:
> 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'
Hello!
I tried to build the same for my Harman/Kardon Soundsticks.
I found this in dmesg when I switch them off and on again:
Code:
[ 126.710090] usb 1-1.4: USB disconnect, device number 4
[ 131.288928] usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
carsten_h wrote:
> Hello!
>
> I tried to build the same for my Harman/Kardon Soundsticks.
> I found this in dmesg when I switch them off and on again:
> >
Code:
> > [ 126.710090] usb 1-1.4: USB disconnect, device number 4
> [ 131.288928] usb 1-1.4: new full-speed U
corrobor wrote:
> My writing mistake, i have just correct the post: i missing a "comma"
> before "RUN" in udev rules (after idproduct). Add a comma and try.
I added it, made a backup, tried your commando, but nothing happened.
Then I did a reboot, looked at the file and it was changed, but noth
carsten_h wrote:
> I added it, made a backup, tried your commando, but nothing happened.
> Then I did a reboot, looked at the file and it was changed, but nothing
> happened. :-(
Ok. So when you Power on your USB dac , nothing happened.
The udev rule: i made a specific rule, i called It 10-rote
carsten_h wrote:
> I added it, made a backup, tried your commando, but nothing happened.
> Then I did a reboot, looked at the file and it was changed, but nothing
> happened. :-(
>
> These are the rights of the files:
> >
Code:
> > -rw-rw-r--1 root root
corrobor wrote:
> Try this:
> Change the Number of the rule from 97 to 10;
> remove sudo from udev in the run dection;
> Change script permission ti 777 (chmod 777 soundstick.sh)
> Let me know
I changed the number to 10 and changed the filetool.lst file.
I removed the sudo in the udev-rules fil
carsten_h wrote:
> i changed the number to 10 and changed the filetool.lst file.
> I removed the sudo in the udev-rules file (is it that what you meant)?
> I changed the permission.
>
> Now it is working!
>
> I changed the permissions back to 755 and it is still working.
> It seems to be the s
corrobor wrote:
> perfect
Thank you for your very fast help!
Now I don't have to use a script from Home Assistant to start
squeezelite again when I switch on the Soundsticks with Home Assistant.
I think it is better handled in piCorePlayer directly.
pi4 4gb picoreplayer with lms and squeezel
just pushed an update
caught another edge case
some fixes in tag logic too - composer and quoted strings (JSON side
effects)
let me know how that looks
if still seeing odd behavior add the --verbose flag and post the output
cheers
As of *13-Jan-2021* my digitized collection is (25074 hours 42
kbeast wrote:
> Sorry not sure i caught the whole story, but if your trying to wake a
> device on wifi, the device can't be sleeping either, typically they will
> still show network status lights.
>
> In addition, ususally have to be on the same switch as its a broadcast
> packet. Try to wake
Can one of you collect the files and info and the submit them to the pCP
documentation project?
https://docs.picoreplayer.org/publishing/create_new_document/
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc aust
Paul Webster wrote:
> Can one of you collect the files and info and the submit them to the pCP
> documentation project?
> https://docs.picoreplayer.org/publishing/create_new_document/
Ok i will do It tomorrow!
corrobor's
carsten_h wrote:
> Thank you for your very fast help!
> Now I don't have to use a script from Home Assistant to start
> squeezelite again when I switch on the Soundsticks with Home Assistant.
> I think it is better handled in piCorePlayer directly.
Sorry a question: why you have add this string
corrobor wrote:
> Sorry a question: why you have add this string in the script? "sudo
> /usr/local/sbin/alsactl restore"
I have set a higher output level with alsamixer for the Soundsticks
because they are too quiet with the normal setting. To restore this
value after reconnecting, I use this c
verbose looks ok, but still the same results.
Soft power on, display stays black:
...
2021-01-14 20:43:16 :: src/lmsmonitor.c-1029 : isRefreshed
2021-01-14 20:43:16 :: src/lmsmonitor.c-1067 : activeScroller test
2021-01-14 20:43:16 :: src/lmsmonitor.c-1072 : display clock test
2021-01-14 20:43:1
It has to be something unique to your LMS or network.
If you haven't changed LMS port numbers, then do you have a firewall
that is not giving access to port 9090 for LMS CLI.
Greg Erskine's Profile: http://forums.slimdevi
carsten_h wrote:
> I have set a higher output level with alsamixer for the Soundsticks
> because they are too quiet with the normal setting. To restore this
> value after reconnecting, I use this call. Normally it will only be
> called at boot time.
Understood
We transitioned away from the CLI interface a while back. We are using
the JSON interface, since the buttons are in your browser, they are
fully subject to crossposting rules on your server.
TomS,
What do you have "CSRF Protechtion level" security set on your LMS
server?
Settings->Advanced->
Since updating (in-situ) to pCP 7.0, every few days the player seems to
lose network connection. This is a WiFi, but the pCP and the router are
in the same room, so the signal strength is 100 %. I'm not sure if it is
coincidence, but it seems to happen (sometimes) when initiating play
from the "o
pputzer wrote:
> Since updating (in-situ) to pCP 7.0, every few days the player seems to
> lose network connection. This is a WiFi, but the pCP and the router are
> in the same room, so the signal strength is 100 %. I'm not sure if it is
> coincidence, but it seems to happen (sometimes) when ini
paul- wrote:
> We transitioned away from the CLI interface a while back. We are using
> the JSON interface, since the buttons are in your browser, they are
> fully subject to crossposting rules on your server.
>
> TomS,
>
> What do you have "CSRF Protechtion level" security set on your LMS
>
TomS wrote:
> Thank you Paul! My CSRF Protection was set to medium. Frankly I have
> no idea how it got set that way, I don't remember ever looking at that
> screen, but maybe I set it years ago and it has just maintained through
> upgrades over the years.
>
> All working now. Amazing.I once
0.96inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SSD1306
https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-3/0.96inch-oled-b.htm
1.3inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SH1106
https://www.waveshare.com/1.3inch-OLED-B.htm
1.5inch OLED Module OLED White (16 gra
@Aki7 - very odd
this is a nice to have but I'll keep poking at it to see where it could
be going awry - until I do remove the argument from your call
that extra line in the script controls the mute/unmute on one of my amps
- it shouldn't be in the deployed script so remove it
I'll be pushing an u
shunte88 wrote:
>
> @LiFePO4
>
>
> The SSD1306 and SH1106 are fully supported and work OOTB
>
> The grey scale and color aren't on the radar, although 1327 should be a
> quick tack on top of the 1322 implementation
>
> I've both of those devices but no plans for the color 128x128 - I'm
> fav
37 matches
Mail list logo
