I’m using LMS alarm since 10 years and never had problems until i
upgraded to 8.3.
Are you on 8.3.0 or 8.3.1? The latter should be behaving much better.
___
beta mailing list
beta@lists.slimdevices.com
Can you point me to where you actually force 10.x to use the dated
5.*18*? Unless it's not in a perl script etc. and you excluded this when
you compiled the binary.
It's in the executable file's header:
% head
/Library/PreferencePanes/Squeezebox.prefPane/Contents/server/slimserver.pl
After installing Dec 4's LogitechMediaServer-8.4.0-*1670141288* on my
mac *10.15*, LMS started using the default perl 5.*18* again (BTW 10.15
That's correct: some older macOS versions would not run with binaries I
created. So I decided to keep things simple and only use those on macOS
11
When registering a notification callback for a particular player
($client), e.g.
Code:
Slim::Control::Request::subscribe( \, [['power', 'play',
'playlist', 'pause', 'mixer']], $client);
is it expected/intended that the callback should also be
Michael doesn't seem to believe Material is to blame - however, I have
tested several times without Material installed and not had any alarm
failures, but there's a caveat to that - the only way I can "reliably"
induce failures during testing is by playing around and changing between
players in
@mherger Any thoughts on why the Radio and the Touch behave differently
when the alarm is paused or stopped from a remote source? I wonder if
I don't know... some of the very last changes were indeed related to the
Alarm. But I've lost track of what is in which firmware version.
Just to add another usage case, my morning alarm is set up for a stereo
pair of Google Nest Minis using Philippe's Castbridge plugin. The alarm
had become unreliable in recent months but has not failed since applying
the most recent updates to Material Skin and LMS. Following is a debug
log of
At the moment I would say the change in code fixes or at least
drastically improves the problem where an alarm fails to trigger, but
completely breaks stopping the alarm with a pause or stop from a remote
controlling device.
Thank you very much for all the work you've done on this subject! This
If I pause now then the alarm screen continues to be displayed but I do
not hear the fallback alarm after 60 seconds. If I stop playback with
the optional Stop button then I get my clock screensaver and the alarm
screen disappears. This is definitely different to previous behaviour
and I wonder
So it looks like the behaviour of pressing pause from a remote control
device has changed.
But the change would be in 8.3.0, too?
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
New 8.3.1/8.4 builds should be available with this additional check on
the source.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
I actually think that the MAC address is included in the source string
when the associated session is controlling a different device, i.e.
In that case it would be a /slim/request - which is excluded explicitly.
___
beta mailing list
Okay. I've got it this time. No, REALLY!!! :o
(I verified it with a regex testing utility.)
The problem is missing quantifiers after the components of the MAC
You're correct!
Hopefully this post will redeem my technical credibility to at least a
minor extent. In any case, the change should
41 alarms, no failures, so looking like Craig's proposed tweak in
MaterialSkin has helped the situation.
I don't think I can do any more with this current setup, depending how I
feel tomorrow I may go back to the released version of Material and see
if I can break it again and then try with a
Do note that the SB devices themselves appear to use cometd as well as
indicated by this log snippet:
But that's ok, isn't it? If you hit power off on the device then the
alarm is expected to stop.
So it isn't strictly necessary to be using Material, it may also be e.g.
The difference
Shows the Material client shutting down the alarm 99% of the time in all
8.x versions.
Does it really _fail_ the alarm, or just log that one statement? Because
we still believe this was a 8.3 only issue...
___
beta mailing list
So despite Michaels feeling that the "playerprefs" source is a red
herring, I'm still only seeing failures when such a source is presented,
That could very well be true. But I do not always see failure when those
calls are logged. I had a whole series of cases where the alarm worked
as
Need to note that I patched Alarm.pm in both 8.2.0 and 8.0.0 to report
the source of the _alarmEnd signal. Using the scheme I reported earlier
the logs show it is the Material client that shuts down the alarm. Thus
Please note that I believe that message is a red hering: yesterday I've
seen
I had apparently not subscribed to the Radio correctly. The error is
there in 8.2.0 as well. Sorry for the wild goose chase.
What error? The alarm failure?
___
beta mailing list
beta@lists.slimdevices.com
Argh... this is so frustrating. I thought I was able to reproduce the
issue using Kebul's procedure (switching players in Material). But
turned out that this would indeed toggle the log entry from "ignored" to
"fired". But the alarm did still work... So that whole log thing and
Cometd might
/4fd1bca6/slim/playerprefs/00:04:20:26:xx:aa|335||4fd1bca6|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15
This looks odd to me. And the only part that -could- be from Material.
Material subscribes to player preference
alarm issue. It doesn't appear to be widespread.
And it's not an "always broken". It shows up sometimes, but we haven't
figured out yet how exactly to reproduce, did we? I'll have to re-read
KeBul's report.
FWIW: I've set about three dozen alarms on three different devices over
the past
Thinking I may well dig out a spare SB Radio and set it up next to my
usual lounging area and then set hourly alarms for some more intensive
testing, Although I wouldn't be surprised if Michael's investigations
progress before I get round to that.
Please do that setup (using the latest nightly,
[22-11-20 11:59:00.0462] Slim::Utils::Alarm::_alarmEnd (1980) Unknown
source:
/5ce23ddd/slim/playerprefs/00:04:20:2c:c9:61|13||5ce23ddd|Mozilla/5.0
(Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like
Gecko) Version/16.1 Safari/605.1.15
That's exactly the kind of output I
Just to be sure - do you confirm it is (player.alarmclock) and
(player.source) to enable for debugging?
player.alarmclock I'm most interested in. But I think Kebul already
posted some interesting log snippet.
___
beta mailing list
Can you share, so more of us can test?
Just install one of the nightly builds:
https://downloads.slimdevices.com/nightly/?ver=8.3
https://downloads.slimdevices.com/nightly/?ver=8.4
___
beta mailing list
beta@lists.slimdevices.com
And nobody thought of adding a debug log line to get a report of what
source is being reported instead of the expected 'ALARM' string?
I did exactly this a few hours ago.
___
beta mailing list
beta@lists.slimdevices.com
And while trying to do this I had again a failed alarm (15:40) and then
one that worked (15:47):
Without restarting LMS in between?
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
didjean - thank you very much for this posting and the log file! I think
we got a lead:
invalid:
[22-11-17 20:45:01.7436] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-17 20:45:01.7442] Slim::Utils::Alarm::_alarmEnd (1992) Stopping
alarm
vs. correct:
Is there already a cure for this.
I don't even haven understanding for what exactly is failing, yet.
I've had this for about a month or two.
It failed when I started the thread. Then we were happy campers again
for weeks and months. But yesterday it failed again...
An old windows devil seems to be Back:
After change to winter time every file is discovered as changed...
(so LMS just tries to update 1.100 k entries in my DB...)
Is this _all_ your library? When did the scan kick in? Could it be the
time changed during the scan? What Windows version are you
are there any plans to add library view support to the plugin? The quote
is just about 4 years old :)
LastMix v2.2.0 is on its way to you. Please give it a try (and report
back in a LastMix specific thread, if needed).
___
beta mailing list
I've got four different DontStopTheMusic.pm for Random Play. Which one
do I change?
There's only one. Please check the exact folder.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
What player types is everybody using?
Is anybody in this thread (haven't read it again) using a Classic
player, or Boom/Receiver/Transporter?
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Again, an alarm out of 3 radios failed this morning - with no back up.
That last remark actually is a good point: when mine failed there wasn't
any backup either. Which firmware are you using on your Radios?
___
beta mailing list
As stated earlier, it is Material that is invoking JSONRPC to add a
track to a -stored- playlist via:
["playlists", "edit", "playlist_id:", "cmd:add", "url:"]
The original poster mentioned a message "adding null to playlist". I
can't find this string in LMS. Are you showing this?
(IMHO, I'm guessing that probably wouldn't happen at all if DSTM
included the #EXTINF data for streamed tracks, because that's the one
and only difference between those tracks and all the other tracks that
have always worked properly.)
#EXTINF is a playlist file format specific thing. DSTM
I don't think that's the problem, because when I use other options for
DSTM (*not* LastMix/Last.fm), the same null/unknown issue still happens
with streamed tracks that have been integrated into my music library
from Tidal and Qobuz. No matter which option I choose, any streamed
track added to
It absolutely does. I don't have a Spotify account, but I enabled the
plugin thinking I might try Spotify at some point. So "Spotify
Recommendations" appears as an option for DSTM. When I select it, it
adds local tracks.
Most likely because DSTM would fall back to random tracks, as Spotty
I just now tried some other options (MusicIP Mix, Spotify
Recommendations). Each one added songs from my music library (most
Spotify Recommendations certainly does not add local tracks. But that
doesn't really matter.
Again, I'm only experiencing this problem when streamed songs are added
Weird thing is, when I tap on the "null" entries in my playlist, they
actually queue up the correct songs.
I think you should try to figure out what is adding those track. Disable
the Playlist Manager plugin and see whether you still have those menus.
Or ask in a Material thread, whether it's
How are you trying to add to a playlist? Are you using a plugin like
Playlist Manager?
I'm just tapping the three dots to the right of the song in the queue
and selecting "Add to..." from the menu that pops up.
But do you have the Playlist Manager plugin (or some other dealing with
I had to do a bit of research to get Don't Stop The Music to function
properly. Now that I have, it seems like a nice substitute for Roon
Radio, especially using the LastMix/Last.fm option. However, I've found
that when DSTM adds songs to my queue and I try to add one of those
songs to a
Did that join all tracks on one album again? I would expect this to
"fix" the database. And thereafter touch some tracks should no longer
cause splitting the album.
I expected this, too - but it didn't. Scanner recognized all (13) tracks
as scanned but still kept them in 2 different albums as
- library.db was "unchanged" (one album with 11 tracks, one album with 2
tracks - 2 different values in tracks.coverid (one or 2 tracks, one for
11 tracks), same tracks.cover for all 13 tracks.)
Please note that the change would _not_ "fix" an already broken
database. It would only prevent the
Thanks a lot Frank! I think we're one more bug down... new builds are in
the pipeline.
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/beta
Never mind: I'm able to reproduce the issue. This must be a bad
regression... it's enough to change a file's filestamp to make it end up
in a new album :-(.
Might be yet another !@#?! Umlaut problem... I only see it if the album
title has an umlaut (or probably some other accented character)
Never mind: I'm able to reproduce the issue. This must be a bad
regression... it's enough to change a file's filestamp to make it end up
in a new album :-(.
___
beta mailing list
beta@lists.slimdevices.com
Meanwhile I was able to reproduce the behaviour by changing the title
again the other way round:
I changed the (track) title from "Sommarens sista sang (Radio Edit)"
back to "Sommarens sista sang".
On another track "Bland nattens skuggor" I just pressed "save" (wthout
any changes) to have scanner
- I have an existing album
- I change the title tag (in this case adding "(Radio Edit)" to the
existing track #3 - no other changes, no renaming
- I do a "new & changed"-scan
- I have 2 albums by the same artist with the same name in my db - one
containing only track #3, and one containing tracks
MAI has this feature. You'd find it in the web UI's (Default, not
Material!) Extras menu.
...Material can show 'Extras' too :)
But it doesn't make coffee, does it? :-)
Where would that Extras menu be?
___
beta mailing list
Aha OK that has always bothered me. I have around 3100 albums though.
Maybe the others don't have coverart.
Or they use embedded artwork?
Is there an easy way to check how
many have missing cover art?
MAI has this feature. You'd find it in the web UI's (Default, not
Material!) Extras menu.
Probably not related but my new and changed scans always discover more
than 2000 updated coverart files even when no changes at all have been
made to the library.37466
No, it's not finding updated coverart, but it's verifying whether they
have been updated.
Remember the issues with daylight savings time changes on Windows? We
had a DST change over the weekend. You solved it for scanning the music
files, but apparently cover art still gets pre-cached again with a new
and changed scan.
One more question: would you know whether these files were
Remember the issues with daylight savings time changes on Windows? We
had a DST change over the weekend. You solved it for scanning the music
files, but apparently cover art still gets pre-cached again with a new
and changed scan.
Argh... of course. Would you please submit an issue on
Needs some with paying subscriptions to confirm that it continues to
work for them.
Those users should be in the vast majority, we'll hear from them quickly
if things fail :-D.
___
beta mailing list
beta@lists.slimdevices.com
Correct - individual songs cannot be selected with a free account - at
least that is what I think is the problem.
Please give 2.1.0 a try. It tries to figure out what kind of
subscription you're using and would disable Deezer integration if it
wasn't Premium.
I have DSTM enabled - and I have Deezer FREE enabled.
DSTM (version 1.0.0) is picking songs from Deezer (version 1.0) - but
they cannot play because that does not work with Deezer FREE.
In the player settings I have "LastMix - Don't Stop The Music support
using Last.fm" selected.
What you're
It's 7.317 (so for the first 4 seem to be headlines (see below), it
makes sense):
Not surprisingly that's a lot. Does the fulltext search still provide
some value to you? All those 7k popular terms would only be searched for
in titles, but eg. not in comments.
I'm not saying "turn off FTS"
Your crash happened when the FTS plugin tried to create the list of
popular terms. I don't know how any of the recent changes would have
added any additional effort this. So... while I don't like that, let's
consider this a random crash :-/.
OTOH: could you please check how many lines you
[22-02-13 11:01:17.0761] Slim::Schema::Storage::throw_exception (121)
Error: DBI Exception: DBD::SQLite::db selectcol_arrayref failed: out of
memory [for Statement "
SELECT term, d FROM (
SELECT term, SUM(documents) d
FROM
Ok, 2nd try, same result:
"Rescanning Media Library... Geänderte Dateien werden durchsucht (511
of 298)"
Argh... that's likely due to my attempt at not running a last,
unnecessary request over the tracks table. I've now committed an
alternative approach, which might actually be slightly
OK, MANY MANY thanks, I've just installed, made sure I changed more than
50 files and started a "new" (which takes a little longer due to
the changes, I guess - till now it was about 45 min. for a new &
changed, now it is after 45 min. halfways through the database so I
guess it will be "times 3"
Ok, time for another batch of updates :-).
I believe there was a bug in the scanner introduced more than a decade
ago... the processing of changed files happens in batches of 50 tracks.
After closer inspection I figured out that only ever _one_ such batch
would have been processed. Which
Ah, OK! I just wanted to express, till then we concentrated on trying to
see why scanner does "wrong changes" or doesn't remove artists and in
which order scans happen.
But if server doesn't detect the files as changed (eg for "windows
reasons") and they aren't even handled by scanner, the
In German "Das erklärt, warum es einmal geht und einmal nicht (obwohl
nichts am Code oder an den Dateien verändert wurde)"
I even don't understand in German :-D. I didn't understand _what_
explained the behaviour.
I looked in "tracks" (library.db) there it was unchanged with added_time
=
So I looked into scanner.log - all files that were found now -
10.02.2022, 18:30 - were changed by me on 08.02.2022 between 23:00 and
23:59.
That's just odd. I have no idea why some changes would require multiple
scans to be be recognized as modified files. It just doesn't make sense,
unless
So it looks very good ... - though I'm careful to call it "solved
forever" after one try ...
Forever is a long time out :-). Thank you very much for your extensive
testing!
___
beta mailing list
beta@lists.slimdevices.com
OK, thanks - then I will now turn the files back in "broken" status =>
scan => correct the tags => scan ... :)
You don't have new files to clean up today?... :-D
___
beta mailing list
beta@lists.slimdevices.com
I tested by "touching" the files again (changing mtime) so they were
discovered by scanner.
It did but it did no changes to the db.
Am I right that this is "expected behaviour" for scanner didn't see that
the old "Deejay Ötzi" artist is as orphaned entry still connected to the
album in
a) with renaming: changed "ATB: Topic" => "ATB; Topic" (as album artist
and track artist) AND renamed the file
b) without renaming: I changed "Deejay Ötzi => DJ Ötzi" (it's an album
by "Various Artists" with comp=1 ) and DIDN't rename the file
Thanks for the additional information! I believe I
In both cases it were misspelled artsist.
Both were the only entries from those artists a) "ATB: Topic" b) "Deejay
Ötzi"
a) with renaming: changed "ATB: Topic" => "ATB; Topic" (as album artist
and track artist) AND renamed the file
b) without renaming: I changed "Deejay Ötzi => DJ Ötzi" (it's an
ok, 4 scans further with different sets: The "you" issue seems to be
back - and there seems to be another issue with casesensivity (Atb =>
ATB, just tried A-ha => a-ha and R3HAB => R3hab)
Can't reproduce the case sensitive case: test with and without file name
change. In both cases the change
In my experience tagging changes aren't always picked up properly in a
new and changed scan anyway. I always remove and replace the affected
albums doing a new and changed scan twice.
I've fixed a few of those issues in the past week. Please give it
another try.
[22-02-05 22:06:56.4989] Slim::Utils::Scanner::Local::deleteTracks (364)
Removing deleted audio files (29)
[22-02-05 22:07:22.1622] Slim::Utils::Scanner::Local::updateTracks (531)
Rescanning changed audio files (70)
[22-02-05 22:07:31.6498] Slim::Utils::Scanner::Local::addTracks (447)
Scanning
Just doin' the same with HUGEL => Hugel and have a close look.
I'm sure if you zipped the resulting database file it would shrink to
"only" a few hundred MBs :-D
https://www.dropbox.com/request/T3RctyzGgNg0oFDubq6a
___
beta mailing list
To see if there is (still) a bug I wanna know:
How does new scanner detect what files to scan?
Timestamp and file size.
I guessed, it takes the "file change" date (from windows) - but this had
been changed with all files...
Yes, that should be used (mtime equivalent on Windows).
I then
I deleted them in tracks-table (all) and started a new -
and they were imported again (and only once imported :))) )
So you're good again?
Next time you encounter a problem please keep a copy of scanner.log and
library.db for further investigation. How large would the latter be in
your case?
Is there any "easy" way to get rid of ALL playlists (and import them
new).
I think it should just work... easy as that :-).
There was an error during my last re-scan so it couldn't see all
playlists (only 60 of 1.259 - my fault).
Running a new" said it found 1.259 playlists (that's right) but
Is there a preferred way of tidying up a library to avoid scanner /
server crashes?
Try to understand why it is crashing first. There are a hundred or more
reasons why it might fail, but none should happen. It's important to
understand what's wrong before you try to fix whatever.
So...
It's running Windows on a small Intel NUC (Celeron) with about 4 gig of
RAM (maybe 8 gig, will check once I get home).
Could you please check memory usage while the scanner is running? In
particular during the Fulltext Search indexing?
I have the DB memory setting at maximum in the
It looks like full text search is choking because of the name of a
playlist. I have nearly 900 playlists so I would help to know what I
should be looking for. Any suggestions?
It's not the name, but likely just the number of tracks overall: the
scanner is running out of memory. What hardware
When Full text search is activated, the option "Search within words"
under "My Music" seems to have no effect.
That's correct. The fulltext index is working with "tokens", which
baseically are words. It doesn't use substrings, or any kind of
similarity (which I would love to implement at some
I habe NO idea what is blocking here.
Maybe
https://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-tcp-or-udp-port-on-windows
can help?
___
beta mailing list
beta@lists.slimdevices.com
But again, honestly, who knows how many folks still have i386 hardware
lying around gathering dust that they'd want to slap a LMS on?
I tend to only support a platform once there's been demand for it. But
the definition of "demand" remains a bit flexible. One voice usually
isn't enough...
Hmm I see in the comments for the pull request that Michael wasn't
totally convinced of the logic behind it and said it would be easy to
revoke if it caused issues. It has caused issues.
Please define "issues", and some number to allow for the plural :-).
If the issue is a change in behaviour
What would such a clean up do which the regular scan shouldn't already
be doing?...
It was just an idea to keep the "new" quick (and I like it to be
this quick ;)) to "outsource" options like looking for orphaned entries
in a separate routine You only use once a week or once a month... (the
"n"
Maybe we could invent something like a "Database cleanup" routine (in
addition to the "new & changed") - I saw something like this in Media
Monkey.
What would such a clean up do which the regular scan shouldn't already
be doing?... I think we have to clearly identify the open issues we
have.
Makes sense but isn't there the danger of a longstanding user forgetting
which email address they might have used for MySB.com?
Rather than delete credentials entirely wouldn't it be sensible to leave
the email address in place but clear the password?
You're right, only the password is being
There's a difference between a password for LMS locally and a password
for MySB. As I understood it, the change applies to MySB authentication
only.
LMS up to 8.2.x would store your mysb credentials locally to sign in to
mysb to use its features (music service integration, prefs syncing,
So in general I should be using a strong password for LMS?
In general all your passwords should be strong. But I personally don't
use any password for LMS, as it's an in-house application only.
___
beta mailing list
beta@lists.slimdevices.com
Why aren't they deleted even by a "playlist only" change? Shouldn't the
scanner detect, there are 0 (or in may case: 1) playlist in the given
directory and delete anything else?
Hmm... that's a good question. They certainly should be removed. Would
you mind dropping me a copy of your
Yes. problem is, for security reasons I don't have my server running
over night so I have to break and restart it three times (means 3 days
no music).
Are you saying that you cancel the scan and restart a "rescan" the next
day? That's likely to ask for trouble. You should definitely find a way
So it's no an option to "re-save" all of my files.
Is there any way to do an "only artwork" scan, so the server scans all
the files, where it has no artwork stored?
I'm not sure of a clean way to do this. But you could shut down LMS,
delete artwork.db, restart and run an incremental rescan?
Will MIN_TRACKS_LEFT always be a constant or could you imagine letting
plugins/mixes set that value (within a certain range) as you do with
number of used seed tracks and such?
Nothing's forever. But I have no plans to change it.
I'm only asking because sometimes I skip tracks very quickly
IO::Socket::SSL: 2.049
Is this SSL version outdated? I just wonder because everything worked
fine until yesterday or the day before.
It's not latest, but not that old. Is the time on your system correct?
And does this log entry about DSTM mean anything?
[21-07-08 14:42:51.2394]
I love "Don't stop the Music"! Unfortunately, it stopped working
sometime in the last days (LastMix local only).
[21-07-07 16:16:31.4340] Slim::Networking::Async::connect (114) Failed
to connect to nav.dl.sourceforge.net:443, because
Net::HTTP: connect: timeout
You might be using outdated SSL
do you think you could add Erland's *DynamicPlaylist* plugin to the
'list of mix plugins that DSTM watches out for'
Can you say what class and property name to look for? When does
DynamicPlaylist kick in? How do they conflict? I'm surprised this only
comes up now, as DSTM has been out for
Does high work OK with 1GB of RAM? How many tracks do you have and what
size is your swap space?
It should, unless you run a lot of other services on the same Pi. I've
been using "max" on a pCP based server for years (Pi 3B+). It handles
about 21k tracks smoothly.
What Pi? How much RAM? How large is your data partition where the LMS
cache lives?
Raspberry PI 4B 1GB
Do you mean dphys-swapfile ?
Where does TMPDIR live? What does "df -h" say? Can you check memory and
free disk space while the scanner is running? Anything in scanner.log?
1 - 100 of 4084 matches
Mail list logo
