Tír Na HiFi

Aleg wrote:

nige2000 wrote:Dunno if tasker is fully overriding the high priority in mqnplay
As there was still difference between the high priority and real time versions a while back while using tasker set for real time
Was an irrelevant test anyway because of that error
Think we would be further on using real time and lower buffer

Yes, tasker will set the priority of mqnplay when issued after mqncontrol has launched mqnplay.
Nothing mqn istelf can do about that

I'm sure your right but there was a more detail in 7.55 rt than 7.55 high priority
When using tasker with rt set
Even though rt did have an uneasy sound to it likely was more to do with the error in the render loop

I have a little clicks every 5-10 seconds with all the new ones (7.58; 7.59 and 7.61)!

I think this means the issue is with CPU type and not driver software, as others have WaveIO/Thesycon 2.23 working fine.

You and I have Ivy Bridge CPU I think.

Any ideas Gordon? It's frustrating not to be able to enjoy your latest work for seemingly quite a few of us.

"Then, the HI-FI revolution began and the very start of the 1950's. Engineers tried everything to make their records sound "Hi-Fi" even if they didn't have a clue as to what that meant to a consumer. Mercury Records and engineer Bill Fine, put a single microphone in a big concert hall and recorded the first Mercury "Living Presence" LP. This was the start of the "Hi-Fi" craze, and most engineers from other companies quickly came to the understanding that ECHO = Hi-Fi. "
http://www.stevehoffman.tv/dhinterviews/HoffLesson4.htm

does the latest versions reproduce enough ECHO!?!?

jesuscheung wrote:"Then, the HI-FI revolution began and the very start of the 1950's. Engineers tried everything to make their records sound "Hi-Fi" even if they didn't have a clue as to what that meant to a consumer. Mercury Records and engineer Bill Fine, put a single microphone in a big concert hall and recorded the first Mercury "Living Presence" LP. This was the start of the "Hi-Fi" craze, and most engineers from other companies quickly came to the understanding that ECHO = Hi-Fi. "
http://www.stevehoffman.tv/dhinterviews/HoffLesson4.htm

does the latest versions reproduce enough ECHO!?!?

I have a recording of the ugly duckling and can quite clearly hear an echo.

7.62 avx2 2496 works perfectly for me and sounding excellent.
KM

jrling wrote:

I have a little clicks every 5-10 seconds with all the new ones (7.58; 7.59 and 7.61)!

I think this means the issue is with CPU type and not driver software, as others have WaveIO/Thesycon 2.23 working fine.

You and I have Ivy Bridge CPU I think.

Any ideas Gordon? It's frustrating not to be able to enjoy your latest work for seemingly quite a few of us.

think there are a number of possibilities

1. device is not selected ie default is 0 and device 1 should be selected

2. laptop output device not selected

3. unicode filter name not interpreted.

4. driver not able to work with render loop

5. latency issues

6. cpu issues

sbgk wrote:

jrling wrote:

I have a little clicks every 5-10 seconds with all the new ones (7.58; 7.59 and 7.61)!

I think this means the issue is with CPU type and not driver software, as others have WaveIO/Thesycon 2.23 working fine.

You and I have Ivy Bridge CPU I think.

Any ideas Gordon? It's frustrating not to be able to enjoy your latest work for seemingly quite a few of us.

think there are a number of possibilities

1. device is not selected ie default is 0 and device 1 should be selected
I only have one device connected. What number should it be to work correctly?

2. laptop output device not selected
I am not running on a laptop. See answer to 1. above

3. unicode filter name not interpreted.
How do I check that?

4. driver not able to work with render loop
Seems unlikely as others have got all versions working with Thesycon 2.23

5. latency issues
I am running the second lowest latency setting in Thesycon CP - as I always have

6. cpu issues
It is Ivy Bridge - again only had one previous issue with clicking before (as did several others) which was solved in your code


I think it started (7.55 1644 Normal) when you took control of Thread Priority within your code.

Perhaps others experiencing clicking could compare their system specs with mine and see if there is a commonality that might be the cause?

Thanks

Jonathan

Jonathan, you perfectly described my "case"! I will only ad that from the first PA day I had only one device at "0", no other choices.

Aleg, I'm using Tasker the same way I always did. I never changed anything!

sima66 wrote:Jonathan, you perfectly described my "case"! I will only ad that from the first PA day I had only one device at "0", no other choices.

Aleg, I'm using Tasker the same way I always did. I never changed anything!

Me too on both points.

Just to chime in,I have exactly the same soft clicks as Jrling and sima66 describe through Thesycon 2.20 with minimal latency on my Zuma using 24/96 MQn avx2 7.55-7.61.Tasker with realtime priority doesn´t change anything except perhaps softening the clicks a bit .Swapping to JKDAC with M2Tech Young solves the problem. So for Thesycon 2.20/2.23 at least,the problem seems to be CPU related .Haswell is apparently the "solution".Moving my Geek Out (with Thesycon 2.20) to my SandyB I5 desktop PC doesn´t resolve the issue,I only get a different kind of noise,more like a continous background buzz....JKDAC works perfectly here too.
Audiophilleo is even worse and only produces distorted sound from any MQn version after 7.52 on any computer here...
So the latest MQn´s demonstrate to things:
-Excellent sound for the lucky few with the right CPU and/or driver .7.55 avx2 and upwards deliver to my ears unprecedented micro- and macro detail level with an extremely airy presentation and no hint of treble glare.Best ever I have heard for sure.
-Really reduced usability for most users .

Cheers

Jorgen