Active Room Treatment (ART) by Dirac

[neRok]

Any idea on why with ART I do not notice not having DEQ, I thought I would miss it? Bass levels seem to me always the appropriate amount regarding the volume. Could it be because my volume knob never gets lower than -30?

I would say its because ART is reducing the decay, which means various frequency bands aren't being "shielded" as much when the SPL increases both in-room and psycho-acoustically.

I have learned I like a Goldilocks middle of the road. ... Now I'm fiddling with the best compromise for me, it's a lot of fun!

I reckon you should put it all to default and listen to it that way for probably 2 weeks, so you can get your "baseline" reset. Because right now you've probably gone years listening to audio in rooms that haven't had any bass treatment (which is hard to achieve <200Hz), and so the only thing you know is bass with high decay. So what you're doing with this "compromise" is finding settings that are not too different to what you already know, but you shouldn't be doing that, because what you know is wrong.

 

[JRowland]

I would say its because ART is reducing the decay, which means various frequency bands aren't being "shielded" as much when the SPL increases both in-room and psycho-acoustically.

I reckon you should put it all to default and listen to it that way for probably 2 weeks, so you can get your "baseline" reset. Because right now you've probably gone years listening to audio in rooms that haven't had any bass treatment (which is hard to achieve <200Hz), and so the only thing you know is bass with high decay. So what you're doing with this "compromise" is finding settings that are not too different to what you already know, but you shouldn't be doing that, because what you know is wrong.

View attachment 498139

It’s just how I learn, starting from no known reference then deciding where to go is harder for me. Breaking things down to a somewhat known starting point and building from there is usually better for me. When I get to where I think I want to be I will give your suggestion a try for sure, I saved the initial tune for that very purpose.

 

[kawauso]

JRowland’s trial-and-error logs are valuable. I don’t think it’s really
about whether something is “right” or “wrong.” Especially
with ART being such a new technology, we’re all basically beginners.

 

[peng]

Any idea on why with ART I do not notice not having DEQ, I thought I would miss it? Bass levels seem to me always the appropriate amount regarding the volume. Could it be because my volume knob never gets lower than -30?

That could be, but can't go by the volume -30 by itself for several reasons. To really answer your question, you would have to know the SPL you were listening to.

I found my archived copy of an article on EEQ, that might be difficult to find now:

Noticed the Y axis is SPL in dB, not volume. Volume -30 would be close to - 30 dB at you MLP if calibrated with Audyssey Auto setup and you followed instructions to the letter, and you are playing test tones recorded at 0 dBFS level, others all bets are off.

 

[JRowland]

That could be, but can't go by the volume -30 by itself for several reasons. To really answer your question, you would have to know the SPL you were listening to.

I found my archived copy of an article on EEQ, that might be difficult to find now:

View attachment 498144


Noticed the Y axis is SPL in dB, not volume. Volume -30 would be close to - 30 dB at you MLP if calibrated with Audyssey Auto setup and you followed instructions to the letter, and you are playing test tones recorded at 0 dBFS level, others all bets are off.

Sorry, -30 is 65dba in my system now, -20 is 75, -10 is 85. I realized I should have stated that yesterday and used my Niosh app to confirm again last night wondering if that would come up. I should add with Audyssey 0 on the volume was 85dba in my room.

 

[JRowland]

The Center channel is the most active in home theater scenarios, so I think it's probably best *not* to use it for support of other channels. In fact, several folks have seen best results using only subwoofers as support because they have the most output <150 Hz.

I think it depends on the user and also how strong the center channel is. A lot of folks have home theaters and care about multiple seats and others enjoyment while some folks have a single seat and not a care for what it sounds like 3 feet away. For music, even with Atmos it does not seem like the center channel does much so why not put the woofers to use in support duty? What the effect (to me) feels/sounds like is a blending of the front soundstage, I prefer the separation myself so far but messing with the support levels can get the best of both ish. I think a lot of the don't use the center for support talk is for multiple seats and dialog more than for music listeners, but that's just my opinion. The difference in how folks use their systems and what their goals are make it very difficult in my opinion to start comparing things. I'd love to look at some music only set ups as long as I knew they were music focused. I could care less about home theater but that's a huge part of this hobby with to me somewhat different goals.

 

[JRowland]

In my 7.4.6 setup, I found that reducing the number of support speakers from the default 93/94 to 69, limiting support to only the same group and the subwoofers, resulted in better FR and decay at the MLP.

In my case, the default results were not particularly problematic, but this more conservative support configuration performed better than the default in all five of my rooms. The results are more than sufficient, so I am using this configuration.

In theory, having more support speakers should be more effective. However, it is unclear whether this behavior is due to a bug in ART or whether ART is prioritizing results away from the MLP. For now, I am making decisions based on the FR at the MLP.

dlaloum, if you have added a subwoofer and there is a performance difference between the subs, it may be effective to separate them into different subwoofer groups. For example:
• SW1: 20–150 Hz (Infra Bass ON)
• SW2: 25–150 Hz (Infra Bass OFF)

Could you also check the results with the second subwoofer turned off? Even with a single subwoofer, you should be able to confirm that the results are better than your initial default ART measurement. While you will likely use two subs for normal operation, a single sub can already produce very good results.

I found it beneficial to play with support of each sub as well, I have a stronger sub and leaving it at -24 in the LFE channel and moving support to the other sub to -18 seems for me to have let the better sub take the lead although they are both playing an active role.

 

[neRok]

starting from no known reference then deciding where to go is harder for me

Breaking things down to a somewhat known starting point and building from there is usually better for me. When I get to where I think I want to be...

The fact is (IMO) that the "cutting edge" of audio technology/algorithms/etc is far beyond what a "normie" can achieve. Because here's a simple fact to understand: if it was easy to do, it would have already been done/copied in the DIY/OSS space! What companies like Dirac are doing with ART is far-beyond trial and error. That's why car companies have been paying them big-bucks for their technology/algorithms for years.

Now that's not to say that you cant "help" ART do it's thing, but I can't see how making significant changes to its variables is going to help...

The way to "help" ART (according to my understanding) is to alter the position of the speaker/sub/whatever within the room, because that changes it's " natural in room response" (ie, impulse response), and that new IR might happen to have certain "characteristics" that are better suited for "active cancellation" of problems that other/more-important speakers are having.

And so you're probably thinking "I spent heaps of time in the past getting the sub(s) in to the best position according to [multisub/REW/whatever], so how isn't that the best position for ART?". And that question has a rather simple explanation, which is that you positioned it/them for where their "total" output worked best. And in that context, "total" output is the "source" output (DSP'd or not). What ART is doing is making certain speakers output certain sounds at times that are relevant to the room, not the source (music/movie/whatever). So the "total" of old isn't the same as the "total" of what ART is doing, and hence the speaker/sub might perform better "within the system" when located in a different position.

And I haven't got ART, and so this particular tip is a total guess, but I reckon putting the subs right up against the walls might work best. That's because "every mode" will get "activated" near 100% that way, which means every driver is activating every mode "in time and at max power", which means any driver has its best chance of cancelling a problematic mode from a different driver at the listening position. And if the "theoretical best driver for cancellation" of a particular problem is putting in the majority of the effort to "actively" cancel a particular problem, then I presume that means the end-result will have the best decay/timing and distortion characteristics.

 

[JRowland]

The fact is (IMO) that the "cutting edge" of audio technology/algorithms/etc is far beyond what a "normie" can achieve. Because here's a simple fact to understand: if it was easy to do, it would have already been done/copied in the DIY/OSS space! What companies like Dirac are doing with ART is far-beyond trial and error. That's why car companies have been paying them big-bucks for their technology/algorithms for years.

Now that's not to say that you cant "help" ART do it's thing, but I can't see how making significant changes to its variables is going to help...

The way to "help" ART (according to my understanding) is to alter the position of the speaker/sub/whatever within the room, because that changes it's " natural in room response" (ie, impulse response), and that new IR might happen to have certain "characteristics" that are better suited for "active cancellation" of problems that other/more-important speakers are having.

And so you're probably thinking "I spent heaps of time in the past getting the sub(s) in to the best position according to [multisub/REW/whatever], so how isn't that the best position for ART?". And that question has a rather simple explanation, which is that you positioned it/them for where their "total" output worked best. And in that context, "total" output is the "source" output (DSP'd or not). What ART is doing is making certain speakers output certain sounds at times that are relevant to the room, not the source (music/movie/whatever). So the "total" of old isn't the same as the "total" of what ART is doing, and hence the speaker/sub might perform better "within the system" when located in a different position.

And I haven't got ART, and so this particular tip is a total guess, but I reckon putting the subs right up against the walls might work best. That's because "every mode" will get "activated" near 100% that way, which means every driver is activating every mode "in time and at max power", which means any driver has its best chance of cancelling a problematic mode from a different driver at the listening position. And if the "theoretical best driver for cancellation" of a particular problem is putting in the majority of the effort to "actively" cancel a particular problem, then I presume that means the end-result will have the best decay/timing and distortion characteristics.

I don't get (grasp) the anti-waves or cancellation piece for sure, but what you can see when you play with ART is support speakers are added and the show filters tab shows them. So if for example your right front speaker has a dip at 100Hz ART will use whatever support you enable to fill that dip. So that support speaker plays that part of the role, it can be noticeable (to me) when there are "too many cooks in the kitchen" so to speak. So going for anechoic or whatever some folks do (tightest spread in ART) means other speakers are playing along with your right front in the above scenario to output the "cleanest" noise. Until you feel/hear this for yourself it's easy to look at graphs and make decisions for people. For me hearing it both ways and deciding for myself which I prefer is just how I operate, I am not here suggesting others do the same just offering up my observations.

 

[Flak]

Dirac Live Beta 3.14.0 // 2025-12-18​

If you experience inconsistencies with this Beta version, please report them to us and use the latest stable version of Dirac Live.

Features

• ART support range tag-along controls (DS-1989)
  
  • ART support range settings are, by design, constrained by the ART active range of the main group, and vice versa. The way the constraint was originally implemented in Dirac Live version 3.13.9, users had to make tedious adjustments with limited visibility across different groups.
  • With the new tag-along control feature, a user can now force the limiting settings in other groups to tag along with the currently controlled setting by holding the SHIFT button while dragging the support range slider or holding SHIFT when hitting Enter in the F_support_low text box.
• Fail fast if the connected device is in a bad state (LIVE-4815)
  
  • Sometimes, a Dirac Live enabled device can be in a bad state that may cause issues later, for example failing to design a Dirac Live filter or failing to export a filter.
  • To avoid the inconvenience of having made measurements that cannot be used, the Dirac Live application will now recognize some common bad device states already when connecting to it, and notifying the user to restart the device before proceeding.
• Support for legacy devices (LIVE-4793)
  
  • Some older Dirac Live devices have not updated their firmware to support the current version of Dirac Live. Owners of these devices have relied on our legacy application Dirac Live Calibration Tool (DLCT) for new room corrections. The DLCT backend servers will be taken offline in early 2026, and therefore, the DLCT application will stop to function.
  • To not leave customers behind, a new proxy feature has been added to the current Dirac Live application. With that, the current Dirac Live application will be able to connect to legacy devices for measurements and filter design.
  • Important note to customers with such legacy devices: Make sure DLCT is properly installed (but not running) on the computer where you also install and run the current Dirac Live application. This is necessary for the current Dirac Live application to locate and use the DLCT-bundled software component that is used to communicate with the legacy device.
• UI improvements
  
  • Improved contrast on some graphics (APP-570)
  • Improved user guides and error messages (APP-563, APP-574, APP-613)
• Stability improvements
  
  • Updated Qt framework to version 6.9 (APP-593, APP-612)
  • Dropped support for macOS 11.x (affected users can stay on version 3.13.16)

Bug fixes

• ART active range was constrained by its support range setting in another group, even when it was disabled from support. This is now fixed so that the ART active range for a group is only constrained by activated ART support settings in other groups.
• Fixed some cases where Dirac Live could crash or freeze (APP-602, APP-661, DS-2034)

Known issues

• The 120 Hz low-pass filter introduced in version 3.13.2 applied to the LFE channel introduces a delay of about 5 milliseconds compared to the other channels.
• At first launch after first installation on macOS, Dirac Live will not detect devices on the network. Press the Rescan button to detect them.
• Progress tracker can sometimes jump backwards. (LIVE-4356)
• New filter exports are not displayed correctly in the application on some NAD devices. The filter can still be used and will be displayed correctly after reconnecting to the device (APP-555)

Download

Windows: https://artifacts.connect.dirac.com...e-candidate/win64/diraclive-v3.14.0-setup.exe
macOS: https://artifacts.connect.dirac.com...e-candidate/macos/diraclive-v3.14.0-setup.pkg

 

[neRok]

So if for example your right front speaker has a dip at 100Hz ART will use whatever support you enable to fill that dip. So that speaker plays that part of the role, it can be noticeable (to me) when there are "too many cooks in the kitchen" so to speak.

Doesn't ART max out at like 400Hz or something? So perhaps ART is fixing everything under the "lower-mids", and you so you are left hearing the rest?! That actually makes sense with regards to your previous comment regarding "EQ that [no longer] changes with SPL"

 

[neRok]

Dirac Live Beta 3.14.0 // 2025-12-18​

If you experience inconsistencies with this Beta version, please report them to us and use the latest stable version of Dirac Live.

Features

• ART support range tag-along controls (DS-1989)
  • ART support range settings are, by design, constrained by the ART active range of the main group, and vice versa. The way the constraint was originally implemented in Dirac Live version 3.13.9, users had to make tedious adjustments with limited visibility across different groups.
  • With the new tag-along control feature, a user can now force the limiting settings in other groups to tag along with the currently controlled setting by holding the SHIFT button while dragging the support range slider or holding SHIFT when hitting Enter in the F_support_low text box.
• Fail fast if the connected device is in a bad state (LIVE-4815)
  • Sometimes, a Dirac Live enabled device can be in a bad state that may cause issues later, for example failing to design a Dirac Live filter or failing to export a filter.
  • To avoid the inconvenience of having made measurements that cannot be used, the Dirac Live application will now recognize some common bad device states already when connecting to it, and notifying the user to restart the device before proceeding.
• Support for legacy devices (LIVE-4793)
  • Some older Dirac Live devices have not updated their firmware to support the current version of Dirac Live. Owners of these devices have relied on our legacy application Dirac Live Calibration Tool (DLCT) for new room corrections. The DLCT backend servers will be taken offline in early 2026, and therefore, the DLCT application will stop to function.
  • To not leave customers behind, a new proxy feature has been added to the current Dirac Live application. With that, the current Dirac Live application will be able to connect to legacy devices for measurements and filter design.
  • Important note to customers with such legacy devices: Make sure DLCT is properly installed (but not running) on the computer where you also install and run the current Dirac Live application. This is necessary for the current Dirac Live application to locate and use the DLCT-bundled software component that is used to communicate with the legacy device.
• UI improvements
  • Improved contrast on some graphics (APP-570)
  • Improved user guides and error messages (APP-563, APP-574, APP-613)
• Stability improvements
  • Updated Qt framework to version 6.9 (APP-593, APP-612)
  • Dropped support for macOS 11.x (affected users can stay on version 3.13.16)

Bug fixes

• ART active range was constrained by its support range setting in another group, even when it was disabled from support. This is now fixed so that the ART active range for a group is only constrained by activated ART support settings in other groups.
• Fixed some cases where Dirac Live could crash or freeze (APP-602, APP-661, DS-2034)

Known issues

• The 120 Hz low-pass filter introduced in version 3.13.2 applied to the LFE channel introduces a delay of about 5 milliseconds compared to the other channels.
• At first launch after first installation on macOS, Dirac Live will not detect devices on the network. Press the Rescan button to detect them.
• Progress tracker can sometimes jump backwards. (LIVE-4356)
• New filter exports are not displayed correctly in the application on some NAD devices. The filter can still be used and will be displayed correctly after reconnecting to the device (APP-555)

Download

Windows: https://artifacts.connect.dirac.com...e-candidate/win64/diraclive-v3.14.0-setup.exe
macOS: https://artifacts.connect.dirac.com...e-candidate/macos/diraclive-v3.14.0-setup.pkg

Oh, hello "Industry Insider". I don't know if you are a Dirac insider, but that post looks the sort, so YOLO...

People have asked for an update regarding official release of ART on PC. That would be nice!

But also, I came across the Neumann MT-48 today during my internet adventures. The page linked says "And there is still plenty of DSP power for future developments." So I wonder: have/are/can/will any "pro/studio" companies release ART capable products in the near future? And how does Atmos fit in to the mix?

I ask because the Neumann MT-48 can output 4 analogue channels itself, and then you can slap on a cheap ADAT device (eg Behringer AD8200) for 12 outputs. Alternatively, products like the Audient ORIA already exist that can "control and monitor multi-channel speaker arrays from stereo up to 9.1.6, and everything in between".

Edit: Dolby Atmos seems to have struck at the wrong time, because something like the Audient ORIA is relatively affordable for what is apparently the "cuttine edge" (wrt: atmos).

If the people mixing/master Atmos audio are paying $4k AUD, then they may as well bit-bang the I2C signal to me over ethernet... lol

 

[kawauso]

Dirac Live Beta 3.14.0 // 2025-12-18​

If you experience inconsistencies with this Beta version, please report them to us and use the latest stable version of Dirac Live.

Features

• ART support range tag-along controls (DS-1989)
  • ART support range settings are, by design, constrained by the ART active range of the main group, and vice versa. The way the constraint was originally implemented in Dirac Live version 3.13.9, users had to make tedious adjustments with limited visibility across different groups.
  • With the new tag-along control feature, a user can now force the limiting settings in other groups to tag along with the currently controlled setting by holding the SHIFT button while dragging the support range slider or holding SHIFT when hitting Enter in the F_support_low text box.
• Fail fast if the connected device is in a bad state (LIVE-4815)
  • Sometimes, a Dirac Live enabled device can be in a bad state that may cause issues later, for example failing to design a Dirac Live filter or failing to export a filter.
  • To avoid the inconvenience of having made measurements that cannot be used, the Dirac Live application will now recognize some common bad device states already when connecting to it, and notifying the user to restart the device before proceeding.
• Support for legacy devices (LIVE-4793)
  • Some older Dirac Live devices have not updated their firmware to support the current version of Dirac Live. Owners of these devices have relied on our legacy application Dirac Live Calibration Tool (DLCT) for new room corrections. The DLCT backend servers will be taken offline in early 2026, and therefore, the DLCT application will stop to function.
  • To not leave customers behind, a new proxy feature has been added to the current Dirac Live application. With that, the current Dirac Live application will be able to connect to legacy devices for measurements and filter design.
  • Important note to customers with such legacy devices: Make sure DLCT is properly installed (but not running) on the computer where you also install and run the current Dirac Live application. This is necessary for the current Dirac Live application to locate and use the DLCT-bundled software component that is used to communicate with the legacy device.
• UI improvements
  • Improved contrast on some graphics (APP-570)
  • Improved user guides and error messages (APP-563, APP-574, APP-613)
• Stability improvements
  • Updated Qt framework to version 6.9 (APP-593, APP-612)
  • Dropped support for macOS 11.x (affected users can stay on version 3.13.16)

Bug fixes

• ART active range was constrained by its support range setting in another group, even when it was disabled from support. This is now fixed so that the ART active range for a group is only constrained by activated ART support settings in other groups.
• Fixed some cases where Dirac Live could crash or freeze (APP-602, APP-661, DS-2034)

Known issues

• The 120 Hz low-pass filter introduced in version 3.13.2 applied to the LFE channel introduces a delay of about 5 milliseconds compared to the other channels.
• At first launch after first installation on macOS, Dirac Live will not detect devices on the network. Press the Rescan button to detect them.
• Progress tracker can sometimes jump backwards. (LIVE-4356)
• New filter exports are not displayed correctly in the application on some NAD devices. The filter can still be used and will be displayed correctly after reconnecting to the device (APP-555)

Download

Windows: https://artifacts.connect.dirac.com...e-candidate/win64/diraclive-v3.14.0-setup.exe
macOS: https://artifacts.connect.dirac.com...e-candidate/macos/diraclive-v3.14.0-setup.pkg

In this version, changing the support range has become much easier.
Previously, the UI was almost disastrous, but this is no longer an issue now.
One point of feedback is that the error messages should also support multiple languages.
Additionally, the Infra Bass checkbox is still difficult to understand on first use, so I think it would benefit from clearer labeling or explanation.

 

[JRowland]

Doesn't ART max out at like 400Hz or something? So perhaps ART is fixing everything under the "lower-mids", and you so you are left hearing the rest?! That actually makes sense with regards to your previous comment regarding "EQ that [no longer] changes with SPL"

150Hz then the rest of the Dirac suite takes over, I shut that down for me at 250Hz and leave my natural response. Tight spread (more support) cleans up "muddiness/boominess" very well but for me it adds it's own "smear" by having other speakers join in. I most notice it when those other support speakers are not on the same side of the room left/right OR front/back. I can play 2 channel with a lot of rear support and it sounds like rear ambience in multichannel but it's supposed to be 2 channel. The reason I broke it down to a "normal system" was so that I can have my own reference of what support from different areas at different levels feels like, I'm ignoring the boom as I want that gone for sure but focusing on the "feel" of where the sound is coming from. My focus is solely for me I should state that, I don't know or care if "movement" is important to others. My speakers "disappear" but I can still tell from which direction to an extent noises come from, when I have a bunch of support i just get the noise without the direction and I personally don't care for that no matter how "clean" the noise is. When I tried Audyssey with an 80Hz crossover I had "good noise" but not good movement, I found for me I'd rather compromise on the "good noise" a little if I can pick up some movement.

I'd imagine there is a difference with DEQ and not, I thought I would need multiple presets for different volumes but I'm not finding that to be the case for me. Hence my question yesterday about DEQ, I have seen folks lament the loss of it but wonder why I don't notice it. I never paid attention to Fletcher Munson but knew the basics, I was more wondering if the effect is different for different folks and maybe that's why I'm not noticing. I am not complaining about not missing it to be clear, I'm very happy as that (multiple presets) is not something I really want to have to focus on.

 

[Flak]

Oh, hello "Industry Insider". I don't know if you are a Dirac insider, but that post looks the sort, so YOLO...

People have asked for an update regarding official release of ART on PC. That would be nice!

Yes, it's highly anticipated.... I think I can't be wrong in expecting it to be released in 2026

 

[kawauso]

Yes, it's highly anticipated.... I think I can't be wrong in expecting it to be released in 2026

Wow, that’s a pleasant leak.
It looks like my PC-based DLBC setups in three rooms will become ART in 2026.

 

[smygolf]

@kawauso
Now that you have a Cinema 50, can you see how many filters that are used ?
I cant see it on my C50.

 

[OCA]

Dirac Live Beta 3.14.0 // 2025-12-18​

If you experience inconsistencies with this Beta version, please report them to us and use the latest stable version of Dirac Live.

Features

• ART support range tag-along controls (DS-1989)
  • ART support range settings are, by design, constrained by the ART active range of the main group, and vice versa. The way the constraint was originally implemented in Dirac Live version 3.13.9, users had to make tedious adjustments with limited visibility across different groups.
  • With the new tag-along control feature, a user can now force the limiting settings in other groups to tag along with the currently controlled setting by holding the SHIFT button while dragging the support range slider or holding SHIFT when hitting Enter in the F_support_low text box.
• Fail fast if the connected device is in a bad state (LIVE-4815)
  • Sometimes, a Dirac Live enabled device can be in a bad state that may cause issues later, for example failing to design a Dirac Live filter or failing to export a filter.
  • To avoid the inconvenience of having made measurements that cannot be used, the Dirac Live application will now recognize some common bad device states already when connecting to it, and notifying the user to restart the device before proceeding.
• Support for legacy devices (LIVE-4793)
  • Some older Dirac Live devices have not updated their firmware to support the current version of Dirac Live. Owners of these devices have relied on our legacy application Dirac Live Calibration Tool (DLCT) for new room corrections. The DLCT backend servers will be taken offline in early 2026, and therefore, the DLCT application will stop to function.
  • To not leave customers behind, a new proxy feature has been added to the current Dirac Live application. With that, the current Dirac Live application will be able to connect to legacy devices for measurements and filter design.
  • Important note to customers with such legacy devices: Make sure DLCT is properly installed (but not running) on the computer where you also install and run the current Dirac Live application. This is necessary for the current Dirac Live application to locate and use the DLCT-bundled software component that is used to communicate with the legacy device.
• UI improvements
  • Improved contrast on some graphics (APP-570)
  • Improved user guides and error messages (APP-563, APP-574, APP-613)
• Stability improvements
  • Updated Qt framework to version 6.9 (APP-593, APP-612)
  • Dropped support for macOS 11.x (affected users can stay on version 3.13.16)

Bug fixes

• ART active range was constrained by its support range setting in another group, even when it was disabled from support. This is now fixed so that the ART active range for a group is only constrained by activated ART support settings in other groups.
• Fixed some cases where Dirac Live could crash or freeze (APP-602, APP-661, DS-2034)

Known issues

• The 120 Hz low-pass filter introduced in version 3.13.2 applied to the LFE channel introduces a delay of about 5 milliseconds compared to the other channels.
• At first launch after first installation on macOS, Dirac Live will not detect devices on the network. Press the Rescan button to detect them.
• Progress tracker can sometimes jump backwards. (LIVE-4356)
• New filter exports are not displayed correctly in the application on some NAD devices. The filter can still be used and will be displayed correctly after reconnecting to the device (APP-555)

Download

Windows: https://artifacts.connect.dirac.com...e-candidate/win64/diraclive-v3.14.0-setup.exe
macOS: https://artifacts.connect.dirac.com...e-candidate/macos/diraclive-v3.14.0-setup.pkg

As an audio software developer myself albeit an amateur, working on free software and paid mostly in forum posts and bug reports, I know exactly what it’s like to write update logs like these. I can confidently say the team behind this update is clearly paying attention, hearing the feedback, addressing the complaints, and, most importantly, knowing what they’re doing. Dirac in particular has been impressing me lately, which honestly wasn’t the case not that long ago

and of course number PI rules!

 

[kawauso]

@kawauso
Now that you have a Cinema 50, can you see how many filters that are used ?
I cant see it on my C50.

Come to think of it, I can’t see any information about the number of filters either.

 

[dlaloum]

Now that's not to say that you cant "help" ART do it's thing, but I can't see how making significant changes to its variables is going to help...

.

All I can point to is the differences I am finding as I progress, starting with the default from Dirac - subsequent manual tweaks to the support groups and settings have stepwise progressed/improved performance from the defaults.

My results have been posted on this thread...

So yes, making changes to the default variables can help, and in my case has been helping.

However from the very first default configuration there was a noticeable subjective improvement - and I could have stopped at that point, satisfied that my investment in ART was warranted.

Measurements showed there was potentially more to be gained - and subsequent experiments have demonstrably improved performance.

Of course it hinges on what you consider "significant" change to its variables - I have disabled support by my height speakers, I have changed the lower limit of support for my full range speakers from the default, etc... do these qualify as "significant" in your definition?