Page 494 of 804
Re: MQN
Posted: Fri Aug 08, 2014 4:29 pm
by jorm
taggart wrote:sima66 wrote:
I can't play any of the latest avx2 versions! MQn box is there, Tasker box is there, but no sound! No problems with the previous 200(or more) avx2 versions.
Same here. If the newer versions now are "real" AVX2 version, it might be because we're using an Ivy Bridge processor
I am not so sure because then I shouldn´t be able to play the latest avx2 6.08 and 6.10 on a 3 year old Sandy Bridge laptop with Win 8.1 .But I do. I have to run both mqncontrol.exe and mqnplay.exe as administrator to achieve that and no Tasker.
Except from this oddity I have the same experience .No luck with the latest avx2 versions that contain the embedded manifest with Ivy Bridge CPUs and WS R2.Only the sse2 versions of MQn 6.08 or higher are working on my two main machines.
Apparently the manifest has added more complexity to the avx2 functionality ,so I wonder if there should be an option to have avx2 versions of new releases without the embedded manifest-if the sonic penalty is minor compared to manually adding it to the MQn folder or just leave it out.
6.11 needs a bug fix,ut gives out the same vinyl like clicks as 6.05 with thesycon 2.20 and through Audiophilleo(no driver).
Re: MQN
Posted: Fri Aug 08, 2014 5:16 pm
by jesuscheung
manifest file > embedded manifest
SQ better. don't know why
Re: MQN
Posted: Fri Aug 08, 2014 6:22 pm
by sbgk
uploaded 6.15 avx2, suspect it's a step up in SQ
here is the manifest I'm using, removed the embedded manifest
think version 0.0.0.0 is better than 1.0.0.0 aand added uiAccess="false"
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="0.0.0.0"
processorArchitecture="AMD64"
name="mqnplay.exe"
type="win32"/>
<description></description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="requireAdministrator" uiAccess="false">
</requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
Re: MQN
Posted: Fri Aug 08, 2014 7:02 pm
by satshanti
Compared 6.14 avx amd to 6.11 and 5.95 with the following result:
5.95 avx amd
+ great PRAT, dynamic, natural reverb, spacious and breathing sound stage
- ever so slightly too "loose"
6.11 avx amd
+ great micro detail, tonal fidelity, focused instrument placement
- ever so slightly too "edgy"
6.14 avx amd
+ even better micro detail and tonal fidelity
- slightly diffuse instrument placement and sound stage
- PRAT, which means timing, is ever so slightly "off"
Again no clear winner, all have alluring strengths, but also some weaknesses, suggesting that this is not yet the end of the road. :-)
Re: MQN
Posted: Fri Aug 08, 2014 7:19 pm
by jrling
6.11 needs a bug fix,it gives out the same vinyl like clicks as 6.05 with thesycon 2.20 and through Audiophilleo(no driver).
Same here and also 6.14 SSE2/361 Control with WaveIO Thesycon v2.23 (the latest).
If it is the embedded manifest causing the clicks, please we have a 6.15 SSE2 without embedded manifest to try?
My impression listening with the clicks was that it was tight and dynamic but a little dry (i.e without that sweetness mentioned).
Jonathan
Re: MQN
Posted: Fri Aug 08, 2014 7:38 pm
by sbgk
uploaded the other 6.15 versions
Re: MQN
Posted: Fri Aug 08, 2014 8:10 pm
by jrling
Thanks
Re: MQN
Posted: Fri Aug 08, 2014 8:59 pm
by jrling
6.15 SSE2/361 512 Control still has the same clicking as 6.14.
I conclude therefore that it is not the manifest causing it if you removed it in 6.15?
I reported the click first on 6.11 SSE2, which may give you a pointer to the cause?
Re: MQN
Posted: Fri Aug 08, 2014 9:54 pm
by sbgk
uploaded 6.16 sse2/avx/avx amd and avx2, 6.15 with some code rearranged.
Re: MQN
Posted: Fri Aug 08, 2014 10:07 pm
by sbgk
jrling wrote:6.15 SSE2/361 512 Control still has the same clicking as 6.14.
I conclude therefore that it is not the manifest causing it if you removed it in 6.15?
I reported the click first on 6.11 SSE2, which may give you a pointer to the cause?
that's unfortunate, suspect some interaction with your driver. How frequent is the clicking ?