MQN

Anything to do with computer audio, hardware, software etc.
sbgk
Posts: 1950
Joined: Mon Oct 07, 2013 9:45 pm

Re: MQN

Post by sbgk »

wushuliu wrote:
minionas wrote:
jesuscheung wrote:sbgk. try a 4 digits clockrate. 4644 instead of 46440. no need of 6 digits never sounded good.
Hi,
Could you please share a registry path to clockrate variable?
Same registry path as changing Background from False to True listed in the Readme. The clock rate is right above it. Guessing you just modify to one of the numbers mentioned. It would be good if someone could clarify that part.
I think the background setting doesn't improve things, should remove it from the readme file.

by reducing it by a factor of 10 you're making something work 10 times as often, are you sure it's an improvement ?

Any comments about the latest version ?

Taggart should have some good news about his loader program soon. I tried it last night and it's very good/useful.
User avatar
minionas
Posts: 101
Joined: Mon Jul 29, 2013 6:45 am
Location: Lithuania

Re: MQN

Post by minionas »

sbgk wrote:
Any comments about the latest version ?

Taggart should have some good news about his loader program soon. I tried it last night and it's very good/useful.
Im a 24bit dac guy, so am using only 24/96 V5 mqncontrol version until you'll release 24bit full version :) So can't make comments on any of your new mqnplay versions yet :/
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: MQN

Post by jesuscheung »

minionas wrote:
jesuscheung wrote:sbgk. try a 4 digits clockrate. 4644 instead of 46440. no need of 6 digits never sounded good.
Hi,
Could you please share a registry path to clockrate variable?
clockrate is a dangerous tweak. 99% of the time will damage you SQ.
i am still experimenting the clockrate calculation.
according to my ears, i am not convinced clockrate=buffer/44100 is the answer.

i think clockrate is a function f(DACBuffer, playerBuffer, timerResolution, 44100 or 96k or ...). it consists of 4 variables.

clockrate precision is defined by the number of digits. e.g. 4644, 46440, 464400.
i think clockrate precision depends on the quality of clock of your DAC. my xonar STX has a rubbish hardware clock, 4 digits seem to sound best. others have better DAC like audiofire thinks 5 digits is best. someone with a $2000 DAC should test a 6digits clockrate.
wushuliu
Posts: 180
Joined: Tue Oct 22, 2013 2:24 am

Re: MQN

Post by wushuliu »

jesuscheung wrote:
minionas wrote:
jesuscheung wrote:sbgk. try a 4 digits clockrate. 4644 instead of 46440. no need of 6 digits never sounded good.
Hi,
Could you please share a registry path to clockrate variable?
clockrate is a dangerous tweak. 99% of the time will damage you SQ.
i am still experimenting the clockrate calculation.
according to my ears, i am not convinced clockrate=buffer/44100 is the answer.

i think clockrate is a function f(DACBuffer, playerBuffer, timerResolution, 44100 or 96k or ...). it consists of 4 variables.

clockrate precision is defined by the number of digits. e.g. 4644, 46440, 464400.
i think clockrate precision depends on the quality of clock of your DAC. my xonar STX has a rubbish hardware clock, 4 digits seem to sound best. others have better DAC like audiofire thinks 5 digits is best. someone with a $2000 DAC should test a 6digits clockrate.
Lol, okay - Then I think I will not do any of those tweaks then unless sgbk says so...
Eclipse W6520R/Satori TW29R MTM
Hifime Es9038Pro
3eaudio TPA3251
wushuliu
Posts: 180
Joined: Tue Oct 22, 2013 2:24 am

Re: MQN

Post by wushuliu »

Thumbs up for 2.70 sounds 'fuller' than 2.68/9. Vocals pop real nice, top end less prominent. More balanced in my setup.
Eclipse W6520R/Satori TW29R MTM
Hifime Es9038Pro
3eaudio TPA3251
nige2000
Posts: 4253
Joined: Thu Feb 14, 2013 10:47 am
Location: meath

Re: MQN

Post by nige2000 »

will get testing later, but i see all other previous versions removed from the main folder on google drive
is this a sign?
sd card player, modded soekris dac, class a lifepo4 amp or gb class a/b amp, diy open baffle speakers based on project audio mundorf trio 10's
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: MQN

Post by jesuscheung »

your chance of an improved clockrate is about 100 out of 9000. your chance of a perfect clockrate is about 3 out of 9000. i believe a perfect clockrate is 100 times better than those audiophile optimizers. they mostly just disable trivial things.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: MQN

Post by jesuscheung »

sbgk wrote:
I think the background setting doesn't improve things, should remove it from the readme file.

by reducing it by a factor of 10 you're making something work 10 times as often, are you sure it's an improvement ?

Any comments about the latest version ?
so why don't you use 464400? it works 10 times less often. or 46440000. i think it depends on the quality of DAC's clock. a crap clock like one i have needs to work 10 times harder.

2.70 intel sse2 sounds very good. still prefer 2.66 v2 sse4 for vocal. 2.70 has very good vocal too.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: MQN

Post by jesuscheung »

these new versions have similar style- not a lot to comment on their changes.

i think some good stuffs are coffined from much older versions. for example, some old versions were really airy.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: MQN

Post by jesuscheung »

sbgk. possible to have a few versions of various buffer types?

i just realize my DAC is best with buffers
44,88,178,352....

lekt told me his DAC best buffer size are
160, 320...

MQn currently is doing
256, 512, 1024, 2048...

Audiofire's best buffer size are
160, 320, 640....

i only just realize this pattern. buffer is DAC dependent, i think.
Post Reply