Tír Na HiFi

Clive101 wrote:Hi

Just wondering if latest versions of MQn supports 24 bit only containers - ie play 16 bit wavs to a DAC that does only accepts everything in 24 bits?

Thanks
Clive101

Clive
I think idealy you would like to have some switch, a bit like JPlay has, that indicates if you like to use high-res in 32-bit containers (24 in 32-bit container) or in native containers (so 16 in 16, 24 in 24) or forced 24 (both 16 and 24 in 24-bit containers)

That would cover the options I think.

The thing is I don't know if Gordon can support such a feature in MQn given the optimisations he does.
Can you Gordon?

Cheers

Aleg

sbgk wrote:there are 2 v1 control versions, is that with both ? the 200000 files need to be used together.

Neither work on the DiverterHR2/Thesycon combination for 32-bit containers.

Cheers

Aleg

sbgk wrote:

cvrle59 wrote:

sbgk wrote:there are 2 v1 control versions, is that with both ? the 200000 files need to be used together.

I can play hirez only with 200000 versions, so the control I am using is "mqncontrol.exe v1 2000000". It can play only one track, no issues any more as I experience with non 200000, but if I try 2 or more tracks, the second one will lead into continues static noise.

uploaded mqncontrol v2 200000 which should fix things

This v2 version also doesn't work on the DiverterHR2/Thesycon combination for 32-bit containers.

Cheers

Aleg

Aleg wrote: Clive
I think idealy you would like to have some switch, a bit like JPlay has, that indicates if you like to use high-res in 32-bit containers (24 in 32-bit container) or in native containers (so 16 in 16, 24 in 24) or forced 24 (both 16 and 24 in 24-bit containers)

That would cover the options I think.


Aleg

Hi Aleg

Yes, that would be great but I was wondering if in fact 24 bit container support is more difficult to implement technically so hence why not implemented yet or just down to the fact that most DACS appear to process everything internally in 32bit, so not worth implementing?

Thanks

Clive101 wrote:

Aleg wrote: Clive
I think idealy you would like to have some switch, a bit like JPlay has, that indicates if you like to use high-res in 32-bit containers (24 in 32-bit container) or in native containers (so 16 in 16, 24 in 24) or forced 24 (both 16 and 24 in 24-bit containers)

That would cover the options I think.


Aleg

Hi Aleg

Yes, that would be great but I was wondering if in fact 24 bit container support is more difficult to implement technically so hence why not implemented yet or just down to the fact that most DACS appear to process everything internally in 32bit, so not worth implementing?

Thanks

Clive

No, I don't think so.
The current versions are using 24-bit containers for high res and the previous versions till 2.71 did support 32-bit containers for highres. So there is no issue supporting either form.
And treating 16-bit samples as 24-bit samples isn't more difficult, imo, than handling native 24-bit samples.

Cheers

Aleg

whats the 200000 mean

theres still some things i prefer in 2.73 448 for 16bit, i cant say 2.73 is better either
any chance of a hybrid?

With new MQn versions I can play: 16/44, 24/44, 24/48 but nothing above.

nige2000 wrote:whats the 200000 mean

theres still some things i prefer in 2.73 448 for 16bit, i cant say 2.73 is better either
any chance of a hybrid?

From Gordon's post (pg202)

"200000 refers to the period size in 100 ns ie 20ms which some devices seem to require"

cvrle59 wrote: From Gordon's post (pg202)

"200000 refers to the period size in 100 ns ie 20ms which some devices seem to require"

But some don't, so ....

What was 448 then
I'd like to test a tighter version