Welcome, Guest
Username: Password: Remember me

NOTE: This is a "Community" forum. Please be mindful that community members are here to help as part of a community effort. We therefore appreciate your effort in keeping this forum a happy place!

If you have a specific issue (e.g. hardware, failure) and want help from our support team, please use our tech support portal (Support menu - > Contact Us).
Thanks a lot of your help in making a better community.
  • Page:
  • 1

TOPIC:

Corrected curve much lower than target on V2.3 1 year 6 months ago #45785

  • ajellison83
  • ajellison83's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 19
  • Thank you received: 3
I got Dirac Live all set up and working fine on my DDRC-24 and Mac Mojave. Took measurements and made corrections and all was well. I moved some acoustic treatment and wanted to redo the Dirac, so I measured everything exactly as I did before and everything was going just fine until I get to the Filter Design page and see the predicted correction line is 3-4dB lower than my target and isn't smooth at all. Looks quite terrible actually. If I set the target to 0dB all across, the highest peaks of the predicted curve only even touch 0dB a couple times, most of it being far lower than that.

Has anyone else ran into this problem and have any advice for me?

Please Log in or Create an account to join the conversation.

Corrected curve much lower than target on V2.3 1 year 6 months ago #45864

  • devteam
  • devteam's Avatar
  • Away
  • Administrator
  • Administrator
  • Posts: 8902
  • Thank you received: 1261
@ajellison83

Most likely that when doing that modification of your acoustic panels, it obviously modified the response.

Are you also 100% sure that you indeed had the exact same level during that second measurement? Dirac resets the level before any sweep. Most likely that you ran the measurement at a different level? Just a wild thought.

DevTeam
miniDSP, building a DSP community one board at a time.

Please Log in or Create an account to join the conversation.

Corrected curve much lower than target on V2.3 1 year 6 months ago #45870

  • ajellison83
  • ajellison83's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 19
  • Thank you received: 3
I tried to upload a picture of the issue earlier, and it was being a little weird on my end. In this case, a picture is worth a thousand words. I'll give it a shot and see if it works. I've been trying different things and have an email into the DIrac team as well and haven't heard back. I've completely uninstalled both Dirac Live and all Minidsp related programs, caches, preferences, and folders and started completely from new and am still getting the same thing. Next on the list is to start installing older versions of Dirac Live until I find one that works. Anyways. I'll try to upload a pic and see if it goes through.

Attachments:

Please Log in or Create an account to join the conversation.

Corrected curve much lower than target on V2.3 1 year 6 months ago #45901

  • ajellison83
  • ajellison83's Avatar Topic Author
  • Offline
  • New Member
  • New Member
  • Posts: 19
  • Thank you received: 3
The Dirac team got back to me after two days offering to look into the problem. In that time I erased everything again and installed v2.2.0 and it works just fine. Honestly can't tell a difference between v2.2 and v2.3, so oh well.

Please Log in or Create an account to join the conversation.

Corrected curve much lower than target on V2.3 1 year 4 months ago #47129

  • gibbo9000
  • gibbo9000's Avatar
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 29
  • Thank you received: 6
There does appear to be an ongoing and underlying issue which Dirac know about. It seems to depend on configuration somehow. I shared the two attached examples with Dirac asking why one tracked very tightly (DL No Sub), and one was way out (DL 50 Sub). This is on my SHD running the latest 2.4.1. It gets worse if you try to use the curtains to limit Dirac to <500Hz as it creates all kind of local, visual artefacts at the transition point - to the extent I have no idea what it is actually doing.
There response was: "That's a known graphic only bug and it should be fixed in the next update."
That may well be the case, but it is a pretty fundamental to the basic operation of Dirac and users' trust in it, and I would have expected some kind of proactive announcement or advice - along with clearer advice on when we will have a fix.
Gibbo
Attachments:

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Moderators: devteam