Timmy C
Distinguished Member
- Joined
- Oct 10, 2003
- Messages
- 7,973
- Reaction score
- 1,822
- Points
- 1,604
- Age
- 51
That was what I was hoping to find out more about. I searched last night and only found the update mentioned on an Arcam and Onkyo chat thread with no detail.What does the first line mean? Does anyone know what that actually does, as it sounds interesting?
Loading projects has also caused it to crash twice now which is new but I'm not sure that's supposed to be a feature!
If you turn on and off the "detected range" checkbox do they appear and disappear? Or are they connected to the target curve at all?
I'll have a go using fresh measurements at some point, it may be that it's mostly but not fully compatible with older measurements.
I noticed last night that the old measurements loaded onto my receiver using the 3.3.0 app are wrong. Looking in the speaker configuration screen, the two filters I loaded from 3.3.0 don't have levels or distances, they're all 0dB/ms.There was an update from the Dirac guy on AVS saying you can check the conversion by comparing the measured impulse response. If it's the same as it was with the previous version then all should be good with the conversion. Or at least I assume he meant impulse response but he called it something else.
I think I'm getting on fine with it now but my amp only has the one slot so comparison isn't a quick or easy process.
So it's not specific to 3.3.0, just a faulty load? As far as I'm aware it's the first time I've had it, but I've not gone looking for it before.That’s what mine does all the time :-(
So it's not specific to 3.3.0, just a faulty load? As far as I'm aware it's the first time I've had it, but I've not gone looking for it before.
It might explain why even minor adjustments can completely ruin a "good" curve for me though.
Dirac always leaves the levels and distances set to 0. You can change them, but anything you do will be added on top of what Dirac has already done.So it's not specific to 3.3.0, just a faulty load? As far as I'm aware it's the first time I've had it, but I've not gone looking for it before.
It might explain why even minor adjustments can completely ruin a "good" curve for me though.
Dirac always leaves the levels and distances set to 0. You can change them, but anything you do will be added on top of what Dirac has already done.
On my NAD it always sets them to values and they're locked/greyed out.Dirac always leaves the levels and distances set to 0. You can change them, but anything you do will be added on top of what Dirac has already done.
On the Emotiva XMC-2, Dirac sets levels and distances to 0 after calibration. You can change them if you like, but whatever you do with be an overlay on whatever Dirac has already done. I am not sure if Dirac 3.3.0 has changed anything relative to crossover selection, but prior to 3.3.0 the crossover was set in the processor, independent of Dirac. I noticed in Jerry Austin’s paper that Dirac seems to, at least, suggest a crossover point.On my NAD it always sets them to values and they're locked/greyed out.
When entering distances manually they are in meters. When Dirac has measured them they're in milliseconds.
The only adjustments you can make are during the measurements and the target curve.
I am not sure if Dirac 3.3.0 has changed anything relative to crossover selection, but prior to 3.3.0 the crossover was set in the processor, independent of Dirac. I noticed in Jerry Austin’s paper that Dirac seems to, at least, suggest a crossover point.
I think that's for those with the optional bass control (DLBC) add on. Something I don't think is even an option on my older Arcam model.
Thanks. That makes sense. I thought I had missed it. Maybe Emotiva will have DLBC one day…I think that's for those with the optional bass control (DLBC) add on. Something I don't think is even an option on my older Arcam model.