TOPIC:

Very close to pulling the trigger on the upgrade now that you guys worked through all the initial bugs. Thank you for posting up your progress!

TimoJ wrote:

But support said that the Dirac level warning is not a bug and that the level actually is too low, this effects accuracy of the measurements. And it's by design that the system still allows you to make the measurement.

That's odd. I have gotten that message and then on the very same sweep gotten a message about outputs being clipped as the level is too high. Next time I run some sweeps I'll figure out the quietest speaker first (likely going to be one of the rear channels for me) and set the overall output using that, then lower the levels on the individual channels so that they match and see if I still get the same message. It also did not give me that message when I tried just using channels 7 and 8 on mine before they sent out that initial bug fix via email.

rccotroneo wrote:

Very close to pulling the trigger on the upgrade now that you guys worked through all the initial bugs. Thank you for posting up your progress!

No problem

naiku wrote:

That's odd. I have gotten that message and then on the very same sweep gotten a message about outputs being clipped as the level is too high. Next time I run some sweeps I'll figure out the quietest speaker first (likely going to be one of the rear channels for me) and set the overall output using that, then lower the levels on the individual channels so that they match and see if I still get the same message. It also did not give me that message when I tried just using channels 7 and 8 on mine before they sent out that initial bug fix via email.

I did argue about this with the support, got a wise-ass reply and replied to that making them annoyed...
But it's odd that the message appears immediately, it's not even trying to send the signal. And I think it should not allow to continue if the level actually is too low or at least say so after the measurement, like it does with clipped signal. But this is Dirac's code, not MiniDSP's.

Exactly, it does not make a whole lot of sense. I have actually gotten an error after the sweep saying signal too low, so how it knows the signal is too low before even starting the sweep is a mystery.

I should hook up an old speaker, turn the output level way up and take a video showing the too low message, then taking the sweep and it then saying too high.

TimoJ wrote:

New plugin and firmware is released, fixing those bugs I wrote about.

But support said that the Dirac level warning is not a bug and that the level actually is too low, this effects accuracy of the measurements. And it's by design that the system still allows you to make the measurement.

So what level are we talking about?

I have never got that message ever , never seen it. Is it referring to your level on the setting levels tab , makes me wonder if you have a setting within windows audio properties that needs a quick fix.

When does it give you this error message, before or after each measurement or during ?

It gives the error (attached) right after you press Start. Then you press OK to close the message and press Start again and it works. But according to Support the level is still too low and the message is a warning. Not sure if they actually understood this problem.

TimoJ wrote:

It gives the error (attached) right after you press Start. Then you press OK to close the message and press Start again and it works. But according to Support the level is still too low and the message is a warning. Not sure if they actually understood this problem.

Very interesting...... I’ll have to get mine installed and see , it arrives today. I know my gains are dialed in for Dirac so we’ll see.

Are you seeing plenty of audio in waveform in the waveform box ? Is it filling at least half the window with audio and about 3/4 on the peaks ?

Did you see my video on the DIYMA forum ?

www.diymobileaudio.com/forum/technical-a...p-2.html#post5708263

Yep, seeing plenty of audio in the waveform. It's also odd in that the message appears before it even actually does a sweep.

naiku wrote:

Yep, seeing plenty of audio in the waveform. It's also odd in that the message appears before it even actually does a sweep.

My vote is a funky windows setting

The dsp is seen as a soundcard and so is the mic

I’ve heard ppl having some hardware configuration issues in windows.
I want to say the manual talks about it ...
Don’t quote me on that tho

denver8me4dinner wrote:

My vote is a funky windows setting

The dsp is seen as a soundcard and so is the mic

The DSP is not seen as a sound card. I set channel levels correctly before the calibration and still got these errors. So where can the Windows setting error come from?

denver8me4dinner wrote:

Did you see my video on the DIYMA forum ?
www.diymobileaudio.com/forum/technical-a...p-2.html#post5708263

Why do you recommend not using the 90deg mic calibration file and point the mic forward? Since you have tested these, what is different (in the end result soundwise) if you use it and point the mic up?

(I'm wondering about the user manual's and Dirac's recommendation of pointing up since the speakers are usually down and the mic has a low pickup point there. Logical position would be facing down or forward)

TimoJ wrote:

denver8me4dinner wrote:

My vote is a funky windows setting

The dsp is seen as a soundcard and so is the mic

The DSP is not seen as a sound card. I set channel levels correctly before the calibration and still got these errors. So where can the Windows setting error come from?

I could be wrong ,
But when you plug your dsp into computer computer recognize it as audio device a.k.a soundcard

Open audio properties and cdsp should be listed when connected right next to your Realtek or whatever default device you have same with the mic as recording device , so yes it is seen as a sound card , an external one


If you go into cdsp properties or audio properties (can’t remember) there’s some level adjustments in there , maybe something with that just guess honestly

But again if I remember correctly the manual talks about this , I’ll try and find it

TimoJ wrote:

denver8me4dinner wrote:

Did you see my video on the DIYMA forum ?
www.diymobileaudio.com/forum/technical-a...p-2.html#post5708263

Why do you recommend not using the 90deg mic calibration file and point the mic forward? Since you have tested these, what is different (in the end result soundwise) if you use it and point the mic up?

(I'm wondering about the user manual's and Dirac's recommendation of pointing up since the speakers are usually down and the mic has a low pickup point there. Logical position would be facing down or forward)

The direct sound vs reflected sound ratios are extreme in a car, you want it to be able to distinguish which is which the most easily , especially for timing reference

However it’s only at the top oactave I noticed a difference (almost nothing) but still there

denver8me4dinner wrote:

I could be wrong ,
But when you plug your dsp into computer computer recognize it as audio device a.k.a soundcard

Open audio properties and cdsp should be listed when connected right next to your Realtek or whatever default device you have same with the mic as recording device , so yes it is seen as a sound card , an external one

Nope, does not show up as a sound card device. That was one of the first things I checked when I was getting no output, I can double check again tomorrow but I am 99.9% sure it does not show up as a sound card, because the computer does not see it as one. The software does not route any audio via USB, only commands to control the DSP, so I assume that the DSP internal memory stores the sweeps / pink noise used when taking measurements.

naiku wrote:

denver8me4dinner wrote:

I could be wrong ,
But when you plug your dsp into computer computer recognize it as audio device a.k.a soundcard

Open audio properties and cdsp should be listed when connected right next to your Realtek or whatever default device you have same with the mic as recording device , so yes it is seen as a sound card , an external one

Nope, does not show up as a sound card device. That was one of the first things I checked when I was getting no output, I can double check again tomorrow but I am 99.9% sure it does not show up as a sound card, because the computer does not see it as one. The software does not route any audio via USB, only commands to control the DSP, so I assume that the DSP internal memory stores the sweeps / pink noise used when taking measurements.

Yeah you totally could be right I’m going off of memory that is pretty old man ish

Let me browse the manual here for a sec it I think I remember seeing something about this I might be thinking of just the mic