I love the Fractal products. I think of it as a better-than-real amp (well, hundreds of them). But I think there’s some usability issues that could easily be dealt with. Here’s my wishlist, in rough priority order:
So, there. That’s my top-5 wishes. What do y’all think?
- Custom channel names. I would like to be able to look at my FC6, and, instead of seeing “Drive 1A”, see “Hot TS9” or “Mild Fuzz”. I.e. I would like to be able to give each channel a name: a short, custom string, and tell the FM3 to display when that channel is active. Wouldn’t it be better to show “Univibe” or “Mistress” instead of “Phaser 1A”? Or “HBE” instead of “Amp A”?
- Block Library match (an FM3-Edit-only feature). Let’s say I’m looking at a Delay block that matches exactly a saved block in my library. I would love for FM3-Edit to tell me that, so I know which blocks are set according to my “favorites” in the block library, and (consequently) which ones are not.
- “Channel Library” (again an FM3-Edit-only feature). When I download block definitions from the internet, it’s never clear to me if the blocks have more than one channel actually tweaked (and which one(s)). Just like I can save/load/share blocks, it’d be great to be able to load/save/share individual channels.
- “Authentic” elsewhere. Like the Amp block has an “authentic” section with the controls present in the particular amp being modelled, this would be useful for other blocks: particularly things like Drive, Flanger, Phaser, Chorus and Compressor. An “Authentic” section on Drive would save me from looking into Yek’s guide every time I need to remember which control is the fourth knob for the “Tube Drive 4-Knob”. And wouldn’t it be great to have an “Authentic” Mistress or Univibe? I love being able to tweak with parameters not present in the original devices, but many of these pedals were carefully crafted such that the knobs work well together. Having this “Authentic” page would make using the FM3 that much easier, particularly for beginners.
- A better transient detector. I know I can configure an ADSR controller to create, say, a touch-wah effect. But the trigger for the ADSR is a volume threshold. It can’t really be configured such that it works across a variety of input dynamics. I would really love it if I could set it to behave like a “transient analyzer” -- largely independent of the absolute input volume.
So, there. That’s my top-5 wishes. What do y’all think?