The purpose of the graph editor is to be able to edit note properties from step sequencer, note properties are not automatable although with the new VFX Level Scaler plugin for patcher that can now be effectively achieved. I believe the reason the graph editor was removed was because in the past the step sequencer and piano roll were separate entities but then they were essentially re-written and merged, I don't know the exact reason the graph editor wasn't included initially but it was probably deemed not a priority since there was no functionality lost, you just had to go into the piano roll to edit note properties.V_Grey wrote:
In the meantime you bring back an alternative much more limited and seemingly unpractical to use...
In short you have a problem thinking we need *more* stuffs.
We don't need 10 alternatives to do the things. We need *at least one* that is as flawless as possible. Then it is our responsibility as user to learn the flow and use the tools we have correctly... and if one possibility is not perfect, provide an alternative without the problem is a great idea indeed.
But here, really, aside from being fancy, what does this graph editor bring ?
In MS Word, there is not 40 ways to color a text in red. You just select and color, and that's done. And nobody complains because that's just the way it goes.
Why do we need different control per pattern with this graph editor when we already have much better automation tools ?
Or maybe I'm missing the point of this editor... in which case thanks for explaining.
This seems to be in the works, with the new beta groups in the playlist can collapsed allowing to effectively hide automation clips.V_Grey wrote: But what about real workflow improving features ? Like improved grouping on the playlist or in the mixer ? Like possibility to hide automation ?
V_Grey wrote: Like not displaying mixer inserts with no instrument routed to them (taking space for no reason...) ? Like having just the possibility to reassign an automation clip to something without having to go to internal link > select > crazy long list of stuff that are tough to decipher
The long term goal for the mixer is to have 500 maximum mixer inserts which are added dynamically, according to the developers this is not a trivial task. Do you really think they just haven't implented it or other common sense improvements because they don't want to? Give the developers credit, based on the results they are achieving we can assuming that they are both intelligent and capable.
How would you suggest they deal with linking controllers? If you can't make sense of the list of internal controllers then that is your fault, you can name them anyway you like.
You select 'save as preset' and drag and drop it into patcher.V_Grey wrote: What about the number of mixer FX slot ? We need not be limited. Say I put everything, those 10ish slots are used. Then What ? I patcherize this chain or send the output of the mixer to another one mixer insert ?
Well to patcherize, there is no shortcut... To route, there is the latency problem (though should be solved...). Why can't the default mixer FX slots number being unlimited and auto patcherize when trying to put one more FX ?
It sounds like you might happier with a linear DAW, do seriously expect them to make FL into a linear DAW and destroy what makes it unique, not to mention destroy backwards compatibility in a huge way? Improving organization seems to be one of the main focuses of the development team right now, be patient, the complexity of the FL's non-linear framework means there aren't simple solutions, but you can look at FL's development over the last 20 years and observe that it has been in a constant state of improvement.V_Grey wrote: Why is renamming anything in FL so crazy painful ? Sure the linking function you talked about is gonna help, a little, but I am not convinced... because once again, you refuse to remove what creates the mess : the possibility to do anything in anyway...
Please *limit* the possibility to route stuffs and so on because it just makes impossible to get a clean structured software... projects that are big and relying massively on mixer FX and automation are unbearable to sustain...