Re: [SlimDevices: Plugins] [Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)
When this one-track-behind occurs, it also happens on the LMS web interface. > So we can rule out squeezelite on RPI. Agreed, I've seen it happen with the Transporter, too. And yes, I've looked into this before, tried to reproduce in many ways. But I've never been able to so on purpose. It happens sometimes, but I don't know when. Michael, please take a look at the dump; I'm sure it will give you some hints hopefully. Unfortunately all your server.log shows is that it's missing the PLUGIN_RADIOTIME_MODULE_NAME string for whatever reason (did you disable the Radio plugin?). And that you're running a rather old LMS :-). -- Michael ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)
Touch and Radios but there is a piCorePlayer as well. On the piCorePlayer I did change internal stream buffer to 2kb and output buffer to 6kb when messing around testing DXD files. Ok, it's these buffer settings which cause the pre-buffer optimization to be enabled automatically. -- -- Michael ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Spotty playback issues
Spotty is logged in and I can see my stuff but it plays 10 seconds of a song and jumps to next. Those 10s are just the UI claiming to do so, but it actually doesn't play at all? What kind of player are you using? Is this in Spotify Connect mode, or controlled through LMS? If the former, please try LMS directly. -- Michael ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] iPeng on Big Sur
Is it the iPeng iOS app running on an M1 based Mac ? Yes. Or is it available on Intel Macs also ? No. AFAIK the iOS apps are only available on M1. Looks great on the screenshot 🙂 Haven't played much with it yet, as it's not my primary work machine... but impressive in what I've seen so far. My Intel based MB Pro from early 2020 would always run at >60°C, even when I don't do much. That M1 I've only seen once a little above 35°C, while four cores were fully maxed out compiling code. Usually it sits there around 25°C. -- Michael ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] SuperDateTime Screensaver v5.11.0 - Date/Time/Weather/Sports/Stocks
Based on the feedback from @bluetdi I added a setting to select the air-pressure units displayed in the Extras menu. I also made an effort to improve language localization replace by replacing the hard coded English text throughout SDT. I used Google Translate so there may be some mistakes. Feedback on any errors you observe is welcome. I focused on German, Dutch and Spanish. If there is interest in other languages let me know. Even better if you would provide a revised strings.txt file with the language additions you desire. Code: 5.11.9 01/09/21 Added setting to select Air Pressure units displayed in Extras menu. Improved language localization. BoomX2's Profile: http://forums.slimdevices.com/member.php?userid=33529 View this thread: http://forums.slimdevices.com/showthread.php?t=112122 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Looking for someone willing to update Inguz EQ/DRC settings page
Gobuleberbu wrote: > IsnÂ’t ipeng able to control the inguz plugin? Orange Squeeze can and also Squeeze Commander, but the latter no longer runs as of Android 11. Apesbrain's Profile: http://forums.slimdevices.com/member.php?userid=738 View this thread: http://forums.slimdevices.com/showthread.php?t=113604 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)
slartibartfast wrote: > Touch and Radios but there is a piCorePlayer as well. On the > piCorePlayer I did change internal stream buffer to 2kb and output > buffer to 6kb when messing around testing DXD files. > The "clean up album and track titles" box gets ticked automatically as > well as the "optimize pre-buffering" box. > > Sent from my Pixel 3a using TapatalkHmm strange things happen when playing > Spotify Connect to Squeezelite with those buffer settings with or without the "Optimize pre-buffering" enabled. The phone app still jumps a couple of tracks ahead of LMS and at one point the same track kept repeating but the now playing time would jump from near the beginning to the end. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=111923 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Looking for someone willing to update Inguz EQ/DRC settings page
Agreed. IsnÂ’t ipeng able to control the inguz plugin? Anyone succeeded at compiling the plugin for the raspberry pi? Gobuleberbu's Profile: http://forums.slimdevices.com/member.php?userid=68135 View this thread: http://forums.slimdevices.com/showthread.php?t=113604 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] LMS Announce - play announcements / notifications
andyss wrote: > Any progress on this? Just released an update - give it a try. 'Various SW' (https://www.nexus0.net/pub/sw/): Web Interface | TUI | Playlist Editor / Generator | Music Classification | Similar Music | Announce | EventTrigger | Chiptunes | LMSlib2go | ... 'Various HowTos' (https://www.nexus0.net/pub/documents/LMS/): build a self-contained LMS | Bluetooth/ALSA | Control LMS with any device | ... Roland0's Profile: http://forums.slimdevices.com/member.php?userid=56808 View this thread: http://forums.slimdevices.com/showthread.php?t=109096 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)
mherger wrote: > > How would the buffer size be changed. I am pretty sure I haven't > changed > > What kind of players do you have? This usually is only a topic if you're > > running squeezelite somewhere. > > -- > > MichaelTouch and Radios but there is a piCorePlayer as well. On the piCorePlayer I did change internal stream buffer to 2kb and output buffer to 6kb when messing around testing DXD files. The "clean up album and track titles" box gets ticked automatically as well as the "optimize pre-buffering" box. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=111923 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] [Announce] Spotty 4.0 - integrate local library with your Spotify collection (LMS 8+)
pavowren wrote: > here's a log dump which may shed some light on this issue. When this one-track-behind occurs, it also happens on the LMS web interface. So we can rule out squeezelite on RPI. Michael, please take a look at the dump; I'm sure it will give you some hints hopefully. As I stated before, this does not happen each time but often enough to be bothersome. I don't have a clue what triggers it. pavowren's Profile: http://forums.slimdevices.com/member.php?userid=51958 View this thread: http://forums.slimdevices.com/showthread.php?t=111923 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] iPeng on Big Sur
mherger wrote:
> Ahm... nobody mentioned this so far, or did I miss something?
>
> 32899
>
> How well it works on a desktop I'll have to see :)
Is it the iPeng iOS app running on an M1 based Mac ?
Or is it available on Intel Macs also ?
Looks great on the screenshot 🙂
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
Developer of 'many plugins/applets'
(https://wiki.slimdevices.com/index.php/User_Erland.html)
*Starting with LMS 8.0 I no longer support my plugins/applets* ('see
here for more information'
(https://forums.slimdevices.com/showthread.php?49483-Announce-New-versions-of-erlands-plugins&p=998836&viewfull=1#post998836)
)
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=113634
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > I agree it should not affect functionality. My point was that if the > volume shown in LMS was not the volume used on the player, then it has > no real meaning and would be confusing. If it does reflect the real > volume then it should be shown. > > I have updated Material to be consistent - and removed the 'Fixed > volume' label. I've added a server-side yes/no option as to whether > fixed volume should be respected. If set to 'No' then Material will > treat a fixed volume player as a normal player - show volume slider and > value. If set to 'Yes' it will show the slider as disabled and not show > a volume level. I guess this resolves the issue? I just installed the dev version, and it works GREAT for my purposes (for my fixed volume player with receiver run by DenonSerial plugin). I'm in the process of switching over all of my controllers to MS. Thanks so much for your responsiveness!!! DAR's Profile: http://forums.slimdevices.com/member.php?userid=7274 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
[SlimDevices: Plugins] Spotty playback issues
Logitech Media Server Version: 8.0.0 - 1605892076 Runs in a Docker on Unraid Connects to a Pi4 running piCorePlayer v6.1.0 Pandora works NAS music works from unraid server Spotty is logged in and I can see my stuff but it plays 10 seconds of a song and jumps to next. I get no sound though even when it does that. I am seeing this in logs... [21-01-09 09:57:53.4436] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:55.8979] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:55.8988] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:55.9685] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:55.9695] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:58.9606] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:57:58.9614] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:58:01.8904] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:58:01.8912] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:58:02.9127] Plugins::Spotty::ProtocolHandler::getMetadataFor (201) Found cached metadata for spotify:track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:02.9138] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:02.9158] Plugins::Spotty::AccountHelper::purgeAudioCacheAfterXTracks (228) Played 49 song(s) since last audio cache purge. [21-01-09 09:58:02.9285] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:02.9297] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:02.9306] Plugins::Spotty::ProtocolHandler::getMetadataFor (201) Found cached metadata for spotify:track:2ekd04P4oSVuNzo8qYK38m [21-01-09 09:58:02.9314] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:02.9319] Plugins::Spotty::ProtocolHandler::getMetadataFor (201) Found cached metadata for spotify:track:67rLjOwn17i6DLV1lp9c3Q [21-01-09 09:58:05.7441] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:05.7451] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:06.7208] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:06.7217] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:06.8121] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:06.8134] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:07.7364] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:07.7376] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:07.8756] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:07.8763] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:08.8917] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR6y1LnIphG69Vezcvf [21-01-09 09:58:08.8928] Plugins::Spotty::ProtocolHandler::getMetadataFor (181) Returning metadata cached in song object for spotify://track:1TDAR
Re: [SlimDevices: Plugins] Announce: Material Skin
gnackwatschn wrote: > Any tips on how I can download your dev version? I know, I could > download manually and copy the files, but maybe there is an 'official' > way? Never installed fom a git until now. The only way is to clone the git repo, and copy the 'MaterialSkin' folder to your Plugins folder. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
reinholdk wrote: > Craig, I think there is a misunderstanding about the multiple artist > tagging. > You don't need to tell whether "a, b, c" is 3 artists or not. To have > multiple artists one would use "a;b;c" and LMS would treat this as three > artists if the semicolon is defined as the separator in 'Settings/My > Music/Separator for Multiple Items in Tags', which it is by default. I know that. But, I've just tried setting Artist to "a, b;c" - and LMS produces and artist list of "a, b, c". So, as stated, there is no (easy) way of knowing if the comma is to separate artists or is part of an artist's name (and yes I know that is unlikely). *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > > And, as I have stated multiple times, I cannot do this. There is no way > (AFAIK) to tell if "a, b, c" is 3 artists, 2 artists (e.g. "a" and "b, > c", or "a, b" and "c"), etc. If LMS returned an array of artists, then > yes, but it does not. > Craig, I think there is a misunderstanding about the multiple artist tagging. You don't need to tell whether "a, b, c" is 3 artists or not. To have multiple artists one would use "a;b;c" and LMS would treat this as three artists if the semicolon is defined as the separator in 'Settings/My Music/Separator for Multiple Items in Tags', which it is by default. reinholdk's Profile: http://forums.slimdevices.com/member.php?userid=36070 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Squeezelite for Windows / Asio Channels and Multiple instances.
Hi again, I could start a 2nd instance by using a different macadress with -m "FAKE MACADRESS" . So that is working. Does anybody know how to map the Asio channels? THanks S s25a's Profile: http://forums.slimdevices.com/member.php?userid=65256 View this thread: http://forums.slimdevices.com/showthread.php?t=113638 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > I agree it should not affect functionality. My point was that if the > volume shown in LMS was not the volume used on the player, then it has > no real meaning and would be confusing. If it does reflect the real > volume then it should be shown. > > I have updated Material to be consistent - and removed the 'Fixed > volume' label. I've added a server-side yes/no option as to whether > fixed volume should be respected. If set to 'No' then Material will > treat a fixed volume player as a normal player - show volume slider and > value. If set to 'Yes' it will show the slider as disabled and not show > a volume level. I guess this resolves the issue? For me, this sounds perfect. Thank you! Any tips on how I can download your dev version? I know, I could download manually and copy the files, but maybe there is an 'official' way? Never installed fom a git until now. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: WaveInput for Linux
yas1 wrote: > But I don't see any maxVersion defined in the install.xml, only a > minVersion, what am I missing here? > > Squeezecenter > 7.3 > * > IIRC The maxVersion used to be set to 7.* - I changed it to * which means no limit - if set to 8.* then when 9.0 came along same problem would arise. The original intent of the plugin update procedure (i.e. leave code installed that was not compatible) was to allow a user edit the install.xml manually to override the compatibility constraint. However in practice - some users had difficulties editing the file. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=49584 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
[SlimDevices: Plugins] Squeezelite for Windows / Asio Channels and Multiple instances.
Hi all, I have a 64Bit Asio Interface here which I would like to use with Squeezelite. It appears in the Audio List and can be selected. It plays on Channel 1+2. 2 questions: 1) Is it possible to have multiple instances of squeezelite? Under Linux this is very easy as you just have to start it twice on a second command line. In Windows it appears that it is not possible but maybe there's an option. 2) If it would be possible to start a 2nd (or 3rd) instance how can I assign The channels of the Interface. Under Linux I have done that in the asound config. With foobar e.g. there is an option called channelmapping where I could assign this in the software but with squeezelite I have not found anything yet. There's no option in the driver as far as I could see. Thanks for your help S s25a's Profile: http://forums.slimdevices.com/member.php?userid=65256 View this thread: http://forums.slimdevices.com/showthread.php?t=113638 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: WaveInput for Linux
bpa wrote: > The WaveInput was only valid for 7.9.* before 8.0 was released. When > 8.0 was released for a few months and I had time to check out the plugin > with 8.0 - I then updated WaveInput plugin so that it would compatible > with 8.* > > I think you are saying you had WaveInput already installed with 7.9.3 > (and maybe earlier) - this wasn't clear from earlier post. > So the version of the plugin already installed in 7.9 had validity > marked for 7.9.* in install.xml from the pre-existing installed version > of WaveInput - whereas the repository version of WaveInput has an > updated install.xml for 8.* compatibility. > After upgrade to 8.1 - the plugin version did not change so no plugin > update, but the compatibility as indicated in install.xml still show > only 7.9.* compatibility. > To get an updated install.xml which had 8.* compatibility - plugin had > to be uninstalled and reinstalled. > > This "install.xml" issue is true for many plugins which did not have a > version update as there is no code change. That makes sense *bpa* thank you. But I don't see any maxVersion defined in the install.xml, only a minVersion, what am I missing here? root@x:/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/WaveInput# ls -l total 32 drwxr-xr-x 3 squeezeboxserver nogroup 60 Jan 8 19:20 HTML -rw-r--r-- 1 squeezeboxserver nogroup 1671 Oct 9 2009 Plugin.pm -rw-r--r-- 1 squeezeboxserver nogroup 2031 Oct 9 2009 Settings.pm -rw-r--r-- 1 squeezeboxserver nogroup 2293 Oct 9 2009 WAVIN.pm -rw-r--r-- 1 squeezeboxserver nogroup 355 Oct 12 2009 custom-convert.conf -rw-r--r-- 1 squeezeboxserver nogroup 478 Dec 17 2008 custom-convert.conf.eca -rw-r--r-- 1 squeezeboxserver nogroup 301 Jul 5 2008 custom-types.conf -rwxr--r-- 1 squeezeboxserver nogroup 652 Feb 27 2020 install.xml -rwxr--r-- 1 squeezeboxserver nogroup 538 Jul 18 2008 strings.txt root@x:/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/WaveInput# cat install.xml PLUGIN_WAVEINPUT Plugins::WaveInput::Plugin RADIO 1.04 PLUGIN_WAVEINPUT_DESC bpa enabled plugins/WaveInput/settings/basic.html plugins/WaveInput/html/images/waveinput.png 2 Squeezecenter 7.3 * Linux yas1's Profile: http://forums.slimdevices.com/member.php?userid=70424 View this thread: http://forums.slimdevices.com/showthread.php?t=49584 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
gnackwatschn wrote: > Secondly: I agree, cosmetics do matter. But cosmetics should not impact > functionality to a level that makes software unusable for some users. In > case it really matters so much in our situation, also the volume buttons > and the volume controls in the 'manage players' view should be disabled, > to be consistent. I agree it should not affect functionality. My point was that if the volume shown in LMS was not the volume used on the player, then it has no real meaning and would be confusing. If it does reflect the real volume then it should be shown. I have updated Material to be consistent - and removed the 'Fixed volume' label. I've added a server-side yes/no option as to whether fixed volume should be respected. If set to 'No' then Material will treat a fixed volume player as a normal player - show volume slider and value. If set to 'Yes' it will show the slider as disabled and not show a volume level. I guess this resolves the issue? *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > Actually, AFAICS, iPeng has the volume control disabled - except on the > lockscreen, but the control does not seem to work. > > > > Cosmetics do matter. > > I have no real fixed volume devices, so I cannot really test. But, does > the volume shown in the Default web UI reflect the real volume? i.e. if > you change the volume on the real player, does LMS show the real volume > level? If not, then showing the level here is bad - as it implies its a > value it is not.If you have any Squeezelite players I believe they can be set > as fixed volume. As far as cosmetics goes I assume anyone who has a device set to fixed volume would ignore the volume slider anyway unless they have an amplifier controlled by it. I generally have my Touch at 100% volume but don't use the fixed setting just because it is sometimes handy to be able to lower the volume temporarily using an app. It would be interesting to know how many people use the fixed volume setting who don't have an amplifier with LMS controlled volume. Sent from my Pixel 3a using Tapatalk slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > Actually, AFAICS, iPeng has the volume control disabled - except on the > lockscreen, but the control does not seem to work. > > > > Cosmetics do matter. > > I have no real fixed volume devices, so I cannot really test. But, does > the volume shown in the Default web UI reflect the real volume? i.e. if > you change the volume on the real player, does LMS show the real volume > level? If not, then showing the level here is bad - as it implies its a > value it is not. Firstly: I am only using default skin and also Squeezer. So I can definitely confirm, that on both the volume controls are working perfectly and also reflect the values of the AVR volume. As iPeng is recommended by the Denon plugin developers, I suggested that it works the same. I apologize if that part of my post was wrong. Secondly: I agree, cosmetics do matter. But cosmetics should not impact functionality to a level that makes software unusable for some users. In case it really matters so much in our situation, also the volume buttons and the volume controls in the 'manage players' view should be disabled, to be consistent. I understand totally understand the point, that some people want to keep it as it is. That's why I requested this as an optional setting. I never intendend to change the default behaviour for everyone. So maybe that would be the best way to go? I also did not want to start a big discussion about that, just wanted to give feedback. That said I think it is up to you, to decide and I will respect your decision in every case. Keep up the great work. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: WaveInput for Linux
yas1 wrote: > Well I updated from 7.9.3~1591161343 to 8.1.0 and WavInput remained in > the active plugins list but with *no tick* in the box and its > description was 'Plugin is incompatible with this version of Logitech > Media Server. Please update.' The WaveInput was only valid for 7.9.* before 8.0 was released. When 8.0 was released for a few months and I had time to check out the plugin with 8.0 - I then updated WaveInput plugin so that it would compatible with 8.* I think you are saying you had WaveInput already installed with 7.9.3 (and maybe earlier) - this wasn't clear from earlier post. So the version of the plugin already installed in 7.9 had validity marked for 7.9.* in install.xml from the pre-existing installed version of WaveInput - whereas the repository version of WaveInput has an updated install.xml for 8.* compatibility. After upgrade to 8.1 - the plugin version did not change so no plugin update, but the compatibility as indicated in install.xml still show only 7.9.* compatibility. To get an updated install.xml which had 8.* compatibility - plugin had to be uninstalled and reinstalled. This "install.xml" issue is true for many plugins which did not have a version update as there is no code change. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=49584 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
DAR wrote: > I'm happy to test but am not sure how to install the dev version. I > tried editing my install.xml to switch "2.1.3" with "DEVELOPMENT-TIME" > and restarting LMS, but the plugin files don't seem to have updated. > Should this occur automatically, or do I need to synchronize the files > manually? No, you would need to checkout the code fro mgithub and then manually copy the MaterialSkin folder to your plugins folder. I do not make dev/nightly releases - too much hassle. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: WaveInput for Linux
bpa wrote: > > IIRC Those messages do not appear unless log level plugin.extensions has > been changed from ERROR and set to be retained after LMS restarts - so > that sounds like it is historical - a change made a good time ago. > No I had turned on debug for the plugin.extensions and restarted LMS in order to get the debug output for WaveInput after reading the previous post #508 about the same issue following update to 8.1 bpa wrote: > > The "uninstall" and "install" shows you probably haven't been restarting > LMS after requesting a plugin to be installed/uninstalled. > Please see above, I had restarted when turning on debug. The uninstall and install appeared when I installed the update to BBC Sounds and restarted. bpa wrote: > > When uninstalled, it is in 3rd Party plugins. Did you manually add a > repository ? > Yes it is. No. bpa wrote: > > Unless you describe what "ODD happening" is - I can't help. Well I updated from 7.9.3~1591161343 to 8.1.0 and WavInput remained in the active plugins list but with *no tick* in the box and its description was 'Plugin is incompatible with this version of Logitech Media Server. Please update.' I enabled debug and got the messages in the log as I posted. I also ticked the box next to WaveInput in the active plugins, applied and restarted: this made no difference. Later I noticed there was an update available to BBC Sounds so I applied that and restarted and at that point I got the uninstall message for WaveInput in the log. WaveInput then appeared in the 3rd party plugins list and I was able to select it, apply and restart, at which point the plugin works. That whole sequence does not seem like the 'normal' one to me and I therefore surmise it to be 'odd'. Short of sending you the complete server.log, which you are most welcome to, I'm not sure what else I can tell you, the plugin is fine now and I'm very grateful to you for the effort you've made to create it in the first place and to help idiots like me when things go wrong! yas1's Profile: http://forums.slimdevices.com/member.php?userid=70424 View this thread: http://forums.slimdevices.com/showthread.php?t=49584 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
gnackwatschn wrote: > Consistency: It would work like default skin, Squeezer and iPeng. All > those ignore the fixed volume setting, or, at least have an option for > doing so. Actually, AFAICS, iPeng has the volume control disabled - except on the lockscreen, but the control does not seem to work. gnackwatschn wrote: > - Functional vs. cosmetic: Cosmetics do matter. I have no real fixed volume devices, so I cannot really test. But, does the volume shown in the Default web UI reflect the real volume? i.e. if you change the volume on the real player, does LMS show the real volume level? If not, then showing the level here is bad - as it implies its a value it is not. *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Announce: Material Skin
cpd73 wrote: > The dev version sends +/- the defined volume increment when using the > up/down vol buttons when a player has fixed volume. This is also > extended by a server-side Material setting that will cause Material to > 'ignore' the fixed volume state. When that is set, the volume for fixed > volume players will be controlled as if they are not fixed volume - so > the slider will be active, and the up/down buttons will set a volume > relative to the current (as shown in the slider) volume. So, if vol=80% > and increment=5%, then down will set volume to 75% > > However, I'm not sure if this is really required. Or if Material should > just ignore fixed volume? In my opinion MS should ignore the fixed volume setting (slider and button) , or, at least give an Option to do so. Here a short sum up of the reasons I see: - Consistency: It would work like default skin, Squeezer and iPeng. All those ignore the fixed volume setting, or, at least have an option for doing so. - Less development effort: Fixed volume string is not localized yet, manage player settings still ignores it - Functional vs. cosmetic: Leaving the slider fixed strongly impacts the usability in some cases and forces users to switch to another skin. On the other side there is just a small cosmetic downside for others, when the slider isn't fixed aymore. This is only my opinion, but there are some objective reasons to think so. gnackwatschn's Profile: http://forums.slimdevices.com/member.php?userid=71199 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
