I've just installed the latest version of this, logged into my account,
put the API key in, all seemed to work, except when I try to play
anything it reports:
Error:Can't connect to server for "Track Name"
I've not used this for years, is there something more I need to do?
location 1: lms
Or maybe I'm losing my mind I tested it two more times today, now
with logging enabled, and both times DSTM successfully added tracks just
like it's supposed to (and how it has been working on other players).
I'll keep an eye on it, but right now things seem fine.
Seanf wrote:
> Yes, you are right. I don't visit here very often and wasn't sure if it
> is a Tidal or Material issue. I find the huge amount of sections
> overwhelming!
>
> Thanks, I'll repost.
>
> Sean
Don't bother. I managed to recreate this issue in Material by browsing
"Band's Campout"
philippe_44 wrote:
> It's strange b/c I dont think CryptX is used anywhere by LMS. I've never
> hit that issue, so I'm not sure what I can do about it.
Ok, nevermind. I ended up installing LMS in a virtual machine running
linux. Everything works.
Thanks a lot for your help and such a great
mherger wrote:
> > I've now discovered something: in the interface settings, if I select
> > 'show artwork', it displays correctly. If I turn this option off, I
> get
> > the weird 'F's and '%'s.
>
> I think you should either post to a Material skin related thread, or
> start a new one with a
I've now discovered something: in the interface settings, if I select
'show artwork', it displays correctly. If I turn this option off, I get
the weird 'F's and '%'s.
I think you should either post to a Material skin related thread, or
start a new one with a meaningful title.
I've now discovered something: in the interface settings, if I select
'show artwork', it displays correctly. If I turn this option off, I get
the weird 'F's and '%'s.
This never used to happen, I could switch between the two without any
problems.
This only happens when viewing lists on Tidal when using the Material
skin using Chrome or Firefox. It displays correctly on Edge.
It only started a while ago and I thought it was just a blip that would
go away, but it's been a long time now. Any ideas what is causing this
and how to fix it?:
