This is from the Release Notes of 2.08 :

•There's official support now for Windows Server 2016 (and an OSIsW2016.tss coming along with it, to be renamed to OSIsW2016.tst in case WS2016 is not automatically detected - see Release Notes elsewhere).

I am almost sure that if you apply this now, thus act as if this is WS2016, this will work all the way, unless there's something special in WS2019 what I don't know yet.

Otherwise in 2.11 there will be the OSIsW2019.tss file for the same purpose.

Peter

Sadly No. My DAC can not be operated in 16 bits (and ditch the inherently present extra 8 bits). Maybe it could have made like that, but it just wasn't …


H*ll yes it does ! You are throwing out half of the buffer length. Think the other way around for your comfort : if 32/44.1 is played, the SFS buffer lasts twice as long vs 32/88.2. All is different now … (and now extend to 32/705.6).


That is indirectly what I meant in my previous post, but slightly differently approached … You can't upsample 16 bits material even to 2x without adding a bit. So you can't upsample at all. Oh (and again) you can try to tweak things, but again it will fail similarly.

Do notice that I could have made it so that 16/44.1 can be upsampled to 16/88.2, but you'd have a strange kind of distortion because of twice too "small" (finer) jumps in sampling rate vs not-at-all-possible jumps in bit depth. This must be/remain in balance. Maybe an other player can do it, maybe you like the different sound for the better, but it *is* not for the better. It would be illegal to do.

Best regards,
Peter

PS: Does WASAPI also doesn't work out for you, in this case ?

Hi Laurence,

First off, you surely can be right that something is amiss, because I have no way since long to check for genuine 16 bit output as I have no DAC for that. Otoh, I feel that you are not obeying "rules" or "laws" at the same time. So, not sure …


We can't just "require" to cross the boundaries of physics. I mean, yes, we might like that for perceived SQ reasons, but if something can't cope, it can't.
Ever back the lowest we could go was 1.00 and the fact that we now can do 0.06 or some times (not me) 0.05 is because special prerequisites were created, found in various other combined settings (don't ask).


Same thing - you can't pad bits on a 16 bit DAC beyond 16 bits. Maybe you can tweak the lot alright like telling the program the DAC is e.g. 18 bits, but then you are cheating or lying and nothing can work as intended.

So you see, you are a bit prone to pilot error.

Check the KS Mode setting; If that is set to Special, I'll bet you that's the cause. Set it to Adaptive instead. Note : Special uses a special KS buffer means; Not each DAC can handle that which actually is a deep down inherent OS bug (our own NOS1 can't either).

Notice that not only the SFS, but also the net result of Q1 are buffer(-length) settings and at knowing that, you may be able to detect which of them "doubles" the time a glitch etc. stays away by doubling the number of the setting (this works out almost linearly). A driver control panel for your DAC - if existent - may also influence buffer lengths.  The ClockRes may also influence slightly, but I would not blame that easily. Still it can imply "resonant" OS behavior, the OS choking at regular intervals (which can easily be at more than 30 seconds).

Q3,4,5 influences as well. The implied internal settings are eased when they are all set to 0.


Unlikely. At least I never heard of it.

Regards,
Peter

Thank you, Colin.
Peter

So Yes, Tidal changed something. It is solved for the next version.
For now, don't forget to add the * in the field for Artist Name. But obviously, mind the Result which now is "wildcarded". See second album in second picture below.

Peter

Hey Brian - Thanks.
Regards,
Peter

Thank you Colin, but …

This is from my phone. I can't imagine how I can get farther away from the server. So it works all right. Or at least at the best I can check it myself.

Can you go to a PC where you can easily refresh the Browser cache ? Like Windows and Ctrl-F5 ?

Thanks a lot,
Peter

Huh ?

Can you give me a link to a page with missing pictures please ?
There are several sources for pictures so maybe this is about something else now ?


Thanks !
Peter

Thank you very much, Stanley.
Peter

Thank you VERY much guys. I would have been searching for that needle in the haystack which just isn't there.
Quite a stupid Tidal change.

Peter

Hi Arvind,


But it is not meant to work like that. And for sure it didn't a while ago. So since when is this, do you think ?
If you would ask me, I would say "since 3 days".

Best regards,
Peter

 … Do you notice too that when you don't enter an * to the Artist Name for searching Artists, you don't get a result any more ?

I did not look yet what's happening in the code, but point is that as far as I know I did not change a thing. And suddenly since somewhere 2 days ago, nothing is found when not adding the *.

?

Peter

Something along those lines, yes.

Possibly people don't even inject cr*p into forums but they don't participate any more at all. Maybe all has been discussed by now.
Maybe take up model railroads

Regards,
Peter

Dear Dave,


Actually No, because it doesn't make sense.
a. the sound *will* be different because the topology will change;
b. the original config is already not used by me any more for 6 weeks or so.

ad b.:
The Lush^2 is still shipped with the original configuration because of lack of response of too many people (what about 100% from this very forum). So :


So I'm afraid you are right.

The best option could be that you get yourself the original Lush (I assume you don't have that ?) because at least that one has proven itself too. It is not better than the Lush^2 but that depends on the configuration (configs of the Lush^2 exist which are worse than the Lush^1).
The real advice is and remains to step over the high-wire thing (haha) and get the Lush^2. Now I already know you won't, so … 


Peter

And so I say … It should be solved now …

Peter