mftech wrote:
> Do we know if an API is available for jazzGroove ?
> Their web site mention a collaboration with Sonos.
> https://jazzgroove.org/blog/sonos-jazzgroove-app?channel=mix1
Here's the answer for Support.
*supp...@jazzgroove.org*
14:22 (il y a 8
heures)
[image:
Since updating to the most recent version (1.8.2), I've been having an
(minor) issue where for some reason track and album titles are using
HTML character encoding for some characters (e.g.
Would you have an example?
--
Michael
___
plugins mailing
emanue|e wrote:
> I can browse albums and songs, but when i try to play something i
> received bad request...
Another specific Qobuz issue: They only allow streaming on one device at
a time. So if you have a player open somewhere else that could be a
problem.
I see that they are still only mainly supporting AAC and MP3. I think
flac would have been nice but anyway ... So it will be mp3 as I have not
yet implemented an aac encoder.
Can you remind me what you have in mind wrt player creation? UPnP, Cast
and AirPlay are discover-based solutions. A
bpa wrote:
> OK. Just figured out I've been looking at old prototype code. I followed
> the sourceforge link in the repo XML and assumed the file were the
> latest. My bad.
oh yes! whoops, that is very old prototype code. I've fixed that link,
now. thanks.
You have to add your Qobuz account data, i.e. login (e.g. email address)
and password to the Qobuz plugin configuration. That is done by the LMS
web interface (Server settings -> Plugins -> Qobuz).
I have done it.
i enabled debug settings for this plugin and i can see my account
details in the
jd68 wrote:
> The Qobuz plugin is still working.
Same here. Playing almost exclusively Qobuz these days.. Did you check
that the "preferred format" settings matches your account?
jeroen2's Profile:
philchillbill wrote:
> Would that choice affect the player in the GUI? It would be great if the
> Alexaplayer behaved in the GUI or iPeng just as a normal squeezebox does
> without having to say Alexa, resume after every manual change to the
> now-playing track.
In both cases, there would be
expectingtofly wrote:
> I'm not using the OPML "parser" in that sense. I'm using a direct link
> to sub routine with a callback, so hopefully that listen doesn't apply.
OK. Just figured out I've been looking at old prototype code. I followed
the sourceforge link in the repo XML and assumed
bakker_be wrote:
I can help with the "access rate limit exceeded": most of the users of
the Spotty plugin use the same "Spotify Client ID", and its amount of
allowed connections is limited. You can however register a Spotify
developer account and get your own, that you can fill out in the Spotty
Would that choice affect the player in the GUI? It would be great if the
Alexaplayer behaved in the GUI or iPeng just as a normal squeezebox does
without having to say Alexa, resume after every manual change to the
now-playing track.
Any ideas why I get this in scanner log:
Plugins::MusicArtistInfo::Importer2::startScan (56) Artist Image Folder
either does not exist or is not writable: D:\My Music\Artist Artwork
You'd get this for the reason given in the message :-).
The Scanner has previously filled the folder with
Hi
Any ideas why I get this in scanner log:
Plugins::MusicArtistInfo::Importer2::startScan (56) Artist Image Folder
either does not exist or is not writable: D:\My Music\Artist Artwork
The Scanner has previously filled the folder with images but no updates
since 2nd Feb.
I'm on Windows 10.
One thing Im wondering now that I know better the LMS core is if it
would be easier to reuse a bridge like before or if creating a virtual
player inside LMS directly (like I do in group players) would be
feasible
LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet,
bpa wrote:
>
> Since you are using "parser" in opml menus, there is a potential LMS
> issues with Favorites if the menu item is playable and a favorite saved
> from the menu item. Not sure if issue will show up with your plugin.
> Main symptom is: "Touch to Play" the Favorite may not work on
>
Hi
Is there anyway to mimic Imagus add-on behaviour in SLX? It works fine
in Material with a web browser with the add-on.
mr-b's Profile: http://forums.slimdevices.com/member.php?userid=10044
View this thread:
jd68 wrote:
> The Qobuz plugin is still working.
>
> You have to add your Qobuz account data, i.e. login (e.g. email address)
> and password to the Qobuz plugin configuration. That is done by the LMS
> web interface (Server settings -> Plugins -> Qobuz).
I have done it.
i enabled debug
emanue|e wrote:
> i don't understand if that plugin works or not.
> Is there someone that have it installed and can confirm that it's still
> working?
>
> Thanks.
The Qobuz plugin is still working.
You have to add your Qobuz account data, i.e. login (e.g. email address)
and password to the
dmcdayton wrote:
> How hard is it do a plugin?
Sometime writing a plugin is the easy bit. The service is never static.
To keep plugin going requires a commitment of time for many years.
bpa's Profile:
expectingtofly wrote:
> Yes, I think you are right, although I guess we need to make sure that
> there doesn't end up a smorgasbord of plugins!
It would be great to have a large smorgasbord.
In AlienBBC we tried to have multiple parsers (for different stations
using RealAudio) in same plugin
dmcdayton wrote:
> Hey Michael, I will inquire. Thanks.
Do we know if an API is available for jazzGroove ?
Their web site mention a collaboration with Sonos.
https://jazzgroove.org/blog/sonos-jazzgroove-app?channel=mix1
Tête à FLAC
2 X SB Classic
2 X SB2
1 X SB Boom
1 X SB Touch
1 X
i don't understand if that plugin works or not.
Is there someone that have it installed and can confirm that it's still
working?
Thanks.
emanue|e's Profile: http://forums.slimdevices.com/member.php?userid=70721
View this
bpa wrote:
> I think this is the right sort of way to extend BBC listening - users of
> certain BBC features develop specific plugins to suit their needs using
> BBCiPlayer as the playing engine.
>
Yes, I think you are right, although I guess we need to make sure that
there doesn't end up a
I think this is the right sort of way to extend BBC listening - users of
certain BBC features develop specific plugins to suit their needs using
BBCiPlayer as the playing engine.
The preferred interface to BBCiplayer would be the "iplayer://" URL. I
presume BBC Sounds plugin eventually plays
Regarding number of stream.mp3 I have not tried to break it but
have had 3 working.
I suspect it is around the same load as proxying streams to players or
playing local music ... ie plenty of capacity.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering
expectingtofly wrote:
> ... for those that would like the "Sounds" experience.
>
> It currently provides the overall access to the Search capability, the
> Daily picks (promoted content), Music Mixes and curated/categorised
> content. I plan to continue to develop it to provide access to the
>
The metadata is not expected as part of the stream but via the separate
audioItem.metadata object. It's what I use currently to display a static
image during streaming. It would be up to the skill to refresh that when
a title change happens. To do that, the PlaybackNearlyFinished directive
from
I'm a fan of the BBC Sounds App experience of curated and personalised
content (and search capability), I've therefore created this
experimental plugin that tries to replicate this.
It is not intended to replace the already excellent BBC Iplayer and
Extras plugins , but be complementary to
bakker_be wrote:
I can help with the "access rate limit exceeded": most of the users of
the Spotty plugin use the same "Spotify Client ID", and its amount of
allowed connections is limited. You can however register a Spotify
developer account and get your own, that you can fill out in the Spotty
CrankyTom wrote:
> Adding this skin as a web app in Nova Launcher using Kiwi Browser saved
> the day, thanks.
If you are just using kiwi for Material, I suggest you use the Material
APK instead -
https://f-droid.org/en/packages/com.craigd.lmsmaterial.app/
*Material debug:* 1. Launch via
Thank you for this excellent Skin. I recently bought the Xiaomi Poco X3
NFC which has MIUI12 on Android 10 and I couldn't get SqueezeCommander
to work without crashing.
I tried other apps but as a long time SqueezeCommander user, they did
not feel quite right.
Adding this skin as a web app
I think that in this case the route would be
Skill works out which LMS proxy player maps to which Alexa device and
gets IP address.
Then when play is to be started ... Alexa grabs the pls via https (has
to be https) from the back-end of the skill which returns the IP address
of the proxy
All the docs are in the url I posted earlier.
Its just a https url as far as Alexa is concerned. In the case of this
skill, that url is one I control and it creates a pls playlist file
using a php script, where the contents of the pls just point to the
/stream.mp3 url on your lan. Pauls
philchillbill wrote:
> Would be really great to have it because those big touchscreens on the
> Echo Show devices are going to waste currently with this skill.
>
> It would also be very helpful if there was a JSON command to create a
> named network player. Right now the only way to do it is
Would be really great to have it because those big touchscreens on the
Echo Show devices are going to waste currently with this skill.
It would also be very helpful if there was a JSON command to create a
named network player. Right now the only way to do it is to GET the LMS
url with
This is what Phillipe and I discussed when I first came up with the way
to stream from LMS to Alexa - basically starving Alexa.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc australia, cbc/radio-canada and
philippe_44 wrote:
> Oh I was not expecting to provide you with sync with other LMS players.
> I've only been able to do that with AirPlay as it uses RTSP/RTP and I
> was able to "proxy" RTP to LMS way of controlling playback timing.
>
> I was referring to your comment of sync between LMS
Mercenary wrote:
> Hm... So nobody knows what to do on that screen?The instructions are on the
> YouTube settings page. Make sure you copy
the required items without any accidental spaces. I am pretty sure when
I first tried this part of the set up it didn't work for me either but
when I tried
philchillbill wrote:
> The size of that buffer is unpublished but is no more than maybe a
> second before playback starts. Enough to mess up sync with other
> players. Thats how it starts out - after a few seconds its already
> minutes of buffer. If you start a stream by voice and watch the
Mercenary wrote:
> Hi guys,
> I tried to get my Youtube plugin working again, after not really using
> it for quite a while.
>
> I followed the steps in the first message of this thread and everything
> works but at some point I need ot fill in this "OAuth consent screen"
> page and I am
philippe_44 wrote:
> I mean if the source controls the stream, will alexa buffer for a very
> long time before starting to play? Id assume, like for my other
> bridges, there is a min buffer size before it starts to play and of
> course it will try to get as much it can but if the source does
philchillbill wrote:
> No, theres no buffering controllability. You have 3 basic commands to:
> clear the queue entirely, add something to the end of the queue, or
> replace the entire current queue and start playback immediately with the
> new queue. Thats all there is and it works just fine
philippe_44 wrote:
> There is one thing that could be done (I started a LMS-Alexa bridge a
> while ago and stopped as I had other priorities) and that's to act as a
> real time stream and send data accordingly to Alexa. I don't remember
> exactly where I left that, but I think Alexa can be told
43 matches
Mail list logo
