Tex wrote:
> I tried the regular Spotify plugin & the Protocol Handler and it loads
> faster.
>
> http://forums.slimdevices.com/showthread.php?79706-Announce-Spotify-Premium-Plugin-(Beta)/page613
I'm not using the official Logitech plugin along with the protocol
handler, because it doesn't
DanSmedra wrote:
>
> The "glitch" is rather regular now, and drives me crazy. :/
OK, I've tested this a bit with TIDAL (can't test Pandora over here) and
I think there's a problem with the TIDAL App on MySqueezebox.com, I'm
getting problems as well (Search results not working).
Do you get
Can you add Joggler, Max2Play and picoreplayer to the list
Thanks
Transporter (Lounge)
Joggler Squeezeplay as Remote (Lounge)
Joggler Squeezeplay (Office)
Joggler Squeezeplay (Kitchen)
Joggler Squeezeplay (Conservatory)
Radio (Bedroom)
Radio (Garage)
LMS 7.8 on DIY Vortexbox (i5)
Squeeze
Another question ... when playing a stream via its URL (as opposed to
playing it by name in TuneIn or a favourite) the stream URL is shown (on
a Touch-like display) just below the title/artist.
When playing a station by name then it is the station name that is
shown.
Can I return an attribute
th00ht wrote:
> That is funny! Squeezeplay on my PC is seen by LMS, I can play music,
> but in the app itself the playlist is not shown and I cannot connect to
> the music system.
>
> So I can control playback in the lms:9000 webpage but not on the app
> itself. What is the problem?
Hi there,
Hi Henrico
You might read the other thread but it seems Spotify is losing
interest in supporting Squeezebox. No the official app doesn't handle
multiple accounts so you just have to suffer:(
I recently was able to install Google Music which was good but I
prefer Spotify, then there's Tidal...
oyvindo wrote:
> Yes, you're right. I found the solution in our earlier post #781
> Thanks Philippe :-)
I've now added an option to bind the interface to whetever interface LMS
is bound to
LMS 7.7.5 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos 2xPLAY:1,
PLAY:3, PLAY:5, Marantz NR1603,
bpa wrote:
> You asked before about increasing the "delay" setting, I assumed it was
> at default. Can you confirm the value of the "Second to delay start of
> live stream" ?
I have not changed it so default 15 seconds.
Sent from my SM-G900F using Tapatalk
slartibartfast wrote:
> This may be of use. It is a debug log from just before an interruption
> until playback resumes 30 seconds later.
You asked before about increasing the "delay" setting, I assumed it was
at default. Can you confirm the value of the "Second to delay start of
live stream"
Burning from my backup image worked ? now is up and running .
Wonder which settings killed the system ?should i get 2.40 anyway .
why not a true static IP setup ?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621
If you bought the SD card from us, the quality should not be an issue.
In this case, a freshly burnt image would indeed be the best solution.
We actually recently released our new 2.40 image which offers sound card
support for HiFiBerry, JustBoom, etc. without needing a dedicated image
(in
philippe_44 wrote:
> Wasn't it a problem with the docker instance having multiple network
> interfaces?
Yes, you're right. I found the solution in our earlier post #781
Thanks Philippe :-)
QNAP TS-453Mini 4x3TB RAID5 QTS 4.2.2
LMS 7.9.0 running in Docker
Madsonic 6.2 running in Docker
Plex
Hi,
I'm very interested at taking a part in testing an addon Alexa with LMS.
I'm very exited such a tusk and following thread has been started. Great
job.
fondoftri's Profile:
bpa wrote:
> A possible explanation. There is an IS8601 DateTime parameter in DASH
> MPD file which says when player can start live stream - BBC have set to
> this -15 secs - acting on BBC engineer comments I've been checking code.
> I found the library ISO8601 conversion routine to Epoch time
castalla wrote:
> Ah! Think that's solved it. Will test further during the day & report
> back
A possible explanation. There is an IS8601 DateTime parameter in DASH
MPD file which says when player can start live stream - BBC have set to
this -15 secs - acting on BBC engineer comments I've
Ive activated Kodi ? That was the only thing .
And your static ip support , how does that work i can only set the ip
not netmask gateway and DNS ?
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
Max2Play wrote:
> Hi Mnyb,
> Sorry about the inconvenience you experienced. Have you tried hooking up
> a screen to see whether the Pi boots correctly? You might also try just
> entering the name of your device in the URL bar (default "max2play/").
> We recommend using microSD cards with at
Hi Mnyb,
Sorry about the inconvenience you experienced. Have you tried hooking up
a screen to see whether the Pi boots correctly? You might also try just
entering the name of your device in the URL bar (default "max2play/").
We recommend using microSD cards with at least Class 10 writing speed
Ah! Think that's solved it. Will test further during the day & report
back
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8
speaker; Pioneer WX-SMA1 speaker; - PURE One Flow internet radio: PURE
Jongo S3x ;
castalla wrote:
> Settings: .. delay to start - no delay
Please return to default setting of 15 secs. Following comments by BBC
streaming engineer "No delay" is not right - this may not be the problem
but it doesn't please BBC.
bpa wrote:
> thanks, I didn't unserstand your "BBC" and "all players" ref in earlier
> post - now I'm guessing you meant all LMS players.
>
> The fifteen sec delay is strange as the log I cannot see where the delay
> is coming from.
> Are you doing a test where you skip from one station to
castalla wrote:
> Difficult to say - as PC is already slow - but maybe 2-3 secs. Just
> tried R4 on LMS - 15 secs to play
thanks, I didn't unserstand your "BBC" and "all players" ref in earlier
post - now I'm guessing you meant all LMS players.
The fifteen sec delay is strange as the log I
bpa wrote:
> Do you mean the delay is there on BBC web player site ?
Difficult to say - as PC is already slow - but maybe 2-3 secs. Just
tried R4 on LMS - 15 secs to play
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony
bpa wrote:
> The "Connection timed out" without any other messages mean the network
> interface on server is up but the destinmation hosts does not respond to
> the initial TCP connection. Without other chunk request timeout message
> it means no outstanding chunk requests so usual stream
castalla wrote:
> The delay in sound is there for all players on BBC
Do you mean the delay is there on BBC web player site ?
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread:
Without really knowing why ... this is now working.
Next step is to make it a bit more tolerant of faults in the source and
to work out why things don't work so well when 2 different unsynched
Squeezeboxes are playing the same station (I think in my suppression of
actions when getting too many
bpa wrote:
> Not synced to another player ?
No sync
The delay in sound is there for all players on BBC
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8
speaker; Pioneer WX-SMA1 speaker; - PURE One Flow internet
27 matches
Mail list logo
