Did anyone find a solution to this?
I just set up a 3B+ running PCP and the Spotty plugin, wired to router
with gigabit, but find Spotty just as slow as others have described in
this thread...
piguy's Profile:
beans wrote:
> hey mherger,
>
> Running Raspian. Memory looks fine. top says ther's 500BM free. So I
> guess not memory bound.
>
> When I start playing a track squeezebox has around 12% usage with a
> brief spike up to 50%ish
>
> 25637
>
> While the track is playing spotty-hf seems to be
What do you mean by all wireless mode? As in, the way the pi connects to
the network? The server pi is connected via ethernet cable. The three
Ok, that's what I wanted to know.
tips for debugging? Looks like I use the docker image to build spotty
"Looks like I use docker" - didn't you do
What do you mean by all wireless mode? As in, the way the pi connects to
the network? The server pi is connected via ethernet cable. The three
clients are connected via WiFi (Pi ZeroW).
If I find a spare few hours I might try to build and debug the spotty
plugin on the pi. Hopefully that'll
Running Raspian. Memory looks fine. top says ther's 500BM free. So I
guess not memory bound.
Agreed, nothing obviously wrong there.
When I start playing a track squeezebox has around 12% usage with a
brief spike up to 50%ish
Hmm... I wouldn't even expect LMS to do much work in this case. It
hey mherger,
Running Raspian. Memory looks fine. top says ther's 500BM free. So I
guess not memory bound.
When I start playing a track squeezebox has around 12% usage with a
brief spike up to 50%ish
25637
While the track is playing spotty-hf seems to be using between 3-15%
with an occasional
beans wrote:
>
> Server: Raspberry pi 2B (exclusively running LMS)
>
What OS are you using? Could you be running low on memory? Can you watch
"top" while you tart playing a track? Is it CPU, RAM or I/O bound?
Michael
http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo
Hi! I just wanted to give my feedback as well with version 2.33.
Starting a new song will take:
- regular song in lms : instant
- web radio: less than 1 sec
- spotty from Spotify: 6 seconds (current playing song stops 2 seconds
after changing track followed by a 4 seconds gap)
- spotty from
Apologies for the threadjack
FWIW: that query is poorly implemented in that it doesn't give the
server time to "breath". LMS is basically cooperative multi-tasking: a
long running task can tell LMS to do some streaming every now and then.
I don't do this in that particular case. I probably
mherger wrote:
> > I built LMS onto some new (secondhand) hardware today.
> > An HP Microserver, AMD Turion(tm) II Neo N40L Dual-Core Processor, 2
> > cores with 8GB RAM and a 32GB SSD i.e. a very capable machine
> > OS is Vortexbox 2.4 hacked about a bit and with Logitech Media Server
> >
I built LMS onto some new (secondhand) hardware today.
An HP Microserver, AMD Turion(tm) II Neo N40L Dual-Core Processor, 2
cores with 8GB RAM and a 32GB SSD i.e. a very capable machine
OS is Vortexbox 2.4 hacked about a bit and with Logitech Media Server
Version: 7.9.1 - 1521043527
Music is
I built LMS onto some new (secondhand) hardware today.
An HP Microserver, AMD Turion(tm) II Neo N40L Dual-Core Processor, 2
cores with 8GB RAM and a 32GB SSD i.e. a very capable machine
OS is Vortexbox 2.4 hacked about a bit and with Logitech Media Server
Version: 7.9.1 - 1521043527
Music is
mherger wrote:
> > Actually I have realised that the piCorePlayer move Cache etc
> probably
> > creates a symlink in which case iPeng is correct but it is
> misleading.
>
> Can you confirm that Settings/Information would report the same as
> iPeng?
>
> And could you move the cache back to
Actually I have realised that the piCorePlayer move Cache etc probably
creates a symlink in which case iPeng is correct but it is misleading.
Can you confirm that Settings/Information would report the same as iPeng?
And could you move the cache back to on-device, just to be sure the pCP
<->
d6jg wrote:
> @Pippin
>
> iPeng is misreporting the location of the Cache etc - LMS is on
> piCorePlayer based Pi3 but the Cache & Prefs are on my NAS !!
>
> See post above.
Actually I have realised that the piCorePlayer move Cache etc probably
creates a symlink in which case iPeng is correct
mherger wrote:
> > Make sure that items per page for the web-UI is the default 50 .
> Having
> > 200 or so so that you can scroll a bit before selecting next page
> does
> > have a performance impact .
>
> And make sure you have decent storage media for your cache: when you're
>
> browsing
So, no solution found.
Flac/PCM setting on filetypes makes no difference.
Card is Samsung Evo 32GB.
System seems quite idle while streaming from Spotify (check image).
Connection is good (other local LMS works fine with spotty).
So, no clue, really.
24703
Class 10 card. Items per page is 50.
Cache is here
[image:
https://uploads.tapatalk-cdn.com/20180311/03c7cb6d98ae0615c9c8bcbb05e26eeb.jpg]
Sent from my iPhone using Tapatalk
PI3 PCP/LMS STORAGE QNAP TS419P (NFS)
*Living Room* - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
*Office* -
Make sure that items per page for the web-UI is the default 50 . Having
200 or so so that you can scroll a bit before selecting next page does
have a performance impact .
And make sure you have decent storage media for your cache: when you're
browsing albums LMS will have to read all the
d6jg wrote:
> I am running piCorePlayer on a wired Pi3 as a dedicated LMS with FLACs
> on a NAS via NFS.
> No issue with Spotty but I think I have found a limitation of the
> hardware.
> If I ask LMS (via the web interface) to display "Albums with small
> artwork" it kills playback until the
I am running piCorePlayer on a wired Pi3 as a dedicated LMS with FLACs
on a NAS via NFS.
No issue with Spotty but I think I have found a limitation of the
hardware.
If I ask LMS (via the web interface) to display "Albums with small
artwork" it kills playback until the search has completed.
This
Happens with both squeezebox touch & squeezelite.
Was 10 seconds with raspbian, so I should be happy now :/
Running on pCP behind a slowish 10Mbps connection a skip usually takes a
bit more than one second here.
It will play a playlist just fine, when a song ends the next one loads
Try PiCore player its even faster than max2play much less overhead.
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3
sub.
slartibartfast wrote:
> Are you saying that skipping to the next song takes 5 seconds? I use
> max2play and skipping has no delay.
>
> Sent from my SM-G900F using Tapatalk
Yeap, that's what I'm saying.
Happens with both squeezebox touch & squeezelite.
Was 10 seconds with raspbian, so I should
philosopher wrote:
> So, tried Max2play, works noticeably better, around 5 seconds
> between skips.
> Max2play does not seem to be my thing (how can I boot to console? lxde
> is awful), but anyway, I'll see if I can live with it.
>
> So, max2play performs better, why is that?
> Can anyone
So, tried Max2play, works noticeably better, around 5 seconds
between skips.
Max2play does not seem to be my thing (how can I boot to console? lxde
is awful), but anyway, I'll see if I can live with it.
So, max2play performs better, why is that?
Can anyone tell us what does the max2play
Spotty on rp3 with pcp, running fine
*SqueezeBoxes:* 2x SB2 (Living room and study), 1x Radio (Kitchen), 1x
Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden)
1x OSMC + Squeezelite (Movie room), 1x Touch (Bedroom)
*Server:* LMS on Pi3 7.9.1. on PcP 3.21
*Network:* AVM
Man in a van wrote:
> In what way "basically followed"?
>
>
> I have followed Gerrelt's blog for both LMS and Squeezelite installs on
> rpi3b without any problems.
>
> I have also, in the past, run the spotty app from LMS, trouble free. I
> don't, however, now listen to Spotify so can't
philosopher wrote:
>
>
> Do you have a guide for Lms installation on pi? Maybe some library
> missing/bad version?
> I've basically followed this one
> http://www.gerrelt.nl/RaspberryPi/wordpress/tutorial-stand-alone-squeezebox-server-and-player-for-bbq/
>
> Thanks
In what way "basically
philosopher wrote:
> Installed the plugin, did not build it.
>
> Forgot to mention, when client is connected to Lms running on other
> machines, same network/internet access, everything is perfect. So there
> is something wrong with the pi. Maybe this double pcm/flac conversion is
> causing
DJanGo wrote:
> tbh - my old LMS was fitted with a better CPU and 2GB RAM running plain
> Debian.
> Picoreplayer run in the limited RAM so compare my old lms with your
> setup is pretty ...
>
> AFAIK ->You only get what you pay for..
Very true, so I'm not to troubled. Actually, it's when
Grumpy Bob wrote:
> running on a Raspberry Pi3 with piCorePlayer/LMS7.9.1
tbh - my old LMS was fitted with a better CPU and 2GB RAM running plain
Debian.
Picoreplayer run in the limited RAM so compare my old lms with your
setup is pretty ...
AFAIK ->You only get what you pay for..
I have Spotty running on a Raspberry Pi3 with piCorePlayer/LMS7.9.1 and
I find selecting albums, playlists, searching and so forth to be rather
too slow to be usable.
That would be a different problem. But anyway: what do you consider "too
slow"? How long does it take to eg. get Top Tracks, or
I have Spotty running on a Raspberry Pi3 with piCorePlayer/LMS7.9.1 and
I find selecting albums, playlists, searching and so forth to be rather
too slow to be usable. The Pi has a wired connection to the router, and
download speed is generally pretty high. When playing, I don't see
buffering, the
And your internet connection?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3
sub.
Bedroom/Office: Boom
Kitchen: Touch + powered
Added Spotty, which is ridiculously slow though.
You simply installed the plugin, didn't build it yourself?
I have to wait 10 seconds between the songs (connecting... buffering...
etc).
This sounds like networking issues. I know, your connection is fast. But
is your connection to Spotify,
So, I've set lms 7.9.1 on rpi3 (I've tried on raspbian, ubuntu mate,
osmc, no difference).
Added Spotty, which is ridiculously slow though.
I have to wait 10 seconds between the songs (connecting... buffering...
etc).
Once it starts playing, there are no dropouts/hicks.
Skipping to next song
37 matches
Mail list logo
