You are not logged in. Please login or register.
RME User Forum → DIGICheck → DigiCheck NG for Windows – first beta public release - now available
Thanks for the update. All seems to be working well here with DG 0.63b, Win 11 Pro and ADI Pro 2/4.
DigiCheck NG now starts and works with no errors on both my mainrig running windows 10 pro with dual ultrawide screens on a Nvidia GeForce GTX 760 and also on my crappy sidetable Lenovo Laptop.
This is why i chose RME. Solid hardware, softapps and excellent customer care.
I'm looking to get some extra I/O for recording and i just decided what make and model to get.
Thanks RME, keep the excellent work up!
Over and out!
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?
@lordadb
It's the same for me, as well ! Same error(and same line 207), slightly different GPU(R7 240).
If you read @MC 's post #100, it 's propably because of our older GPUs.
Note: other errors like '4' will not be addressed, they require more up to date graphics cards.
Myself, it 's time to upgrade to a newer GPU, anyway(I 'm thinking of a Sapphire RX 6750XT), but this might take a few months.
I 'm gonna be using the "old" DigiCheck until then, which I love anyway!
But maybe, error 207 is specific to AMD GPUs? Perhaps RME team could investigate! 
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.
You 're welcome, @lordadb!!
So, maybe there is nothing to do without upgrading the GPU
I think so, yes, but you never know!
Some time ago, there was not even a possibility for DC NG for Windows!
I'm a little scared because my system actually works well with Cubase 12 and 3 different type and resolution of screens
Yeah, I can relate! Mine works very well with Reaper and 2 monitors with different resolutions!
I, also, like the low power consumption of my system(CPU is a Ryzen 5 2600, 65Watts), but I think I 'll pull the trigger on a new GPU.
If you don't mind waiting, I 'll post here to report how it will go!
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!
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!
Did you also test without loopback ?
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.
It was entirely my environment.
I checked today and it was working fine.
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?
By Loopback active in the Main channel and looking at the corresponding input channel via Vector Scope.
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.
You read this thread? Then you know that error 4 and a 13 year old graphics card won't work.
By Loopback active in the Main channel and looking at the corresponding input channel via Vector Scope.
Thanks :-)
I guess I missed that part. Well, it happens. Thx
You read this thread? Then you know that error 4 and a 13 year old graphics card won't work.
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.
Colin OOOD wrote:NG is not running here:
"Returned 80070057 at 109"Ryzen 7 3700X 32GB 4.20GHz, Win10 x64
GeForce GT730 4GB (2020) - latest driver
Fireface 800 - latest driverSolution is in this thread.
v0.63 solved the problem, working fine now. Looking forward to more Instrument layouts!
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
Hi again
After finding and looking at the xml configuration file (I found it)
There is a weirdness going on.
If I set the digicheck to maximise on the third display I can get the correct values:
<val e="AlwaysOnTop" v="0"/>
<val e="PositionX" v="960.00000"/>
<val e="PositionY" v="1080.00000"/>
<val e="SizeX" v="1440.00000"/>
<val e="SizeY" v="900.00000"/>
But when I restart Digicheck NG it automatically sets to:
<Window00>
<WindowData>
<val e="AlwaysOnTop" v="0"/>
<val e="PositionX" v="944.00000"/>
<val e="PositionY" v="1072.00000"/>
<val e="SizeX" v="1456.00000"/>
<val e="SizeY" v="886.00000"/>
this bleeds onto the first and second display (above and left)
We'll have a look at this.
Thanks
It might be linked to this thread and users of windows explaining similar issues:
https://answers.microsoft.com/en-us/win … e4a?page=1
Cubase is fine, as are most other applications.
Wwise 2022.1.8 audio engine also spreads over to top display when opening child windows moved to second or third display which are positioned like this (all 4 displays):
1 (primary) 1920x1080
2 3 1440x900
4 (touch screen in desk) 1600x900
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 get a white screen at each start, can't load save file because i got a white screen also
I need to create a new window to have the graphics working
-------------------------------------
would be cool to have the possibility to launch only 2 instruments in the window instead of the minimum of 3
@lordadb
It's the same for me, as well ! Same error(and same line 207), slightly different GPU(R7 240).
If you read @MC 's post #100, it 's propably because of our older GPUs.MC wrote:Note: other errors like '4' will not be addressed, they require more up to date graphics cards.
Myself, it 's time to upgrade to a newer GPU, anyway(I 'm thinking of a Sapphire RX 6750XT), but this might take a few months.
I 'm gonna be using the "old" DigiCheck until then, which I love anyway!But maybe, error 207 is specific to AMD GPUs? Perhaps RME team could investigate!
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:
Even though it supports DirectX 12, the feature level is only 11_1, which can be problematic with newer DirectX 12 titles.
So, this explains why it cannot run DC NG !!
Digicheck NG just suddenly stopped working for me from one day to the next. I was working with it last night; turned on the studio computer this afternoon and it wouldn't display its window, with only a tiny Windows-minimum title bar showing at the top left of my primary monitor (saved window position should be on another monitor entirely).
New error message: "Returned 80070057 at 206".
Can anyone advise please?
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.
On Windows: when DC NG starts with a tiny window, then I can restore it by slightly increasing the window size by around 8 or 10 pixels to access the "File" menu.
Careful here, if the window is opened too wide, it crashes again, and you have to restart the procedure.
Within the file menu, there is an option to "open recent workspace".
This restores DC NG workspace completely and reliably.
Now close DC NG.
On the next start, it will restore windows sizes and positions and work properly again.
The easiest method to restore the tiny window: press Alt+F -> Open recent workspace. Done.
The easiest method to restore the tiny window: press Alt+F -> Open recent workspace. Done.
Good idea thanks.
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
Isn't it true that no ASIO software works for you? Is it a UCX or UFX? And is it shown in Device Manager, and Settings and TM FX open? Unplug the UFX/UCX from USB and replug. Something happens?
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!
Wow,
didn´t expected this.
Since working on Win and Samplitude more than on MacOs and Cubase
these days I am very very happy.
DC NG is working fine over here. God bless RME :-)
Is there an option for custom Channel Names ?
I use 2 Channels for metering my Studer 961(instead of the original Meterbridge)
and 2 Channels for Insert Returns from Langevin and TAB EQs.
Running Win10 Pro and MacOs 10.X on I7 Six Core Mac Mini.
MadiFace USB - AlphaLink
Cheers
Chris
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.
I like the look of the new DigiCheck much more as well, sadly it's not usable for me as all my Workspaces are based on the old horizontal mode. Is it planned to get the horizontal meters back ?
And this is?
While this is being discussed, are there any plans to add a horizontal display option to the R128 loudness meter as well?
RME User Forum → DIGICheck → DigiCheck NG for Windows – first beta public release - now available
Powered by PunBB, supported by Informer Technologies, Inc.