The load/save DSP chain feature is at present quite hidden and not graphically bound to a specific track. My idea was to convert DSP load/save into presets that can be stored and restored. The list with presets are (as logically) placed as an (extra) field left or right from the DSP tree pane.
When hovering over the different presets, you get an small popup text like [dist->delay->reverb].
I’m not sure yet how the user can view the DSP presets. It can be by:
Hmmm, guess nobody uses the load/save feature, or is happy with how it now works…
(I thought it would be really cool to cycle through your saved DSP chains that way)
Im/Export of DSP Chains is indeed often overlooked in Renoise. I think we should right now at least offer a “Save Device Chain As…” context menu entry in the chain, just like we did for Samples & Instruments?
Exactly! I always forget it, and end up with recreating the same chains over and over again. Also because it is not specifically/graphically “bound” to a track has not helped to improve the user-friendllyness of this powerful feature.
Saving is nice, but not of that need if loading is not improved as well. Thats why cycling through them is so nice. But you need another list-pane for that somewhere in the track-context - and that cost expensive space (maybe a fold-away-tab?).
Don’t know how the sound buffer/CPU reacts during a lot of cycling through (long) DSP-chains, could that be a problem?
When you currently load a Chain does it load it over or insert it into the existing dsp chain? The name always made me think it would overwrite the current DSPs.
Ledger’s solution sounds fairly workable, especially if it would insert like with normal DSPs.
One thing that would make it even nicer would be the possibility to tie DSPs together, so dragging and moving one would move the whole group of them. Obviously this would be something that can be enabled and disabled at will.
Then, once this is done, bring in the streamlined view where you can select a collection of sliders to be displayed on a meta-interface and have access to the most used parameters from a minimised view.
There is an option under files in advanced edit for this. If my solution were implemented then this could be added under the right click menu aswell:
Load over current chain
I guess the way to do this would be to have a Shift/ Ctrl select system when the DSP view is in focus. i.e.Ctrl + middle mouse-click allows a discontinuous selection, Shift for continuous.
It could work, but it sounds a bit quick and dirty. Since the outcome of the DSP tree click now is always a single dsp which is always inserted (so the behav is pre-known). Suddenly replacing this with a bunge of them, implies a different workflow and could obfuscate the way of insertion (replacing the previous chain? or always append chain to the end?). I’m more a fan of a tab (also saves a right click when trying multiple chains) that if you click it, the DSP-tree-pane slides left and the DSP-chain-pane itself becomes squeezed in. This new tab gives you the list of presets and the ability to delete/rename them. When double-clicking a list entry, the chain is fully replaced. Other actions can be covered by the right-click context menu, like the insertion of a whole chain somewhere in the existing chain. This allows you to apply your earlier saved “building blocks” (small parts of chains) as well (very useful with the new signal follower!)
Smart! Would make me use the whole saving/loading chain thing much more often I think. But creating chains from within the dsp list should be made easy as well than imo. Either by dragging dsp/vst’s to the chain node, or by being able to highlight selections (ctrl and or hold shift clicking) in the list and have a ‘create chain’ option.
This does indeed sound like a more complete solution, with the expense of an extra tab. The extra tab is for me the strongest arguement I can think of for my solution (and maybe easier to implement). But not strong enough to oppose your solution fully also. I could live with either
Sounds good, I think the Ctrl/ shift option you mention would be the more practical of the two, though with the current more button the dragging could be quite efficient also…
Been mentioned in another suggestion but I couldn’t find the thread to link you. Not sure if it’s in this forum or was put in the one for the 2.5 Beta release. Nice idea I though.
