Heaven sent!
Works great on X.5.8!

Thanks chaps!

Hey MC, thanks for the update!

What exactly does this mean?

Ah, thanks alot!

You did. It is included in the 25 Hz bar.

It's quite simple: The 25Hz BAR shows the maximum level of a 25Hz band pass and a separate low-pass filter for DC. Together they still have a response like a low pass filter, but with an upper edge matching exactly the other band pass filters. So you still can detect low frequency rubbish, without wind up of the 25Hz band for normal signals...

nice! this is my first version of digicheck on the mac, and I have a question: is it possible to analyze the sound playing from the computer, not only the input of my FF400? thanks!

bm, thanks for the detailed feedback. This happens under high CPU load. We think we were able to improve DC's performance, or better responsiveness in such a situation greatly. Please try version 0.541:

Link no longer valid!

Did you see the same with version 0.54?

Hey guys.  If you are hating the "framerate" of the latest digicheck, try deleting your pref file.  Seriously, when MC said hey we fixed it, grab the latest, I did.  Upon opening it, I was getting completely frozen meters on anything using core audio input.  The totalizer would update about once every 2 or 3 seconds... I deleted the preferences and bam, the best performance I'v seen yet.

A couple things though... one is that after deleting my prefs, everything works fine until I try and load a workspace that was created with a previous version of digicheck.  At that point the problem returns and the refresh rate falls to below a frame a second.  My 8 core macpro is sitting idle during tests.  I am not encoding video or even recording audio.  There is NO cpu load besides the load generated by digicheck.  Something with the old preferences and workspaces just doesn't jive with the new build.  Also, I can't load a workspace without having at least one digicheck window open.

Here are my preferences which cause the low frame rates: Digicheck plist file

Also, here is a troublesome workspace which should effectively demonstrate the phenomenon: Sample Workspace

Upon loading the workspace, the bottom meter should be relatively frozen; updating at a max of a frame a second.

When installing a new build, I think we should all be starting from scratch.  Thats the only way to really know the full potential of the new build.

Since we are still in beta, I'm expecting stuff like this.  I think we all need to remember that and do our part as users to do a bit of troubleshooting.  After all, digicheck is a FREE addition to an already great product and RME seems to be listening to user input very well.  Especially in light of the fact that there really isn't a cent to be made...

Hi,

i deleted the preference file and 0.51 is still smoother. The 0.51 goniometer with release 1 set to 0.05s looks like an hardware goniometer, 0.541 looks like a vst plugin (dunno if there are any smooth vst goniometers, i have never seen one).

Besides the 'smoothness' difference i noticed something else, the goniometer in 0.541 looks different.

Here is a screenshot of both, 0.51 is on top, 0.541 at the bottom. For me the 0.51 goniometer looks better and more useful.

Regards

[img align=L]http://img187.imageshack.us/img187/7792/picture3enf.png[/img]

Not working for me I've trashed pref file and totalyser works ok but only when one window is using coreaudio. when I open another window with hardware level meter it start to respond with 2 or 3s latency. I tryed to switch nominal update time to 45ms and it started working but still worse whan 0.52v

MC, is there a version of DC with trace and a console output?  I thought if I could get the (probably worse performing) developer, build I could send the logs in when I have a problem...

This version is running great here.  I have a mix of hardware and core audio meters with OVS, a totalyser, global input meter, vector scope, bit statistic, and spectrum analyser all operating simultaneously at 35-40 fps at a nominal 15ms update time.  Currently, this is taking about 56% of one of my 8 cores, meaning that digicheck is using about 5% of my system resources.  Just fine with me.  I'll never be using that many digicheck windows at the same time anyway.

Hey, MC, one thing I noticed is that for a second when I launch a new window, the system somehow was able to split the load between 2 of my cores.  Is there possibility of allowing each meter window it's own thread, thus allowing multicore support?  Right now, most of the time, I have one core burning at 50% instead of all cores burning at 6-7%. 

Not complaining, it is working really well here, just asking.  Oh and the FPS in the title bar is a nice touch.

Thanks,
Brian

DIGICheck 0.542: on my recent 13' mbp (2,26 ghz; 4GB ram) it feels stable.. I am running totalyser  (nominal update time 15ms) with default settings: CPU is at 25-28%.
fps are quite constant at 57.4, but it drops to as low as 45 every few seconds just to go back up immediately.

now that I figured out how DIGICheck works I am looking forward to global record on the mac

I have to admit that I didn't really use Digicheck on Mac yet, so here are my first impressions:

CPU load:

CPU load on a 2.8 gHz C2D for "Hardware" based level-meters is around 3% when the CPU is clocked to maxed. When Speedstep clocks down the CPU to 1.6 gHz CPU load rises to around 4%.

According to the helpfile DigiCheck should only use around 1% for calculating the graphic-display. But the relatively "high" CPU load even happens when DC is minimized or hidden.

Measuring Playback/Output:

Do I understand right that DC on Mac can only measure playback/output for level meters because CoreAudio doesn't allow to chose playback/output? For me that's a big drawback compared to the Windows version, because I'm mainly using the Spectral Analyzer.

Sure you can workaround that restriction by routing the output back to an input via Totalmix, but I'm using the Fireface for live effects, which means I'm going from input -> DAW+FX -> output. So I cannot just route outputs back to inputs without major feedback problems (ouch).

Also according to the helpfile using Totalmix and DC at the same time leads to wrong level metering.

Settings Dialog:

In order to switch a button of the Settings window you first need to move the mouse-pointer away from the button. It is not possible to just switch a button on/off while the mouse-pointer hovers over the button.

The "AUTO" setting for "Top Level" on the Analyzer switches the display only upwards (towards 0 dB) but not downwards (towards -140 dB). That's a problem I had with the Windows version in the past, too.

Helpfile:

Please include a shortcut to the Table of Contents / Index that's permanently displayed at the top of the helpfile window (like seen on Apple's Preview and ITunes applications). Or maybe just turn the Index into the startpoint/homepage instead of the Overview.

Starting in "Overview" then scrolling all down to reach the Index is quite inconvinient. And after clicking through several links having to hit the back button several time or returning to Overview just to scroll all the way down again isn't perfect neither.

The help on Bit Statistics & Noise is missing btw. fryingpan

Hope my "rant" (you know me, they ain't rant, but constructive criticism) help to make this a better product.

Ah, fair enough. I can still use manual settings then. :-)

What about the other points?

This is still the Windows help. Under Mac OS the same simple graphics routines work with a really bad performance. We could improve this for drawing bitmaps as in the SA, but the Level Meters work differently and can not further be optimized. A complete rewrite is in order, which will be done later.

DC on Mac can only display Hardware output levels. The Windows function that allows for displaying software outputs is a special driver feature not available under Mac. Therefore this feature needs more work to be added, a totally different solution, means later.

That is the same under Mac, yes.

No one else ever reported this, so either your description is misleading or this only happens on your machine. (?)

We will rework that, thanks for the reminder.

Thanks for the informations, Matthias! :-)

Too bad. Seems like I have to get my hands on some good OS X spectrum analyzer then.

This is how it happens here:

1. Move mouse-pointer over a button and click -> button changes state.
2. Click again -> nothing happens.
3. Move mouse-pointer away from button and then move it back over the button and click -> button changes state.

Works as always. It seems you simply click too quick, which will be seen as double-click by DC then.

yes. v. 0.52 versus v. 0.542 and looks promissing.

I said v0.51 not v0.52.

And to MC, what do you say about the goniometer screenshots? Shouldn't they look the same?

Ok, next thing I did was uninstalling DigiCheck via AppCleaner (which deleted the DigiCheck application + a corresponding plist file. Then I ran the installer again and now the helpfile version is 0.6!

Is this an installer issue or an issue with one of OS X caches (is there a cache for helpfiles)?

I tried to install the new Mac digiCheck software (0.6), but the installer tells me that it won't install because there is a newer version of the software already installed.  It tells me this even after I have deleted the old copy of digiCheck from my Applications folder, along with its preference (plist) file.  How can I force the installation?  Does the Fireface need to be connected to the computer and turned on to make this work?

I noticed I missed the 0.542, I still had 0.541. Nevertheless 0.6 seems to be working fine. Nice update, thanks.