Tír Na HiFi

v24 has the fantastic detail of v23 and more solid bass, what's not to like. Nearly there.

v24 had a small error

uploaded v25 which fixes it. I would be happy to go with this one.

Some are still favouring v15 ldn, haven't listened to it for a while, anybody else like it above v25 ?

Listened to mqnplay v21, v23 and v24.
v21 still has a small but noticable veil, which I dislike. and detail is not quite as good as v23, v24, so I forget v21.

v23 and v24 are both very fine, no veil, with very good detail. differances more up to systems?
For me in orchestral pieces with mostly string sound, v23 is darker sounding, high violins less prominent than v24. best?
high voices, sopranos and tenor: I like v23 best, a little more smooth and more colour. but I only listened to one record.
piano: v23 also a little more colour than v24, maybe(?).

They are both very good, more listening needed.

janh, don't know if you saw I just uploaded v25, think it is the most correct as far as alignment goes, amazing snap on the bass and drums, quite intense to listen to.

only has 3 instructions between the wait and the device call, so in theory should have minimum timing issues. The second syscall is aligned on a 16 byte boundary which is optimal.

syscall ;wait ; 40001095 _ 0F 05
mov rdx, r14 ; 40001097 _ 49: 8B. D6
mov r10, rdi ; 4000109A _ 4C: 8B. D7
mov rax, rsi ; 4000109D _ 48: 8B. C6
syscall ;device ; 400010A0 _ 0F 05

sbgk wrote:janh, don't know if you saw I just uploaded v25, think it is the most correct as far as alignment goes, amazing snap on the bass and drums, quite intense to listen to.

Just saw it. Tomorrow.

think both syscalls need to be aligned, v25 a bit lacking in treble

uploaded v26 which is hopefully better.

think the alignment instructions affect the sq, so v27 just aligns the wait instruction.

For me the latest mqnplayer v15 ldn with hardcoded device name is still the best. I am using it with newest mqncontrol and loader for haswell (best combination so far). mqnplayer with device name in text file gives a little haze in my setup.
Most preferably I would like to listen to the newest mqnplayers but with hardcoded/fixed device names ldn.

That is interesting.

I find the mqnplay ldn15 with its original mqnloader and mqncontol (v7 both) to be best by quite a margin. Actually I think play LDN15 + control and loader 7 are nothing short of amazing and if I could only load any size test.wav with this combo I would probably live happily ever after with them :)

I have also been trying ldn15 mqnplay with new controls and loader but they are not as good as original matching, unfortunately the gap is quite big IMHO. The sound is tiring and loosing in dimensionality and presence in compare to original LDN15 and its control and loader, no matter which combination of any new loaders and control with Mqnplay ldn 15 I try (and I also find play 15 ldn better then any of the new MQNplays up to 21 where my testing has finished so far).

Still have to try anything past 21. But I can confirm that 21 was step back over 20 in clarity. 21 is hazed in compare to 20.

I cannot remember which but I narrowed it down to either MQNloader or Control in their new versions after 16 causing a lot of strain not MQNplays itself which were affecting other areas of sound but strain was mostly down to one of those two (control and loader), so probably some improvements to be had there.

Cheers

keeping the device id in the play exe will make it less user friendly, but I guess if it's the best sounding then it should be kept.

Still learning about the alignment, it's not intuitive.

Hi Gordon,

What about this:
1. mqndeviceinfo.exe >> mqnparam.txt
2. mqnDeviceNameReplacer.exe
- reads what is in mqnparam.txt
- opens mqnplayer.exe for edit
- replaces the device name and fills with 0s at the end if needed

Both sound quality and user friendliness is saved.

Me personally I do not mind using HexEditor.

TioFrancotirdor wrote:Hi Gordon,

What about this:
1. mqndeviceinfo.exe >> mqnparam.txt
2. mqnDeviceNameReplacer.exe
- reads what is in mqnparam.txt
- opens mqnplayer.exe for edit
- replaces the device name and fills with 0s at the end if needed

Sounds fine to me. But device name string has to be way longer to prevent situation in which user's device name string longer than original one