Hi Nick,

Thanks for your reaction, and I will try your suggestion and try another short cable.

I'll keep you informed.

Regards,

Stanley

I will check the DC-offset in the coming period.

Thanks Peter!

Hi Peter,

Once the connection is established, I can reboot as many times as I like and the connection remains. Only after a longer period (say several days) it becomes harder to make the connection.

Something to do with grounding, potential differences, static electricity?

For now I'm fine, if the problem persists I can always try another Lush^2.

Thank you!

Regards,
Stanley

No that did't help, BUT when I DISconnected all the wires at both ends, the connection was made.

And when I REconnected the wires, while leaving the cable attached at both sides, the connection remains.

However, for me this an awkward procedure to make the connection, because the B-connector at the NOS side is very hard to reach and see in my setup.

Regards,
Stanley

Hi Peter,

Yes, this is the procedure I followed many times and all cables I have will connect, but not my Lush^2. 

Stanley

Update: Lush ^1 also works perfectly, so it seems it's the problem is in Lush^2.

I now also recall Lush^2 didm't want to connect from the start and only after many attempts it did.

Regards,
Stanley

Hi Peter,

My audioPC has been switched off for a few days and today I wanted to activate the system.

However, when switching on the AudioPC it doesn’t see the NOS1. This is with the Lush^2. My settings were not changed (see signature).

Plugging the Lush^2 in "U" (omitting Phisolator) also makes no connection. The green LED stays dark.
When I replace the Lush^2 with a cheap USB cable, all works fine (green LED blinks), both in "i" and "U".

I had difficulties with the Lush^2 before, but after changing settings it worked in the end (see above).

But this time the Lush^2 fails to make connection, while the settings were not changed.

It looks like it's related to the Lush or it's settings (A:B-W-Y-R, B:B-W-R).

Can you make something of this?

Regards,
Stanley

    

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 

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

I rebooted the Audio PC and did the following tests:

1. €1 USB cable in i: driver shows, but “playback stopped because the data did not arrive in time”.
2. €1 USB cable in U: driver shows, but “playback stopped because the data did not arrive in time”.

3. Old Lush USB cable in i: Driver shows, Sound OK.
4. Old Lush USB cable in U: Driver shows, Sound OK.

5. Lush^2 USB cable in i: No driver.
6. Lush^2 USB cable in U: Driver shows, Sound OK.

Other USB ports on the PC make no difference.

 

Regards,
Stanley

Hi Peter,

This is what I found:

- Connecting the Lush^2 with the U USB input: no LED.
- Connecting another USB cable to the i USB input: no LED.
- Connecting another USB cable to the U USB input: solid green LED.

Does this make sense to you?

Regards,
Stanley

Hi Peter,

Tonight, I planned to continue my listening sessions and enjoy the glorious sound (especially since the Lush^2). Yesterday, after listening I just left the Audio PC and Musicserver PC as they were (I didn’t shut them off).

When trying to continue with the album I left yesterday, I got the message that the audio device could not be found.

The USB Audio Control Panel indicates that the driver is not available. Turning OFF the NOS1 and a few minutes later ON again doesn’t help. Also the DC-offset displays show “-1mV”, instead of the usual values. And I recall that there should be a LED visible in the left leg of the NOS1 and now it isn't.

Furthermore I now recall that during the past 2 weeks or so, when turning ON the AudioPC, the speakers produced a soft, distant and distorted sound, and only when shutting the NOS1 OFF and ON again, the normal sound returned.

What to make of this? Broken NOS1?

Regards,
Stanley

Very clear!

Thank you Peter.

I'm finally convinced I should be using Galleries and now have the time and peace of mind to create them  .

But where can I locate these best? On the spinning disk on the MusicServer PC (too slow?) or somewhere on the Base Boot of the RAM OS Disk on the and use them from memory?

Or or?

Thanks.

Stanley

It happens at different SFS settings and different Balanced Load settings and only with one album

Therefore I assume it's the music and I probably noticed it as off XXHE version 2.10.

So no big deal for now.

Thanks Peter.