What would the new-gen even have that the current gen doesn’t?

BobXX said:
It's easier to replace a tablet/smartphone than a FMx touch panel
Click to expand...
That’s for sure. I use an old iPhone connected to my fm3 for backing track playback (with preset switching via MIDI), vocal effects, and it also has FracPad installed. When I want to change something, I pick it up from the pedalboard, do whatever I need to do, and then put it back. So my FM3 already has a touchscreen and a wired connection :)
 
vangrieg said:
That’s for sure. I use an old iPhone connected to my fm3 for backing track playback (with preset switching via MIDI), vocal effects, and it also has FracPad installed. When I want to change something, I pick it up from the pedalboard, do whatever I need to do, and then put it back. So my FM3 already has a touchscreen and a wired connection :)
Click to expand...
1763901101680.png
 
An Ai prompt to adjust the tone to your specifics like "please reduce the attack pick noise", or "smooth the hi freq", or "more tighter bass frequencies "
 
Possibly mentioned already...

"If I was Cliff" the HUUUUGE no-brainer would be to have selectable firmware on startup (and default to last one used).

If an SSD is involved, let the user add as many as they like -- but at least 2 or 3.

The user can decide if they use certain preset banks for the old or newer firmware, or the process could be made configurable (e.g., tie a firmware to a bank) so the wrong presets don't get tweaked too easily by accident.

OTOH, if it needs to be written to a chip, I guess it cannot happen -- but still...; there is some benefit to have them ready in the device.

OTOH 2: You might include a chip that can hold two firmwares and go back to one if you run out of memory.

TIA! ;)
 
Last edited:
Brewce said:
Possibly mentioned already...

"If I was Cliff" the HUUUUGE no-brainer would be to have selectable firmware on startup (and default to last one used).

If an SSD is involved, let the user add as many as they like -- but at least 2 or 3.

The user can decide if they use certain preset banks for the old or newer firmware, or the process could be made configurable (e.g., tie a firmware to a bank) so the wrong presets don't get tweaked too easily by accident.

OTOH, if it needs to be written to a chip, I guess it cannot happen -- but still...; there is some benefit to have them ready in the device.

OTOH 2: You might include a chip that can hold two firmwares and go back to one if you run out of memory.

TIA! ;)
Click to expand...
I would rather see the firmware split into two parts - #1 amp modeling & #2 everything else. There have been several times in the past when I preferred previous amp modeling but wanted the effects, improvements and bugfix updates. I think this could solve a multitude of complaints (until we figured out something else to bitch about) :p.

Edit: Just wanted to add the modeling is excellent and we have seen great progress moving toward tube amp emulation perfection, but sometimes our ears and fingers get tuned to a certain sound that is still great although slightly different.
 
Last edited:
Brewce said:
Yeah, that's a great idea too!

I will always lust after some of the "plastic" leads of Gen I -- LOL. But I'm slightly diverging. Pls include "plastic amps" ;)
Click to expand...
maybe amp modeling slots for two versions to pick from. this could also be helpful for people that want identical tones from their older recordings but jump to the latest and greatest when needed or that itch needs scratched.
 
Brewce said:
Possibly mentioned already...

"If I was Cliff" the HUUUUGE no-brainer would be to have selectable firmware on startup (and default to last one used).

If an SSD is involved, let the user add as many as they like -- but at least 2 or 3.

The user can decide if they use certain preset banks for the old or newer firmware, or the process could be made configurable (e.g., tie a firmware to a bank) so the wrong presets don't get tweaked too easily by accident.

OTOH, if it needs to be written to a chip, I guess it cannot happen -- but still...; there is some benefit to have them ready in the device.

OTOH 2: You might include a chip that can hold two firmwares and go back to one if you run out of memory.

TIA! ;)
Click to expand...
Imagine how hard is to officially support a device with multiple firmwares.
 
zebric21 said:
Imagine how hard is to officially support a device with multiple firmwares.
Click to expand...
For example?

Maybe you're misunderstanding...

It goes w/o saying that if people want most bugs fixed they should use the latest. But older ones usually work well enough to be usable if you prefer them at some point.
Esp. in the current gen, one may want to go back to the earlier "idealized amp" philosophy, for example. Sure, you can already do that -- but maybe it can be made easier.

Also, since this may be the last ever flagship under Cliff's reign, it would be cool to have some history built into it (like a mode that goes to "idealized" again.)
 
Brewce said:
For example?

Maybe you're misunderstanding...

It goes w/o saying that if people want most bugs fixed they should use the latest. But older ones usually work well enough to be usable if you prefer them at some point.
Esp. in the current gen, one may want to go back to the earlier idealized amps, for example. Sure, you can already do that -- but maybe it can be made easier.
Click to expand...
Software fragmentation is not a good thing. You can still use older firmwares if you like but you can't expect to get any help if anything happens.
 
zebric21 said:
Software fragmentation is not a good thing. You can still use older firmwares if you like but you can't expect to get any help if anything happens.
Click to expand...
I guess I don't see it as fragmentation...
Not being able to get at your old sounds has been one of the HUGE frustrations throughout the years. I think anything that can help relieve that is a help, however small.

Also: IMO much more people would beta test if it was made easier ( ! ) -- which it would be if you can more easily use versions.
 
Brewce said:
I guess I don't see it as fragmentation...
Not being able to get at your old sounds has been one of the HUGE frustrations throughout the years. I think anything that can help relieve that is a help, however small.

Also: IMO much more people would beta test if it was made easier ( ! ) -- which it would be if you can more easily use versions.
Click to expand...
Old sounds. You mean the slight adjustments to play more accurate models. If you are not willing to turn maybe 2 knobs then maybe it's not your thing with fractal. Not a personal argument offcourse. You do you.
 
zebric21 said:
If you are not willing to turn maybe 2 knobs then maybe it's not your thing with fractal. Not a personal argument offcourse. You do you.
Click to expand...
You're just being closed-minded or lacking long-range experience?
You cannot go back to the idealized amps by "turning a few knobs," AFAIK.
Every firmware can potentially have a gem that subsequently disappears. I even remember magic from Gen II fw 4 that never came back. People have preferences depending on the situation, etc.
I've been w FAS since early Gen I, BTW. I'll let you do you from here...
 
Brewce said:
You're just being closed-minded or lacking long-range experience?
You cannot go back to the idealized amps by "turning a few knobs," AFAIK.
Every firmware can potentially have a gem that subsequently disappears. I even remember magic from Gen II fw 4 that never came back. People have preferences depending on the situation, etc.
I've been w FAS since early Gen I, BTW. I'll let you do you from here...
Click to expand...
I never had any problem replicating my sounds through firmware updates.
 
vangrieg said:
What’s that philosophy? Don’t think I’ve ever heard about it, what do you mean?
Click to expand...
AFAIK, it's what Cliff was all about until he felt pressured into having amps behave as real as possible... I don't remember which firmware started making the change but it was maybe 3 or 4 years ago.
Every time I mention this in some way, some people are getting their panties in a knot, yet it's there somewhere in his own words! I received a massive attack in a thread once when mentioning the same thing... Yet it's all there and very clear.
 
Last edited:
Brewce said:
It's what Cliff was all about until he felt pressured into having amps behave as real as possible... I don't remember which firmware made the change but it was maybe 3 or 4 years ago.
Every time I mention this in some way, some people are getting their panties in a knot, yet it's there somewhere in his own words!
Click to expand...
If you’re talking about somehow running code from 3 or 4 years ago in future firmware, I can bet it won’t happen.
 
NeoSound said:
maybe amp modeling slots for two versions to pick from. this could also be helpful for people that want identical tones from their older recordings but jump to the latest and greatest when needed or that itch needs scratched.
Click to expand...
For a while, the Axe Fx II supported an option to select the current or previous amp modeling algorithm (not the entire firmware).

It didn't last too long...

It makes the code larger, which takes longer to load and (I think) to boot.

Allowing the hardware to store multiple firmware versions to boot from is an option, but that takes additional storage which costs money and most people probably wouldn't use the feature.

Additionally, remember that presets saved under a newer firmware are "empty" on a prior version...

This would also potentially be further complicated because of the DynaCabs.
 
vangrieg said:
If you’re talking about somehow running code from 3 or 4 years ago in future firmware, I can bet it won’t happen.
Click to expand...
I wouldn't bet, seeing how much Cliff was into it himself... Why not respect/offer both philosophies (if it isn't too difficult)...?
But I will bet you could be right... ;)
IMO both philosophies have their charm. I would find it sad if a dev suddenly thinks one philosophy is "too inferior." IMO it would be cool if we can emulate anything from the past, so to speak.
 
unix-guy said:
For a while, the Axe Fx II supported an option to select the current or previous amp modeling algorithm (not the entire firmware
Click to expand...
But even then it wasn’t an independently installed component, so old models were never released this way. There’s just nothing to install from 3 years ago, and I doubt anyone would spend resources on building, testing, compiling and packaging some old models.
 
You must log in or register to reply here.
Back
Top Bottom