mherger wrote:
> This should work, no matter whether the player does support Spotify
> natively or not. After all this effort is in preparation of the end of
> libspotify support. I'm regularly using multiple Radios, sometimes pCP,
> Transporter or desktop Squeezeplay added to the mix.
So in
JSON::XS::to_json has been renamed to encode_json, either downgrade to
pre-2.0 versions of JSON::XS or rename the call at
We're using
use JSON::XS::VersionOneAndTwo;
Instead, which provides a compatibility level between the two versions.
Well spotted - for some reason, I don't get that
Brilliant work on this, and apologies if I miss obvious details;
first-time post. I have a librelelec system on an x86-64 platform
simultaneously running Kodi, LMS, and Squeezelite, behaving perfectly.
When I attempted to run sq2r via the Plugins panel in LMS, only the
x86-64-static version
ChrisNY wrote:
> I noticed this issue when I upgraded my server a while back. Seems to
> be related to a change to a JSON library based on the log file output.
> Not sure how to resolve the issue but others may have recommendations.
>
> [17-05-22 21:40:02.3769]
tjoek wrote:
> The man page is showing, but running it with the above supplied
> parameters crashes straight away:
> >
Code:
> > thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:
Error { repr: Os { code: 92, message: "Protocol not available" } }',
Giza2020 wrote:
> I'm guessing the issue must be the boom and pi don't use the native
> player like the radio does. So two players that require spotty cannot
> use two different forks.
This should work, no matter whether the player does support Spotify
natively or not. After all this effort is
pinkdot wrote:
> I have a DS115, Armada375, similar arch. Your helper folder points to
> the arm-linux folder, so just swap both binaries from the armhf-linux
> and arm-linux folders. Worked for me.
Ok, I guess I'll have to come up with my own bin search, trial & error
etc. Thanks a lot for all
I'm on PcP 3.02 and it offers no update to 7.9.1, I'll update to the
latest PcP 3.2-something later this week ( was in the planning anyway)
maybe that also offers LMS 7.9.1
It doesn't automatically, but there's a how-to:
http://picoreplayer.sourceforge.net/how_to_upgrade_lms.shtml
--
oyvindo wrote:
> Well, I think you misunderstood me.
> 0.2.8.0.1 is the version number for your Castbridge that was
> automatically installed in my LMS. I just wanted to check with you that
> it indeed was the last available DEV version.
>
> Anyway, thanks for your dedication and support
mherger wrote:
> Just run this as a starter. It would print some help page. If that's
> fine, then you can add "-n test -c /tmp -a" and see whether you'd see it
> in your Spotify application (desktop or mobile).
The man page is showing, but running it with the above supplied
parameters crashes
I can also play on my phone via the native app without effecting the LMS
output. What a result :-) not sure it'll last though if Spotify work
that one out!
I'm guessing the issue must be the boom and pi don't use the native
player like the radio does. So two players that require spotty cannot
Hi Michael. Once again I have to say great work!
I've finally got this up and running (time delayed me not the tool) but
I wanted to check something with you and the guys on the thread.
On my set up I can sync a boom and a pi squeezelite player (max2play)
but if I try to play two different
philippe_44 wrote:
> I do think it is.
Well, I think you misunderstood me.
0.2.8.0.1 is the version number for your Castbridge that was
automatically installed in my LMS. I just wanted to check with you that
it indeed was the last available DEV version.
Anyway, thanks for your dedication and
oyvindo wrote:
> That was 0.2.8.0.1 right?
> It seems to work - as far as I can tell. Which is good. The delay is
> noticeable, but just barely...
> So why did this problem surface so suddenly? Was it a CC background
> update from Google that screwed up?
I do think it is. As soon as you move
tjoek wrote:
> How do I run spotty in armhf-linux? I will ssh into my box tonight and
> report back.
I have a DS115, Armada375, similar arch. Your helper folder points to
the arm-linux folder, so just swap both binaries from the armhf-linux
and arm-linux folders. Worked for me.
-Synology nas
That was 0.2.8.0.1 right?
It seems to work - as far as I can tell. Which is good. The delay is
noticeable, but just barely...
So why did this problem surface so suddenly? Was it a CC background
update from Google that screwed up?
QNAP TS-453Mini 4x3TB RAID5 QTS 4.2.4
LMS 7.9.0 running in
mherger wrote:
> Above command doesn't expect output. But can you use your Spotify app on
> mobile or desktop to select "testing"? And what UI are you using where
> seek wouldn't work?
If I disable firewalld on my Fedora VM running LMS I can see the
'testing' Spotty instance on my desktop
mherger wrote:
> > mhmm, reading the response I wonder if it will be fixed for the LMS
> > plugin.if it is the switch to secure http that Michael mentioned
> > they would have to revert to plain http.
>
> Try the 7.9.1 nightly build. It should improve https support.
>
>
> --
>
> Michael
cramcram wrote:
> Still no seeking here. The rest works perfectly. Can I help with logs?
> If yes, please point me to the right direction.
Oh, you'll need 7.9.1 for seeking to work. Sorry about that.
Michael
http://www.herger.net/slim-plugins - MusicArtistInfo, MusicInfoSCR
philippe_44 wrote:
> Good - The ideal buffer is 1000 (1 sec). I still have a mind boggling
> issue with the remote control part of the E5. It's the only one of all
> the players that does not work with the remote controller server I've
> added ... hours trying to understand why
I have the
tjoek wrote:
> How do I run spotty in armhf-linux? I will ssh into my box tonight and
> report back.
I take it from your previous posting that you would find it in the
following location:
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/armhf-linux/spotty
Just run
mhmm, reading the response I wonder if it will be fixed for the LMS
plugin.if it is the switch to secure http that Michael mentioned
they would have to revert to plain http.
Try the 7.9.1 nightly build. It should improve https support.
--
Michael
Thanks all for your suggestions.
I will no doubt try them out in due course and report back here.
For the moment I would like to enjoy the stability I have at the moment.
Changing to a NAS has been a steep learning curve for me over the last
four days. Somewhat brought on by last weeks global
Deco-Doctor wrote:
> I raised a support request with Qobuz. It seems they know about the
> artwork problem.
>
> Here is the reply I got from them:
> -
> Hello,
>
> Thanks for your message.
>
> The artwork issue has been identified.
> This will be fixed very soon along the next release of the
Thanks a lot for the update philippe_44!
Works better than ever for me. Jumping from local to stream, skipping,
replay... works like a charme!
Moe1980's Profile: http://forums.slimdevices.com/member.php?userid=66896
View
mherger wrote:
> Hmm... armle, but Synology's spec sheet says it was featuring hard
> float. Can you ssh in to the box and try to run the spotty version in
> armhf-linux?
How do I run spotty in armhf-linux? I will ssh into my box tonight and
report back.
I raised a support request with Qobuz. It seems they know about the
artwork problem.
Here is the reply I got from them:
-
Hello,
Thanks for your message.
The artwork issue has been identified.
This will be fixed very soon along the next release of the app.
For others app, we have forwarded
seems to be working on my debian x86_64-linux system too Michael
adamdea's Profile: http://forums.slimdevices.com/member.php?userid=37603
View this thread: http://forums.slimdevices.com/showthread.php?t=107418
ian_heys wrote:
> I think I'm getting somewhere.
>
> Squeezelite tries to start when I name your static binary armv5te and
> try to start it.
>
> But I get this in the log:
>
> Starting Squeezelite:
>
marcelveldt wrote:
> 1) There is no output on the settings page... Spotty also crashes when
> trying to authenticate using Connect protocol.
> ...
> 5) As soon as I move the i386 binary into the x86_64 folder it's working
> fine.
> Did you test the x86 binary ? If not, I can fire up some VM to
ian_heys wrote:
> I think I'm getting somewhere.
>
> Squeezelite tries to start when I name your static binary armv5te and
> try to start it.
>
> But I get this in the log:
>
> Starting Squeezelite:
>
I think I'm getting somewhere.
Squeezelite tries to start when I name your static binary armv5te and
try to start it.
But I get this in the log:
Starting Squeezelite:
/volume1/@appstore/LmsRepack/Cache/InstalledPlugins/Plugins/LocalPlayer/Bin/squeezelite-armv5te
-d all=debug -f
I've installed Shairtunes2 (fork) (v0.60.2) on LMS 7.75 running on a
Win/XP box. My Macbook Air with OSX 10.11.6 and Itunes 12.6.1.25 reports
both my Squeezeboxen SB3 Classics as devices. Windows firewall exception
added. However when I play an Itunes file and select either SB3 as
output speaker
I guess using getResult is better, even if requires accessing the name
using an underscore despite your earlier comment?
Yes... I guess I'm still not familiar with all of LMS' secrets :-).
--
Michael
___
plugins mailing list
I've installed Shairtunes2 (fork) (v0.60.2) on LMS 7.75 running on a
Win/XP box. My Macbook Air with OSX 10.11.6 and Itunes 12.6.1.25 reports
both my Squeezeboxen SB3 Classics as devices. However when I play an
Itunes file and select either SB3 as output speaker I get no sound on
the SB3 and
ian_heys wrote:
> I've tried to follow your instructions but I can't get Local Player to
> "see" the binaries.
>
> This is a view of the binaries folder.
>
> 22752
>
> I think the naming convention is correct and I've relaxed the
> permissions to be the same as the windows binaries. I've also
One question on choosing the spotty device from the android or windows
spotify client - should it turn green and say listening on spotty to
indicate success?
No. As soon as the helper got authenticated it will exit.
I think if I use -u and -p and try to connect via the
spotify client, it
Hi
Thanks for your help. To answer your questions
mherger wrote:
> > a) If i try to run spotty from the install then the squeezeserver log
> > shows it starting then being killed.
> _When_ does it start and is being killed? The spotty helper is not a
> daemon like the older protocol handler.
pinkdot wrote:
> Just remove the port from the firewall settings. If it's not there,
> reboot the nas.
That did it. Had to reboot, there was nothing showing in the firewall.
Thanks
LMS: 7.9.0 - 1488878280 @ Tue Mar 7 09:28:02 UTC 2017 on Raspberry Pi 3B
piCorePlayer v3.20 Server/ARCAM rPAC
39 matches
Mail list logo
