mruddo wrote:
> >
Code:
> >
> [22-03-08 20:02:23.9265] Slim::Formats::Playlists::M3U::write (270) Error:
Couldn't retrieve objectForUrl:
[file:///M:/My%20Music/FLAC/Marina%20and%20the%20Diamonds/Froot/07-Can%E2%80%99t%20Pin%20Me%20Down.flac]
- skipping!
>
mruddo wrote:
>
>
> >
Code:
> >
> [22-03-08 22:50:10.7627] Slim::Formats::Playlists::M3U::write (270) Error:
Couldn't retrieve objectForUrl:
This is an LMS issue - as stated before.
Do we have an easily reproducible case? Hopefully I didn't miss that part...
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
Update, Spotty plugin is back and working. I re-deleted the Spotty.db,
removed it from the trash and restarted LMS. thanks for all your Help
mherger, it's appreciated. Gerardo.
bigG's Profile:
Hi Everybody, PicorePlayer Ver7 will not recognize the USB Dac I have
connected to it. I've tried all these output settings in Squeezelite,
but none of them make music, even though the file will be playing in
S.Lite. can you suggest something?THANKS.
I HAVE USED AND TRIED THE FOLLOWING
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
Ok, I deleted the Spotty.db file and restarted LMS which created a new
Spotty.db file with the same errors?
bigG's Profile: http://forums.slimdevices.com/member.php?userid=62156
View this thread:
mruddo wrote:
> Yes, I appreciate you've mentioned this before - it was more the
> observation that it appears to be triggered by the ampersand in a track
> title.
Were these tracks added by a DSTM mixer? MusicSimilarity, Bliss? If so,
any errors logged in LMS's log files? Do you see similar
mruddo wrote:
> Yes, I appreciate you've mentioned this before - it was more the
> observation that it appears to be triggered by the ampersand in a track
> title.
I don't doubt there is an issue - just I'm not convinced Material is to
blame.
*Material debug:* 1. Launch via http:
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.
mruddo wrote:
> 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
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
I'm still not sure what to do. Per Microsoft you should not delete the
(Programdata Folder).
Nobody told you to do so. I don't know why you would even consider this...
So are you saying to delete the Squeezebox Folder
and all the entries?
No.
in my
Hello,
I'm still not sure what to do. Per Microsoft you should not delete the
(Programdata Folder). So are you saying to delete the Squeezebox Folder
and all the entries? in my C:\ProgramData\Squeezebox\Cache\spotty.db
drive? the Squeezebox folder has (219 files and 197 folders) Cache
folder
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
mruddo wrote:
> Sorry I missed that in the earlier thread - that's fixed it... I'm
> getting 10 tracks now so I know it's using Bliss, and I can see the
> executable running... and *Create bliss mix* now works too.
>
> So now I'm really up and running ! ;)
>
> Thank you.I didn't realise
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
mruddo wrote:
> That's definitely the case here then...
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.
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
>
mruddo wrote:
> That's a good question... as to whether or not it's running! Silly
> question perhaps, but how do I tell if a plugin is running?
the plugin starts an executable named "bliss-mixer" - it was this you
needed to check if it was running. (via "ps -eaf" on Linux)
mruddo wrote:
>
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
gorman wrote:
> For the moment I will keep your version in use, so that in case the
> problem resurfaces I'll just need to activate debug on player.source to
> see what's going on.
>
> I wish to thank you for all the help, really.
Yes - logging will only happen if player.source is set to
bpa wrote:
> My socketwrapper 1.12beta2 which creates the log file
> \Windows\Temp\socketwrapperdebug.log is the *same as 1.11beta* - it
> does *not* have the latest change from sle118.
>
> edit2:
>
> I'm mixed up - my 1.12beta2 is based on the 2019 version of 1.12beta (it
> has a fix for
mruddo wrote:
> Selecting a track in the interface and requesting *Create bliss mix*
> does not seem to work for me either - although DSTM mixes do.
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
RCST wrote:
> Just did a quick update to support Tidal mix, but I can't test it now
> due to the reason mentioned above, can anyone test it of me?
>
> https://drive.google.com/file/d/1YTB8ICmxxybYsavn_-nm-VDJkh_Ede6M/view?usp=sharing
I tried it with tidal, on a fire tablet, shared "my daily
mherger wrote:
> >>
>
> I extended the regex to support URLs
> with and without the "browse" in the path.
Did you? I almost thought the direct https link doesn't work until I
found that the "browse" isn't included in the https link within the
Tidal shared text!
Just did a quick update to support Tidal mix, but I can't test it now
due to the reason mentioned above, can anyone test it of me?
https://drive.google.com/file/d/1YTB8ICmxxybYsavn_-nm-VDJkh_Ede6M/view?usp=sharing
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
Just use the https://tidal.com/browse/mix/abc123 link. I didn't
implement a custom URI schema for this.
Thanks Michael! Got a chance to test it today and it does work! And just
fyi, the custom URI "wimp://mix:[tidal id].tdl" also works.
Haha... why do people prove me wrong all the time, even
mherger wrote:
> > Michael, could you please let me know what's the url scheme for Tidal
> > "Mix"?
>
> Just use the https://tidal.com/browse/mix/abc123 link. I didn't
> implement a custom URI schema for this.
Thanks Michael! Got a chance to test it today and it does work! And just
fyi, the
bpa wrote:
> For completeness, I'll check out my version of 1.12beta and the latest
> github build.
My socketwrapper 1.12beta2 which creates the log file
\Windows\Temp\socketwrapperdebug.log is the *same as 1.11beta* - it
does *not* have the latest change from sle118.
The pre-roll announcement about the streams changing has gone away
(disappear early last week I think).
I assume that they have hit a technical problem that is delaying the
switch rather than it being a decision to leave things as they are ...
because they have not removed/edited the
gorman wrote:
> I honestly don't know what to say. What could explain this? I am sorry,
> I feel bad for wasting your time, bpa. You saw the logs, I wasn't
> imagining things :-(
You do/did have a problem. This was not imagination.
When audio source is a file or an encoding in an audio
33 matches
Mail list logo