You can already save and load the configuration for the entire DSP Studio. That was a new feature in MC21.
It seems like that would work pretty well.
Swapping out the entire DSP chain is what I'm looking to avoid.
I'm looking to have quick presets that I can can change for certain tasks, similar to the way that we can load/save presets for other individual DSPs.
One example would be to EQ for a specific headphone.
Depending on the headphones that I'm using, I will have a different EQ preset which is a list of 5-10 filters that I currently have to manually switch on/off.
I could set up a zone for each headphone, but they all connect to the same playback device, so then I would have to disable zone switch.
Being able to add additional Parametric EQ stages would help separate complex EQ chains.
There is some EQ which
must be performed early, and other EQ which must be performed
after another stage.
I currently have both Parametric EQs performing multiple tasks at once. One at the very top (well, as high as JRiver allows) and one as the very last thing.
I would prefer to use one Parametric EQ plugin for each task, making it possible to toggle a task in a single click or easily make adjustments, instead of selectively enabling/disabling/editing parts of one of the two Parametric EQ DSPs.
There are a lot of ways that I would like to see zones, presets, and tagged files expanded.
JRiver is probably leading in its field in most cases involving DSP. However it falls down on relatively "simple" tasks like assigning an EQ to a single file, compared to something like iTunes.
Because you can do so many things in DSP Studio at once, saving the whole lot and assigning it to a file is not a very useful thing to do - especially when the changes are not transient. The way it works in JRiver right now can actually be quite destructive.
I think we have to draw the line when things just make no sense. This is a completely pointless option, in my opinion.
FLAC does have better tagging support than other uncompressed audio formats.
I don't know why anyone would use it to store their music, but when I do a "convert video to audio" or if I'm converting DSD to PCM, I use WAV because if I'm doing that I will be dropping the file into an editor and cutting it up before creating my final track.
So the conversion in JRiver is just an intermediate format, and conversions to WAV go a
lot faster than FLAC because it's uncompressed. Even FLAC 0 takes a lot longer than WAV.
If I could get that speed without losing tags (which I think is more an issue with the "receiving" program not reading extended tag info with WAV files) that would be a small thing which saves a bit of time every so often.