Cool

Thanks! FireWire devices were not supported correctly. I changed the first post from v 0.80 to v 0.81 which fixes this.

Of course. Why you ask?

v0.81 still not working for me, also checked by selecting inputs 1/2 and loopback on and still no signal in Digicheck

Works for us with a Fireface 800. I wonder if you selected the FF800 in the Options / Audio Device Setup, then selected the input channels that you want to use by a right click on the instrument.

If you did this then please send us the workspace file so we can check all settings.

It is somehow not working for me, I don't know why. I open the App and it always tells me: NO CONFIGURED AUDIO DEVICE, GO TO AUDIO DEVICE SETUP.  So I go to AUDIO DEVICE SETUP, check IN USE, choose the Multiface ii from the drop-down menu and then click OK. Back on the app, when I try to ENABLE AUDIO PROCESSING, it comes always the same NO CONFIGURED AUDIO DEVICE, GO TO AUDIO DEVICE SETUP. I just won't work.

Could you help me? Would be much appreciated.

All the best,
Ernesto

awesome! thank you!

Check the inputs first before trying Loopback.

Thank you for your prompt advice.

Sorry but it is still not working..
I checked DigiCheck inputs first before trying Loopback.

Thank you for your response.
I mean there is still no signal in DigiCheck.
The title of DigiCheck window is "DigiCheck NG - processing active: fireface UC Mac". No popup window.

That was a simple fix. The name 'Hammerfall DSP Multiface (serial number)' was simply too long (shame on us). This issue is not limited to the Multiface, it depends on how long the shown serial number is. Version 0.82 (first post updated) fixes this now.

where should I send you the workspace? should I upload to wetransfer and put the link here?

Also tried v0.82 ... still nothing

trying to have some audio signal ...

Yes, please.

Thanks again, we're liking DigiCheck NG. We transitioned from Mojave to Catalina and worked around our remaining concerns:
1. Missing hardware level metering. Additional routing and loopback (Playback 01-32 -> Output 33-64 -> Input 33-64) allows monitoring input and playback during live broadcasts.
2. Settings seem volatile (e.g. turn on/off K-metering, close/reopen a window?). Designed workspace and settings files to (re)load studio and mobile configurations.
(3. tangent) Missing (32-bit) MIDI Remote. Lost remote control of OctaMic XTC sync/routing/headphones and M-32 DA sync/routing/fan. Thankfully, those change infrequently.

Thank you for your response!

The current firmware version is v138. The driver was v3.18, so I just updated to v3.19.
But still no signal in DG NG.

I also checked the Interface Statistics. The load column shows 3%.

Thank you! Love RME.

couple intriguing things I'd like to ask:

1) how is buffer size treated, within MacOS CoreAudio? I thought MacOS default is 512, here in DigiCheck 256 is default which can be changed, and most DAWs offer various buffer settings too - will those affect visualization, latency or overall performance of DigiCheck? I mean, I would guess DigiCheck is reading RME internal DSP, not acting as audio application, right? I don't see any change in % shown in Interface Statistics when changing buffer either

2) is it possible to monitor output without using Loopback? I've been testing new DigiCheck with multiple RME interfaces simultaneously and it gets quickly messy when using all Multichannel meters which are actually showing Loopbacks and physical inputs only, while TotalMix is literally flooded with output meters only (since it cannot display Loopback inputs)
see, this is what I mean for ex.:

3) one little inconvenience - if using right-click in MacOS (not enabled default though), I can right-click DigiCheck while inactive and whatever window is opened (Type Selection, Input, Appearance etc..) it doesn't pop up in front, just bounces in MacOS dock;
on the other hand if DigiCheck is window is active in front, right-clicking and opening any aforementioned element does show it in front

4) bug I found - in Audio Device Setup, by default it messes up with multiple interfaces somehow, so later if I (re)assign various RME devices, but leave some of them unticked (=not "In Use") I still get error "Same Audio Device can not be assigned twice!") see pic:

Yeah! I love it!
Thanks RME for that great tool … finaly! This Version of DC NG is nearly perfect to me!

@Mathias: Thanks a lot for your support in this Forum!

Beside at noticed: The App Logo is cool! Now it matches the Totalmix Logo! – But, what about the "Fireface USB Settings" Logo ;-)
I'm joking! There are more important things!

Hi!

Any chance we will see Bit Statistics & Noise !?

and a big thank you RME for this new DigiCheck NG :-)

regards S-EH

Yes, the smaller the buffers the more quick and fluid are the level meters. That's not different to ASIO Windows. 256 is fully sufficient IMHO.

No. This is CoreAudio only. Hardware level meters would be different.

We plan to add this later on.

Changed in version 0.84.

I wouldn't call this a bug. It is a useless entry/choice performed by the user. Anyway, we added a routine to remove this doubled entry, so problem fixed.

Very nice.
Looking forward to the bit info being added.

Yes!
That was the solution, thank you!