Hi, first poast.
Does anyone know how to disable the LEDs in picoreplayer?
Particularly the blue and blinking LED of my Edimax 2.4 GHz WLAN adapter
is bothering me. But, if possible, I'd also turn off the LED on the Pi
board itself as well as the one on the I2S sound card.
nietgiftig wrote:
Black tape?
Black paint?
What I had in mind was some Linux command line wizardry ;)
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
JackOfAll wrote:
If that adapter is the Edimax 7811 using the RTL8188 chipset and the
8192cu driver Not sure you can do this at runtime via a module
option. ISTR, that the module needs to be 'compiled without CONFIG_LED
being defined'
Jesperlykke wrote:
Yep...
So if i/we should be able to try to make this, we need the following
from poing::
Output from lsmod
tc@hifiberry:~$ lsmod
Module Size Used byNot tainted
snd_soc_hifiberry_dacplus 2445 0
bcm2708_dmaengine 7465 1
virt_dma
Jesperlykke wrote:
Email it to me, the file config.tgz - lykkelinux at gmail.com
I am trying to download config.gz to my PC but it doesn't work.
On my picoreplayer (it has hostname hifiberry), I copied config.gz to
my home folder.
Then, from my PC, I use scp tc@hifiberry:~/config.gz
. I am
Jesperlykke wrote:
Hope it helps ???
Jesper,
Thank you so much for all your help. Still trying to find my way around
tinycore...
I did install mc following your instructions. But mc doesn't run. See
below
Code:
tc@hifiberry:~$ tce-load -i mc
Jasper, JackOfAll, Greg:
Very grateful that I receive so much help here as a newbie to tiny
core.
Jesperlykke wrote:
Email it to me, the file config.tgz
I've attached the config.gz file to this forum post. Turns out the
compressed size is only 26 KB. 16757
JackOfAll wrote:
PS. On another
JackOfAll wrote:
And at that point, I don't have anymore time to spend on this right now.
That's fine, thanks for taking the time to respond (and for your
previous testing).
@Jesper: You're the man, thanks you are still trying to figure this out!
JackOfAll wrote:
I did make an image for you guys.
w00t, thanks a lot!
I will test this as soon as I get home. Will report back.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
poing wrote:
I will test this as soon as I get home. Will report back.
Sorry for the belated update (I was actually doing some upgrades to my
stereos in the meantime.)
I just wanted to confirm that JackOfAll's build has been working
perfectly for some time now. Finally, no more blinking LEDs
^^^I would use the Linux i386 binary if you're on a Linux x86 system.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread: http://forums.slimdevices.com/showthread.php?t=97046
Nope, the Ethernet port is still hooked up internally via USB.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread: http://forums.slimdevices.com/showthread.php?t=103048
I'm a little lost.
I guess transcoding is CPU-bound. So it's nice to know the RPi 2 is up
to the task. But what are the relevant benchmarks for other LMS
functionality such as library scans, web gui access, artwort resizing or
multiple concurrent player accesses? Is that CPU-bound as well? Or is
Michael,
A big thank you for the answers! The info you provide is extremely
useful for me :)
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
JackOfAll wrote:
I'd be inclined to stay away from USB drivers
A typo, I assume? (USB hard disks should be class-compliant.)
Personally, I don't hold USB drives in high regard. The drives tend to
run hotter in an USB enclosure than in a NAS, as the latter usually have
a fan. Thus, I wouldn't
Quad core ARM, 1 GB RAM.
Announcement expected for later today. The best bit: same $35 price
point as the B+. Should be really nice for running LMS.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
JackOfAll wrote:
I actually have 7x Pi2B's humming away right now
Krisbee wrote:
I need seven of them?
I thought Mr. Jack forgot the irony tags.
Krisbee wrote:
is the Pi2B a candidate for a LMS sever with local USB HDD drive
storage, or is the hardware still too limited?
I
JackOfAll wrote:
You'll be lucky to see real-world speeds of 65Mb... ;)
pippin wrote:
Still definitely more than USB...
No, pippin, that can't be right. A USB 2.0 HDD must be faster than 65
Mbps, even on a Pi. After all, 65 Mbps = 8 MBps (perhaps more commonly
written as 8 MB/s).
USB 2.0
pippin wrote:
I'm using gigabit Ethernet which the Pi doesn't have
Yeah, the fact that the Pi2 doesn't have Gigabit ethernet concerns me a
bit. It's probably the reason why I'm not getting it and put SoA on it.
Michael confirmed in another thread that various functionality of LMS is
jfo wrote:
The alsamixer volume level on 1.19 seems to be set at 50% as default. I
just installed it this week and also found the volume to be low. You can
use Putty to change it to a higher level.
Thanks so much!! Changing the volume in alsamixer resolves the issue
indeed. This was driving
alnames wrote:
The alsamixer is set to 50% by default on the HDMI connected Pi while
the analog are all at 100% by default.
Yeah, I ran into this issue, too, after upgrading to 1.19. The value
used to be at 100% in prior versions.
While it's no big deal--I got excellent help in this thread--I
For a few days, I've been having the problem that the output level of my
B+ is waaay too low. I am not sure that the issue is picoreplayer, but
am out of ideas on how to fix the issue and would surely appreciate some
help.
The player is a B+ is running picoreplayer 1.19. It is hooked up to my
Squeezemenicely wrote:
I seriously hope he is well and will return, since he is one of the very
few really important developers here.
I am extremely grateful to them.
+1 million
Triode has some amazing projects going, I'm very thankful for the stuff
he puts out. I'm certainly willing to
^^^ I've hardly ever used Arch but my guess would be such kernel
parameters can be specified in the bootloader's configuration file
(e.g., you could edit /etc/default/grub on a Debian system).
poing's Profile:
Since upgrading from 1.19 to 1.19i, I'm getting severe dropouts on a B+
with HDMI audio. Like, not just short glitches, but long dropouts of up
to one-fifths of a sec or so.
Any suggestions? Should I just downgrade or is there something else to
try first?
I hope it's RL intruding and not some BS legal stuff. I'm quite thankful
for his innovative and useful projects.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
JackOfAll wrote:
And rather than crapping all over Steen's thread, we should leave it
there.
The thread belongs to the community, not Steen. (Legally it belongs to
Logitech.)
Back-to-topic: I think your claim that the HDMI out is not bit-perfect
is controversial. Via Google, I found
^^^ Interesting. I realize you know much more about this stuff than I
do, but I'm still wondering if there are other possible causes for your
finding.
Are you sure you disabled all processing in squeezelite, picoreplayer,
LMS and such, including easy-to-forget stuff such as Replaygain?
psketch wrote:
Hi Jack
Curious about your reference to HDMI limitations - not saying there
aren't any of course, but would be curious on what issue you see with
the Pi (2) HDMI output.
+1, I'd be curious as well.
I am a happy user of the RPi B+ with audio over HDMI. I don't believe in
CommanderROR wrote:
Thanks.
I found that it has something to do with the later versions of xterm.
Apparently they use xterm-256 as their standard, and picoreplayer only
supports the old standard. My Android SSH app allows me to change the
setting, and then I can access alsamixer. I'll see
sbp wrote:
We have dropped support for the cli setup in the most recent versions of
piCorePlayer. So now all settings are changed via your web-browser.
Ah, okay, I was just about to post the same thing.
Two other things I've noticed:
1.) During the upgrade from 1.19i to 1.19k, my
Greg Erskine wrote:
What audio out are you using?
I don't think the ALSA volume was ever remembered during upgrades? I
haven't seen any code that would have done this, but it would be nice if
it happened!!
Greg,
Thanks for taking the time to reply.
This happens on my Hifiberry DAC+
seq
crw-rw 1 root audio 116, 33 14. Jun 14:51 timer
[root@cubie ~]#
Krisbee wrote:
poing,
Now I've had a chance to do a bit googling, the situation with the
Cubietruck using Archlinux ARM and SOA seems to be this:
(1) Triodes' Cubietruck installer is now
Man in a van wrote:
Try a re-format of the card with the recommended tool
https://www.sdcard.org/downloads/formatter_4/
then re-burn the image and try again.
Sometimes a different card works.
Ok, I tried those suggestions to no avail.
Also look further back in this thread
So, I did get SoA to install via the manual route (i.e., installing it
on top of a base Arch system).
Two quick questions: I'm currently running the Squeeze Server 7.9
install in the SoA web interface. Will this get me the most recent
nightly of LMS 7.9?
If not, is it doable for someone like me
Sorry guys for all my questions.
I have one major problem with SoA on the Cubietruck: No soundcards are
available!
Code:
cat /proc/asound/cards
--- no soundcards ---
Note that the SoA installer failed (see above). So I install SoA via
Bump. Ideas on the no-sound issue on the Cubie? '#1453'
(http://forums.slimdevices.com/showthread.php?101624-Announce-Squeeze-on-Arch-developer-versionp=821307viewfull=1#post821307)
poing's Profile:
Krisbee,
Many thanks! I wasn't aware of those thread. I will start over that way.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
I'm trying to do a clean install on a Cubietruck but am stuck.
I placed the image for the Cubie (latest from github, dates Feb 15 or
something) on the microSD and booted it. Installation step 1 completed.
I got a popup to reload my browser which I did. After that, I can't
access the web GUI
sbp wrote:
Yes we have a new version in internal testing
Cool, can't wait :)
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread: http://forums.slimdevices.com/showthread.php?t=97803
d6jg wrote:
Generally I am more interested in now playing display than control
however in one intended use case I would prefer just a Pi with a
HiFiBerry Amp to power some bathroom or kitchen speakers and perhaps a
touchscreen built into the wall. In most cases I'd just want a Pi with
DAC+
soundcheck wrote:
I think ARCH Linux as a base for the CubieTruck can not be used
anymore!!! Being bleeding edge comes at a high price, at least in the
Cubitruck case.
Not trying to steer the discussion too far off-topic... But, as I've
come to the same conclusion, let me ask: Is there a
Krisbee wrote:
Not seen anything other than what I posted two months ago @ #1483 -
https://wiki.debian.org/InstallingDe..._SD_card_image or
http://www.igorpecovnik.com/2013/12/...sd-card-image/
Thanks for the reminder. Of course, back then, your post #1483 was very
useful and I installed
Is there a new major version about to go live? The screenshots in the
how-to on the picoreplayer website look suspicious...
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
utgg wrote:
the HifiBerry DAC+ measures well enough to be considered 'transparent',
even if feeding very high quality amp and speakers. I've no reason to
think that any other DAC would sound any better.
Seconded.
Next issue with my Cubie. (It's running the LMS server only; as the
kernel misses the module for the Cubie's sound card, there's no
squeezelite running.)
I can't update Arch anymore. When running
Code:
pacman -Syu
I get the following error
^^^ Thanks, guys.
Going back to Perl 5.21 seems to work.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
probedb wrote:
> Any thoughts anyone? I have no issue with any of the other sources on
> the AVR.
In piCorePlayer -> Squeezelite Settings, have you got "80:4:32:0" under
ALSA params? In case you haven't adjusted that, you're bound to get
dropouts.
Recently (with 1.21), I can't ssh into my picoreplayers anymore from a
cygwin shell.
Code:
$ ssh -l tc picoreplayer
Unable to negotiate with 192.168.1.76: no matching host key type found. Their
offer: ssh-dss
ssh works with my Ubuntu
Greg Erskine wrote:
> Hi poing,
>
> We develop piCorePlayer using PuTTY and winSCP so both of these still
> work fine...but...and I am not sure if this is related
>
Hi Greg,
Thanks for taking the time to reply. Based on JackOfAll's hint, I
checked out which version of openssh
sbp wrote:
> I can't reproduce - but please notice that a change will only become
> active after a reboot.
>
Steen, thanks. Ultimately, with your comment, I was able to resolve the
issue.
I had a different host name (let's say foo) stored under Tweaks prior to
updating picoreplayer to 1.21. My
Thanks a lot for the update, guys :)
I have two small issues:
1.) It seems the new version 1.21_RPI (running on a B+) doesn't obey the
hostname I set in the "Tweaks" section of the web UI. Despite me
changing the hostname to something different, my router displays it as
piCorePlayer. When
I don't know why logo78 needs to login as root, considering he can just
su to root after logging in.
Greg Erskine wrote:
>
> By default, piCore doesn't have a root login. Try adding the "superuser"
> bootcode to cmdline.txt. I have never tried this because I am old school
> about using "root"
Title says it all. I just did a clean install of 1.21g on a B+ with a
Hifiberry DAC+. Squeezelite won't start. Reboots don't help.
Of course, I changed the Audio Output device in the web gui (in section
Squeezelite Settings) and saved those.
The web GUI says the squeezelite command string is:
feeder6 wrote:
> I have changed the settings. But it doesn't work.
Just to confirm: After saving the new settings, did you restart
squeezelite?
Also, you provided some more info in the German forum. I can only second
that shielded ethernet cables can be a substantial noise source (German
probedb wrote:
> I had to switch output to headphone (onboard), reboot, switch output to
> DAC+, reboot and it seemed to sort it. However I've since removed the
> DAC+ as HDMI out is fine :)
Thanks for the suggestion. Unfortunately, it doesn't do the trick in my
case.
I don't know if you guys remember: The Hifiberry DAC+ hat on a B+ was
broken in 1.21g. I just upgraded from 1.21b to 1.22 and am happy to
report that it's working again. Thanks :)
poing's Profile:
IIRC, the Max2Play Website (shop.max2play.com) sells one but it's quite
pricey.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread: http://forums.slimdevices.com/showthread.php?t=104897
Just a tiny little thing: The insitu from 2.00 to 2.01 disabled WiFi for
me.
I had to move the Pi to a location where LAN is available to regain
network access. After firing up the web UI, going to WiFi settings and
hitting the "Save/Connect" button, it connected just fine.
Greg Erskine wrote:
> Hi poing,
>
> You shouldn't have to do "amixer -c0 cset numid=3 2" because we have it
> in our startup script, so we need to work out why it missed running
> the command.
>
> By any chance do you have "ALSA output level" set
JackOfAll wrote:
> You could try "amixer -c0 cset numid=3 2" to force it to route to HDMI
> rather than headphone jack
This did the trick. It even seems to survive a reboot (after running
your amixer command, I executed the usual "sudo alsactl store" and "sudo
filetool.sh -b").
Thanks so much
I can't get the HDMI output to work. I'm using a B+. The last version
that works for me is 1.21b (and I've tried each release since!)
In 2.00, I've noticed that after switching the Audio output to "HDMI
output:" and rebooting, picoreplayer sets the output (the -o flag) to
"hw:CARD=ALSA." That
The Pi Zero is currently in stock at pimoroni in the UK. No, I'm not
affiliated with them. I'm bringing this up as I think it would be nice
if picore users donate one (or two) Pi Zeros to the devs. I'd throw in
5. Any other user up for this?
Any chance this thread could be locked up?
It's not helpful that questions regarding picoreplayer 2.x are posted in
two separate threads. It appears random which question appears in which
of the two threads. Unless there's any system which I fail to
comprehend.
So I just put a fresh 2.04 image into my Pi Zero. It's hooked up to my
LAN via a Micro SB 5pin Um RJ45 10/100M Ethernet Adapter Model
KY-RD9700. The KY-RD9700 is a cheap 1-2 unit from China, but it
supposedly works with the RPi.
My Pi Zero is hooked up to an AVR via HDMI. I can see the log of
Steen,
Thanks a lot for the heads-up and for the sweet new version of
picoreplayer!
I might just go the WiFi route. Of course, if anyone else got an
microUSB ethernet adapter working, I'd be curious to find out how you
did it :)
I reported this issue a few month ago when the openssh version built
into cygwin stopped working with picoreplayer.
Code:
ubuntu@ubuntu:~$ ssh tc@picoreplayer
Unable to negotiate with 192.168.0.21 port:22: no matching host key type
found.
Their offer: ssh-dss
Greg Erskine wrote:
>
> Does loading the extension openssh.tcz help?
Thanks for the suggestion.
Actually, before reading your reply, I was able to find another
solution. It is to pass the following option to the openssh client:
Code:
ssh
Greg Erskine wrote:
>
> Does loading the extension openssh.tcz help?
Thanks for the suggestion.
Actually, before reading your reply, I was able to find another
solution. It is to pass the following option to the openssh client:
Code:
ssh
paul- wrote:
> I just realized, I did the notice in the old 3.0 thread.
>
> pCP3.11 changes
Just a very minor thing: On the pCP website, the release date of the
3.11 update is given as Feb 23, 2017. Perhaps someone has the chance to
fix that.
Julf wrote:
> Ethernet has better reliability and throughput, especially on a Pi, so
> it will give less of a risk of dropouts. If by "soundquality" you mean
> something else, I suggest discussing it in the "audiophile" section.
The shielding of ethernet cables can be a noise source. I'm not
I upgraded some RPi 1 Model B's from 2.0.6 to 3.0.2 via the "save
settings in 2.0.6 to USB and attach thumb drive on first boot of 3.0.2"
route. I'm loving the convenience of it.
Now, I would like to some something like that with my Pi Zeros. However,
each Zero's sole Micro USB port is occupied
Sorry if the question is redundant (I searched this thread trying
various keywords and also did some google searches).
I have a Pi Zero (non-W). As is standard, it's set up using a wifi
dongle hooked up via a USB OTG adapter. I installed Jivelite in pcp
4.0.0 but can't get through the initial
paul- wrote:
> what port is your LMS server web interface running on, you will need to
> set that in pCP
Thanks for the quick reply, my LMS server's HTTP port is 9002. I've set
that on the pCP in question and saved it. It's still not working when
directly issuing the command in an ssh session.
paul- wrote:
> Do the LMS control buttons on the pCP Web page work properly?
Yes, they do.
Thanks for looking into it.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
mherger wrote:
> Would you have another Pi to set pCP/Jivelite up with? You then could
> copy all of ~/.jivelite to the Pi Zero. That's where all of the settings
>
> are stored.
>
Michael, many thanks!
This is the solution I was looking for. I couldn't image otherwise. It's
a *nix box,
I'm trying to turn off a squeezelite player off every night at 11 pm.
The player is a RPi 3 running pcp 4.0.0. LMS 7.9 runs on a Synology NAS
in the local network.
So, I'm not good at scripting and might have to ask you guys later about
that, but for now my problem is at an even earlier
@Jeff07971 and @mherger
Many thanks and a bit of a rookie mistake on my part. It works perfectly
now.
poing's Profile: http://forums.slimdevices.com/member.php?userid=63617
View this thread:
78 matches
Mail list logo
