Hi there,
I’d like to see the preset system expanded to include FFT settings as a checkbox option when saving an Module preset.
In the preset list, the user would also be shown which presets have FFT stored with a little +FFT icon next to the preset name.
Additionally, it would be great if the list of modules and the modules themselves had some sort icon designation to inform the user they are FFT based.
Thanks
typo? do you mean sort of icon?
or “sort icon” an icon that identifies what is sorted?
I cannot fathom this being a priority for SLP. Is it really that difficult to consult a PDF? Where’s he minus one vote button 
In use; actual manual selection and editing in the spectrogram (which is the truly time consuming activity when using SLP). I can see many other suggestions being more important which have been suggested over the past 18 mos.
I mean, we have only recently with launch of SL12 had the ability to load previous presets into future version releases.
I’d much rather have reduced lag with preview selection tools (for example clone stamp); and would LOVE hot buttons for 3 most used brushes’ size and shape per tool. Even expansion of user selected layer color is something I would like more…things that SLP is currently not capable of as opposed to a luxury.
A lot of improvements could be made to the spectral editing in SL.
My concern is the developer has lost heaps of time dealing with ongoing problems related to unmixing since release of SL12. Improvements to spectral editing are being neglected.
Sort of.
It’s not a priority but it’s also an easy GUI implementation.
I’ve read the manual.
There are a lot of processes to remember which is FFT, I’m not always using SL daily, and sometimes I have hired assistants so it’s quick intuition to have things colour coded/signified.
well, then we might as well have some visual differentiation for tools that tie to transforms and tools that are free form, which frankly affects me far more in my day to day
or tools that are destructive and non-destructive
Hey, all my opposition aside, I had thought @Robin_Lobel was considering something along the lines of what your OP is requesting…I might have that wrong
it’s just, I think a fair amount of the regulars here are looking for Robin to address more serious issues for day to day
and we do have quite the different camps of post for film and TV and the music unmixers 
Robin did mention it would be looked into for SL12 here: https://forums.steinberg.net/t/fr-add-visual-cue-on-modules-tools-that-depend-on-fft-size
right, 11 months ago
They also need to make the product as intuitive and quick to pick up, with people getting good results quickly and easily, so that they head to the shopping cart button after the 30-day trial… So that Steinberg/RL can afford to work on bigger features/issues that you and others seek to acquire.
Someone new to the program, might not realize that FFT plays a part in a particular process and thus, not get a good result and thus - not buy the software.
Another reason why I think FFT controls should actually be built into the modules
How it could work is:
This allows users to store FFT settings with their presets and in the case of the chain module - can have a series of FFT settings automated as a single process.
It also allows users to leave their main FFT/resolution settings at a standard working average instead of having be always messing with it.
As it stands, for example when I’m working on a problematic source material such as a location recording of a moving dialog boom mic that is very inconsistent… I’m having to write down all these FFT settings per preset per section or even sometimes per word to be able to recreate processes when applicable to the source material in a bid to even out and balance the audio to sound like a stationary close mic.
Personally, I only adjust FFT settings when targeting specific “out of focus” frequencies. I suppose if someone specializes in low end editing, the delay can be difficult to tolerate.
When I work in SLP, I mainly have FFT set to 1530-2048 for 80-90% of my tasks (mostly dialog NR). When I need to work on low end, I pretty much set my display area (time range) before changing FFT settings and then change FFT; carry out the editing and switch back to smooth navigation FFT settings after the edits.
goodness, yeah, no I don’t do that. Are you just mainly processing modules? I seldom run modules; I mostly do manual selection work after running unmix noisy speech
or NR on ambience
I’m doing everything every which way of combination, forwards backwards up and down, to get the desired result - which works but takes time and requires organization.
I always take notes, it’s very important for step recreation.
I just use non-destructive (as possible) processes which is fairly self-explanatory
I mean, I certainly have a set way of doing things in SLP as I’ve described many times on this forum. How long have you been using SLP?
since they came to Steinberg, I think that was version 6. Prior I used RX
right, so a lot more experience than I have
Well, I still need reminders about which modules are FFT 
… Mind you, a lot of new ones have been added since version 6 and many features I haven’t used, at least not without a deep understanding/research yet.
100%
This is not so hard to understand and implement, imho.
SL is still in beta-phase, technically. So many bugs and crashes, I am tired of this.
It’s the nature of being on the user end of cutting edge software development.
Adobe
Davinci Resolve
etc, etc. All have bugs and crashes.
Sure, but all the basic functions should work flawless and intuitive as one can expect.
Instead of more and more implementatios of this and that, they should work on stability and reliability first. SL 12 still feels like a beta.
New feature videos sell products while introducing new problems.
It’s just the nature of trying to make money off software. I’m sure they are working on bugs and stability, because stability reputation does catch up with software sales eventually.
For me it is working pretty good, not too many crashes - and I religiously hit ctrl-alt-s (nearly after every change I make in Cubase/ARA2).
Speaking of crashes, just got one 
I seem to get quite a few when it comes to ‘Preview’/bypass in modules. Once my work movements get too fast and brash, clicking things on off, preview, stop, bypass, preview, etc, etc… I’ll get a crash. I learned to be gentle here..
Izotope RX is stable and offers much better spectral editing features IMO.