Eyerex wrote:
>
> Only problems is meters as think you can only load one image at a time
> in \SqueezePlay\lua\applets\JogglerSkin\images\UNOFFICIAL\VUMeter
Where to get them?
seekasoul's Profile:
I have a MacMini M1, would love to use this VUMeter skins on
SqueezePlay...
Sure I have an rpi runinng pCP but without a display attached.
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View
Still not clear how to update from piCore command line.
paul- wrote:
> The latest default RPI4 bootloader is 2021-04-29
> Otherwise you can download an extension from github that has that
> firmware in it and use the command line tools.
>
> https://github.com/piCorePlayer/rpi-eeprom/releases
Is there a new Rpi4 Firmware available?
How can this be installed?
Currently running: 000138a1
Wed Mar 17 11:25:36 UTC 2021 (1615980336)
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View
paul- wrote:
> That's likely a compatibility issue with the Waveshare screen, you
> might try looking at the waveshare support. How does that screen
> connect?
It's a Audiophonics RaspDAC based on Raspberry PI 2 B rev a01041
tc@pCP:~$ uname -a
Linux pCP 5.4.83-pcpCore-v7 #1 SMP Fri Dec 18
paul- wrote:
> I built that driver/extension, you can install it from the extension
> interface.
>
> rtl8821cu-5.4.83-pcpCore-v7.tcz
>
> source repo is https://github.com/brektrou/rtl8821CU
Unable to install this WiFi Dongle, looks like the device is seen as USB
Mass storage:
tc@pCP:~$
cortegedusage wrote:
>
> I see you've got plans to get the raspdac mini v1 16x2 display to work,
> I believe this is the same display.
> What can I do to get it to work?
>
I've got it too! Never found a way to get the display work with
piCorePlayer. It would cool to have it working!
shunte88 wrote:
> Release 0.4.72 inclusive of updates to the binary has been uploaded to
> the repo
>
> 'LMSMonitor 0.4.72' (https://github.com/shunte88/LMSMonitor)
>
> This is a maintenance release for the most part
>
> The intermittent memory reallocation abend has been resolved
>
> Lots
shunte88 wrote:
> what you've posted looks good - nothing out of the ordinary
>
> did it lockup?
>
> if so what did you see with the logged output?
>
>
Yes. Very easy to reproduce. When I start playing a track it freezes
now!
2021-01-31 08:18:07 :: src/lmsmonitor.c-1029 : isRefreshed
shunte88 wrote:
> -V on the monitor not squeeze
>
> you need to run the monitor manually so you can observe and capture the
> logging
>
tc@piCorePlayer:~$ sudo /mnt/mmcblk0p2/tce/lmsmonitor --name
"piCorePlayer" -k -w -c -rixv --meter "rn" -x 0x3d -c -f 7 -z -w0 -db
-V
OLED Mode
shunte88 wrote:
>
> have you run with -V - what does the monitor "-think-" its doing?
>
What do you mean?
Putting: -V in Squeezelite Settings -> Various Options?
seekasoul's Profile:
shunte88 wrote:
>
> i added additional safety code for the realloc and those changes are in
> the current available build
Just uploaded latest build, but after playing about 10 min with airplay
the clock display is already frozen!
No blinking ":" beetween hour and min...
It's very annoying.
shunte88 wrote:
> how long is a piece of string? :p
>
> not sure what you mean by stuck
> is the monitor freezing?
> are you referring to the colon flash not being bang on the second?
>
> a bit more detail...
The monitor freeze with the time stuck at random hour:min displayed.
Then only a
Why the time get stuck so easily on the display?
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View this thread: http://forums.slimdevices.com/showthread.php?t=111790
paul- wrote:
> Error message are common as hardware and drivers may not be present at
> the time the firmware/overlays cause the kernel to probe the driver.
> What are you looking for?
My idea is to understand the reason for the error. I know some cosmetic
bugs can still be there without
I have this at the moment (running *dmesg*):
[0.638437] BCM2708_FB SOC:FB: UNABLE TO DETERMINE NUMBER OF FBS.
DISABLING DRIVER.
[0.638450] BCM2708_FB: PROBE OF SOC:FB FAILED WITH ERROR -2
ls -l /dev/fb*
CRW--W--W-1 ROOT ROOT 29, 0 DEC 19 16:18 /DEV/FB0
What's wrong?
Hello, bit out of topic, sorry. Is the driver for this cool DAC Hat from
OSA Electronics (Spain) be likely to be (ever) impemented in
piCorePlayer?
DACBERRY ONE+
Some info there:
https://www.osaelectronics.com/product/dacberry-one-plus/
shunte88 wrote:
> I'll get a system setup and poke around some
> Are you setup on Pi3 or Pi4?
Rpi 4 and DAC is I2S.
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View this thread:
shunte88 wrote:
>
> let me know if you do hit snags, I have the code open today so I'm ready
> to start any type of review
Unable to make it work with pCP 7.0.0 Beta, can you help me into doing
it?
seekasoul's Profile:
Any chance to use it with 7.0.0 Beta version?
*i2c-tools-dev.tcz* seems no more downloadable as an extension on the
repositories...
Let me know.
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
Roland0 wrote:
> Run
> >
Code:
> > sudo squeezelite-cdsp.sh status
> >
> to see if camilladsp is running
>
> tc@piCorePlayer:~$ sudo squeezelite-cdsp.sh status
>
> Running processes:
> PID User ELAPSEDCPU Command
> 10209 root 4:16
fastfwd wrote:
> Do some processing that has a large, unmistakable effect. For example,
> delay only one channel by 1000 milliseconds, or insert a highpass filter
> with a 10 KHz cutoff frequency.
Can this verified with some commands on the pCP after applying the
changes?
ralphy wrote:
> You need to Install LIRC for squeezelite if you want the remote to
> control squeezelite headless ie. not running jivelite.
>
> You are using the configuration file for lircd not the client. It
> should be /home/tc/.lircrc which is installed as part of the LIRC setup.
Now it
mherger wrote:
> > But how to understand if something is really changed in the sound?
>
> Trust your ears. If you can't hear the difference, then it's probably
> not worth the hassle ;-)
>
> --
>
> MichaelI meant, is there a way to see if the DSP process is okay? Aside the
placebo effect
Is this sound correction all done automatically?
I followed the instructions for having ir running on pCP 6.1.0 here:
https://github.com/Lykkedk/Camilladsp-SampleRate-Control
But how to understand if something is really changed in the sound?
Paul Webster wrote:
> Have you enabled IR in the pCP Tweaks page and the IR page.
Sure, this is what I have in the Tweaks:
32081
32082
+---+
|Filename: lirc1.JPG|
|Download:
I cannot use this remote with LMS 8.0.0 on pCP .
irw gives me correct ouput messages but LMS does not seem to receive IR
keys at all...
32080
What I am missing?
Running on:
RPi4 with IS2 hat DAC OSA Electronics DACBerry ONE+
piCorePlayer v6.1.0 | linux 4.19.122-rt52-pcpAudioCore_v8
After last update i get blank screen and this message:
tc@piCorePlayer:~$ cd /mnt/mmcblk0p2/tce
tc@piCorePlayer:/mnt/mmcblk0p2/tce$ sudo /mnt/mmcblk0p2/tce/lmsmonitor
-n "piCorePlayer" -m sa -x 0x3d -
f 7 -z
This is lmsmonitor (0.4.58) - built Sep 20 2020 09:57:04.
SSE NOT SUPPORTED,
Solved with latest update, thanks!!!
shunte88 wrote:
> repo updated including binary
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View this thread:
I think after one of the latest update my screen stopped working. I used
to set OLED address to 0x3d. BUT NOW:
tc@piCorePlayer:/mnt/mmcblk0p2/tce$ sudo /mnt/mmcblk0p2/tce/lmsmonitor
*--addr 0x3d* --name "piCorePlayer"
lmsmonitor: Too many arguments
Try `lmsmonitor --help' or `lmsmonitor
Hi Again. Also on my other *RPI3* Audiophonics RaspDAC, I see just a
blinking cursor, but nothing else on the display (*WINSTAR 16x2 OLED*)
even if all looks right...
DAC HAT is *Audiophonics ISabre Q2M*
tc@piCorePlayer:/mnt/mmcblk0p2/tce$ ldd lmsmonitor
linux-vdso.so.1 (0x7e952000)
I attach you here the files used in Volumio where the display work.
Hope these are useful to you...
+---+
|Filename: DacBerry_Display_Volumio_Plugin.zip |
|Download:
Thanks, so can I try later when at home...with a new pCP install
(https://github.com/shunte88/LMSMonitor) ?
Will let ya know for sure!!
seekasoul
shunte88 wrote:
> Hi @seekasoul, apologies for the delay
>
> I updated the bcm code under the OLED driver to account for changes
&g
Please note: In Squeezelite settings I am using the Output as:
*hw:CARD=sndrpihifiberry*
The DAC is connected via Coaxial (digital) cable to my Amplifier.
tc@pCP:~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Thanks shunte88 !!! I'll keep on waiting for the new build... thanks in
advance...!
shunte88 wrote:
> after a bit of digging it looks like the bcm2835 driver code needs to be
> updated
> really not sure why it didn't complain on my builds???
> I'll post back when a new build is submitted to
I've set both switches. Still the same. See attachments...
+---+
|Filename: Various.jpg |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=29826|
I am a getting this now:
tc@pCP:~$ cd /mnt/mmcblk0p2/tce
tc@pCP:/mnt/mmcblk0p2/tce$ ./gomonitor sa
killall: lmsmonitor: no process killed
kill: sending signal to 9759 failed: No such process
Start LMSMonitor. Player: pCP
sudo cp /mnt/mmcblk0p2/tce/libArduiPi_OLED.so.1 /lib/
sudo
Still not getting it to Work... how to install *libArduiPi_OLED.so.1*,
tried to copy it manually with:
sudo cp /mnt/mmcblk0p2/tce/libArduiPi_OLED.so.1 /lib/
and rebooted but still missing it...
tc@pCP:~$ cd /mnt/mmcblk0p2/tce
tc@pCP:/mnt/mmcblk0p2/tce$ ls
gomonitor
38 matches
Mail list logo
