0.4.62 is now "live" on github including an updated binary; same
install/update procedure as before
this release is mainly aimed at a reduced memory foot-print and
stability
all "PROGMEM style" resources have been removed and replaced with define
on call implementations. This leads to much
did you add the switches to expose the audio data through squeeze
player
> From the Squeezlite page of the pCP web frontend type *1* in the "*m*"
> ALSA parameter section
>
> And, in the Various Options add *-v*
>
> See the squeezelite page for more details
>
you can see its entering the
Don't ask what i did, but no i got i connected.
Put my AP to channel 1, Set b+g+n (instead of only g+n)
And no it is connecting again.
Don't know which setting did the trick.
I update now the last one of my pCP Player (4 in summary) to 6.1.0 and
hopefully i am good again for the future.
Just
Thanks Ralphy :)
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread: http://forums.slimdevices.com/showthread.php?t=97046
___
unix
Barnosch wrote:
> Thanks for your reply.
>
> If i use another SD card with a freshly installed 6.1.0 it works
> perfectly. So i think it is not a issue with the channel (currently i
> use 11 fixed)
> Very weird. I did not change somehting or configured something funny
> like WPA3.
>
> This is
Man in a van wrote:
> >
Code:
> > sudo nano /var/log
> [09:07:08.328223] stream_sock:543 unable to open SSL socket -1 (1)
> [09:10:21.631165] stream_sock:543 unable to open SSL socket -1 (1)
> >
>
> Does this mean that I have to perform the
paul- wrote:
> My guess is that your AP is using a WiFi channel that the zero doesnt
> like. Try changing the WiFi channel on your AP.
Thanks for your reply.
If i use another SD card with a freshly installed 6.1.0 it works
perfectly. So i think it is not a issue with the channel (currently i
2012 Mac-mini running High Sierra
I have managed (after a few trials and tribulations) to install
Squeezelite-x86_64-1.9.7r1278.dmg
Thanks Ralphy :)
It works but I have this message in the logs
Code:
sudo nano /var/log
[09:07:08.328223] stream_sock:543 unable to
sander wrote:
> I've been following this thread for a while and I have two simple
> questions regarding the compatibility of underlying systems.
>
> If I set up a docker compose file with all the mount points and ports I
> want, I should be able to seamlessly switch between docker containers
