Falcon is all over the place.[
Complete different opinion here:
1.) Sampling is not a killer feature (except semi-automatic instrument sampling), because in DAWs you don't need it. Just record with the daw and pull the WAV-file in each sampler.
2.)GUI/workflow ist the worst in Halion because
a) It's easy to make failures and hard to find and fix them
b) Limited polyphonic Envelopes/LFOs per keyzone
c) Mixer and Effects on several layers is somehow messy for me
d) And OC the non-resizable GUI
3.) Not saying Halion is shitty. It has it's qualities, but I like working with Falcon waaaay more
Different trees, everything is siloed, confusing hierarchy, busy modulation section, cramped windows, too many menus for sample editing etc. etc.
Halion has one tree where you can see everything.
You can float windows, nest windows, make windows persist and configure it exactly the way you want it and then save those configurations to be recalled at a click of a button.
Being able to sample is a fantastic feature because it's part of the workflow of the plugin itself.
Of course you can do it in a daw but you can also add sequencers, filters, reverbs and delays in a Daw too. Is it not better to just have it right there in the plugin.
Resampling Halion's own output and then using that sample to build another sound without ever leaving the plugin is a fantastic workflow.
The only downside to Halion's UI is that the UI elements are very small.
Statistics: Posted by kraster — Wed Oct 16, 2024 3:21 am