• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Dirac Live Exclamation Mark issue

I have a new set up which is pretty straight forward and was going to give DLBC another try. Any advice on whether to try the newest beta version or the latest stable version or an old version greatly appreciated. Thanks
.
In doubt DLBC v3.4.4 is the last stable reliable version.
 
I just tried 3.13.8 after waiting 9 months. I was pleasantly surprised that I got no error messages during the measurement process and the filters sub delay made sense and the FR looked good when reviewed with REW. The filters also sounded good. My system set up is much more straightforward that the one I tried before, 2 subs and 2 mains vs 4 subs and 2 mains previously so I can't say for sure everything is "fixed" but for my relatively "easy" current set up it worked as expected.
 
I just tried 3.13.8 after waiting 9 months. I was pleasantly surprised that I got no error messages during the measurement process and the filters sub delay made sense and the FR looked good when reviewed with REW. The filters also sounded good. My system set up is much more straightforward that the one I tried before, 2 subs and 2 mains vs 4 subs and 2 mains previously so I can't say for sure everything is "fixed" but for my relatively "easy" current set up it worked as expected.
I'd say the same. 3.13.8 finally fixed Harman Luxury receivers lines DLBC bug since above 3.4.4
 
Not sure I can stomach another try. Has anyone had the imprecise measurement error with the latest version?
New to the forum, first post . Been searching as I had the imprecise measurement problem, my amp is a nad m33 and i have a 2.2 set up. Looked through the thread and thought, great, the beta versions have solved my problem! Deleted the old versions and downloaded 3.13.9.......same problem i.e. imprecise measurement. Deleted that and loaded 3.13.8........same problem. The microphone is an earthworks xlr into a scarlett solo, then usb into my laptop, this has been lent to me by the nad m33 dealer, as he believed the problem was the standard nad puck. Eventually loaded 3.4.4 and that works fine, I'm not an expert in this and my only reference point is that after running 3.4.4, my system sounds great. But, I can't help wondering and being annoyed that the latest versions don't work.

The one thing I will say, is that my laptop is not Windows 10 pro or Windows 11 compliant, could this be the issue?
 
New to the forum, first post . Been searching as I had the imprecise measurement problem, my amp is a nad m33 and i have a 2.2 set up. Looked through the thread and thought, great, the beta versions have solved my problem! Deleted the old versions and downloaded 3.13.9.......same problem i.e. imprecise measurement. Deleted that and loaded 3.13.8........same problem. The microphone is an earthworks xlr into a scarlett solo, then usb into my laptop, this has been lent to me by the nad m33 dealer, as he believed the problem was the standard nad puck. Eventually loaded 3.4.4 and that works fine, I'm not an expert in this and my only reference point is that after running 3.4.4, my system sounds great. But, I can't help wondering and being annoyed that the latest versions don't work.

The one thing I will say, is that my laptop is not Windows 10 pro or Windows 11 compliant, could this be the issue?
Disappointing, I thought that was fixed since 3.11., at least it is for my setup. From the Release Notes of 3.11.:
  1. Improved error detection on all platforms: An improved algorithm for detection of missing samples in the measurement recording is introduced. This will generate significantly less false alarms about measurements being “imprecise” (showing an exclamation mark). The improved algorithm will always be applied, both when using microphones connected to the AVR/receiver device and to the PC/Mac.
  2. Improved recording quality on Windows: The Windows WASAPI driver will be used in Exclusive Mode by default. Exclusive Mode significantly reduces the probability for losing samples during the recording. It is possible to opt-out of Exclusive Mode by setting the environment variable: DAUDIO_WASAPI_NON_EXCLUSIVE = ON

Maybe try setting exlusive mode on/off and try again? Unfortunately the "Imprecise Measurement" message is also a very imprecise error message in itself....
 
In my case, 3.13.8 beta apply the best results ever obtained from Dirac. But this is true after disabling gain/delay in the upper menu.
Maybe it’s a matter of the Umik1 imprecision but enabling gain/delay is a disaster, sound moves to the left, loses high frequency range… and music sounds unnatural.
Disabling gain/delay just focuses on solving minor problems with good results. In my case reduced Dirac some gain in the 150-200hz to gain clean mid bass and clarity.
 
I tried the latest and whilst I got some good measurements the imprecise measurement was still the result in about 70% of runs :(
 
I wonder how much of a problem the imprecise measurements really are? I think you wouldn't want it in the first measurement of the main listening position, where delay and gain are determined.
I wish Dirac would be more forthcoming with information on the topic.
 
In my experience if you follow this to the letter you will not have any problem with Dirac 3.4.4 or 3.13.8


My laptop in on Win 10 not pro and it is fine. If you are on older Win like Win 7 or other then I can't
Thanks, I have been through the process with Dirac and MiniDSP multiple times but it was some time ago now. I’ll have a read and if I get the energy I’ll give it a go. I can’t see why Dirac / MiniDSP would omit something thats in your attached, but who knows…
 
I just got a pioneer lx805, this bug is real. The only change I made was a move from the lx505 to the 805. The 505 did Dirac runs with no issues. same mic, same speakers, same positions. I have tried most of the solutions offered up in the thread to no avail. I use a dayton audio umm-6, that doesn't seem to be the issue. The documented process shared in the last post also doesnt get past this bug. Will try to roll back the Dirac version but I am not confident that is going to do anything. was gonna layout the money for bass control but not if this is gonna be something I have to keep fighting with.
 
I tried the latest and whilst I got some good measurements the imprecise measurement was still the result in about 70% of runs :(
I am currently at a 100% fail rate. You seem to have been fighting this battle for a long time. Doesn't give me much hope to get past this.
 
Do people running the Dirac processor on a PC or Mac also encounter the exclamation mark errors? Is this issue exclusive to people running Dirac on AVRs? Or does this problem occur across all platforms?

I for one have never seen the exclamation mark measurement error, running Dirac processor on a Mac.
 
Do people running the Dirac processor on a PC or Mac also encounter the exclamation mark errors? Is this issue exclusive to people running Dirac on AVRs? Or does this problem occur across all platforms?

I for one have never seen the exclamation mark measurement error, running Dirac processor on a Mac.
I had the issue on a PC based system but for me it cleared up with the latest beta. Not for everyone apparently.
 
I had the issue on a PC based system but for me it cleared up with the latest beta. Not for everyone apparently.
So my recent attempt was with 3.13.4, are you saying 3.13.4 wasn’t working for you but the Beta 3.13.9 did work?
 
Back
Top Bottom