#Os x preview for windows update#
#Os x preview for windows mac#
#Os x preview for windows windows#

Details of 0.84 see here:Д¬ouple intriguing things I'd like to ask:ДЎ) 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Дў) 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)ДЈ) 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 Update: this text and link has been updated from 0.81 to 0.82 to 0.84 to 0.85.

We hope this will be a stable, first version for an official public release, a solid base for further additions and extended functionality.

Please note that this setting does not become active until the app is exit and started again. The new option will use the directly connected graphics card, no matter which one that is. Instead of giving you three options (select Intel manually, select nVidia/ATI manually, Auto) we opted for the easiest one. This additional transfer step seems to cause a slightly worse graphics performance. Everything rendered on nVidia/ATI is first transferred to Intel, then send to the screen. The reason is that our MacBook's display is directly connected to the Intel graphics card. Examining the situation on our MacBooks we found that letting DC run on the integrated Intel graphics is more efficient (and completely frees up the other one).

#Os x preview for windows mac#

If your Mac also has an nVidia or ATI graphics card, then DC usually runs on these. If you have only one (Intel) then this option is greyed out - nothing to select. This is an automated version of selecting the graphics card where DigiCheck runs on. Added an option to let DigiCheck run on the GPU that is directly connected to the display Added a note when Metal is not supported

#Os x preview for windows windows#

Size and position of Settings windows is now stored Fixed crash when opening or closing a new window Fixed crash when starting the R128 meters 2 Vector Scopes in one window caused corrupted graphics Fixed frozen window when moved to Dock and back Further graphics optimization for lower resource usage and reduced GPU load Fixed Spectral Analyzer and Multichannel Level Meter when running on nVidia graphics cards Made sure no I/Os are missing on units with lots of channels (MADIface XT, HDSPe MADI FX) Smaller minimum width is now available on 2 and 4 bar meters, and smaller overall size for all windows A big thanks to all who gave feedback, and those who even tested with us over the weekend! The suggestions posted on the other thread are on our list now, so don't worry if there is not much news in v 0.82.

#Os x preview for windows update#

In our first update (v0.82) we focused on fixing all reported (and some more) issues. Basic information about DC NG is found in this thread post: вЂ¦ 60#p154260 DigiCheck Next Generation v 0.85 is now available as preview for download.