When I set the input transformer to a preset – such as “Pass Channel 01 Only” the preset is lost after closing and re-opening the project. Why? This renders the input transformer useless.
And the settings of the given preset are also lost ?
On my end, the preset name indeed no longer appear in the involved module Presets field (the Input Transformer has always behaved like this, actually), but its settings are still both displayed and functional.
Actually, I did some tests and you are absolutely right. How confusing! It is still functional, but the bug is that MODULE 01 shows “No Preset” loaded. It looks like it is lost - but it isn’t. Thanks for the pointer!
1 Like
Actually it’s probably not a bug but a common Cubase design philosophy for all kinds of settings including preferences and key commands and many more.
Cubase or a specific project remembers the settings, but not via a preference setting name.
Those settings are best thought of as “imports” and “exports” - more similar to MIDI files and less like plugin presets.
Arguably it’s actually more consistent than “presets” in plugins, because when you change a preset in a plugin in one project - it doesn’t generally change the settings in another project that uses the same preset (unless you specifically re-load the preset in the plugin).
But this “consistency” also has drawbacks compared to how plugins typically show presets.
So I’m not defending one way or another - it’s just trade-offs between different design philosophies and Steinberg has chosen theirs for Cubase.
That would be an odd design choice. It is inconsistent. The filter shows that a preset is applied until you close and re-open the project. Then it shows that you don’t have a preset applied, when you do have a preset applied. If that is a design philosophy it is from the UI School of Wackadoodle. I think they should fix it.
1 Like
If I remember well, the school mentioned is located somewhere in northern Europe, near a hanseatic city, but I can’t find again exactly which one. 
Indeed, but I don’t hold my breath : I’ve been grumbling against it since, at least, Cubase 4 days… 
Step 1 in the process of gaining higher visibility amongst the right individuals on this forum might be to tag threads accordingly - by editing the optional tag field in the thread title editor.
There’s an “issue ” tag for reporting bugs, and a “feature-request” tag for requesting functionality/design changes/additions.
Step 2 would be to be polite, and giving reasons. The “This is a stupid way to do things, my way is much better” style of request will just slip off the table into the circular filing cabinet. Good manners go a long way.
I don’t think anyone needs to be coddled. I prefer to be direct and to the point. If it were my product I’d appreciate it a customer told me something was broken.