Windows > Third Party Plug-ins, Programs, and Skins
beqdesigner: a jriver dsp simulator and editor
jjazdk:
--- Quote from: mattkhan on March 04, 2023, 02:58:48 am ---definitely a couple of bugs in the latest impl of the XO filter in how it generates mix filters for your particular setup (combining RL/RR, cloning the SW to multiple sub outputs) so I'll have to look at those, nice test case for me as I hadn't thought of some of these as things to try
I also assume the .1 is an LFE channel so force the -10dB offset but you don't do that so I guess it really isn't an LFE channel?
--- End quote ---
The .1 is indeed an LFE channel, and I did have -10dB offset on the summation.
I have redone the entire signal chain via BEQ now, and will try it tomorrow. There are some bugs, or visual issues, with the view of the signal path, but it is a very nice overview.
Also I sometimes encounter an "unexpected error" when creating a peak filter. If I move position in the signal path and create the filter again it works, and after that I move the filter to the correct position.
I am still on beta14, but will download the latest again :-)
mattkhan:
--- Quote from: jjazdk on March 04, 2023, 02:25:11 pm ---There are some bugs, or visual issues, with the view of the signal path, but it is a very nice overview.
--- End quote ---
yes unfortunately it gets a bit confused with some mix operations since I changed it to show more of the actual filters, it's trying to minimise the no of redundant blocks in the graph to make it readable but failing to coalesce nodes properly at times (times which are commonly present in this sort of bass management operation). I plan to return to this once I finish fixing the filtering itself.
--- Quote from: jjazdk on March 04, 2023, 02:25:11 pm ---Also I sometimes encounter an "unexpected error" when creating a peak filter. If I move position in the signal path and create the filter again it works, and after that I move the filter to the correct position.
--- End quote ---
I have to fix this too but I've not yet been able to reliably reproduce it, if you do happen to find a way to do that then do lmk as then I can surely fix it.
fwiw the filter simulation is accurate on a per filter basis but I think it's difficult to be 100% sure about the routing that the XO filter can create, it is quite complicated to get this right without writing loads of unmaintainable code so pls do check this carefully. I would generally say measure (e.g. via REW) the digital only output as a sanity check after eyeballing the filters.
mattkhan:
the reason I rewrote the XO filter implementation is to support the matched delay subtractive filter approach that came up in this thread https://www.diyaudio.com/community/threads/why-not-iir-filters-a-global-phase-linearization-by-fir.393435/page-18#post-7227228
this is what the MDS button does on the XO filter dialog & it's implemented using an appropriately delayed set of mix operations with some tweaked bessel filters. It produces a linear phase result with a delay set by the DC group delay of the lowest crossover point. This currently has the following limitations:
* summation for bass management has to be done manually
* there is not normalisation of delays across channels if different MDS filters are used for different channels (i.e. each channel will have a linear phase result but the channels themselves will be misaligned)
both of these are easy to fix manually after the XO filter (though both aspects will be supported in the near future)
mattkhan:
beta.18 will be up shortly with a few more fixes which sorts out a few more routing issues (as seen in @jjazdk's setup, example attached) and some of the rendering issues in the filter graph view
https://github.com/3ll3d00d/beqdesigner/releases/tag/0.11.0-beta.18
StabMe:
Great tool!
I am trying to get a hang of Crossover and Bass management module. So, i want to set up a configuration that will be used for Stereo processing.
Physically, my system is set up like this:
L -> Left midbass
R -> Right midbass
C -> Left tweeter
SW -> Right Tweeter
SL -> Sub1
SR -> Sub2
RL -> none
RR -> none
C9 -> Sub3
C10 -> Sub4
In the crossover matrix, intuitively i am trying to set it up like this:
But it returns an error. Something along these line:
model.jriver.ImpossibleRoutingError: Overwriting an input channel is not supported - [2.1 -> 4 COPY]
I suspect, that my intuition has failed me and i am setting up routing the wrong way.
What i want to achieve, is to route L signal of the stereo mix to channels L, C, SL, SR, C9, C10, where L and C are midbass and tweeter and SL, SR, C9, C10 are sub channels. Of course, applying crossovers. Same to the right side of the mix.
In the future i'll be adding center and sides, so would like to know how to handle this as well with this tool. (i have two spare channels for multiway center and two for sides).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version