wt0 wrote:
> Thank you for doing the tests. I figured out why it's always 6 times.
> It's a simple typo on my part. I'm saving the preference as "maxRety"
> and reading it back as "maxRetry". The default is 5 (that doesn't
> include the first connection).
Glad it helped to identify the issue
It's been up and running completely unattended for a couple of days
now.
Thanks for fixing it.
mruddo's Profile: http://forums.slimdevices.com/member.php?userid=65325
View this thread:
Thanks for getting back to me... I've checked the Wifi settings, and it
should be on all the time - on both the S3 and the Nexus. What I've
noticed is that "infinite" (or indeed any other number for that matter)
shows the same behaviour in the debug log:
UNABLE TO CONNECT TO SERVER
Hi wt0,
I'm trying to use the app in my daughter's bedroom - they key point
there being that I'd like it to be plugged in and out of reach and just
available as and when required.
I've configured it, and it runs perfectly when connected, but if for any
reason the server goes down for any length
Just wanted to add my thanks for this plugin.
I've just re-organised my Squeezebox setup, and because of space issues,
I switched an SB3 in my living room, with a receiver I had in another
room... Trouble is, that left me without any visible display (aside from
the remote obviously). So, using
d6jg wrote:
> You can achieve the same (perhaps better) with a Pi3, piCorePlayer, and
> Jivelite via HDMI (and a remote of some kind if you wish). It includes
> Visualisers and will properly sync.
Thanks for the tip - I may look into that when I've some free time.
d6jg wrote:
> Has anyone else noticed MAI misbehaving lately. I think its something
> at Allmusics end as nothing has changed with plugin.
> It seems to fail (or timeout?) on things where there are valid entries
> in the Allmusic database.
> Any pointers as to what may be going on? Could it be
Some years ago I was amazed by the mixes MusicIP gave me, but abandoned
it because analysing my collection took forever and I occasionally ran
into issues etc., but more recently I've been using the LastFM mixer and
these are pretty good on the whole for a ramble through my music
collection.
mherger wrote:
> My thoughts? Sounds interesting! That said: I doubt there are many Mixed
>
> In Key users out there... so unless you do this yourself for your own
> needs, there's little chance you'll find someone picking up the idea.
>
> Are you up for the challenge? Willing to learn some
Well, I can't be too sure, but it took about 3 hours to scan those 681
files, and I ended up with 661 in the database. Which confirms it was
just those with accented characters (and variations on the apostrophe)
that were excluded. So as far as I can tell, there were no issues with
the writing
I'm currently mid-way through a second pass analysis of my 681 files,
and so far there's only been the one failure - so it's looking like the
change to allow accented characters has worked successfully.
(Incidentally, I believe the track that failed this time was OK in the
last run.)
I'll
cpd73 wrote:
> If you re-run then newly, or un-analysed, tracks will be analysed and
> added. Any tracks that are in the DB but not on disk will be removed
> from the DB. If you want to keep these non-existant tracks in the DB the
> pass "--keep-old"
Thanks for confirming... sure enough, a
cpd73 wrote:
> You will need to compile your own Essentia extractor - the pre-built
> ones don't support the models. To be honest, I'm not 100% convinced on
> the need for the filtering with high-level attributes.
I think you may be right...hence I've moved on, to see what sort of
mixes I get
Sorry, I got distracted trying to get the high-level essentia analysis
working in Windows. (No joy yet with that one.)
cpd73 wrote:
> Odd. Can you run ffprobe against this file? ffbrobe.exe should be in the
> 'windows' folder - and it should print info such as the track's
> duration. Also, if
I'm back, and giving it another go... This time, with Alpha 2, I seem to
be getting further - albeit the main issue with me was I believe an
outdated Python install, so I've upgraded to the latest 3.10.1 64bit
release.
Analysis (of those 681 FLAC files) is under way.
It's definitely
cpd73 wrote:
>
> Ah! Its short length is -probably- why the analysis fails.
Certainly looks like it. I'm still working through the analysis of my
library... several similarly titled "Interlude" tracks have also failed.
Generally though, it's progressing well.
Hi Craig
Have just noticed this, and I'm going to give it a go on my Windows
setup... I'll report back when I can - but I only have a few minutes
this evening, then I'm away for a couple of days - so it may be a slow
process.
First thing I've hit which looks odd, having installed the various
OK, so that got the analysis running, but I've not had much luck with it
working...
I edited config.json to include paths path for the db - but I'm not sure
I've understood local correctly - below it's set to where I installed
the files,
So I've changed:
cpd73 wrote:
> Ah! Thought it might, I just did not have a system to check. I guess I
> need to add this to my analyzer :) Thanks.
Intersting... The Music In Key harmonic mixing guide is here:
https://mixedinkey.com/harmonic-mixing-guide/ i.e. with the equivalent
notes. (For which I think A#
cpd73 wrote:
> Initial implementation added to music-similarity :)
That was quick..! Looks like I need to see if I can find some time to
enable the Musly analysis on a PC.
mruddo's Profile:
Thanks for the information... much appreciated. I'd love to have a go at
something in this space - just can't commit to any timescales as free
time is short at the moment.
mruddo's Profile:
cpd73 wrote:
> I would use DISCSUBTITLE, but it is not provided by the LMS JSONRPC API
> that Material uses - so cannot access this, if it was then this would
> (obviously) be the best solution. I am not going to write custom SQL
> code for this, and definitely do not want to rely on
So far I'm impressed... It's playing a good mix from most starting
points, and no odd behaviour to report so far. What I like about the
analysis approach is that it seems to pull in a more broad range of
alternative tracks than a simple grouping determined by a website like
LastFM - which is my
Just an update on full my library analysis...
As mentioned previously, I was running this on a desktop PC. I use this
to rip CDs/download music etc. then have a robocopy clone job that sends
the files to the mini-PC where I run LMS.
So the plan was to simply analyse on the more powefull PC,
Sigur Rós present another set of interesting characters that seem to
give problems:
2022-01-06 09:19:59 D [ 114/2495 4%] SIGUR RóS/ÁGæTIS
BYRJUN/01-INTRO.FLAC
2022-01-06 09:20:59 D [ 115/2495 4%] SIGUR RóS/ÁGæTIS
BYRJUN/02-SVEFN-G-ENGLAR.FLAC
2022-01-06 09:21:23 D [ 116/2495 4%] SIGUR
cpd73 wrote:
>
> [Edit] I've added code to handle this. See docs/OtherConfig.md
>
Thanks.
I've updated my config.json file to add the the exclusions, as below:
Code:
{
"paths":{
"db":"M:\\My Music\\MusicSimilarity\\db",
"local":"M:\\My Music\\FLAC"
},
Just to reiterate, these failures were _prior_ to your most recent utf-8
change - so they're OK now!
All tracks on this album failed:
Code:
Angel Dream (Songs and Music from The Motion Picture She's the One)
And there were a few other 12"
That's great - thanks... I got an additional 60 or so tracks added after
those changes (turns out another issue was double quotes - so having 12"
in the name for example was also causing exlcusions prior to this).
Additionally, I see you've also got the check for track length in there
- which
I think like apostropes which have both "straight" and cuved (opening
and closing) variations, you can use the curved variation in a
filename.
So you have " vs ... and variations on that theme. I can't be too
sure which is actually being used in all cases though, as looking at
charmap in
I don't think it's that. I've generally been testing the results, and
did again just now..
Code:
M:\My Music\MusicSimilarity>.\music-similarity\music-similarity.py
--log-level INFO --test
2022-01-10 09:08:11 I Testing musly
2022-01-10 09:08:15 I Loaded 30962
Thanks for the info... I'll experiment a little more with exclusions
when I can.
Just an update on mixes though - as a trend I've noticed seems to
indicate a bias towards artists at the tail end of the alphabet. My
music is stored in folders by Artist then Album. So my analysis database
is
cpd73 wrote:
> No, the genre filtering only happens at analysis time - its used to
> discard tracks. It will not affect tracks already in the DB.
>
> You should not manually remove rows from the DB, this will lead to
> 'gaps' in the row-IDs, and will break the similarity. If you have
> removed
Something I noticed today that may represent a possible improvement with
respect to not repeating artists/songs.
Below are two lines from my database showing the same track on two
different albums that the mixer correctly defined as being somewhat
similar! :D
These songs came up with only one
cpd73 wrote:
> When filtering song titles, it is *only* the title.
I think ideally, this should really be -artist -*and* -title-. Although
unlikely to be a common issue, there are a number of repeated song
titles out there. Off the top of my head, "The Power of Love" springs to
mind - Huey
cpd73 wrote:
> Perhaps this is an issue with the mutagen library that is used to read
> tags.
>
Could this be related to the issue I had where the meta data was missing
from my database? I did wonder if I'd run the analysis incorrectly or
something, but I'm not sure I did - as I've scripted
As discussed with @cpd73 It turns out the issue I had was down to my
database file not containing all required meta fields, which was
adversely impacting the matching and causing the majority of tracks to
be disregarded.
This was likely caused by my use of incorrect parameters when running
the
cpd73 wrote:
> I've just tried with:
>
> >
Code:
> >
> "excludegenres":["Pop", "Rock"]
>
> >
>
> And I see the following during analysis:
> >
Code:
> >
> 2022-01-09 21:28:12 E Failed to analyze ABBA - Gold -
tia this time - so as far as I know it should be Bliss only.
But when I attempt to run the analysis I get a total failure of all
files. i.e:
Code:
mruddo@Moet-BL1MBQ1:~/music-similarity-master$ ./music-similarity.py
--analyse m -l DEBUG
2022-02-13 14:34:53 D (Defaults
following errors now:
Code:
----
mruddo@M:~/music-similarity$
/home/mruddo/music-similarity/linux/x86-64/bliss-analyse "~temp-library/Wolf
Alice/Visions Of A Life/11-After The Zero Hour.flac"
/home/mruddo/music-similarity/linux/x86-64/bliss-analyse:
/lib/x86_64-lin
cpd73 wrote:
> So, now you need to find out why. Ah wait... You're running on Windows?
> If so you need to rename "BlissMixer/Bin/windows" to
> "BlissMixer/Bin/MSWin32" You might also need to install vcruntime140.dll
> -- all this is fixed for next release.
Sorry I missed that in the earlier
cpd73 wrote:
> Hmmm... This is working for me, but @afriend has noticed that it fails
> the first time for them. The LMS plugin starts bliss-mixer on demand,
> and it stays runnnig for up to 1 hour after the last command. Perhaps
> the start-up time is too slow for you? How many tracks are in
cpd73 wrote:
> the plugin starts an executable named "bliss-mixer" - it was this you
> needed to check if it was running. (via "ps -eaf" on Linux)
>
> If a mix cannot be created, the LMS plugin will fallback to using
> LastMix or Spotty. Perhaps this is what is happening. You would need to
>
slartibartfast wrote:
> I didn't realise "Create Bliss Mix" was there until you mentioned it
> [emoji2]. I got used to not having "Create MusicIP Mix" after removing
> the plugin I didn't think to look.
Happy to (inadvertently) help! Although I probably tend to use DSTM
more, that's my go-to
After testing with the MusicSimilarity plugin for some time, I'm a bit
late to the Bliss party, but finally up and running! :)
I've had a number of issues to work around... not least losing my media
drive for a while that caused LMS to reset a number of parameters which
broke a whole host of
but we'd still have this issue:
mruddo wrote:
> Interestingly, (something slartibartfast noted) when browsing by year
> you only actually see the years for which you have albums designated to
> that year.
>
> e.g. In theory, I have no albums for 1961 or 1962, and those years do
>
Thanks. The error I was getting from the analyser was caused by an short
album track of complete silence - so nothing to analyse! :)
I decided it was surplus to requirements and deleted it, so analysis
scans are error free now.
slartibartfast wrote:
> Snap. What was the track? Mine was on Tin Planet by Space. I can't
> remember the last time I played the album [emoji1787]
>
> Sent from my Pixel 3a using Tapatalk
Silence - on Rilo Kiley's, The Execution of All Things. :D
kidstypike wrote:
> If you click the 3 dots alongside the year, "play now".
>
> Does that suffice?
>
> 37460
Thanks, but unfortunately not.
If for example I do that for 1967. I get a few albums with all tracks in
that year along with a number of compilations with tracks in a broad
range of
cpd73 wrote:
> 2.9.3 release of Material will have an "All Songs" entry for genres and
> years.
Great! :) Thank you.
mruddo's Profile: http://forums.slimdevices.com/member.php?userid=65325
View this thread:
kidstypike wrote:
> Advanced search > Year equals > does that work for you.
>
> 37461
>
> 37462
Yes, that works too... but again, not so convenient as "All Songs".
I admit it's an occasional use option, I guess I just wondered why it's
not present in the Material skin too? I admit, it's
slartibartfast wrote:
> Kidstypike's first suggestion would do the same thing. The advanced
> search idea is better though.
>
> Sent from my Pixel 3a using Tapatalk
But it doesn't, e.g. for 1967 - it includes all tracks on the following
album:
37463
(In both Material and Default skins.)
But
Apologies if this question is buried somewhere in this thread, but I
could not find it...
If I want to play all tracks from a given year, and select "My Music",
"Years", "" - then I only see albums deemed to be of that year. So
let's say I select 1997 for example, I'll see all albums with
slartibartfast wrote:
> Doesn't "All Songs" just play the tracks from the albums listed under
> the chosen year?
>
> Sent from my Pixel 3a using Tapatalk
Yes, it does - and it is "All Songs" (not "All Tracks" as I mentioned
above - I will correct), but that's not present in the Material
slartibartfast wrote:
> Really. I must admit I didn't check but assumed that All Songs would
> also play all the tracks of that album. So default skin only lists
> tracks from the year the album displays but how would you play other
> tracks from the same album? If other tracks are from a
Hi @cpd73,
When analysing my tracks, I always get a "1 Failure(s)" message. i.e. if
I add a new album with 10 tracks, it will find 11 and report 1
failure... so all new tracks seem fine, but there's obviously a track
out there it's picking up that it does not like.
Is there any way to log
cpd73 wrote:
> The next release will print (up to 100) tracks that fail to analyse - my
> thinking being that 100 is a lot to show, and if you have more than this
> there's a major issue somewhere.
Great, that sounds most reasonable...
I'll be interesting to see what it is. The only issues I
cpd73 wrote:
> @mruddo Following on from the discussion on the Material Skin thread...
> I have, I think, resolved issues on Windows - but I'm not 100% sure, and
> was hoping you could try the version before release? The steps would
> be:
>
> > >
- Downl
cpd73 wrote:
> Were these tracks added by a DSTM mixer? MusicSimilarity, Bliss? If so,
> any errors logged in LMS's log files? Do you see similar issues if the
> tracks are manually added?
DSTM Bliss. I can't see anything obvious in the logs - although there
are a number of errors for missing
Something I've mentioned previously on the Music Similarity thread - a
scenario were you end up with an "extra track" queue - and thereafter,
sometimes that becomes a misaligned track/cover-art image... I'm not
sure if there's anything in this, but I thought the other day that
ampersands in the
cpd73 wrote:
> This is an LMS issue - as stated before. LMS tells Material there are X
> tracks in the queue, but only provides (e.g.) X-1 tracks in the queue
> listing. Material, therefore, thinks there should be more tracks and
> asks LMS for these, and this is where the duplication occurs.
cpd73 wrote:
> According to https://www.urldecoder.io/: "That's not a valid URL encoded
> string" And its the encoded quotes that are breaking things, if I remove
> them then the URL is accepted.
At the moment, I'm thinking a tag-cleaning exercise may be the way to go
for me.
It's actually
cpd73 wrote:
> If you could hold off for a few days that'd be appreciated. I'm going to
> change the mixer and plugin so that the path conversion is all done in
> the LMS plugin. This will -hopefully- resolve these issues.
>
> If you leave your files as is, then when I make the next release
cpd73 wrote:
> I'm 99% sure this is the reason. Can use use an SQLite UI (e.g.
> SQLiteBrowser) to look for that track in LMS's library.db file. Should
> be in the 'tracks' table. When you find it, can you post the URL entry
> for this here.
These are the two URLs in question for the above
cpd73 wrote:
> Yeah, as stated before I'm writing a new analyser and mixer for Bliss in
> Rust. The code is done, I just need to test some more. I also, thanks to
> some ideas I borrowed from Spotty, have it compiling for Linux, macOS,
> and Windows. I'm creating a new LMS plugin that starts
FYI, I'm still seeing this issue too... sometimes with the
duplicated/mismatched album covers as per the post in the Music
Similarity thread, but more often now with the flickering in the now
playing queue between the track name/album art that is playing and (I
believe) the next item in the
I've upgraded the plugin to 0.4 and refreshed the files from the master
of the MusicSimilarity backend.
Now every time I try to start the service I get this:
Code:
Traceback (most recent call last):
File "M:\My
cpd73 wrote:
> Update music-similarity - I've wrapped these checks in try/except
> blocks, so if a check fails it returns False
That's got me up and running again, thanks. :D
Just one thing to comment, I don't know if there have been any
significant changes in similarity selection, but I seem
cpd73 wrote:
> Well, you are using only Musly for similarity, and nothing has changed
> on that front. Musly *only* analyses a portion of the file - by default
> the middle 2 minutes (starting no later than 3m30 seconds) of a track.
> The mixer gets a certain amount of similar tracks per seed,
cpd73 wrote:
> Thinking about this some more. Would it make sense to allow creation of
> 'Smart Mixes' that will select a number of tracks, allow this to be
> added to the queue, and then DSTM takes over adding new tracks. DSTM,
> however, would not know about the SmartMix, just that these
prabbit wrote:
> Out of curiosity, what are values for your settings?
I did play with them initially, then think I put them back to the
defaults... I have:
Code:
Don't repeat artist for x tracks: 15
Don't repeat album for x tracks: 25
Don't repeat track for x
cpd73 wrote:
> Can you manually run essentia against these? e.g.
> Does that produce any errors? If not then its Musly which is failing -
> but I'm not sure there is much I can do. Perhaps what I need to do is
> use the windows 'short' filename - e.g. its DOS equivalent.
>
No errors:
cpd73 wrote:
> Glad to hear is working for someone else. Perhaps I'll formalize the
> release...
That'd be great.
Whilst I can't spend all day listening to music, I'm very impressed with
the mixes I'm getting...
I did say I would try utilising the Genre groups, but I'm not thinking
that's
I'm no expert, but I had problems at first with the database missing all
the metadata... i.e. if I looked at the music-similarity.db file most of
the fields were null - hence the line below leads me to suspect it could
be a similar issue that you have:
Code:
cpd73 wrote:
> Initial, semi-tested, version in master of lms-musicsimilarity:
>
> Requires 2.9 branch of Material for user interface. Not sure if I really
> like the range sliders - I'm thinking 'Danceable' / 'Ignore' / 'Not
> danceable' might be simpler to use. with 'Danceable' being 70..100
Of course I rather foolishly forgot that having analysed these with
Essentia in Windows I'm lacking the high-level analysis that'll make
this work anyway!
Hence, *"sqlite3.OperationalError: no such column: danceable"* when
starting the music-similarity up! :rolleyes:
cpd73 wrote:
> No, the code will normalize. The default is 100% as its there to reflect
> the current/previous state.
This is interesting, but since the upgrade I feel sure I'm getting
smoother mixes than I recall previously... Which is why I stopped by
here to see if there was any other
76 matches
Mail list logo
