MQN

[jesuscheung]

these new versions are exciting!

a b compare to the old mqn.exe2.82

i still think mqn.exe2.82 is better

weight and depth are so well tuned it lays between the real thing and hifi.

from testing hundreds of versions of software players, i learn that

if drum is 100% real, then vocal will have too much power.
if vocal is 100% real, then drum and musical instruments will be lacking weight and depth.
if vibration is 100% real, then treble density will be lacking.
if depth is perfect, then overall stage is usually unnaturally stretched.
if density is too high, then vibration will be difficult.

i think mqn2.82 has perfect balance in music presentation.
nothing is 100%, but everything is 95%. everything is between hifi and the real thing.

[nige2000]

losing focus/stage/position and clarity without vp 0x0

2.81 vp 0x0 > 2.84
vp 0x0 might fix

[sbgk]

2.84 has 0x0

[nige2000]

ok must be something else

[jesuscheung]

(with all new versions, doesn't anyone else think there is strain in music? takes a few mins to detect with headphones. with speakers, 30 mins is needed to strain my ears to rest)

i get it now. the clockrate was changed by mqn. that's why it strains
in which case, need to loosen the timing (timer resolution) like everyone else is. cannot use 0.5ms makes sound much worse

[Aleg]

(with all new versions, doesn't anyone else think there is strain in music? takes a few mins to detect with headphones. with speakers, 30 mins is needed to strain my ears to rest)

i get it now. the clockrate was changed by mqn. that's why it strains
in which case, need to loosen the timing (timer resolution) like everyone else is. cannot use 0.5ms makes sound much worse

Just change it back after MQn has started. Easy enough to run a batch to change the registry setting.

[3daudio]

As my DDC only understands 24bit files, I always used the hirez versions.

All my files are in 24/44.1 for that reason.

I just discovered that 24/96 do work with "mqnplay.exe 24 bit sse2 10ms R2.84 win8.1-r2" , but 24/44.1 do not.

Is there a chance to get a version that works with 24/44.1? Where can I make a donation, Gordon?

[jesuscheung]

(with all new versions, doesn't anyone else think there is strain in music? takes a few mins to detect with headphones. with speakers, 30 mins is needed to strain my ears to rest)

i get it now. the clockrate was changed by mqn. that's why it strains
in which case, need to loosen the timing (timer resolution) like everyone else is. cannot use 0.5ms makes sound much worse

Just change it back after MQn has started. Easy enough to run a batch to change the registry setting.

thx. that works too.
actually quite like the 10ms clockrate of mqn. more forgiving then my own clockrate. i don't have to focus on OS jitters all the time.

[Aleg]

Prefer 2.84 to 2.83/2.81 0x0 because it gives more insight into the structure of the deep bass notes.

2.81 vp 0x0 has a somewhat more dry upper mid, not as much reverb, a bit shortened.
2.83 has a bit more of the reverb in upper mid, prefer that to the dryness of 2.81 0x0.
2.81 0x0 also a bit more aggressive in the attack.
Both equal on many other aspects.

Prefer all three over 2.82 (which has closed up sound again)

So 2.84 > 2.83 > 2.81 vp 0x0 > 2.82
All with R1.6 control

Cheers
Aleg

[taggart]

Just change it back after MQn has started. Easy enough to run a batch to change the registry setting.

Aleg, are you sure that this works? A process (mqnplay.exe) must register itself at MMCSS to get under its control. I assume that Pro Audio settings from registry are read exactly at this time and not over and over again when registering has already taken place. But don't know exactly.