MQN

[jesuscheung]

JC what clock rate you using with 100000

Do you think clock size and period size connected?

can't help you if you don't know what buffer size your DAC likes...

just don't forget 44100's clockrate is wrong for hires playback.
think most people here uses 23220. doesn't work for hires
remember to change it

im playing with it only with 16 44
with 100000 i like 448 clockrate
dunno if thats related to my dac or the period size of this version

sounds good
from my experience, correct rate gives max resolution
for my setup:
352 > 320 > 448~256

best clockrate can make sound worse, as it is just reflecting jitters of OS.
448 in my setup can very easy sound good with other software players too.
makes sense, 448 has lower res, more compromising.

448/44100=10159. (tightest clockrate)
try loosen it to 10160, it is even more compromising. it is even less resolution. but it is more easy to sound good.

same for timer resolution. 0.5ms doesn't compromise at all. it will reflect bad sound if OS/software is bad or hardware is slow(e.g. downclocking CPU).
software player itself doesn't decide all the sound.
why same WASAPI sounds different in 8.1 and R2?
because one must have metro. one can get rid of it.
every little thing affects sound.

[cvrle59]

I believe you JC, but I found no tweaks so far to change the SQ on my system like different versions of player, especially 100000.
I can't say that I experimented a lot, but I kind of gave up, as I haven't found enough gain to spend time on it, plus computer I am playing of is not dedicated for music only.
For example changing priority in task manager, I hear no difference at all.
Actually, it could be that my current setup is in sweet spot for this version, I don't know. I will get a dedicated computer eventually, to start playing with different tweaks to see how it reacts.

[nige2000]

theres definitely something in this
think im of the belief that the tightest settings that the system can cope with/without jitter or noise will be sound best

[Sligolad]

I am beginning to pity all those poor souls I pointed towards this thread at Scalford given that even I have lost touch in what is a good setup with MQN these daya given all the permutations under discussion!!
I hope someone with a handle on where we are at can someday write up a simple table of combinations that work well with possible clock rates and timer settings.

Seems like a long time ago but there was somrthing like this written up for the JLP Player which made a lot of sense at the time, maybe we can get another volunteer?
Would do it myself if only I knew what works with what these days............

Need to go back and see if I can get any of these 100000 versions to work, had no sucess at the weekend :-((

Cheers, Pearse.

[tony]

+1 phew thought I was the only one

[jesuscheung]

...
I can't say that I experimented a lot, but I kind of gave up, as I haven't found enough gain to spend time on it, plus computer I am playing of is not dedicated for music only.
For example changing priority in task manager, I hear no difference at all.

i also cannot hear difference if on a new installed windows.

after you have successfully accumulated about 50-100 correct changes (zero mistake!!).
every micro-change = 1-5% difference.

at a certain tipping point, the resolution grows exponentially.
let's face it, a fresh OS is a big piece of jitter. even in non-gui mode. you are only listening to jitters. treble and bass and mid are all unstable.

[Aleg]

I am beginning to pity all those poor souls I pointed towards this thread at Scalford given that even I have lost touch in what is a good setup with MQN these daya given all the permutations under discussion!!
I hope someone with a handle on where we are at can someday write up a simple table of combinations that work well with possible clock rates and timer settings.

Seems like a long time ago but there was somrthing like this written up for the JLP Player which made a lot of sense at the time, maybe we can get another volunteer?
Would do it myself if only I knew what works with what these days............

Need to go back and see if I can get any of these 100000 versions to work, had no sucess at the weekend :-((

Cheers, Pearse.

Pearse

There is only one 100000 version of mqnplay and of mqncontrol and they have to be used in combination. You can't go wrong there!

W.r.t. timerresolution, this is something you cannot easily set at all. I have a program that will do it, but it is not simple as you don't have absolute control over it esp. not on a general purpose computer, because it will be set to the lowest value requested by any program running on your computer not necessarily the value you requested. On a dedicated audio-PC it can be done, because you have a decent control over which programs are running.
Setting timerresolution IMHO only makes sense if you can set the buffersize of your DAC-driver, preferably in ms and not in number of samples. Only in that case you can have a good fit between timerresolution and buffersize.

Clockrate can be set always in registry, the best value in theory however is dependent on sampling frequency, so not very convenient for those that use a mixture of sampling frequencies having to change clockrate all the time. Furthermore I personally don't notice much difference when using 23220 for all sampling frequencies.

So I would not bother too much with clockrate just set it to 23220.
If you can't set your buffersize in DAC-driver I wouldn't bother with Timerresolution at all.

Cheers

Aleg

[cvrle59]

...
I can't say that I experimented a lot, but I kind of gave up, as I haven't found enough gain to spend time on it, plus computer I am playing of is not dedicated for music only.
For example changing priority in task manager, I hear no difference at all.

i also cannot hear difference if on a new installed windows.

after you have successfully accumulated about 50-100 correct changes (zero mistake!!).
every micro-change = 1-5% difference.

at a certain tipping point, the resolution grows exponentially.
let's face it, a fresh OS is a big piece of jitter. even in non-gui mode. you are only listening to jitters. treble and bass and mid are all unstable.

I believe so...I will play with it once I get a computer for music only.

[cvrle59]

Aleg - I know you appraised 100000 very highly, what really made me to put some effort to change driver and to make it work. Do you still find this version to be #1 choice for 16/44, or there is a new favorite in these R1.0's?

[Aleg]

...
let's face it, a fresh OS is a big piece of jitter. even in non-gui mode. you are only listening to jitters. treble and bass and mid are all unstable.

I believe you would when listening straight from a computer
But certain DACs do reclocking and certain people use highly stable reclockers, so I believe the effects maybe less prominent when not listening straight from the PC.

Cheers

Aleg