Yatsushiro wrote:
> A wifi dongle with a different chipset!
hehe! Yes, I think you might be onto something. I got mine cheap off
ebay so maybe that explains it.
pufnstuf's Profile:
Looking for advice from you clever people. The udev rule is working
very nicely in my setup - Squeezelite starts quite reliably when the DAC
appears.
But there's a related issue. If the USB DAC disappears while
Squeezelite is running, it causes problems with other synced players -
playback
I think I have a solution. There are a number of 'substitutions' that
are available when a udev rule is triggered ('see here'
(https://linux.die.net/man/7/udev)). The most appropriate one for my
case seems to be $parent.
> $parent, %P
> The node name of the parent device.
These temporary
Realtek drivers are awful to maintain. I may end up dropping all of
them Im trying to maintain. Its just that pCP doesnt have a dkms
environment. But its not hard to compile. Its on my list to make a
utility for pCP to build out of tree drivers.
piCorePlayer a small player for the
philippe_44 wrote:
> Have you tried with transcoding but without use of sox (choose a
> transcoding requirement that does not need it like "ops mp3" or "mp3 mp3
> transcode forced by bitrate limitation. The idea is to see if this is
> specific to an external transcoder, especially sox, or if
I went with '$kernel' in the end (-"The kernel name for this device"-),
rather than '$parent'. It looks something like this:
Code:
1-1.3.1
It meant that it took less effort to create, after boot, the text in the
file that is checked by the
That seems to work as hoped. I just need to fix the condition after I
power up my DAC and RPi simultaneously. In that case the DAC is
available before Squeezelite needs it, so the original udev rule for
detecting when DAC appears is never triggered, and my file with the node
name isn't
Howard Passman wrote:
> https://www.amazon.com/gp/product/B08HV9P6KV/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8=1
>
>
> OSOYOO IPS 5 DSI Portable Touch Screen Display Monitor for Raspberry Pi
> 4 3 2 Model A B
>
> Worked right out of the box, touch screen and all. Make sure the
> rotation is
philippe_44 wrote:
> Yous aid it does not happen with x64, right? What Perl version is this
> on x86?
What?
all the system I have tested on are 64bit, Perl version 5.32
https://audiodigitale.eu
Simonef's Profile:
Simonef wrote:
> Same problem if transcoding without sox. Flac->mp3 and Flac->pcm dont
> use SoX and shows the same beahviour.
> I just tried with lms 7.9.4, same behaviour again.
>
> w/o transcoding it seems to not happen at all.
Excellent, that seems to point around the pipeline then
LMS
Pommes wrote:
> I am running pcp 7 64bit on Raspberry 3 with a usb dac sound blaster
> play3.
> I had to increase the volume in alsamixer.
> I tried all described in this thread, but only putting alsactl restore
> into tweaks commands solved my problem
Same for me, the alsamixer level setting
philippe_44 wrote:
> Have you tried with transcoding but without use of sox (choose a
> transcoding requirement that does not need it like "ops mp3" or "mp3 mp3
> transcode forced by bitrate limitation. The idea is to see if this is
> specific to an external transcoder, especially sox, or if
Make sure you backup after saving. Nothing is retained between reboots,
unless you backup.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Simonef wrote:
> What?
> all the system I have tested on are 64bit, Perl version 5.32
Sorry my bad: from memory, I was remembering
>
> With Debian 64bit this bug does not seem to happen at all.
>
And for some reasons I thought it meant your actual system was 32 bits
LMS 7.9 on Pi 3B+ &
Nice that we can buy almost any size touch screen now and make them work
with very little effort. I ended up building a case/stand out of black
acrylic for mine. Holds the screen and the pi with plenty of room to
spare.
Enjoy :-)
jeroen2 wrote:
> I bought the 3.5" and can confirm it works out
chill wrote:
> In practice it seems to work well - the Squeezelite player now appears
> and disappears in sync with the DAC powering on and off, so my remaining
> synced players are only briefly interrupted when Squeezelite starts.
I really don't understand why here at the first switching on
carsten_h wrote:
> I really don't understand why here at the first switching on of the USB
> speakers still nothing works. Only when switching off and on again it
> works.
Yeah, that's a puzzle. You might get a clue if you run 'sudo udevadm
monitor' before you plug the speakers in the first
And then the second switch on (it works then):
Code:
KERNEL[116241.326971] add
/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.4
(usb)
KERNEL[116241.329235] add
paul- wrote:
> Make sure you backup after saving. Nothing is retained between reboots,
> unless you backup.
I definitely did a backup (pcp bu) after saving but it didn't retain the
setting.
coyrls's Profile:
In case anyone else finds it useful, this is my script for starting and
stopping squeezelite in response to udev events.
Code:
#!/bin/sh
# Script to be used by udev rules that detect when a USB DAC is connected or
disconnected,
# in order to start or stop
What is in your boot log?
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=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you like the
philippe_44 wrote:
> Sorry my bad: from memory, I was remembering
>
> And for some reasons I thought it meant your actual system was 32 bits
Oh! no problem. If you need some help for testing or other things don't
hesitate to contact me.
@mherger I made a pull request on slimserver-vendor
Can you tell whether your script is being triggered by the first
insertion? In other words, is the problem due to the script not
running, or because the command to start squeezelite is failing?
In my case the use of the 'bind' action solved the same issue, but
that's possibly only because it
paul- wrote:
> Its just that pCP doesnt have a dkms environment.
Hi Paul, thank you for the reply. I have found loads of guides online
for compiling the drivers myself but they all refer to using dkms...
What should I use in its place on PiCore?
Cheers!
@mherger I made a pull request on slimserver-vendor
Would that PR fix the issue you've reported here?
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
25 matches
Mail list logo
