Jens Erik Jensen wrote:
> I have installed piCorePlayer 2.02 on an RPi1b+ and have problems when
> listening to web radio. The LMS is on a separate RPi3 running max2play,
> with music stored locally, and connected to my router via cable. The
> client RPi1b+ is connected via a TP-Link TL-WN725N
atrocity wrote:
> I've just obtained one of those mounts that insists on holding the
> screen updside down. I'm using Pi B+ with piCorePlayer 3.10 and have
> selected "Rotate screen" and rebooted, but everything is still upside
> down. Is this possibly a limitation of the older B+ hardware?
>
>
Greg Erskine wrote:
> Hi guys, RE: screen rotation.
>
> What is normal now?
>
> The "original" screen was upside down but we made the default to rotate
> it (even though SCREENROTATE="no").
>
> Do most people have the "newer" screen and have to rotate it all the
> time?
>
> Are your cables
Greg Erskine wrote:
> Thanks,
>
> I meant the flat ribbon cable between screen and screen PCB.
>
>
The ribbon cable is at the bottom.
AngloCuencano's Profile: http://forums.slimdevices.com/member.php?userid=64040
View
Benicz wrote:
>
> the field "output settings" is commented "should be empty" but states
> exactly what's set on the squeezelite settings page and is not
> editable.
> If I use sqlt settings to make it empty, sqlt won't start.
> How is that meant?
>
This might be part of your problem. For me,
Benicz wrote:
> ...coming from 3.02 (or so), I an now expieriencing mono output on the
> extra Asound page doesn't work anymore.
> I just get stereo whatever I change the settings to, and it used to be a
> nobrainer...
This probably won't be helpful to you, but mono output still works for
me
Stoker wrote:
> Hi
>
> I've just up graded to pCP 3.10 onto my rPi2B +IQ DAC, all went well
> until I enabled JiveLite, then I noticed I could no longer access the
> web server and on boot I am seeing the little yellow lightning bolt in
> top right corner of console. I guess this means my power
jemhayward wrote:
> Yes, it's present when using the DAC, and its present with analogue, and
> present when using a real Squeezebox Touch as well. I think it may go
> away when nothing is synchronised, but I only tried that for a short
> time last night, and the pops/clicks are quite random,
badsoden wrote:
> I did a fresh install of 3.0 as suggested with config backed up to a USB
> stick. I'm using a hifiberry Digi + board. Squeezelite will not start.
>
> Sent from my Nexus 6P using Tapatalk
I had a similar problem with a fresh install of the new 3.0 and a backed
up config using
sbp wrote:
> Those of you with HifiBerry problems - would you try to change your
> /mnt/mmcblk0p1/config.txt so that analog audio is changed to off.
> So please try to change the line so it is: dtparam=audio=off
>
> Then reboot and see if your Hifiberry DAC is working.
> Steen
This does not
Bemused wrote:
> Hi guys, is there a way to force mono?
> Using PI2 headphone jack to drive some garden speakers, need mono.
> Or do I ned to do it on the hardware side.
See this thread:
http://forums.slimdevices.com/showthread.php?105470-PicorePlayer-and-LMS-how-to-get-a-MONO-downmix
paul- wrote:
> @Anglo, When you installed the 3.20 image, did you start with config on
> a USB stick?
No, I just did a fresh install on the SD, and then configured everything
from scratch when the web GUI came up.
I am having a problem with vanilla version of 3.20.
System is a Pi 2B/IQAudio DAC+ and I am currently running a wired
connection. PCP appears to load correctly and I can access the web GUI
without any problem. I have selected the correct output, Squeezelite is
running and I can play music.
The
Greg Erskine wrote:
>
>
> 1. Jivelite requires a resizefs, then reloading. I think people could
> forget to come back and try again to load jivelite after resize.
>
> [/QUOTE,
>
> This was probably my problem the first time; I did forget to resize the
> file system before downloading
paul- wrote:
> The startup commands from PCP are perfectly normal. Can you check the
> diagnostics pages to see if there are errors in dmesg? (or just ssh
> into your box and run dmesg) You might also check your cables, to make
> sure you didn't unseat the ribbon cable while changing your SD
Greg Erskine wrote:
> hi AngloCuencano,
>
> Your issue sounds like a network problem.
>
> When you initially install piCorePlayer it automatically sets the
> timezone, this requires internet access. Does your timezone get set
> correctly? You can manually set this
I have two piCorePlayers (Pi Zero/phatDAC and Pi A+/IQAudio DAC +, both
wireless) neither of which consistently sets the correct time on boot
and then defaults to December 1969.
This doesn't seem to affect the performance of the Zero, but the A+ has
the official Raspberry Pi touchscreen and
Greg Erskine wrote:
> Hi AngloCuencano,
>
> Glad to see you got it working even after my false lead. :)
>
> What happens when you ping pool.ntp.org?
>
>
The average ping is a bit slower than yours (28
Greg Erskine wrote:
> I wonder why you are having problems then?
Well, if you don't know...
I think the ping response is a bit of a red herring though. I tried
pinging south-america.pool.ntp.org, and that response is significantly
slower (~150ms). Nevertheless, using the south america pool
epoch1970 wrote:
> It could be this:
> https://www.raspberrypi.org/forums/viewtopic.php?f=28=141454#p938961
> Before meddling with iptables, I would suggest trying to connect with an
> USB ethernet dongle or another make of wifi interface that doesn't use a
> broadcom chip to confirm this is not
zi99y wrote:
> I'm having a problem connecting Wifi when there is a dollar symbol ($)
> in the password. I have tried saving it in Wifi Settings in the web
> config page, as well as the CLI setup tool on the pi itself. In both
> cases the Wifi password becomes truncated at the dollar symbol. It
paul- wrote:
> Yes, the RPi2 is an armv7 device. What Dac are you using? Hifiberry
> Dac+ on a RPI3 is working flawlessly. Did you check your digital volume
> control on the "Card Control" page? Otehrwise more diagnostics is going
> to be needed.
I repeated the in situ upgrade to 3.5.0
I did an insitu update from 3.22 to 3.5.0 audiocore. Everything appeared
to go OK, audio output was set automatically to Hifiberry DAC+ (and Pro,
AMP2) and squeezelite was running. If I attempt to play a file, the web
UI shows the file to be playing, but there is no sound. Rebooting and
powering
TimG wrote:
> Hi psketch,
>
> I'm not surprised I'm doing it wrong...!
>
> Normally (ie by default, before I started doing anything to mess things
> up) the output device was specified as hw:CARD=sndrpihifiberry. The
> default setting plays stereo, but I only have one speaker connected to
>
psketch wrote:
> I certainly used the UI controls in the past, but
>
> 1) I haven't tried them in pcp 7, and the underlying card control has
> changed with the latest kernel. Probably still works of course, but
> not sure - e.g. if you're using HDMI, which devices is device 0?
> 2) It's
Greg Erskine wrote:
> Tick.
Actually, I don't think the card was my problem.
There seems to be an odd interaction between the Tweaks page and the
ALSA settings. If I toggle the LMS control bar on or off, after the
automatic squeezelite restart, the ALSA settings are blank, and of
course there
I successfully did in situ updates on a few piCore players, but one
player fails to play after updating.
This is a Pi A+ that I use with analog output in an old transistor radio
to make a portable player. The player connects to the wifi network,
Squeezeplayer is running, and "Headphones" is the
Greg Erskine wrote:
> Audio output device settings = Headphones
> Output setting = hw:CARD=Headphones
> ALSA setting = 80::0:
>
> Should be your settings. This is the default for pCP8.0.0.
I tried a fresh install on a new card, and now it works.
I guess my old card is getting worn out.
28 matches
Mail list logo
