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
*wow*
WW !!!
This is working incredibly well, this is such efficient !!! :D
I've plaid a couple of hours with sliders in parallel of making review
of tracks played in bliss.db using DB.browser
the weighting algorithm do exactly what is it for and work pretty well,
no mistake !!
Here are
cpd73 wrote:
> Just tried making the github action use Stretch, and it failed. Sorry,
> but I'll leave on Bullseye.
This is not blocking for me, don't worry for that ^^ thx
chourmovs's Profile:
slartibartfast wrote:
> Do the sliders always need to total 100% or is the default just
> coincidence?
No, the code will normalize. The default is 100% as its there to reflect
the current/previous state.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http:
Do the sliders always need to total 100% or is the default just
coincidence?
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread:
cpd73 wrote:
> Just uploaded 0.3.1 with bliss-mixer rebuilt on Debiab Stretch. This
> -should- be the same as before.
0.3.1 fix bliss mixer on debian buster ;)
Let's begin to play with sliders
Thank you for all, I will report experience
Actually the analyser didn't work as is before for the same reason, I
had to build it within my debian using cargo. It didn't change with new
release i had to build also
chourmovs's Profile:
chourmovs wrote:
> sorry, no I've messed with vbulletin on my phone trying to edit my
> previous post, it's buggy.
> I still have bliss-mixer 0.1.0 not working on debian buster over ARMf71
> due to glibc...
Just uploaded 0.3.1 with bliss-mixer rebuilt on Debiab Stretch. This
-should- be the
Still present
39511
39512
My proposition was : I try to rust build on debian buster... or you can
easily fix what look like regression for me coming from previous release
You tell me
Thx
+---+
|Filename:
sorry, no I've messed with vbulletin on my phone trying to edit my
previous post, it's buggy.
I still have bliss-mixer 0.1.0 not working on debian buster over ARMf71
due to glibc...
chourmovs's Profile:
chourmovs wrote:
> ARM link seems broken
You posted a message stating the mixer did not run, due to glibc. But
this message has been deleted? Does the mixer now work?
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http:
The update broke the plugin here, I think I found why
Platform : ARMv71
39501
if i launch bliss-mixer via ssh on the headless machine, I get
39502
this is a bliss-mixer 0.1.0 regression for my config
Do I need to "cargo build it" and provide it to you or could you check
what has changed in
chourmovs wrote:
> ARM link seems broken
Oops! Should be fixed now.
*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
cpd73 wrote:
> Analyser 0.2.2 and Mixer 0.3.0
> Analyser binaries (initial post updated):
>
> > > >
- 'Linux (ARM, 32-bit and 64-bit )'
>
(https://github.com/CDrummond/bliss-analyser/releases/download/0.2.2/bliss-analyser-arm-0.2.2.zip)
> > >
>
ARM link seems broken
slartibartfast wrote:
> Will this mean analysing the whole library from scratch?
No, the analysis data has not changed.
*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)
cpd73 wrote:
> Analyser 0.2.2 and Mixer 0.3.0
Thank you for this quick effort, Santa can always try to do better :)
chourmovs's Profile: http://forums.slimdevices.com/member.php?userid=72073
View this thread:
cpd73 wrote:
> Analyser 0.2.2 and Mixer 0.3.0
>
> Plugin changes (0.3.0):
>
> > >
- Allow genres in genre groups to use wildcard, and other regular
> expressions.
- Allow supplying weights for bliss metrics.
> > >
>
> Analyser changes (0.2.2):
>
> > >
- Update version of
Analyser 0.2.2 and Mixer 0.3.0
Plugin changes (0.3.0):
- Allow genres in genre groups to use wildcard, and other regular
expressions.
- Allow supplying weights for bliss metrics.
Analyser changes (0.2.2):
- Update version of tag reader library.
- Update version of bliss
Idiots don’t know whom you are sending emails?
Thanks
Sridhar
Sent from my iPhone
> On Dec 19, 2022, at 1:22 PM, chourmovs
> wrote:
>
>
> cpd73 wrote:
>> I've implemented this in git - but I'm not 100% sure. Bliss has 20
>> Metrics (1 for Tempo, 7 for Timbre, 2 for Loudness, and 10 for
Idiots
Thanks
Sridhar
Sent from my iPhone
> On Dec 19, 2022, at 1:22 PM, chourmovs
> wrote:
>
>
> cpd73 wrote:
>> I've implemented this in git - but I'm not 100% sure. Bliss has 20
>> Metrics (1 for Tempo, 7 for Timbre, 2 for Loudness, and 10 for Chroma) -
>> and currently the mixer
cpd73 wrote:
> I've implemented this in git - but I'm not 100% sure. Bliss has 20
> Metrics (1 for Tempo, 7 for Timbre, 2 for Loudness, and 10 for Chroma) -
> and currently the mixer config has sliders for all 20. But, this seems a
> bit overkill to me.
That's funny, by analyzing the database
chourmovs wrote:
> Hi Craig
> I've made an enhancement proposition
> https://github.com/CDrummond/bliss-analyser/issues/6
>
> Hope you'll find a way
I've implemented this in git - but I'm not 100% sure. Bliss has 20
Metrics (1 for Tempo, 7 for Timbre, 2 for Loudness, and 10 for Chroma) -
and
chourmovs wrote:
> Hi Craig
> I've made an enhancement proposition
> https://github.com/CDrummond/bliss-analyser/issues/6
>
> Hope you'll find a way
There's no need (but no harm) to post here - as I get emails when issues
are created, or updated. Anyhow, I had considered this previously -
Hi Craig
I've made an enhancement proposition
https://github.com/CDrummond/bliss-analyser/issues/6
Hope you'll find a way
chourmovs's Profile: http://forums.slimdevices.com/member.php?userid=72073
View this thread:
cpd73 wrote:
> As stated, Bliss only stores the path -within- the music folder. So if
> you analysed c:\Some\Path\Artist\Album\Track.mp3 and set c:\Some\Path\
> as Bliss analyser's music path, then only Artist/Album/Track.mp3 is
> stored in the DB. When the mixer is run, it removes all LMS
bakker_be wrote:
> Thanks, I think a path issue is indeed what's happening.
> Daphile is configured out of the box to use /srv/mediaserver/music/ as
> the LMS music path. Any disk you add is automatically mounted under that
> path, in its own folder (which makes adding more discs containing
cpd73 wrote:
> Don't think you would needed to have run a re-analysis, bliss only
> stores relative paths. e.g. If you have
> "c:\MyMusic\LMS\Artist\Album\Track.mp3" and bliss-analyser is configured
> to find music in "C:\MyMusic\LMS" then it will only store
> "Artist/Album/Track.mp3" in the DB.
bakker_be wrote:
> Hi, with the current energy prices being what they are I've shut down my
> original server (Lenovo Dual Xenon P700 workstation) as it was solely
> responsible for around 30% of my total electricity consumption :eek:
> I've moved my home automation (Home Assistant) to a Pi 3 I
Hi, with the current energy prices being what they are I've shut down my
original server (Lenovo Dual Xenon P700 workstation) as it was solely
responsible for around 30% of my total electricity consumption :eek:
I've moved my home automation (Home Assistant) to a Pi 3 I had laying
around, and
chourmovs wrote:
>
> Please help
Forget, problem was a discrepancy between plugin.ini folder and LMS
music folder that was not at the same level
chourmovs's Profile:
Hi
Could someone confirm that DSTM+bliss is still working on LMS 8.3.0
On my instance it find the database but don't queue similar song :(
It used to work on 8.2.0
Thank you by advance, I will post debug later
cpd73 wrote:
> Must amdit I do my analysis on a laptop, and only use the Pi4 for
> mixing, etc. Which OS and version are you using?
Debian GNU/LINUX 10 (buster)
dbinder101's Profile:
dbinder101 wrote:
> I just discovered this thread and wanted to try bliss on my Raspberry
> Pi 4. I received the following error when I tried running analyze:
>
> pi@raspberrypi:/tmp/bliss-analyser-linux-arm-0.2.1 $ ./bliss-analyser
> analyze
>
>
I just discovered this thread and wanted to try bliss on my Raspberry
Pi 4. I received the following error when I tried running analyze:
pi@raspberrypi:/tmp/bliss-analyser-linux-arm-0.2.1 $ ./bliss-analyser
analyze
/tmp/bliss-analyser-linux-arm-0.2.1/bin/bliss-analyser-aarch64:
goharbourview123 wrote:
>
> So the directory rename seems to have done the trick. Thanks so much for
> helping out, looking forward to playing around with this!
Thanks for the confirmation, I'll make a release with the correct
directory name later.
*Material debug:* 1. Launch via http:
cpd73 wrote:
> You need to be within the directory to run "./bliss-mixer"
>
> ... the following -should- exist:
>
> > >
-
>
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/BlissMixer/Bin/armhf-linux/bliss-mixer
-
>
goharbourview123 wrote:
> In both cases, I get the response "-bash: bliss-mixer: command not
> found", or "-bash: ./bliss-mixer: No such file or directory" when I use
> the dot-slash prefix. Also tried with sudo just in case, but that just
> reports "sudo: unable to execute ./bliss-mixer: No
Thanks for getting back to me so quickly, really appreciate it.
cpd73 wrote:
> In "/Cache/InstalledPlugins/Plugins/BlissMixer/Bin" there
> will be "armhf-linux" and "arm-linux" - does the "bliss-mixer" in ether
> of these run from the commandline? Try "./bliss-mixer --help" in each
> folder.
goharbourview123 wrote:
> Should I expect this to work on an RPi4 with 64-bit Bullseye?
Hmmm My Pi4 is still on 32-bit, so have not tested. In "/Cache/InstalledPlugins/Plugins/BlissMixer/Bin" there will be
"armhf-linux" and "arm-linux" - does the "bliss-mixer" in ether of these
run from the
Should I expect this to work on an RPi4 with 64-bit Bullseye?
I don't see an aarch64 binary in the plugin's Bin directory, and I get
the following errors in the LMS log when I try to start a Bliss mix:
Code:
[22-04-10 15:21:05.2449]
cpd73 wrote:
> By default the analyser tries to write bliss.db in the current folder,
> perhaps you do not have write permission for c:\ ??? Try setting
> "db=c:\Bliss\bliss.db" (or whaterver path you want). This is all
> mentioned in the README.md
It worked perfectly (as in found the correct
cpd73 wrote:
> By default the analyser tries to write bliss.db in the current folder,
> perhaps you do not have write permission for c:\ ??? Try setting
> "db=c:\Bliss\bliss.db" (or whaterver path you want). This is all
> mentioned in the README.md
Yes, sorry for being dim, this was somewhat
plasticator2 wrote:
> Thanks for response
>
> Ran that in a command prompt and it returned:
>
> C:\>c:\Bliss\bliss-analyser.exe analyse
> thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:
> SqliteFailure(Error { code: CannotOpen, extended_code: 14 },
> Some("unable to
cpd73 wrote:
> Are you running from a console/power-shell window? There should be some
> output. Are yo using the following: "c:\Bliss\bliss-analyser.exe
> analyse"
Thanks for response
Ran that in a command prompt and it returned:
C:\>c:\Bliss\bliss-analyser.exe analyse
thread 'main'
plasticator2 wrote:
> Hi Craig,
>
> I have been following this thread with interest and keen to give the
> bliss mixer a try, but seem to have fallen at the first hurdle - I
> cannot get the analyser to run.
> I have downloaded version 0.1.0 and it is sitting in C:\Bliss on my Win
> 11
cpd73 wrote:
> Plugin changes:
>
> > >
- Add support for CUE tracks.
- Get LMS IP from 'Slim::Utils::Network::serverAddr()'
> > >
>
> Analyser changes:
>
> > >
- Add support for analysing CUE files.
- Output list of (up to 100) tracks that failed to analyse.
- When
cpd73 wrote:
> Just to let you know, the 'tag reader library'
> (https://github.com/Serial-ATA/lofty-rs) I'm using now supports (or will
> in its next release) ID3v2 in FLAC:
> https://github.com/Serial-ATA/lofty-rs/commit/c6d1ef505d0f2a86ca4d19b308c476b02fd5916c
>
> When a newer version of
slartibartfast wrote:
> I've PMed a couple of tracks.
Just to let you know, the 'tag reader library'
(https://github.com/Serial-ATA/lofty-rs) I'm using now supports (or will
in its next release) ID3v2 in FLAC:
staresy wrote:
> Ah yes, that's it, I had two bliss directories (0.0.1 and 0.1.0) and had
> used cd bl*.* from cmd which put me in the wrong one, thanks.
>
> The offending tracks were on the album "Who Is Jill Scott", 5 tracks
> (space 1 -5) used to "hide" a final bonus track.
I had failure
When I try to upload the bliss.db I get the follow error:
C:\bliss-analyser-windows-0.1.0>bliss-analyser.exe upload
[2022-03-17 14:25:33 I] Requesting LMS plugin to allow uploads
[2022-03-17 14:25:34 I] Uploading bliss.db
[2022-03-17 14:25:34 I] Length: 5218304
[2022-03-17 14:25:55 E] Failed to
slartibartfast wrote:
> Any idea why a non silent but low volume track would fail? Is a minimum
> amplitude required?
No, sorry. I did not write the analysis code, see
https://github.com/Polochon-street/bliss-rs for that.
*Material debug:* 1. Launch via http:
Any idea why a non silent but low volume track would fail? Is a minimum
amplitude required?
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this
cpd73 wrote:
> You need to be using the latest version - 0.1.0, you have the first
> released version 0.0.1
Ah yes, that's it, I had two bliss directories (0.0.1 and 0.1.0) and had
used cd bl*.* from cmd which put me in the wrong one, thanks.
location 1: lms 8.3 on win 10 brix server, x3 sb
staresy wrote:
> OK, so if I wanted to see what caused the failures, how do I do that?
You need to be using the latest version - 0.1.0, you have the first
released version 0.0.1
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http:
cpd73 wrote:
> There is no log file. "-l error" just sets the logging -level- to error
> - as in only log lines that are error, or above, are shown.
OK, so if I wanted to see what caused the failures, how do I do that?
37507
staresy wrote:
> When I run the bliss analysis I get 5 failed tracks, I have set the
> logging to:
>
> bliss-analyser analyse -l error
>
> But I can't seem to find where the log file is stored to see what caused
> the failures?
There is no log file. "-l error" just sets the logging -level-
staresy wrote:
> When I run the bliss analysis I get 5 failed tracks, I have set the
> logging to:
>
> bliss-analyser analyse -l error
>
> But I can't seem to find where the log file is stored to see what caused
> the failures?Just running
bliss-analyser analyse
lists the failed tracks in
When I run the bliss analysis I get 5 failed tracks, I have set the
logging to:
bliss-analyser analyse -l error
But I can't seem to find where the log file is stored to see what caused
the failures?
location 1: lms 8.3 on win 10 brix server, x3 sb radios, x1 touch, x1
controller : location
gorman wrote:
> Ok, before updating... is it possible to use ignore.txt to tell both
> plugin and analyzer to ignore .CUE files? They are in my rips folders
> but I do not want to have them analysed, being afraid that it would lead
> to each track appearing twice (or worse: being included and
cpd73 wrote:
> Plugin changes:
>
> > >
- Add support for CUE tracks.
> > >
>
> Analyser changes:
>
> > >
- Add support for analysing CUE files.
> > >
>
Ok, before updating... is it possible to use ignore.txt to tell both
plugin and analyzer to ignore .CUE files? They are
Apart from the silent track the other failure in my library was actually
a 30 second track with peak amplitude 0.088567, the other track with
amplitude 0.18589 is analysed successfully.
Sent from my Pixel 3a using Tapatalk
mruddo wrote:
> Silence - on Rilo Kiley's, The Execution of All Things. :D
>
> I have Tin Planet - but don't appear to have any 4 second tracks on
> there. I do also have a rather sad habit of removing long silent pauses
> ahead of hidden tracks when burning CDs - because I hate it when a mix
cpd73 wrote:
> Plugin changes:
>
> > >
- Add support for CUE tracks.
> > >
>
> Analyser changes:
>
> > >
- Add support for analysing CUE files.
> > >
>
Great stuff - thank you!
I've traced my problem tracks too - it was a couple of multi-track flacs
of radio recordings,
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
mruddo wrote:
> 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.Snap. What was the track? Mine was on Tin
cpd73 wrote:
> Plugin changes:
>
> > >
- Add support for CUE tracks.
- Get LMS IP from 'Slim::Utils::Network::serverAddr()'
> > >
>
> Analyser changes:
>
> > >
- Add support for analysing CUE files.
- Output list of (up to 100) tracks that failed to analyse.
- When
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.
Plugin changes:
- Add support for CUE tracks.
- Get LMS IP from 'Slim::Utils::Network::serverAddr()'
Analyser changes:
- Add support for analysing CUE files.
- Output list of (up to 100) tracks that failed to analyse.
- When performing a dry-run analysis (--dry-run) print paths
cpd73 wrote:
> The analysis code is the same - as this is from a library. But
> bliss-analyse (no r) is intended to analyse one file (as passed on the
> commandline) and outputs the results to stdout - where the Python reads
> results from. bliss-analyser iterates the music file tree, checks if
bakker_be wrote:
> Is the bliss-analyser used in this plugin different from the one in the
> music-similarity plugin? While scanning with this one access to file
> shares on the machine where it runs are virtually impossible. I didn't
> have this with the other scanner, running on the same
Is the bliss-analyser used in this plugin different from the one in the
music-similarity plugin? While scanning with this one access to file
shares on the machine where it runs are virtually impossible. I didn't
have this with the other scanner, running on the same machine.
Main System:
On second thought, can brew be used to build M1 binaries? Could I create
another 'macOS_arm' job in my action file to build an arm only macOS
build? If so, I guess "brew install" would need to be changed to install
arm binaries?
I don't know, tbh. Maybe prefixing the commands with "arch
mherger wrote:
> > Yes, but I have no idea what this is. My initial thought was perhaps
> > brew needs to be told to install deps for arm as well as x86 - but as
> I
> > don't own a mac, let alone an M1, I have no experience of this.
>
> It seems Homebrew decided NOT to support fat binaries:
>
mherger wrote:
> > Yes, but I have no idea what this is. My initial thought was perhaps
> > brew needs to be told to install deps for arm as well as x86 - but as
> I
> > don't own a mac, let alone an M1, I have no experience of this.
>
> It seems Homebrew decided NOT to support fat binaries:
>
Yes, but I have no idea what this is. My initial thought was perhaps
brew needs to be told to install deps for arm as well as x86 - but as I
don't own a mac, let alone an M1, I have no experience of this.
It seems Homebrew decided NOT to support fat binaries:
cpd73 wrote:
> Yes, but I have no idea what this is. My initial thought was perhaps
> brew needs to be told to install deps for arm as well as x86 - but as I
> don't own a mac, let alone an M1, I have no experience of this.
Ah, ok - understood. In that case I'm especially grateful that you
Not sure if "brew install ffmpeg@5" also installs for arm? The github
action file is:
https://raw.githubusercontent.com/CDrummond/bliss-analyser/master/.github/workflows/build.yml
That's very similar to what I'm doing with Spotty in
chill wrote:
> Thanks for trying! The Intel build seems to run plenty fast enough
> anyway (under the right CPU allocation conditions!), so it's not an
> issue for me.
>
> Just curious though - did you see the "Try use `bindgen` feature"
> message in relation to the error?
Yes, but I have no
cpd73 wrote:
> I don't compile the binaries myself but use github actions. I've just
> tried updating this action to build a fat-binary for macOS (which is
> what i build for the mixer) - but this has failed:
>
Thanks for trying! The Intel build seems to run plenty fast enough
anyway (under
chill wrote:
>
> PS. Do you have the facility to compile for Apple silicon? I noted in
> Activity Monitor that bliss-analyser is an Intel app, which means it's
> running under Rosetta on the M1 Macbook. I could imagine it would fly
> if it ran as a native Apple app.
I don't compile the
cpd73 wrote:
> No. The code builds 1 list of all tracks to be analysed - the .notmusic
> prevents files within those folders from being added to this list. This
> is then split between cores.
Understood. There does seem to be something inconsistent about the CPU
allocation though. I've now
chill wrote:
> The scan completed after 1hr43m, with no errors. While it was running
> it was using about 2.5% CPU and 12 threads.
>
> I've just restarted it with the path set specifically to that 'Lossy'
> folder, and it's started up with ~500% CPU and ~30 threads, so clearly
> it's going to
cpd73 wrote:
> Sorry, not really. The bliss-analyser code is pretty simple - just
> collecting a list of files then asking bliss-rs to analyse them.
The scan completed after 1hr43m, with no errors. While it was running
it was using about 2.5% CPU and 12 threads.
I've just restarted it with
chill wrote:
> Any idea why this scan is so much slower?
Sorry, not really. The bliss-analyser code is pretty simple - just
collecting a list of files then asking bliss-rs to analyse them.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http:
cpd73 wrote:
>
> As to why its crashing, not sure. Perhaps you could run analysis on each
> folder separately to see if its a particular file type.
I'll certainly try that. I'm currently re-running the analysis with
every folder except 'Lossy' excluded via the .notmusic method. The
analysis
chill wrote:
>
> I'm curious what could be causing inconsistent/different failures. Does
> the analyser pick a different/random section of each track each time?
The analyser code iterates the filesystem to build a list of files to
analyse. This list is not sorted. Then each CPU core is given
I've been giving this a try while I look forward to a version that
handles CUE files. I have around 6500 tracks that are in individual
MP3/OGG/M4A files, with traditional tags. I'm getting some inconsistent
issues with the analysis phase.
I have a separate 'Lossy' folder within my music
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
slartibartfast wrote:
> Mine always shows 2 failures. It would be interesting to know what they
> are [emoji2]
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.
cpd73 wrote:
> Unfortunately not - which, I agree, is bad. I'll add some logging to
> list of to (e.g.) 20 failed tracks. If you run with no new tracks, it
> should try to analyse the failed track again - and then this track path
> should be visible next to the progress bar.Mine always shows 2
mruddo wrote:
> 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.
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:
> As stated before, mixer does not read config.ini that's *only* for the
> analyser. Anyhow, I've updated the code to call
> 'Slim::Utils::Network::serverAddr()' to get the LMS IP address. This
> will be the same IP as shown in Material's information dialog.Ok, perfect.
> That
gorman wrote:
> Bear in mind there is still need for the bliss-mixer executable to get
> the addresses from config.ini (in my case, don't know how widespread my
> situation is... you could have a default at 127.0.0.1 that one can
> override in config.ini maybe?).
As stated before, mixer does
Ok, turns out it was easier than I thought. Luckily Trackstat saved only
the path in the actual folders, without the shortcut portion. So I
rearranged stuff as needed, rescanned library from scratch, restored
trackstat data and... Bliss mixer now appears to be working. Which leads
me to believe
cpd73 wrote:
> ..ah, wait. Are you saying you have (e.g.):
>
> - LMS music folder set to c:\User\name\Music
> - Within c:\User\name\Music you have windows shorcut files (e.g. 'FLAC
> Music.lnk' which links to 'D:\Music')
> - When you play a track from 'c:\User\name\Music\FLAC Music' LMS
>
gorman wrote:
> I think I know whats happening. My music folder is set to one with
> shortcuts (I use Windows 10) to the actual folders where I have
> organised the music. This is from when LMS allowed for just one folder
..ah, wait. Are you saying you have (e.g.):
- LMS music folder set to
gorman wrote:
> I think I know whats happening. My music folder is set to one with
> shortcuts (I use Windows 10) to the actual folders where I have
> organised the music. This is from when LMS allowed for just one folder
> (and anyway your plugin uses just the first folder in the list, so in a
cpd73 wrote:
>
> When sending the track list to the mixer, the plugin -should- strip your
> configured media folder path from the tracks path. e.g. if media folder
> was "D:\Music" then "FLAC/Tears..." would be sent (the plugin converts
> "" to "/" - so that you can, for example, analyse on
gorman wrote:
>
> Problem is that my LMS does not respond from 127.0.0.1 but only from
> 192.168.10.101 and I have that in the config.ini, like this
>
> lms=192.168.10.101
>
Mixer does not use config.ini, only the analyser. Mixer is designed to
be started/stopped by the plugin so has no
1 - 100 of 199 matches
Mail list logo
