Tír Na HiFi

138 is still a bit harsh for me, 140 definitely has something missing eg acoustic guitar strings are a bit muffled, but otherwise is highly optimised. Shall see if I can isolate the cause.

sbgk wrote:138 is still a bit harsh for me, 140 definitely has something missing eg acoustic guitar strings are a bit muffled, but otherwise is highly optimised. Shall see if I can isolate the cause.

Listened to Alan Taylor "In The Grove"
I could not enjoy v140 with this album
v138/v52 on tubes sounds much better IMHO
You are right v140 something is messed up
Thanks Gordon

uploaded play v141 and counter v19, hopefully improved, think it sounds ok.

sbgk wrote:uploaded play v141 and counter v19, hopefully improved, think it sounds ok.

I try v143/v19/v51 it is better then v138/v52
Seems like you still can tweak a little more somehow
I think you are getting to the end here
Does anyone test these versions?
Post your findings
No one listen to music with MQnplay anymore sad
Thanks Gordon

elaprince wrote: I try v143/v19/v51 it is better then v138/v52
Seems like you still can tweak a little more somehow

+1. Also thank you.

Just wondering what is the control v52 for??
It doesn't work with either versions except v138
Thanks

my last good ver is play 134, control 51, counter 15, loader 30 (23ms). If it gives a tighter bass, that would be very good.

v_141_ctrl51_load30_counter19_w10 and previous versions of same series cracks for some 20 seconds from start of play.

think the dac driver is the black hole in the chain. Only a few make the hardware buffer size user adjustable.
Some even don't support kernel streaming.

iori wrote:my last good ver is play 134, control 51, counter 15, loader 30 (23ms). If it gives a tighter bass, that would be very good.

v_141_ctrl51_load30_counter19_w10 and previous versions of same series cracks for some 20 seconds from start of play.

think the dac driver is the black hole in the chain. Only a few make the hardware buffer size user adjustable.
Some even don't support kernel streaming.

I always check if the DAC uses the Thesycon USB-drivers, which I consider to be the best and are certainly the most configurable I have seen. Though the Thesycon sometimes still had issues where Gordon's drivers did not (I'm not sure which drivers Gordon is actually using).

I have been in (sometimes nasty) discussions with manufacturers about their drivers and (lack of) support for kernel streaming.
I have rejected certain DACs just on the basis of this, regardless of how well they were perceived or reviewed by others.

As it now shows, these drivers and they level they can be configured are crucial for getting best out of computer audio.

Aleg wrote: I always check if the DAC uses the Thesycon USB-drivers, which I consider to be the best and are certainly the most configurable I have seen. Though the Thesycon sometimes still had issues where Gordon's drivers did not (I'm not sure which drivers Gordon is actually using).

I have been in (sometimes nasty) discussions with manufacturers about their drivers and (lack of) support for kernel streaming.
I have rejected certain DACs just on the basis of this, regardless of how well they were perceived or reviewed by others.

As it now shows, these drivers and they level they can be configured are crucial for getting best out of computer audio.

Aleg,

I have a Chord Hugo too. Does Hugo use the Thesycon USB driver? How can I configure it? My Hugo produces noise for MQn versions above mqnplay v134.

Adolfo

adolfo.a.aguiar wrote:

Aleg wrote: I always check if the DAC uses the Thesycon USB-drivers, which I consider to be the best and are certainly the most configurable I have seen. Though the Thesycon sometimes still had issues where Gordon's drivers did not (I'm not sure which drivers Gordon is actually using).

I have been in (sometimes nasty) discussions with manufacturers about their drivers and (lack of) support for kernel streaming.
I have rejected certain DACs just on the basis of this, regardless of how well they were perceived or reviewed by others.

As it now shows, these drivers and they level they can be configured are crucial for getting best out of computer audio.

Aleg,

I have a Chord Hugo too. Does Hugo use the Thesycon USB driver? How can I configure it? My Hugo produces noise for MQn versions above mqnplay v134.

Adolfo

No Hugo doesn't use TheSycon driver
I don't think they even know existence of it LOL
Thanks