HQ Player

[der_yeti]

On 1/12/2020 at 6:06 PM, Miska said:

 

Looks like you are about at maximum performance you can get out of your current computer. You can compare if you prefer higher DSD rate with ASDM7 modulator instead (assuming supported by the DAC). But likely it is a close call, ASDM7EC is a good modulator...

 

Tried your suggestion, but I decided to stay with the EC modulator. My DAC supports up to 512.

 

What computer upgrade could take the performance to a next level?

[Miska]

On 1/12/2020 at 8:43 PM, Hammer said:

Hi, for some reason, when I start up HQPlayer in Windows, I'm seeing a command window come up with the following:

 

OMP: Warning #123: Ignoring invalid OS proc ID 1.
OMP: Warning #123: Ignoring invalid OS proc ID 3.
OMP: Warning #123: Ignoring invalid OS proc ID 5.
OMP: Warning #123: Ignoring invalid OS proc ID 7.
OMP: Warning #123: Ignoring invalid OS proc ID 9.
OMP: Warning #123: Ignoring invalid OS proc ID 11.
OMP: Warning #123: Ignoring invalid OS proc ID 13.
OMP: Warning #123: Ignoring invalid OS proc ID 15.
OMP: Warning #123: Ignoring invalid OS proc ID 17.
OMP: Warning #123: Ignoring invalid OS proc ID 19.
OMP: Warning #123: Ignoring invalid OS proc ID 21.
OMP: Warning #123: Ignoring invalid OS proc ID 23.
OMP: Warning #123: Ignoring invalid OS proc ID 25.
OMP: Warning #123: Ignoring invalid OS proc ID 27.
OMP: Warning #123: Ignoring invalid OS proc ID 29.
OMP: Warning #123: Ignoring invalid OS proc ID 31.
OMP: Warning #124: No valid OS proc IDs specified - not using affinity.

 

This didn't use to happen.  Is there a way to close this?  If I close this window, HQPlayer also ends.

 

Which version of Windows is this? Did it start happening after some OS update?

 

This is 16 core CPU that is supposed to have 32 threads?

 

[Hammer]

3 hours ago, Miska said:

 

Which version of Windows is this? Did it start happening after some OS update?

 

This is 16 core CPU that is supposed to have 32 threads?

 

I realized the Windows shows up because of process lasso.  Sorry about that.

[Miska]

1 hour ago, Hammer said:

I realized the Windows shows up because of process lasso.  Sorry about that.

 

OK! It is not recommended to mess with the OS because it will just break the core allocations done in HQPlayer. This is just one example of such...

 

[521ztz]

Hi Miska,

 

My CPU is 9900K@5ghz, below is my setting to upload red books to DSD, but when I click on a song, there is a loading bar appears and then disappear, after that, it displays "Processing time 1077s". Do you know what's the problem? Thanks.

[Miska]

1 hour ago, 521ztz said:

Hi Miska,

 

My CPU is 9900K@5ghz, below is my setting to upload red books to DSD, but when I click on a song, there is a loading bar appears and then disappear, after that, it displays "Processing time 1077s". Do you know what's the problem? Thanks.

 

At least here looks like output device is missing...

[rzvnz]

Hello Miska,

 

Technically wise, which is the best option:

 

1. Roon -> poly-sinc-ext2 -> ASDM7EC -> DSD128 (maximum without shuttering on my i5 5600k 32Mb GTX 970) -> Matrix Element-M

2. Roon -> poly-sinc-ext2 -> ASDM7 -> DSD512 -> Matrix Element-M

3. Roon -> poly-sinc-ext2 -> NS5(TPDF) -> PCM 768 kHz->Matrix Element-M

 

Also, for my second setup (with the same pc):

 

1. Roon -> poly-sinc-ext2 -> ASDM7EC -> DSD128 (maximum without shuttering on my i5 5600k 32Mb GTX 970) -> ADI DAC-2 fs

2. Roon -> poly-sinc-ext2 -> ASDM7 -> DSD256 -> ADI DAC-2 fs

3. Roon -> poly-sinc-ext2 -> NS5(TPDF) -> PCM 768 kHz->ADI DAC-2 fs

 

Thank you!

 

[Miska]

2 hours ago, rzvnz said:

Technically wise, which is the best option:

 

1. Roon -> poly-sinc-ext2 -> ASDM7EC -> DSD128 (maximum without shuttering on my i5 5600k 32Mb GTX 970) -> Matrix Element-M

2. Roon -> poly-sinc-ext2 -> ASDM7 -> DSD512 -> Matrix Element-M

3. Roon -> poly-sinc-ext2 -> NS5(TPDF) -> PCM 768 kHz->Matrix Element-M

 

With ESS it is better to go for higher rate, so I'd rather go with ASDM7 at DSD512.

 

2 hours ago, rzvnz said:

1. Roon -> poly-sinc-ext2 -> ASDM7EC -> DSD128 (maximum without shuttering on my i5 5600k 32Mb GTX 970) -> ADI DAC-2 fs

2. Roon -> poly-sinc-ext2 -> ASDM7 -> DSD256 -> ADI DAC-2 fs

3. Roon -> poly-sinc-ext2 -> NS5(TPDF) -> PCM 768 kHz->ADI DAC-2 fs

 

Compared to ESS, due to the very different approach in DAC implementation, here it is not so clear cut. If you use ASDM7EC at DSD128, set the DSD filter to 50 kHz in ADI-2. With ADI-2, also always make sure you have "DSD Direct" mode enabled. You could also try for example DSD5EC modulator if you can get it running at DSD256. But it also performs very well with ASDM7 at DSD256.

 

 

If you send 768k PCM to either one, TPDF dither is fine, since both can accept 32-bit resolution. The AKM chip in ADI-2 performs better at 768k than the ESS chip in Matrix.

 

[LoryWiv]

18 minutes ago, Miska said:

 

With ESS it is better to go for higher rate, so I'd rather go with ASDM7 at DSD512.

 

 

Hmmm. I didn't know that and have a Matrix DAC per signature below. Just by trial and error comparing ASDM7EC --> DSD128 versus non EC modulators --> DSD256 I found the former better overall.

 

I have an i7 7700 at 4.2, I can run ASDM7EC --> DSD256 without stutter but cpu load gets quite high and I haven't really been able to detect a huge sonic improvement.

 

Thanks, @Miska 

 

[Miska]

38 minutes ago, LoryWiv said:

Hmmm. I didn't know that and have a Matrix DAC per signature below. Just by trial and error comparing ASDM7EC --> DSD128 versus non EC modulators --> DSD256 I found the former better overall.

 

I have an i7 7700 at 4.2, I can run ASDM7EC --> DSD256 without stutter but cpu load gets quite high and I haven't really been able to detect a huge sonic improvement.

 

If you prefer that way instead, it is not a bad choice either. Background is that ESS has fairly gentle DSD filter, so using higher rate reduces amount of leftover (random) ultrasonic noise. For audio band, the difference is small though.

 

EC vs non-EC modulator differences are primarily in the audio band though.

 

So it is not easy to give a generic advice which way is best even under somewhat known conditions.

 

[LoryWiv]

47 minutes ago, Miska said:

 

If you prefer that way instead, it is not a bad choice either. Background is that ESS has fairly gentle DSD filter, so using higher rate reduces amount of leftover (random) ultrasonic noise. For audio band, the difference is small though.

 

EC vs non-EC modulator differences are primarily in the audio band though.

 

So it is not easy to give a generic advice which way is best even under somewhat known conditions.

 

Thanks, @Miska that makes sense. BTW any recommended settings for the Matrix X-sabre pro for best use with HQ Player 4.x Desktop?

[Miska]

26 minutes ago, LoryWiv said:

Thanks, @Miska that makes sense. BTW any recommended settings for the Matrix X-sabre pro for best use with HQ Player 4.x Desktop?

 

I don't have anything else than what I said above regarding ESS chips. Analog filter implementations in different DACs vary somewhat, but most resort to fairly simple 2nd order filter.

 

Upsampling filter choice in HQPlayer is driven mostly by combination of personal preferences and source material. Modulator choice is maybe more technical, but still it has the sonic and overall system dependent aspect.

 

But it is also straightforward to test for example ASDM7 at DSD512 vs ASDM7EC at DSD256 while keeping other settings the same. It gives fairly good picture of the differences in a particular system.

 

[LoryWiv]

8 hours ago, Miska said:

 

I don't have anything else than what I said above regarding ESS chips. Analog filter implementations in different DACs vary somewhat, but most resort to fairly simple 2nd order filter.

 

Upsampling filter choice in HQPlayer is driven mostly by combination of personal preferences and source material. Modulator choice is maybe more technical, but still it has the sonic and overall system dependent aspect.

 

But it is also straightforward to test for example ASDM7 at DSD512 vs ASDM7EC at DSD256 while keeping other settings the same. It gives fairly good picture of the differences in a particular system.

 

Yes, that's what I've done and quite happy with my current settings. I do think the EC filters sound generally better, and stick with closed-form-16M for 2x up, either poly-sinc.xtr-mp-2s or poly-sinc-ext2 for 1x.

 

Poly-sinc.xtr-mp-2s sounds generally more to my preference but takes longer to initialize for some reason, and both filters give great results. 

 

I'm also doing some tube rolling on my amp recently and it's helpful to have stable, reliable settings on HQ Player to remove that variable when I evaluate tubes.

 

Thanks @Miska!

[shahed99]

I’m currently using HQP V3 on windows. Just found out that my license wouldn’t work on embedded as I was using Euphony trial.

 

Now I’m contemplating purchasing HQP V4. However, I’d like to use it on windows first. In future, I might switch to embedded. @Miska Can you please let me know if I buy HQP V4 for windows, the same license can be used for embedded? If not, I won’t be able to mage a decision unless I finalized about which platform (windows or Linux embedded) I’ll settle down on.

[Miska]

1 hour ago, shahed99 said:

I’m currently using HQP V3 on windows. Just found out that my license wouldn’t work on embedded as I was using Euphony trial.

 

Now I’m contemplating purchasing HQP V4. However, I’d like to use it on windows first. In future, I might switch to embedded. @Miska Can you please let me know if I buy HQP V4 for windows, the same license can be used for embedded? If not, I won’t be able to mage a decision unless I finalized about which platform (windows or Linux embedded) I’ll settle down on.

 

HQPlayer 4 Desktop and Embedded are separate products and require separate licenses. I recommend to use the trial to figure out which way you'd like to go.

 

[ambre]

Hi Miska,

 

To be informed:

Have installed HqPlayer 4 on a brand new Mac Mini I7. And again the Microphone issue is back. With other words I cannot assign microphone to HqPlayer.

 

 I can deal with it because I use nowadays Amoebe Loopback.   But other people who like to use the  Realtime audio inputs may discover the same issue.  

Ps. You had some suggestions like PRAM or to install HqPlayer PRO  but I have done that yet.

[Miska]

55 minutes ago, ambre said:

To be informed:

Have installed HqPlayer 4 on a brand new Mac Mini I7. And again the Microphone issue is back. With other words I cannot assign microphone to HqPlayer.

 

 I can deal with it because I use nowadays Amoebe Loopback.   But other people who like to use the  Realtime audio inputs may discover the same issue.  

Ps. You had some suggestions like PRAM or to install HqPlayer PRO  but I have done that yet.

 

Are you on HQPlayer Desktop 4.2.3? When you set HQPlayer input to built-in microphone, then restart HQPlayer and try to play from the microphone. macOS should ask you whether you want to grant HQPlayer access to the microphone.

 

Quote

I can deal with it because I use nowadays Amoebe Loopback.   But other people who like to use the  Realtime audio inputs may discover the same issue.

 

As long as the sound is going through CoreAudio, it shouldn't matter where it is sourced from... So it shouldn't be working with the loopback either then. But this feature on macOS behaves strange sometimes.

 

[DancingSea]

I’ve been having an odd issue with HQPlayer 4.  Frequently when playing DSD files, during quiet parts I can hear a gurgling whirling type of noise.  With PCM kept as PCM there is no such noise.  While this all happens often, it’s not always.  But because it only happens with DSD, it makes me guess it’s software related. Any ideas?

[Miska]

1 hour ago, DancingSea said:

I’ve been having an odd issue with HQPlayer 4.  Frequently when playing DSD files, during quiet parts I can hear a gurgling whirling type of noise.  With PCM kept as PCM there is no such noise.  While this all happens often, it’s not always.  But because it only happens with DSD, it makes me guess it’s software related. Any ideas?

 

What DAC did you have? Are you playing DSD64 files as such or are you upsampling those to higher rate?

 

[ambre]

1 hour ago, Miska said:

 

Are you on HQPlayer Desktop 4.2.3? When you set HQPlayer input to built-in microphone, then restart HQPlayer and try to play from the microphone. macOS should ask you whether you want to grant HQPlayer access to the microphone.

 I don't have a microphone connection on my Mac mini 2018 🤣 Only by means of an additional USB Mic this maybe doable?

 

As long as the sound is going through CoreAudio, it shouldn't matter where it is sourced from... So it shouldn't be working with the loopback either then. But this feature on macOS behaves strange sometimes.

 

 

[ambre]

I don't have a microphone connection on my Mac mini 2018 🤣 Only by means of an additional USB Mic this maybe doable?

[DancingSea]

39 minutes ago, Miska said:

 

What DAC did you have? Are you playing DSD64 files as such or are you upsampling those to higher rate?

 

 

DirectStream Junior.  I’m playing DSD64 files that are not upsampled any higher.

[Miska]

52 minutes ago, ambre said:

I don't have a microphone connection on my Mac mini 2018 🤣 Only by means of an additional USB Mic this maybe doable?

 

Selecting built-in input probably also works. For some reason selecting some other inputs doesn't always work. I just tested newest version 4.3.0 on macOS Catalina and got this when starting playback from the built-in microphone:

 

So at least for me it is working correctly. But given the amount of discussion on the net about these things, it may not always work. Please check with the newest version again though.

 

[Miska]

33 minutes ago, DancingSea said:

DirectStream Junior.  I’m playing DSD64 files that are not upsampled any higher.

 

You have Direct SDM enabled in HQPlayer's "DSD Sources" dialog? You could also try unchecking that setting and remodulating the files using ASDM5 modulator to see if you hear any difference.

 

It could be at least two problems;

1) Clocking problem may cause such effects, for example some Amanero USB interface firmware versions had such

2) Too much ultrasonic left-over noise at DSD64 and due to gear following the DAC it gets transformed back to audio band.

 

Are you by any chances using I2S input? Trying with USB instead would tell if the clock is behaving bad. To check (1).

 

To check (2) you would need some other amplifier, preferably something like headphone amp and headphones to check.

 

[ambre]

35 minutes ago, Miska said:

 

Selecting built-in input probably also works. For some reason selecting some other inputs doesn't always work. I just tested newest version 4.3.0 on macOS Catalina and got this when starting playback from the built-in microphone:

 

So at least for me it is working correctly. But given the amount of discussion on the net about these things, it may not always work. Please check with the newest version again though.

 

I donnot have a phyically microphone in my Mac mini 2018 compared with the earlier 2012 resp 2014 model. Or your IMac.

Left away by Apple for unclear reason?

Only by adding a separate usb mic this will maybe work