Elmar.F wrote:
> Hello everybody,
>
> Until yesterday TIDAL worked fine on my piCore 7.0.1 based ALLO BOSS2
> Player. Today TIDAL plays only 4 sec silently of each track and skips to
> the last track. Radio Paradise and streaming from my harddrive attached
> to the BOSS2 works fine.
>
> Can
Hi!
Is it possible to add this dev build of shairport sync which finally
allows airplay2 functionality to pCP?
LINK - h t t p s : / /
github.com/mikebrady/shairport-sync/blob/development/AIRPLAY2.md[/
thanks!
received the P02, followed the steps in this thread and successfully
booted using the 64-bit version of picoreplayer. benchmarks showed that
the 64-bit version was more performant despite the 512mb ram. some
notes:
1. P02 boots with a 3.3v power supply just like the older version
2. To turn off
shunte88 wrote:
> ... I'll be pullling the updated graphical engine into the trunk by the
> weekend ...
Okay, six weeks have passed since then. I think there has been no update
yet.
When will the support for the new OLED displays come?
Best regards
PiPlayer
chill wrote:
> I've done a couple of fresh installs under pCP8.0.0 (one on a Pi Zero W
> and one on a Pi Zero 2 W), and can confirm that following all the steps
> described 'this post'
>
Hello everybody,
Until yesterday TIDAL worked fine on my piCore 7.0.1 based ALLO BOSS2
Player. Today TIDAL plays only 4 sec silently of each track and skips to
the last track. Radio Paradise and streaming from my harddrive attached
to the BOSS2 works fine.
Can anybody help me out please? What
mftech wrote:
>
> I've read the thread but it's unclear to me if the code from Chill hans
> been check-in in Picoreplayer 8.0.
>
I've done a couple of fresh installs under pCP8.0.0 (one on a Pi Zero W
and one on a Pi Zero 2 W), and can confirm that following all the steps
described 'this
mboxler wrote:
> I'm a linux newbie as well, but I did get it to connect to my wifi.
>
> Just to be clear, the new firmware-rpi-wifi.tcz ended up in
> /mnt/mmcblk0p1/
>
> The file to be replaced is in /mnt/mmcblk0p2/tce/optional/
>
> I simply executed the mv command to replace the old file
I have a suspicion what might have caused the write permission issue
with my stick.
The USB stick was originally formatted on a Synology NAS. The data was
then copied onto the stick via the NAS. So the rights on the stick were
definitely not belonging to "tc".
That would explain why initially i
