XX 2.10

[Tore]

Hi Peter!

Sometimes when playing in unattended volume is living it`s own life.
When next track starts volume gets many steps back.
To get back to the selected volume i have to go one step back and then one step up. If i only go one step up volume is getting one step loader than the selected volume


Tore

[PeterSt]

Hey there Tore,

Yes, some times this happens - I know. I few versions back I even described it in the releas notes as something which is hard to solve. This is since the "fast volume change" was introduced, thus already quite a while back by now.

It depends on "something" you/we did before maybe even related to the fresh restarting of the sound engine (XXEngine3), like after a reboot.

It may also be related to how "decently" you select the current track. I mean, you can see that when more than one (Volume Normalized) album is in the Playlist Area and Volume Normalization is On, some times you see the Volume (left hand pane) change when you again click the track which was already selected. I think that situation would have gone wrong like you describe, when you had not clicked that track again. It (kind of ?) would have used the Volume you see (at virtual first), while once it plays and you change the Volume, it related to that internal setting you can't see and then it jumps relative to that internal setting.

I always have the feeling that this can happen once per day only, and then in the first album I play ...



Regards,
Peter

[Tore]

Peter, thanks for answering

I bigger problem is a notch i can hear at least one time pr album. It has been like this for a long time.
You have told me that it has to be the USB-connection or the Phisolator.
It is not posible to do more with the USB-connection so i think the problem is the Phisolator

Tore

[PeterSt]

I bigger problem is a notch i can hear at least one time pr album. It has been like this for a long time.
You have told me that it has to be the USB-connection or the Phisolator.

Tore, do you play Hires material ?

Regards,
Peter

[Tore]

I play MQA from Tidal


Tore

[PeterSt]

So Tore, that is the same as Hires, technically.
That "notch" you hear is the switching to the 48 based (like 96, 192) sampling rate. It is "normal". Notice that it depends a little per XXHighEnd version because I always try to solve it.
I have it - everybody has it. But notice that it only appears when you play 48 based material. It is about the switching off of the one oscillator while the other comes on. In the end this started with the NOS1a.

Kind regards,
Peter

[Tore]

OK, god to hear

But it happens in the middle of tracks ?


Tore

[PeterSt]

Tore,

That can happen when the MQA album is not MQA for all its tracks. And this really happens relatively often. And with a mixed playlist of course.
If that is so, you should be able to see it on the Wallpaper Coverart (the bytes/s number in the top (middle).

Best regards,
Peter

[Tore]

But why in the middle of a track?


Tore

[Tore]

I think "notch" is a wrong word for this

It is a crack/collaps for one second


Tore

[Tore]

Hi,
Is it only me having this problem ?
Well, i have found the problem. It is the phsolator, no problem when it is bypassed.

Tore

[Tore]

8 month ago i wrote that the crack/collaps was atleast one time on a album, but it is many times on a album. But it never happens when i bypas the phsolator, Peter 

[PeterSt]

Hi Tore,

But why in the middle of a track?

When I read back on this, I now see that I interpreted this as "in between tracks". My bad. But does not matter much …

What does matter is that I can't keep track of your reporting about this. For example, look at your email from February 9, 2018. This refers to your G3 and how you had it there, but also how it was solved. So you announced the problem x times, but also solved it x times some times explicitly, some times by not responding any more.
Yes, it will be related to the Phisolator (I did not try to find the emails about that), but notice that you now came up with the problem after you connected your Mach II. So … I am afraid it is just too difficult for your situation to a. observe the issue and b. solve it.

Ad a.
If I would run into the issue because of a new PC, I would be sure that it is about how I connect (ground) things. This is easy for me because I know more or less how it works. If you run into the issue at connecting a new PC, the new PC is causing it.

So … too difficult to track for me, by now.

Either
1. Solve it by means of different grounding, combined with different NOS1 Driver buffer size (like 2, 4, 8, 12 or 16ms)
or
2. Bypass the Phisolator.

Notice that the scratches you hear come from the build up of "capacitance" (think like charging a battery) and when it is charged, it discharges and with that causes electrical disturbance. Depending on the situation this can be super regular (like once per 12 seconds, or 10 times in a row per 70 seconds (just making up things !)). But the cause is and remains the grounding somewhere. Or different apparatus (lights / leds).

Best regards,
Peter

[Tore]

I think i can say that the problem is solved. At least the crack/collaps is not so often now, and they are shorter.
Both the usb-cable into the phsolator and the short usb-cable were to loose. Now they are so tight they can be with bending, the short cable is twisted two times.


Tore

[PeterSt]

Ha ! Well done !!

Now Tore, please do yourself a favor and make a document where you refer to your post here, so you can prove to yourself later that you had it solved (with my small note that this happened a few times before ). This is good for your confidence later.

It is and remains true that connections with regard to the Phisolator are crazily fragile. This is a most strange phenomenon in itself (and explained by capacitance leaking-in).

Best regards,
Peter