I can conform the behaviour with "Baby Shark"
spotify:track:5ygDXis42ncn6kYG14lEVG
Playing directly from the LMS WebGUI. The song plays with 160 and 320
kbs while it fails with 96 kbs. Bitrate was changed in the Spotty
Settings.
-
mherger wrote:
> >Would somebody please be kind enough to summarize
> the findings wrt. small files?
Hi Michael,
Welcome back - glad you had a good break!
All of my digging was focused on SpotifyConnect - it turned out you
could see similar stuff in LMS Spotty by tweaking the bit rate in the
mherger wrote:
> > As suspected playback fails in the Windows Spotify app as well. The
> > Windows app acts just like the Android app but both act slightly
> > differently to playing tracks within LMS. For example Arcade Fire -
> > Everything Now (continued) which is 46 seconds long plays within
As suspected playback fails in the Windows Spotify app as well. The
Windows app acts just like the Android app but both act slightly
differently to playing tracks within LMS. For example Arcade Fire -
Everything Now (continued) which is 46 seconds long plays within LMS at
320kbps but does not play
As suspected playback fails in the Windows Spotify app as well. The
Windows app acts just like the Android app but both act slightly
differently to playing tracks within LMS. For example Arcade Fire -
Everything Now (continued) which is 46 seconds long plays within LMS at
320kbps but does not pla
mherger wrote:
> > So I've found the setting in Daemon.pm. Changed to 320 there and now
> > Baby Shark plays.
>
> Ok, I'm back from a relaxing vacation, and I'm overwhelmed by these
> threads already :-). Would somebody please be kind enough to summarize
> the findings wrt. small files? This
So I've found the setting in Daemon.pm. Changed to 320 there and now
Baby Shark plays.
Ok, I'm back from a relaxing vacation, and I'm overwhelmed by these
threads already :-). Would somebody please be kind enough to summarize
the findings wrt. small files? This is quite surprising as I've oft
lookstoomuch wrote:
> So I've found the setting in Daemon.pm. Changed to 320 there and now
> Baby Shark plays.
>
> The issue I found is when I tried to change the song, spotty wouldn't
> listen and crashed.
It's not a proper fix - it's a change that makes things better to a
variable degree, w
lookstoomuch wrote:
> So I've found the setting in Daemon.pm. Changed to 320 there and now
> Baby Shark plays.
>
> The issue I found is when I tried to change the song, spotty wouldn't
> listen and crashed.
>
> This is all being done controlling via the Spotify app.
>
> I really need to fi
So I've found the setting in Daemon.pm. Changed to 320 there and now
Baby Shark plays.
The issue I found is when I tried to change the song, spotty wouldn't
listen and crashed.
This is all being done controlling via the Spotify app.
I really need to find a new song to test with.doo dooo
lookstoomuch wrote:
> Yes I'd like to try making this same change, any tips on how to do it?I think
> we will have to wait for Michael's input.
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://for
Laz wrote:
> Ah - that's interesting. So my approach of editing Daemon.pm
> sort-of-works for the second case (short songs will play up to a point).
> It does sound like the root problem is the same in both cases, just that
> spotty/LMS handles track kickoff differently for the two cases (and
>
lookstoomuch wrote:
> Where would I change this?
Not sure if it's even possible with hardware players. I think
squeezelite has a startup parameter to set the buffer size.
QLMS 8.0.0@2.21 x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4
-
lookstoomuch wrote:
> Same place. The LMS interface plugin configuration section.
>
> If I initiate playing songs with spotty LMS web interface, the bitrate
> set in the spotty plugin configuration makes a difference
>
> If I initiate playing songs from spotify app on my phone, changes to th
lookstoomuch wrote:
> Same place. The LMS interface plugin configuration section.
>
> If I initiate playing songs with spotty LMS web interface, the bitrate
> set in the spotty plugin configuration makes a difference
>
> If I initiate playing songs from spotify app on my phone, changes to th
lookstoomuch wrote:
> Same place. The LMS interface plugin configuration section.
>
> If I initiate playing songs with spotty LMS web interface, the bitrate
> set in the spotty plugin configuration makes a difference
>
> If I initiate playing songs from spotify app on my phone, changes to th
slartibartfast wrote:
> But you just said changing the quality in the LMS web interface to
> 96kbps caused Baby Shark to fail whereas 320kbps played correctly. You
> weren't getting that result the last time you changed the quality. Where
> were you changing the quality when it made no differenc
dolodobendan wrote:
> Just guessing here, but maybe it only starts playing if whatever is
> being played fills the buffer. At 96kbps it might not. If possible, try
> setting the buffer to 1/3 to test this.
Quick math says that @ 96 kbps the 1:25 song length (middle point
between songs that work
dolodobendan wrote:
> Not necessarily. If there were a check if the whole file fits in the
> buffer, playback could be started despite the buffer not being full. IF
> that is the problem.Agreed. The strange thing is these files used to play a
> short time ago.
I remember listening to the Billy
slartibartfast wrote:
> If that is the case there is always going to be a minimum track length
> however small that may be.
Not necessarily. If there were a check if the whole file fits in the
buffer, playback could be started despite the buffer not being full. IF
that is the problem.
QLMS 8
dolodobendan wrote:
> Just guessing here, but maybe it only starts playing if whatever is
> being played fills the buffer. At 96kbps it might not. If possible, try
> setting the buffer to 1/3 to test this.I did speculate that the downloaded
> file size seemed to be important in
another thread w
lookstoomuch wrote:
> No I was using the LMS web interface to change the quality.
>
> If I use the spotify app to play songs, it does not matter the quality I
> put in the web interface it behaves like the 96 KBPS rate.But you just said
> changing the quality in the LMS web interface to
96kb
lookstoomuch wrote:
> Updateif I change the quality settings and initiate play from the
> LMS web interface, Baby Shark does not play @ 96KBPS while it DOES play
> @320KBPS.
>
> From Spotify app it does not matter what quality setting I configure
> spotty with on the back end.
Just guessin
slartibartfast wrote:
> Ah good, same as me then, were you changing quality in the Spotify app
> before?
>
> Sent from my Pixel 3a using Tapatalk
No I was using the LMS web interface to change the quality.
If I use the spotify app to play songs, it does not matter the quality I
put in the w
lookstoomuch wrote:
> Updateif I change the quality settings and initiate play from the
> LMS web interface, Baby Shark does not play @ 96KBPS while it DOES play
> @320KBPS.
>
> From Spotify app it does not matter what quality setting I configure
> spotty with on the back end.Ah good, same
Updateif I change the quality settings and initiate play from the
LMS web interface, Baby Shark does not play @ 96KBPS while it DOES play
@320KBPS.
>From Spotify app it does not matter what quality setting I configure
spotty with on the back end.
---
Laz wrote:
> I think slartibartfast may be talking about changing the default bitrate
> in Daemon.pm rather than in the GUI, which is the hack that changes the
> track length for spotty crashes (quite a few pages back in the other
> thread).No I have never changed Daemon.pm. I was changing the s
lookstoomuch wrote:
> Just tested, it does not seem to matter. The same songs play (or not)
> whether it's low or high bit rate.Weird. If I change to 96kbps Baby Shark
> doesn't play but it does at
320kbps.
Sent from my Pixel 3a using Tapatalk
-
slartibartfast wrote:
> When you play the tracks you will see the selected bitrate on the now
> playing screen. The 96kbps you are seeing is something to do with the
> helper app and not streaming quality.
>
> Sent from my Pixel 3a using Tapatalk
Just tested, it does not seem to matter. The s
lookstoomuch wrote:
> Just tested, it does not seem to matter. The same songs play (or not)
> whether it's low or high bit rate.
I think slartibartfast may be talking about changing the default bitrate
in Daemon.pm rather than in the GUI, which is the hack that changes the
track length for spo
lookstoomuch wrote:
> I may be wrong, are the bitrate setttings in the LMS GUI reliable?
> Seems the start command is at 96 no matter what I put in the GUI.
>
> /usr/local/slimserver/Cache/spotty/fbfb69f4 -n piPlayerBasement
> --disable-audio-cache --bitrate 96
>
> I am doing a bit of this w
slartibartfast wrote:
> OK it is strange that your threshold is different but it seems to be the
> same issue. If you change the Spotify quality to 96kbps do the tracks
> that currently play stop playing?
>
> Sent from my Pixel 3a using Tapatalk
I may be wrong, are the bitrate setttings in the
lookstoomuch wrote:
> LoL.I did a sampling through many tracks on this wonderful album.
> Results:
>
> Baby Shark1:20 Crashes
> Animals Sound Fun 1:14 Crashes
> Jungle Boogie 1:40 Plays
> Penguian Dance1:49 Plays
> My Pet My buddy 1:30 Plays
> Under The Sea 1:22
slartibartfast wrote:
> Baby Shark plays for me (unfortunately) at 320kbps. Are you saying it
> doesn't play for you?
>
> Sent from my Pixel 3a using Tapatalk
LoL.I did a sampling through many tracks on this wonderful album.
Results:
Baby Shark1:20 Crashes
Animals Sound Fun 1:14
lookstoomuch wrote:
> 320kbpsBaby Shark plays for me (unfortunately) at 320kbps. Are you saying it
doesn't play for you?
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/memb
slartibartfast wrote:
> Which quality setting have you chosen for Spotty? I found at 320kbps
> tracks less than around 25 seconds failed to play while at 96kbps that
> limit increased to around 1 minute 40 seconds.
>
> Sent from my Pixel 3a using Tapatalk
320kbps
lookstoomuch wrote:
> Ah OK I think you are correct. Funny...I have been recreating this
> issue by playing songs by Pinkfong, i.e. Baby Shark. I concluded it was
> due to bouncing between playlists and now I see all the Pinkfong songs
> are around 1min 30 secs.
>
> And talk about annoying
Ah OK I think you are correct. Funny...I have been recreating this
issue by playing songs by Pinkfong, i.e. Baby Shark. I concluded it was
due to bouncing between playlists and now I see all the Pinkfong songs
are around 1min 30 secs.
And talk about annoying having to hear these songs over
Looks like you are joining the short track brigade.
See the last couple of pages of
https://forums.slimdevices.com/showthread.php?111923-Announce-Spotty-4-0-integrate-local-library-with-your-Spotify-collection-(LMS-8-)
L
Guess I was a bit too optimistic. Still crashing.
Seems to happen more when I jump to different playlists vs. clicking
around in the same playlist.
Anyone, any ideas?
lookstoomuch's Profile: http://forums.slimdevice
Pretty sure I have resolved the problem. Did 2 things:
- Gave application level firewall Allow rule to
C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe
- Disabled IPv6 on all adapters
Pretty sure it was the firewall. Spotif
O/S: Windows 7, latest updates installed
LMS: 7.9.2
Spotty: 4.2
Client: Spotify App on Android
So I was really excited when I initially heard about Spotty and
streaming it using my Squeezebox Duet players as I've been running this
setup for years.unfortunately I've not been able to spot to w
42 matches
Mail list logo
