RenPa
Member
- Joined
- Dec 7, 2022
- Messages
- 88
- Likes
- 27
In my DLBC projects with 3.4.4 xo are at 80Hz for all groups.What do you have you Sub-mains cross over set to? My comment above assumes that the x-over is set to 80Hz or higher.
In my DLBC projects with 3.4.4 xo are at 80Hz for all groups.What do you have you Sub-mains cross over set to? My comment above assumes that the x-over is set to 80Hz or higher.
Of course:Can you please re-post the above diagram with these settings?
OK.Both those above graphs look way better compared to the DLBC wavelet you had
(from post #22)
View attachment 407151
Have you tried asking Dirac why this is?OK.
What seems evident for you and some others and me too about the importance of mastering the group delay doesn't seem the case for Dirac. I refuse to think they are stupid. So what explanation can we find?
I don't want to seal my ported subs. But do you think it would help DLBC with GroupDelay if I seal all the satellites? I know to safe answer is try it it but in theory ?
Sorry my knowledge doesn't help me to understand what do you mean. If it is important I must to understand before opening a new thicket to Diracpoints to a non-zero DC offset in the impulse response.
No. I opened already a ticket long time ago for Arcam bugs with DLBC firmware update above 3.4.4.Have you tried asking Dirac why this is?
It's a bit too technical but step response swings should normally gradually fade out over time and since it's the integral of the impulse response, impulse average must be non-zero. This is not something Dirac would intentionally do and is most likely a bug. That could harm hardware in the long run, too. More info below:No. I opened already a ticket long time ago for Arcam bugs with DLBC firmware update above 3.4.4.
I wish @OCA will explain what he meant by non-zero DC and will see if I can add it to the ticket.
What I can't begin to understand is if the solutions are not so difficult to find when you know the basics (not like me but like OCA or you) why on earth such a big company like Dirac can't do it ?
I posted an mdat capture of this in another thread, and I think DIRAC is the unintended bug. (Because it's also in known issues)As you can see the GD now looks way better
To me this proves that DLBC is the culprit here and your system could indeed be integrated in a much better way
If you could somehow change the delay values manually, that sould bring much better results (like the one above)
This cannot be normal and intended (at least in my opinion)I posted an mdat capture of this in another thread, and I think DIRAC is the unintended bug. (Because it's also in known issues)
It may be different for each person, but a user from another community who provided me with dlbc vs dlbmdat said that when DLBC was active, it sounded like a lot of sound (negative, almost reverb, not the good side).
View attachment 407308
View attachment 407310
And his auditory feeling is explained by this delay, which of course appears in GD, and the difference of 20ms is something I can't understand in any way.
Of course, some people say that Dirac would have intended it.
OK.It's a bit too technical but step response swings should normally gradually fade out over time and since it's the integral of the impulse response, impulse average must be non-zero. This is not something Dirac would intentionally do and is most likely a bug. That could harm hardware in the long run, too. More info below:
This looks how it should (in my opinion)And here REW measurement for front left + 2subs DLBC off and xo 80Hz and delays in receiver.
The FR is not so cute than with Dirac on:
View attachment 407460
But GD seems better (as alignment tool predicted)
View attachment 407461
Remain to ear how it sounds. DLBC must do other choice than prioritize GD over FR response...