HQ Player

[wolft]

This is what I get:

 

Entpacken von hqplayer4desktop (4.19.0-88) über (4.19.0-88) ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von hqplayer4desktop:
 hqplayer4desktop hängt ab von libmicrohttpd12 (>= 0.9.50); aber:
  Paket libmicrohttpd12 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5charts5 (>= 5.9.0~rc); aber:
  Paket libqt5charts5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5core5a (>= 5.12.2); aber:
  Paket libqt5core5a ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5gui5 (>= 5.3.0) | libqt5gui5-gles (>= 5.3.0); aber:
  Paket libqt5gui5 ist nicht installiert.
  Paket libqt5gui5-gles ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5network5 (>= 5.8.0); aber:
  Paket libqt5network5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5positioning5 (>= 5.6.0); aber:
  Paket libqt5positioning5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5qml5 (>= 5.12.5); aber:
  Paket libqt5qml5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quick5 (>= 5.6.1) | libqt5quick5-gles (>= 5.6.1); aber:
  Paket libqt5quick5 ist nicht installiert.
  Paket libqt5quick5-gles ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quickcontrols2-5 (>= 5.7.1); aber:
  Paket libqt5quickcontrols2-5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webchannel5 (>= 5.6.1); aber:
  Paket libqt5webchannel5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webengine5 (>= 5.7.1); aber:
  Paket libqt5webengine5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webenginecore5 (>= 5.7.1); aber:
  Paket libqt5webenginecore5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5widgets5 (>= 5.2.0~alpha1); aber:
  Paket libqt5widgets5 ist nicht installiert.
 hqplayer4desktop hängt ab von libusb-0.1-4 (>= 2:0.1.12); aber:
  Paket libusb-0.1-4 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5gui5; aber:
  Paket libqt5gui5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5script5; aber:
  Paket libqt5script5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5sql5; aber:
  Paket libqt5sql5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5svg5; aber:
  Paket libqt5svg5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quick5; aber:
  Paket libqt5quick5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webview5; aber:
  Paket libqt5webview5 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick2; aber:
  Paket qml-module-qtquick2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtgraphicaleffects; aber:
  Paket qml-module-qtgraphicaleffects ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtqml-models2; aber:
  Paket qml-module-qtqml-models2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-controls; aber:
  Paket qml-module-qtquick-controls ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-controls2; aber:
  Paket qml-module-qtquick-controls2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-dialogs; aber:
  Paket qml-module-qtquick-dialogs ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-layouts; aber:
  Paket qml-module-qtquick-layouts ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-templates2; aber:
  Paket qml-module-qtquick-templates2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-window2; aber:
  Paket qml-module-qtquick-window2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtwebengine; aber:
  Paket qml-module-qtwebengine ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtwebview; aber:
  Paket qml-module-qtwebview ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-qmlmodels; aber:
  Paket qml-module-qt-labs-qmlmodels ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-folderlistmodel; aber:
  Paket qml-module-qt-labs-folderlistmodel ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-platform; aber:
  Paket qml-module-qt-labs-platform ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-settings; aber:
  Paket qml-module-qt-labs-settings ist nicht installiert.

dpkg: Fehler beim Bearbeiten des Paketes hqplayer4desktop (--install):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
Trigger für desktop-file-utils (0.26-1ubuntu3) werden verarbeitet ...
Trigger für gnome-menus (3.36.0-1ubuntu3) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 hqplayer4desktop

 

[ericuco]

7 minutes ago, wolft said:

This is what I get:

 

Entpacken von hqplayer4desktop (4.19.0-88) über (4.19.0-88) ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von hqplayer4desktop:
 hqplayer4desktop hängt ab von libmicrohttpd12 (>= 0.9.50); aber:
  Paket libmicrohttpd12 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5charts5 (>= 5.9.0~rc); aber:
  Paket libqt5charts5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5core5a (>= 5.12.2); aber:
  Paket libqt5core5a ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5gui5 (>= 5.3.0) | libqt5gui5-gles (>= 5.3.0); aber:
  Paket libqt5gui5 ist nicht installiert.
  Paket libqt5gui5-gles ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5network5 (>= 5.8.0); aber:
  Paket libqt5network5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5positioning5 (>= 5.6.0); aber:
  Paket libqt5positioning5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5qml5 (>= 5.12.5); aber:
  Paket libqt5qml5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quick5 (>= 5.6.1) | libqt5quick5-gles (>= 5.6.1); aber:
  Paket libqt5quick5 ist nicht installiert.
  Paket libqt5quick5-gles ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quickcontrols2-5 (>= 5.7.1); aber:
  Paket libqt5quickcontrols2-5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webchannel5 (>= 5.6.1); aber:
  Paket libqt5webchannel5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webengine5 (>= 5.7.1); aber:
  Paket libqt5webengine5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webenginecore5 (>= 5.7.1); aber:
  Paket libqt5webenginecore5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5widgets5 (>= 5.2.0~alpha1); aber:
  Paket libqt5widgets5 ist nicht installiert.
 hqplayer4desktop hängt ab von libusb-0.1-4 (>= 2:0.1.12); aber:
  Paket libusb-0.1-4 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5gui5; aber:
  Paket libqt5gui5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5script5; aber:
  Paket libqt5script5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5sql5; aber:
  Paket libqt5sql5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5svg5; aber:
  Paket libqt5svg5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5quick5; aber:
  Paket libqt5quick5 ist nicht installiert.
 hqplayer4desktop hängt ab von libqt5webview5; aber:
  Paket libqt5webview5 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick2; aber:
  Paket qml-module-qtquick2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtgraphicaleffects; aber:
  Paket qml-module-qtgraphicaleffects ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtqml-models2; aber:
  Paket qml-module-qtqml-models2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-controls; aber:
  Paket qml-module-qtquick-controls ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-controls2; aber:
  Paket qml-module-qtquick-controls2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-dialogs; aber:
  Paket qml-module-qtquick-dialogs ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-layouts; aber:
  Paket qml-module-qtquick-layouts ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-templates2; aber:
  Paket qml-module-qtquick-templates2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtquick-window2; aber:
  Paket qml-module-qtquick-window2 ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtwebengine; aber:
  Paket qml-module-qtwebengine ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qtwebview; aber:
  Paket qml-module-qtwebview ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-qmlmodels; aber:
  Paket qml-module-qt-labs-qmlmodels ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-folderlistmodel; aber:
  Paket qml-module-qt-labs-folderlistmodel ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-platform; aber:
  Paket qml-module-qt-labs-platform ist nicht installiert.
 hqplayer4desktop hängt ab von qml-module-qt-labs-settings; aber:
  Paket qml-module-qt-labs-settings ist nicht installiert.

dpkg: Fehler beim Bearbeiten des Paketes hqplayer4desktop (--install):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
Trigger für desktop-file-utils (0.26-1ubuntu3) werden verarbeitet ...
Trigger für gnome-menus (3.36.0-1ubuntu3) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 hqplayer4desktop

 

Did you issue: sudo apt install -f  which brings in any dependencies 

[Pratfall]

Hello, I wrote some time ago about an issue of mine, that Client would disconnect on random occations while streaming Qobuz, particularly when the source is 16 bit (?). Meanwhile, I had no issues with Roon or any of the streaming services. I thought I fixed it simply by logging out from Qobuz and then in again, as I could play multiple albums in a row, but not so.

 

I have made sure to allow everything possibly related in the Windows Firewall; I have reinstalled the latest version of HQP Desktop on different locations, tried every PCM filter and dither as well as lowering the sample rate - nothing - except when I switched drivers. ASIO does not disconnect (but has other glitches unrelated to this problem) while WASAPI does.

 

Now I have the 2Qute DAC, and I notice that the drivers are very old. They seem to have been made for Windows 7 while I'm on 10. Again, WASAPI works on everything except Client for me. Is it definitely the driver, and can I try anything else besides buying a new DAC with more recent drivers? Any thoughts would be appreciated.

 

Thanks.

[wolft]

Hello,

so the problem with hqplayer4desktop 4.19.0 is solved. I repair ubuntu 22.04 and now hqplayer4desktop 4.19.0 runs.

thanks for the help.

Wolfgang

[Miska]

13 minutes ago, Pratfall said:

Now I have the 2Qute DAC, and I notice that the drivers are very old. They seem to have been made for Windows 7 while I'm on 10. Again, WASAPI works on everything except Client for me. Is it definitely the driver, and can I try anything else besides buying a new DAC with more recent drivers? Any thoughts would be appreciated.

 

One relatively inexpensive way to work around drivers is to use a NAA. RaspberryPi4 is not very expensive. And booting my NAA image on it is relatively simple and straightforward.

 

Chord's USB interface can be tricky though, so YMMV.

 

[Guf Gufler]

Here’s the latest, I have deleted all the apps, re installed, looks like it’s connecting but still no music.  I have deleted the Roon ready in case thats giving a problem. open to hearing more suggestions. Thanks for all the help. 

[Miska]

5 hours ago, Guf Gufler said:

Here’s the latest, I have deleted all the apps, re installed, looks like it’s connecting but still no music.  I have deleted the Roon ready in case thats giving a problem. open to hearing more suggestions. Thanks for all the help. 

 

Log from the NAA side would be interesting to see...

 

[Quadman]

20 hours ago, Miska said:

you shouldn't use HQPlayer Settings-dialog.

And to think for years and years this is exactly what I did, use HQP settings dialog.  Now for filters and modulators I use HQPDcontrol, but I still use the HQP settings dialog when I change Rates, say DSD1024 to DSD512, which much less frequent then filter or modulator changes.

[Guf Gufler]

8 hours ago, Miska said:

 

Log from the NAA side would be interesting to see...

 

This? Dac Diagnostics?

[Mike Rubin]

13 minutes ago, Guf Gufler said:

This? Dac Diagnostics?

I assume Miska wants the NAA error log.  Unfortunately, I am pretty certain that you cannot access it in Sonicorbiter. 

[Guf Gufler]

I disconnect the optical rendu and usb directly from  sonictranspoter to the dac, set the ALSA and its working but not great. Picking up some kind of fluttering noise. I’ll keep at it. 

[Carlos269]

On 2/13/2022 at 12:50 PM, Bertel said:

I bought the SMSL M500 MkII and received it on Friday, but it has strange issues with occasional electrical noise (low level stuff that sounds like quantisation noise or so, plus high pitched squeal at low volume at the end of tracks at fade out), although I feed it DSD512 only - guess that‘s what you mean with „it misbehaves“… 

 

@Miska have you tested and measured any ESS9038Pro based DAC yet which works without issues and quirks and plays DSD512 without any flaws? I like the very clean and transparent sound a lot and definitely want such a DAC in my collection, but haven‘t found properly engineered units yet it seems…

This is exactly what I’m hearing with my LampizatOr DSD-Only (chipless) DAC with Amanero Combo384 USB interface card, exactly the same noise that Bertel describes in his post. The noise is most noticeable at the end of track and the noise goes away when HQPLAYER goes in active, either through a stop or pause. This issue is not there at DSD256. My dac has played flawlessly at DSD512 with the exact same settings for months and all of the sudden I’m getting this quantization swirling noise every time HQPLAYER opens the USB port and then it stops to a dead silence when HQPLAYER releases the USB port. I reverted back to older HQP Desktop versions and the issue persists.
 

I thought that it was GPU noise from the PC coupling through the USB cable or ground-loop induced noise because of lack of galvanic isolation but after spending money on the various iFi digital enhancer and ground-loop breaking products the issue remains

 

Any ideas? Was Bertel’s issue resolved? What was the root-cause or fix for it? I’m having the exact same issue. As I said before it worked flawlessly for months but all of the sudden this noise is driving me crazy. One other data point, if I don’t use my setup for a few days the issue is not there when I first start playing music but after about 15 minutes of playing it shows up and does not go away unless I shut everything down and de-energize the dac and disconnect the  USBcable.

 

Miska/Jussi and others, all help resolving this issue is greatly appreciated.

 

Could some software have enabled a Spread-Spectrum setting and that is what is causing this noise at DSD512? How can I check if any Spread-Spectrum settings are enabled? Or does HQPLAYER inhibit those types of noises from getting into the DSD stream?

[Bertel]

2 hours ago, Carlos269 said:

Was Bertel’s issue resolved? What was the root-cause or fix for it? I’m having the exact same issue. As I said before it worked flawlessly for months but all of the sudden this noise is driving me crazy. One other data point, if I don’t use my setup for a few days the issue is not there when I first start playing music but after about 15 minutes of playing it shows up and does not go away unless I shut everything down and de-energize the dac and disconnect the  USBcable.

 

Well, the issue I had is likely due to the implementation of the ESS9038PRO chip, as Miska had pointed out. I also tried the SMSL SU-9n which behaves exactly the same (fine with DSD256, noise with DSD512, as well as not being able to play 48k at the right speed). I now have the VMV D1se which works fine and doesn't have these issues.

 

As your Lampi doesn't use the ESS chip, I don't think there's much to learn and transfer from my example. Everything up to and including DSD1024 plays fine with my Holo May KTE, so I don't think there's any influence of the upstream part of my chain (optical, Signature Rendu, USB) to this ESS chip issue.

[Miska]

12 hours ago, Guf Gufler said:

I disconnect the optical rendu and usb directly from  sonictranspoter to the dac, set the ALSA and its working but not great.

 

Seems to be some kind of network problem, or a problem in the Rendu. Without netwokaudiod log from the Rendu it is hard to say which one.

 

How is the sonicTransporter connected to the Rendu? In detail...

 

12 hours ago, Guf Gufler said:

Picking up some kind of fluttering noise. I’ll keep at it. 

 

This you can likely get fixed with USB isolators like Intona.

 

[Zauurx]

9 hours ago, Carlos269 said:

This is exactly what I’m hearing with my LampizatOr DSD-Only (chipless) DAC with Amanero Combo384 USB interface card, exactly the same noise that Bertel describes in his post. The noise is most noticeable at the end of track and the noise goes away when HQPLAYER goes in active, either through a stop or pause. This issue is not there at DSD256. My dac has played flawlessly at DSD512 with the exact same settings for months and all of the sudden I’m getting this quantization swirling noise every time HQPLAYER opens the USB port and then it stops to a dead silence when HQPLAYER releases the USB port. I reverted back to older HQP Desktop versions and the issue persists.

...

Not a problem that can be solved by the firmware of the Amanero card ?

 

https://github.com/lintweaker/xmos-native-dsd/issues/12#issuecomment-860813982

[Miska]

9 hours ago, Carlos269 said:

Any ideas? Was Bertel’s issue resolved? What was the root-cause or fix for it? I’m having the exact same issue. As I said before it worked flawlessly for months but all of the sudden this noise is driving me crazy. One other data point, if I don’t use my setup for a few days the issue is not there when I first start playing music but after about 15 minutes of playing it shows up and does not go away unless I shut everything down and de-energize the dac and disconnect the  USBcable.

 

Miska/Jussi and others, all help resolving this issue is greatly appreciated.

 

That happens with various DACs when the clocking is going wrong. I would say it is likely related to the Amanero USB interface.

 

Have you tried with another USB cable? 

 

Please also pay attention if this is related to 44.1k base vs 48k base output rate?

 

9 hours ago, Carlos269 said:

Could some software have enabled a Spread-Spectrum setting and that is what is causing this noise at DSD512? How can I check if any Spread-Spectrum settings are enabled? Or does HQPLAYER inhibit those types of noises from getting into the DSD stream?

 

No, even if it would, it wouldn't have such implications because computer clocking is not related to DAC clocking in any way.

 

[Carlos269]

57 minutes ago, Miska said:

 

That happens with various DACs when the clocking is going wrong. I would say it is likely related to the Amanero USB interface.

 

Have you tried with another USB cable? 

 

Please also pay attention if this is related to 44.1k base vs 48k base output rate?

 

 

No, even if it would, it wouldn't have such implications because computer clocking is not related to DAC clocking in any way.

 

Miska my settings are for 48K base output rate. This morning I started to narrow down the root cause and made great progress towards resolving the issue.
 

I disabled CUDA offloading and it made no difference. This told me that my previous theory about GPU borne noise is not the culprit.

 

I then followed the Spread-Spectrum theory and looked for the CPU Host Clock Control] setting to change it to [Manual] to disable "Spread Spectrum", but could not find the setting on my Z690 Xtreme BIOS.

 

I then noticed that the noise correlated with the fans speed and CPU temperature going up at start of HQPLAYER playback and coming down after HQPLAYER playback is halted, when the tracks start and then goes away when the tracks stop, after the noise swirls down to complete silence. I went into the Gigabyte BIOS to see if I could find the performance mode switching setting for the CPU and found that Gigabyte has a setting in the Z690 BIOS called “CPU Upgrade” with setting 3 options: 1. Default, which is what it was set to. 2. Gaming Mode, which disables the E-Cores, and 3. MAX-Performace, which boosts the P-Cores and retains the E-Cores on the Intel 12900-KF CPU. I changed this setting from Default to MAX-Performance and HQPlayer and the DAC have been playing DSD512 x48, with 7ECv2 modulator and Gauss-XLA filter, for over 2 hours without issues. I hope this issue has been resolved by keeping the CPU from actively transitioning between speeds during HQPLAYER playback.

[Andrey Boldakov]

10 minutes ago, Carlos269 said:

DSD512 x48, with 7ECv2 modulator and Gauss-XLA filter

That is exactly my lovely settings...

Maybe you know, does it possible to go for DSD1024 with those settings at this planet?

Maybe i9-12900KS with GTX 3090ti?

[El Guapo]

2 hours ago, Andrey Boldakov said:

Maybe you know, does it possible to go for DSD1024 with those settings at this planet?

Just done my initial testing for Ubuntu Server 22.04 "Jammy Jellyfish" with HQPlayer Embedded 4.32. Good news is ASDM7ECv2 finally usable for DSD1024. My current listening combo is 1x gauss-long / Nx gauss with ASDM7ECv2 and fixed rate to 45MHz. 

 

All P-cores fixed at 5.3GHz and ring fixed at 4.4GHz.

 

44.1 -> gauss-long + ASDM7ECv2 -> DSD1024

 

192 -> gauss + ASDM7ECv2 -> DSD1024

 

Performance result

 

BTW I personally still don't think 12900KS would help. Wait for 13th gen i9 is more practical.

[sledwards]

Will be helping a friend build an HQPlayer machine this weekend (i9-12900K and 3080Ti GPU) and was leaning towards Ubuntu Desktop for OS based upon his Linux experience level. Any reason I should not use 22.04 LTS instead of 20.04? Is the initial Jammy release of desktop CUDA compatible?

[El Guapo]

3 minutes ago, sledwards said:

Is the initial Jammy release of desktop CUDA compatible?

I'm not sure about 22.04 Desktop but Server is fully CUDA compatible.

 

4 minutes ago, sledwards said:

Any reason I should not use 22.04 LTS instead of 20.04?

I personally suggest 22.04. Better support for Z690.

[sledwards]

2 hours ago, El Guapo said:

I'm not sure about 22.04 Desktop but Server is fully CUDA compatible.

Does the jammy version of embedded (hqplayerd_4.32.0-134avx2_amd64.deb) require Rocm to function with CUDA?

[privacyguy123]

Nothing but strange bugs since most recent update - tried to roll back to 4.18.1 but problems persists.

 

After about 20 min NAA sound quality becomes unlistenable, pops and crackles as if the buffer setting is not high enough all of a sudden - can't understand why that would change if it's always been fine at "Default" up to this point. No idea how to troubleshoot.

 

EDIT: Actually 1 thing is different, CUDA updated to 11.7.

[Miska]

3 hours ago, sledwards said:

Will be helping a friend build an HQPlayer machine this weekend (i9-12900K and 3080Ti GPU) and was leaning towards Ubuntu Desktop for OS based upon his Linux experience level. Any reason I should not use 22.04 LTS instead of 20.04? Is the initial Jammy release of desktop CUDA compatible?

 

Yes, 22.04 should be fine for such CPU (AVX2 support). And yes, CUDA is supported by Jammy build of HQPlayer Desktop and Embedded. Otherwise I wouldn't have made the release. Both built using fresh official Nvidia support for Jammy, with CUDA 11.7.

 

[Miska]

43 minutes ago, privacyguy123 said:

Nothing but strange bugs since most recent update - tried to roll back to 4.18.1 but problems persists.

 

After about 20 min NAA sound quality becomes unlistenable, pops and crackles as if the buffer setting is not high enough all of a sudden - can't understand why that would change if it's always been fine at "Default" up to this point. No idea how to troubleshoot.

 

EDIT: Actually 1 thing is different, CUDA updated to 11.7.

 

On Ubuntu 22.04? What are you running on NAA?

 

I have also updated default settings. So if something is coming out of default values, those may be different. But if configurations have been stored in HQPlayer earlier and not reset on the update, then those don't change as result of update.

 

Yes, CUDA 11.7 came out meanwhile and it is first version to support Jammy.