0.9z-8e Tick after start

[PeterSt]

What happens to this when you change the SFS from 2 to 1.9 ?

[juanpmar]

And i think USB buffer size 8 gives me the best sound, better than 4 and 16 (SFS=2)

Tore

Really nice sound at 8ms. I´m going to stay with it for a while before I change to the other settings.

Thanks Tore.

Juan

[Tore]

Crack with SFS = 1,9 (USB buffer size 4)  :

With "After SFS Rounds" = 0 , crack after 5 sec.

With "After SFS Rounds" = 1 , crack after 20 sec.


Tore

[Tore]

Is it just me and Arvind that have this problem with USB buffer size 4?


Tore

[PeterSt]

And Tore ...

Q1 ?
Q1Factor ?
Device Buffer Size ?

(and you may change Q1 a little to see whether that makes a difference in the time when it occurs)

[Tore]

Q1=14
Q1Factor=1
Device Buffer Size=4096

Test with Q1=12 and "After SFS Rounds" = 0 - crack after 30 sec. (5 sec. with "After SFS Rounds" = 1)

Test with Q1=15 and "After SFS Rounds" = 0 - crack after 20 sec. (5 sec. with "After SFS Rounds" = 1)


Tore

[Tore]

I have just been playing through Diana Krall`s latest album Glad Rag Doll.
I have played with USB buffer size 4 and 8 and i prefer 4 now.
Everything is clearer or more in focus.

Peter, does the USB buffer size affect the SQ more now with 0.9z-8e ?

I hope you will find a solution to the crack problem.


Tore

[PeterSt]

Thank you for all you data Tore.

Well, this is all the most strange. I'd almost say : what about uninstalling the NOS1 driver and reinstalling it ?

Somehow this must be about something falling together and which point (in time) changes when the buffer size is changed (so, we notice that lengthening the buffer size makes that point earlier in time).

Since I have a PC which is prone to something like this just the same, it could be related to some chipset. However, this is merely about that "crack" which allows solution by the "SFS Rounds", which seems not to be your situation. But FWIW : on this PC it happens with both USB3 and USB2. So *if* it is about chipsets, it should be outside of USB.

Tore, Arvind too ... Are we actually talking about a problem which is new since 0.9z-8 ?

Can both of you watch the Wallpaper and see whether that changes at the moment of the crack ? Notice that (outside you changing the volume) this oficially (!) can only be about the change for the *~* indication, but I think it can also happen after that, in the situation that the *~* is already there right away. This can be called a bug (an unnecessary rewrite of the Wallpaper), but it may also cause the crack. So FYI here the possible situations :

1. *~* is there right away because After SFS Rounds = 0;
2. *~* shows up when the amount of SFS Rounds set have elapsed;
3. *~* is there right away despite After SFS Rounds was set to a value other than 0 (this will happen with small SFS sizes).
4. Bonus : A GDI+ error occurs because two "instances" of the program try to write the Wallpaper at the same time.

Let me add that writing the Wallpaper is a most awkward procedure in the Windows operating system; it requires a lot of cpu and has a high priority as well. This is why it is possible to perceive ticks of it anyway, and which people may remember from early Windows 7 times.
A bit problematic is the fact that it is not necessarily the visual change of the Wallpaper creating ticks; the tick can be earlier because the process concerned is already working on it, or it can be later because the OS likes to do a few things afterwards but with the Wallpaper change as the origin.

I say it once again and to keep in mind please : that crack for which the After SFS Rounds was created, is a backdoor solution to something I am not able to put my finger behind. And also : my normal Audio PC exactly never produces any crack anywhere.

Peter

[PeterSt]

Peter, does the USB buffer size affect the SQ more now with 0.9z-8e ?

It looks to be so, yes. But maybe that is because someone put the attention to it, and now everybody starts to experiment ?

My real answer is this :

At the start of 0.9z-8 I literally said : "All sounds sooooo normal". And this is key I think, because we seem to have entered a new dimension : the one of being able to compare with "not so normal". I always try to read in between the lines of how people judge, and suddenly it is about this phenomenon now. And I don't think this is because I said "soo normal". It will be because you now will be able to see through how things are. Like I explained about Get Yer Ya Ya's Out elsewhere. Don't you have (had) that sometimes ? that you suddenly "know" that you are listening to the real Mark Knopfler while you never spoke to the guy in person ?

So what will be happening now is that it doesn't take much to deviate from "normal" (which will be obvious to everyone) while before it was a mere subjective setting (whatever setting).

But anyway, I too now play with the NOS1 buffer as a key dial.
... and landed at 4, although this is Windows 8. Actually 2, but that isn't reliable (too critical to operate without errors, at least on Windows 8, plus it is hardware dependend (not everybody can use 2 in the first place)).

Regards,
Peter

[Tore]

No crack with USB2 

I`m sorry for all this questions.

Many thanks for all your writing and for the Fantastic SQ

You are a unique specimen


Tore

[PeterSt]

Well, now what.

Weren't you the one who just obtained that USB3 interface newly ? (I'm not sure). If so, then those drivers you found are not good ?

How's the relation with Arvind ? Same interface or chipset on it perhaps ? You both may like to mention your interface ...

Thanks for the kind words Tore.
Peter

[Tore]

I have this: BUFFALO IFC-PCIE4U3S USB 3.0 PCI Express Interface Card (4 Ports)

With this driver: http://drivers.softpedia.com/get/Other-DRIVERS-TOOLS/Renesas/Renesas-Electronics-uPD720201-uPD720202-USB-30-Driver-30200.shtml


Tore

[PeterSt]

So that was you.

Arvind ?

[arvind]

 Hi Peter,

My USB 3 interface is on the Gigabyte mobo X58UD3R. The single tick has been around since the introduction of PA. The duration when the tick occurs from the start of play varies with the SFS round. The higher the SFS round the longer it takes.

However yesterday I changed the driver latency to 8ms (from 4ms) & the tick has stopped. I havent been able to put it on for extensive period but in the 30 mins yesterday, I didnt hear a tick.

Best regards,

Arvind