Still it is not yours.

 

Mani.

Stanley, believe me. For me it happens just the same. I recall with this very situation that I have up because there was 10 minutes of "play time" left anyway, and rebooting the PC as a kind of solution was of no further use. I left that to the next day. Then, with more calmth and less annoyance I could recall what I all did the previous day ... an I set all back. Only later I learned that 80.19 does work. I suppose all above that works too. 60 and lower I think all works. 70 coincidentally does not.
Believe me, you are not "special" regarding this.

Broken NOS1 count is still at zero. Haha.
(apart from two or three I think who blew the USB interface by means of doing something which should not have been done)

Enjoy the weekend !
Peter

    

Thank you Peter and Arvind,

Now things are starting to become a lot more clear. I have been fiddling with the SFS settings (of course), but forgot about it because of other things happening around me at the same time. A mental overload followed by amnesia.

I went back from SFS=140.19 to my old settings SFS=20.19 and SFS=60.19, but, indeed, with the high xQ setting.

Changing to SFS=80.19 now shows normal behavior. With both Lushes  , the green LED blinks and the DC-offset shows the target values after following the procedure.

Now the weekend can commence.

Thanks again.

Regards Stanley 

It may come across as strange to you, but the solution should really be to find a better setting of the Blaxius^2.

And I myself should not forget that I am using the 10/20 processor, which really produces a different sound than your 14/28 (which latter - as you know - again produces an other sound when set to be a 10/20).

Since a few days I have another spare 14/28 again, so I could try it and spoil myself with it again ...

Thank you Arvind, I indeed eperienced the same.
Btw, I ended up with 80.19, leaving all else the same.

The cause indeed is the actually way large implied buffer by Q1 x xQ1. This is actually illegal. You will notice when you, for fun, switch on the Running Time. A message will tell you that the time can't be updated each second, already when Q1 is 30 and xQ1 is larger than 3. If you continue you will see that the Time is not properly updated at all (this is solved for the next version).
This stuff is aldo the cause of tracks ending abrubtly (per album).

In the very end these are all anomalies of the strange combination we apply lately (like last 6 months or so) and which strangely never was tried before in all these years. Slowly we start to "find out" the real anomalies under the hood. But working on them (or some) ...

Peter

Hi Gerard,

Recall someone else had the exact same problem; ChangeWP.exe was simply not "extracted" from the .rar (because of virus detect again ?)

This XXHighEnd version is adjusted such that it won't be seen as having a virus. Notice though that this is XXHighEnd.exe only and that this thus replaces the XXHighEnd.exe which will currently let trip your virus scanner.

Regards,
Peter

Hi Stanley,

It has been my experience, if your SFS is high, like 60.19 (as per your signature), you need to bring down xQ otherwise you get the problem of data not arriving in time.

Maybe you could try this out.

Best regards,

Arvind

This is the most suspicious of all because this is just software (setting). Not that it is intuitive, but it is. And I bet you that this is since people are telling (you) a different SFS than 140.19. For example, 70.19 gives exactly your problem, while 80.19 works. And someone (Robert) suggested the 70.19 ...


If possible this is even more suspicious because it tells (to me) that you did not check the DC Offset, which, mind you, is quite consistently at the "1/-1" position after switching off/on the G3 version of the NOS1a (or reboot the PC or replug the cable). So earlier on you told about this all right, but this time you omitted the checking for this ? And switch off/on a next time and it is fine (also quite consistently).

Nothing is broken (I think) but you broke in to a relatively long time of "it works at this setting" and now suddenly all is "unknown" at changing something.
I had the same this week, up to rebooting by Audio PC which did not help ...



I can't guarantee it, but ...
Let me know how you fare.
Peter

No, there were no changes in the house or the room.


I think it worked  after switching the NOS1 OFF and ON again (see below).

Today I repeated the tests with the (old) Lush and the Lush^2 connected to USB 2.0 and USB 3.0 PC ports. The USB 2.0 and 3.0 ports showed the same results:

1. Lush in i: driver shows, but “playback stopped because the data did not arrive in time”.
Then switched OFF and ON the NOS1 and music plays, but very distant.
Then switched OFF and ON the NOS1 again and music plays OK.
2. Lush in U: driver shows,“playback stopped because the data did not arrive in time”.
Then switched OFF and ON the NOS1 and music plays, but very distant.
Then switched OFF and ON the NOS1 again and music plays OK.

So with Lush all works, but not stable and rebooting the Audio PC gives the same "uncertain" results and asks for turning the NOS1 OFF and ON until it's stable and the music plays.

3. Lush^2 in i: no driver shows.
2. Lush^2 in U: driver shows, but again changing situations: “playback stopped because the data did not arrive in time”.
Then switched OFF and ON the NOS1 and music plays, but very distant.
Then switched OFF and ON the NOS1 again and music plays OK.

With Lush^2 i doesn't work at all and U only after turning NOS1 OFF and ON until it starts working.

 

 

Regards,
Stanley