Hi,

I can't make it work from day 1. See the screen.

• Windows 11

• Fireface 802 (last drivers / firmware)

• AMD Ryzen 7 5800X

• AMD Radeon R7 250

All the system is up to date.
Any suggestion? Something to check?

Thank you @MetalHeadKeys.

So, maybe there is nothing to do without upgrading the GPU. I'm a little scared because my system actually works well with Cubase 12 and 3 different type and resolution of screens. Others have some issue here and there and I need to stay operative for my work.

Everything is working great on windows 11 with adi 2 dac pro fs r and loopback option.
Cant wait for the remote app that you are working on for adi 2. Thank you!

I felt that the vector audio scope was flickering, so I recorded the screen.
This is a video of Digicheck NG recording and sending one frame at a time.
In my environment, Digicheck NG seems to stop every 3-4 frames and the vector audio scope is getting darker.

https://youtu.be/EzHniNgIQkM

Hi all. Apologies if this has already been discussed -  I couldn't find it via search.

I'm using NG with an HDSPe AIO.

Is there a way to get the vector audio scope to be post the "mono" button on the total mix "main / control room " section?

So, if I click "mono" in this section of total mix, the vector audio scope shows a mono display?

Hi, I'm really excited about this product. I just installed beta win_O63b and got error "Returned 887A0004 at 4". My system spec is

Raydat with word clock. external converters.
Asus Prime Delux ii mobo
Processor    Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz   3.00 GHz
Installed RAM    256 GB (256 GB usable)
Device ID    817F292D-C7FD-45D7-9268-642982C37419
Product ID    00330-80000-00000-AA732
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display
Edition    Windows 11 Pro
Version    22H2
Installed on    11/3/2022
OS build    22621.2070
Experience    Windows Feature Experience Pack 1000.22659.1000.0

My GPU AMD Radeon HD 5800 Series. The driver is legacy if that is a factor.

Thanks :-)

I have seen request for full color configuration but I think that's too much complexity.  What I think would be nice is a saturation or gamma type control for each instrument so the user can back off on the brightness a bit.

HI there, thanks RME for this update. Whenever I open Digicheck NG to be maximised full screen (maximised not F5 hotkey FS) it does not remember the setting and the edge strays onto another multi display monitor slightly. (4 x monitors)

Other applications do not seem to have this problem. Is there a config' file I can edit? cant seem to find one!

It could be the windows monitor arrangemnet utility causing the issue and Digicheck cant remember the screen edges locations?

Many Thanks

We'll have a look at this.

Would it be possible to implement an "always on top" feature for the next version? I'd appreciate it if the meters were always visible when using full-screen applications, such as DAWs. I'm sure other use cases could benefit from this as well.
Other than that, Digicheck NG has completely replaced the previous version for me without any stability issues. Well done!

I, finally, managed to switch to a GPU that can run DigiCheck NG in all its glory!!
It is not the Sapphire RX6750XT, but another Sapphire 200 series!! Same driver with my previous one, but different model !!

So, I upgraded from a Sapphire R7 240 https://www.techpowerup.com/gpu-specs/r … -240.c2463
to a Sapphire R7 260X OC  https://www.techpowerup.com/gpu-specs/s … 1-gb.b2717

I tested both cards with both my systems, one with the HDSP 9632(older components, online, fully updated, FW:155, Drv: 4.46)
and the other with the DigiFace USB(newer components, offline, early Win10 Pro build, FW:18, Drv: 0.9827)

DigiCheck NG works on both systems with the R7 260X !!
The difference between them is that the 240 is a PCIe 3.0 x 8, and the 260X is PCIe 3.0 x 16.
And I, also, found this for the 240:

So, this explains why it cannot run DC NG !!

DC NG crashes when the window is minimized to absolute minimum - this is known and on our list. Typically that window size does not get stored. In case it did get stored and you can't start DC NG anymore delete the file "C:\Users\UserName\AppData\Local\DigiCheckNG\lastState.Analyser.xml"

If you had set up a complicated window and forgot to save it as Workspace then open the file with an editor and replace these lines as follows:

<val e="AlwaysOnTop" v="0"/>
<val e="PositionX" v="547.00000"/>
<val e="PositionY" v="430.00000"/>
<val e="SizeX" v="955.00000"/>
<val e="SizeY" v="618.00000"/>

Then it should work again.

The easiest method to restore the tiny window: press Alt+F -> Open recent workspace. Done.

Unfortunately DigiCheck NG 0.63 doesn't work for me:

No Audio Devices found.

I have a UFX, Driver 1.249, HW 361, running on Win 10 64

Older DigiCkeck version don't work either, they crash after selecting the path for recording.

The procedure below didn't help either. Any ideas?

COLD reboot, Device Manager- show hidden devices, uninstall UCX driver,
COLD reboot - check device manager if driver is really out
COLD reboot - install latest usb driver
COLD reboot - connect UCX

More problems showed up: I just found out, that Cubase and Samplitude now don't show a RME Asio driver anymore. Looks like either DigiCheck or my attempts to re-install the driver killed something.
No luck so far.

My DP Log:
INFO:   ****************************************
INFO:   03/01/2024 22:15:23
INFO:   Product Version 2.1.0.0.
INFO:   Version: 6.0.6000
INFO:   Platform ID: 2 (NT)
INFO:   Service Pack: 0.0
INFO:   Suite: 0x0100, Product Type: 1
INFO:   Architecture: AMD64.
INFO:   Interactive Windows Station
INFO:   Command Line: 'C:\Users\Mat\AppData\Local\Temp\rme\dpinst64.exe'
INFO:   DPInst is not multi-lingual.
INFO:   ****************************************
INFO:   Current working directory: 'C:\Users\Mat\AppData\Local\Temp\rme'
INFO:   Running on path 'C:\Users\Mat\AppData\Local\Temp\rme'
INFO:   User UI Language is 0x407.
INFO:   Install option set: Force install if driver is not better.
INFO:   Install option set: uninstall will be set to delete driver binaries.
INFO:   Found driver package: 'C:\Users\Mat\AppData\Local\Temp\rme\fireface_usb.inf'.
INFO:   Preinstalling 'c:\users\mat\appdata\local\temp\rme\fireface_usb.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
SUCCESS:c:\users\mat\appdata\local\temp\rme\fireface_usb.inf is preinstalled.
INFO:   RETURN: DriverPackagePreinstallW  (0x0)
INFO:   ENTER:  DriverPackageGetPathW
INFO:   RETURN: DriverPackageGetPathW  (0x0)
INFO:   ENTER:  DriverPackageInstallW
INFO:   Installing INF file 'c:\users\mat\appdata\local\temp\rme\fireface_usb.inf' (Plug and Play).
INFO:   Looking for Model Section [Devices.NTAMD64]...
INFO:   Installing devices with Id "USB\VID_2A39&PID_3FC8&REV_0001" using INF "C:\Windows\System32\DriverStore\FileRepository\fireface_usb.inf_amd64_f89bc84f40f3869c\fireface_usb.inf".
INFO:   Will force install because driver is not better and force flag is set.
INFO:   ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS:RETURN UpdateDriverForPlugAndPlayDevices.
INFO:   Installation was successful.
SUCCESS:Install completed
INFO:   RETURN: DriverPackageInstallW  (0x0)
INFO:   Successfull installation of 'c:\users\mat\appdata\local\temp\rme\fireface_usb.inf'.
INFO:   Created entry in Add or Remove Programs for 'C:\Windows\System32\DriverStore\FileRepository\fireface_usb.inf_amd64_f89bc84f40f3869c\fireface_usb.inf'.
INFO:   Machine will have to be rebooted to complete installation.
INFO:   Returning with code 0x40000001
INFO:   03/01/2024 22:15:39

The InProcServer part in the Registry loks like this:

Guess there is something missing?

The driver still looks fien in the device manager, but no ASIO Driver, no matter how many times I reboot or unplug.

EDIT: I managed it to make the ASIO driver working again by manually adding the paths in the registry to "fireface_usb_asio.dll" + "fireface_usb_asio64.dll" (found the proper settings on my laptop)
according to Matthias' post here: https://forum.rme-audio.de/viewtopic.php?id=38586

But once I've installed Digicheck 0.63 Beta again, the ASIO was gone again and I even couldn't fix it anymore by "hacking" the Registry!

But then after the following procedure everything works like a charm:

-unplug the UFX
-uninstalled Digicked & RME Driver (remove programs)
-deleted hidden Fireface in Device Manager
-Reboot
-Windows In-Place upgrade
-Re-Install Fireface driver
-Re-install Digicheck 0.63 Beta
-still works, even after switching everything off and reboot!!

Looks like there were some issues for the RME driver when writing to the registry!?

Thanks Matthias for your help anyway!

I like DigiCheck NG much better than the previous version. Now it looks like modern and aesthetically pleasing software. I went through all the parameters and settings, and I think that at the moment everything is very good. Thanks RME for a great job! Looking forward to future news.

And this is?

https://forum.rme-audio.de/viewtopic.ph … 16#p202316

DigiCheck NG has now been released as version 0.90 on our website, including installer and these latest changes:

- help updated

- added Quick Workspace (hotkey W) function

- fixed crash when dragging the window to a minimum size

- some smaller improvements

Direct link: https://www.rme-audio.de/downloads/digi … in_090.zip

Having 2 Madi FX I have an issue with selection of channels. The maximum amount of channels you can select is 200. With 2 Madi FX you'll need almost 400 channels. Would that be possible?

Digicheck NG 0.90 public release isn't working correctly on my Windows11 Pro.

It adds a wrong extra key directly under HKCU "Software/RME/DigiCheck NG" (with forward slashes), while it does correctly add  HKCU\Software\RME\DigiCheck NG.

Apart from that I cannot select an audio device. I recall it did with the UC attached, but not with the UCX II.

* AMD Ryzen9 5900X
* AMD Radeon RX 7800XT

Yes first time installing NG.

When I had both UC and UCX II attached to my pc, I recall that NG said "ASIO Fireface USB". Even in the title bar and under Audio Settings.

I've reinstalled NG after moving the UC to another pc, but the application doesn't see the UCX II.

Edit: on the other pc where the UC is connected, I did a fresh install of Digicheck NG 0.90 and it works immediately (and that's a Windows Server 2022) ;-)

Edit2: it was missing the ASIO driver entirely...sigh. I probably uninstalled that in the process of adding the UCX II. Did not have to install the driver. It is the same driver as the UC of course.

Thanks Matthias!!

And for the great devices you and your team created, in my case since 1999.

Sorry if it's been discussed before, but why does the Bit Statistics not support the 32 bit depth?

I also would love to see a 'Always on top' option, it's very handy to have.

I get that. But it can also analyze software playbacks, and I use that with the ADI-2 DAC, which runs at 32 bits. Anyways.