More > JRiver Media Center 29 for Windows
DSP Change Requests
mattkhan:
there are a few things listed here which are already implemented in my app using the Load/Save DSP MCWS call - https://beqdesigner.readthedocs.io/en/latest/ui/manage_mc/ - which means for me personally I would put assorted UX things on this list as a lower priority :) they are still obviously valid improvements to make to MC itself though (as I wouldn't have implemented those features if MC had them already). The app above is free so you can download it and try it out yourself to see how that is designed if you like.
I suspect "Make per track DSP genuinely usable" is the most broadly useful feature though it's also probably the most complex and/or difficult to do.
For smaller things, I feel like "Raw Biquad filters" and "Allow channel count & mix target to vary independently" would be good (and hopefully relatively simple) additions because they make MC that much more flexible.
I also suspect there are other features out there that are audio pipeline related but the below is what I could easily find through search
mwillems:
--- Quote from: mattkhan on February 04, 2022, 09:28:18 am ---I compiled a list from various threads, tried to group them in some sensible way and provide links where possible
Missing Features
1) All Pass Filter
* implemented in 29.0.6
2) Raw Biquad filters
* i.e. allow user to input a0/a1/a2/b0/b1/b2
* useful to power users, lets them enter literally any biquad they like without having to ask for support from J River
* user interface will be ugly and/or tricky because coefficients vary by sample rate (i.e. you'd need to make user enter the coefficients n times (once per valid sample rate based on Output Format config)
3) Allow channel count & mix target to vary independently
* to make J River more attractive to users with active multiway speakers, particularly for multichannel setups
* e.g. 5.1 target with 12 channel output (2 way mains with 2 subs) or 2.1 target with 10 channel output (e.g. 3 way L + R with 4 subs)
* NB: MC DSP configuration already includes an "Output Padding Channels" which plays this role
4) Extend range of High/Low Pass filter types
* any order for BW, LR or Bessel as low or high pass
DSP Bugs
1) Variable Q High/Low Pass filters specify Q incorrectly
* the value has to be scaled by 2 ** 0.5
* see https://yabb.jriver.com/interact/index.php/topic,127946.msg889106.html#msg889106
2) Shelf filters specify Q incorrectly
* the value provided is used as S not Q
3) Known convolver bugs
* https://wiki.jriver.com/index.php/Convolution#Known_Issues
4) Subwoofer limiter applies boost instead
* https://yabb.jriver.com/interact/index.php/topic,114574.0.html
DSP Improvements
1) Improve bass management filters to avoid cancellations
* https://yabb.jriver.com/interact/index.php/topic,127245.0.html
2) Genuinely fast/transparent filter switching for A/B testing
* https://yabb.jriver.com/interact/index.php/topic,131945.0.html
Small(ish) User Experience Improvements
1) Rework the PEQ window
* keyboard shortcuts
* bulk select + delete + move up/down
2) Analyser tweaks
* Add labels to tick marks on y axis
* Allow user control of y axis limits
* Allow user selection of displayed channels
3) Improved granularity in Room Correction
* allow choice of units (ft/m/cm)
* allow delay to be specified in ms
4) Ability to rename channels
5) Create named blocks of PEQs
* can be approximated using the text "filters"
Bigger UX Changes
1) Visual PEQ editor and/or visualisation of current DSP
2) Ability to manage DSP configuration from another MC instance
3) Provide custom views tailored for common uses of mixing
* channel routing via a matrix mixer
* crossover design
Playback Improvements
1) Make per track DSP genuinely usable
* provide a mechanism to load/unload a configuration on a per track basis
* allow for overriding/extending a base configuration (e.g. to add just a few PEQ filters on top of existing configuration)
* allow for configuration to vary on a per zone basis
(more details in https://yabb.jriver.com/interact/index.php/topic,127946.msg887809.html#msg887809)
--- End quote ---
These all look good and jibe with my understanding of what's missing/might need fixing.
Just to clarify, can you be more explicit about what Missing Feature 4) means? I assume you mean, at minimum, offering filter slopes above 8th order? But do you mean something else too? I think we can currently dial in LRs and Bessels by specifying the Q (after conversion of course), or am I confused on that? Maybe you mean offering labelled "pre-sets" for those filter types that will set the Q appropriately? Or some combination of higher orders and labelled presets?
I think both would be helpful improvements, but the first is definitely missing functionality but the second is QOL (unless I'm mistaken, obviously). I just wanted to make sure the "ask" is clear :-)
--- Quote from: mattkhan on February 04, 2022, 09:33:38 am ---there are a few things listed here which are already implemented in my app using the Load/Save DSP MCWS call - https://beqdesigner.readthedocs.io/en/latest/ui/manage_mc/ - which means for me personally I would put assorted UX things on this list as a lower priority :) they are still obviously valid improvements to make to MC itself though (as I wouldn't have implemented those features if MC had them already). The app above is free so you can download it and try it out yourself to see how that is designed if you like.
I suspect "Make per track DSP genuinely usable" is the most broadly useful feature though it's also probably the most complex and/or difficult to do.
For smaller things, I feel like "Raw Biquad filters" and "Allow channel count & mix target to vary independently" would be good (and hopefully relatively simple) additions because they make MC that much more flexible.
I also suspect there are other features out there that are audio pipeline related but the below is what I could easily find through search
--- End quote ---
For my part, "Allow channel count & mix target to vary independently" is a longstanding wish of mine and has no good workarounds right now.
Also, I know that Visual PEQ Editor is a heavier lift, but every time that's come up it's a very popular idea. That said, I agree with mattkhan that BEQDesigner is a good solution for that right now, so it might make more sense to focus on the missing features and or outright bugs first.
JimH:
Thank you!
mattkhan:
--- Quote from: mwillems on February 04, 2022, 09:49:07 am ---
Just to clarify, can you be more explicit about what Missing Feature 4) means? I assume you mean, at minimum, offering filter slopes above 8th order? But do you mean something else too? I think we can currently dial in LRs and Bessels by specifying the Q (after conversion of course), or am I confused on that? Maybe you mean offering labelled "pre-sets" for those filter types that will set the Q appropriately? Or some combination of higher orders and labelled presets?
--- End quote ---
I just mean named filters up to some reasonable order (upto 24th perhaps which is pretty much a brick wall) limit. I called it a missing feature from the perspective of a typical MC user and was ignoring workarounds.
I.e. you can do it today using the variable Q filter but realistically no one can do that accurately without using a computer (e.g. beqdesigner), partly because how to calculate the required Q is not common knowledge and partly because of the Q bug in pass filters. I think even if you fixed the Q bug it would still be practically impossible for any normal user.
mwillems:
--- Quote from: mattkhan on February 04, 2022, 11:26:52 am ---I just mean named filters up to some reasonable order (upto 24th perhaps which is pretty much a brick wall) limit. I called it a missing feature from the perspective of a typical MC user and was ignoring workarounds.
I.e. you can do it today using the variable Q filter but realistically no one can do that accurately without using a computer (e.g. beqdesigner), partly because how to calculate the required Q is not common knowledge and partly because of the Q bug in pass filters. I think even if you fixed the Q bug it would still be practically impossible for any normal user.
--- End quote ---
Got it! Thanks for clarifying.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version