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

My wishes for a new flagship unit:

Ability to choose how many Effect Blocks of each type can be used instead of having a fixed amount per effect type (for example, ability to have more than 2 Pitch blocks, less Reverb blocks etc)
Ability to attach a Modifer to any parameter.
Even more Analog I/O (5-6 stereo pairs of Inputs, with Input 1 also being a stereo input)
Envelopes from any of the left and right inputs available as multiple controllers per preset.
Expanded Pitch Follower that can be assigned to actual notes that cover the entire 5 string bass and guitar range, allowing specific notes to act as controllers.
Expanded PItch Tracking for the Synth and Ring Modulator Blocks that tracks the entire 5 string bass and guitar range just like several modern pedals can do (eg Source Audio C4)
Ability to host 3rd party plugins.
 
To be honest, I'm incredibly happy with my FM9 as it is. The last few updates have been nice and it continues to improve sonically, but I love how it sounds and I can do everything I need to within reason on a gig. I wish the virtual capo tracked and sounded a little better when you get past a whole step of transposition is probably my only beef.
 
My personal wishlist:

Touchscreen
WiFi
Bluetooth
Dedicated Aux In
Independent headphone volume
USB-C in addition to keeping USB-B. Lose or make USB-A fully functional.
Mobile Apps
2-U only if possible without loosing power or gaining fan noise
AI tone matching and patch creation

Someday - fanless, 1-U

Consider one premier retail partner you could count on to not besmirch your reputation. I think this would improve visibility, turbo-charge sales and quite possibly meaningfully assist with support. I recommend Sweetwater based on 20 years of buying from all over. They are the gold standard IMO on everything but price. They are worth that concession to me personally. If that’s a bad idea for some reason I don’t know…

Ignore all of the above, Team Fractal, if any of it detracts from you doing what you think is best to deliver the best at the most reasonable prices.

I love my AxeIII AND FM3T. I can not adequately thank you for your dedication and world class continued firmware support. I wish you nothing but the greatest of success on all future products. A nice one would be the FM0 concept bandied about. Something similar in form factor to the Nano Cortex as an example. I think a lot of us wouldn’t hesitate to pull the trigger on that and add it to our stable.

Regards and best wishes, Jason

P.S. Thanks for visiting TGF from time to time. That community outreach is much appreciated by me. I’m not affiliated, just a member.
 
Tremonti said:
I guess a touch screen baffles me. It does for the
6 Stadium as well. I would think an iPhone app would be better as who wants to hunch down on the floor?
Click to expand...
I was probably thinking just for the axe4 the floor unit would remain the same but I like the idea of the editor for iOS for the floor unit. I have fracpad and it’s good but not quite as good as the editor.
 
What about being able to shunt a block in a scene instead of disabling it (turning it off to pass-through)?

I know you can achieve the same by creating a similar preset as the original one and simply remove the block you don't need.
Asking if it's doable in a scene - and what the programming/memory overhead would be to achieve this.

Mean dirty dry tone and lush cleans in the same preset?

Just saying.
 
Vio said:
What about being able to shunt a block in a scene instead of disabling it (turning it off to pass-through)?

I know you can achieve the same by creating a similar preset as the original one and simply remove the block you don't need.
Asking if it's doable in a scene - and what the programming/memory overhead would be to achieve this.

Mean dirty dry tone and lush cleans in the same preset?

Just saying.
Click to expand...
I must not be understanding you.

Of course you can bypass blocks on a scene by scene basis. That and block channel settings are most of what scenes consist of.

Am i totally misunderstanding your question?
 
Register and play multiple loops or backing tracks ?
Integratet wireless guitar interface ?
Kill once and for all the AITR syndrome ?
Mooger fooger Murf equivalent block ?
Voice interface and automatic android guitar app that will pilot my left foot toes on the neck just when thinking about a Hendrix solo
An automatic stair walker for when you get home late after a gig.
Etc etc
 
I think there is room for improvement across all modelers when we talk about latency with pitch tracking and polyphony. Fuzz pedal modeling could also be improved, especially the weirder stuff that starts to self oscillate.
 
Let's not forget to add a direct out so we can run a true wet/dry/wet set up if we want to. Like how the Boss sde-3000evh is set up. That would be cool
 
Dave Merrill said:
Color me thick, don't get it.
Replaced when?
Why is that better than bypassing it?
Click to expand...
When it's being bypassed. Instead of the block being bypassed, they want it to be replaced with a shunt, their reasoning probably being that a shunt uses less CPU than a bypassed block.

AFAIK, the way bypassed blocks work (still using CPU, still "listening") is to minimize latency/artifacts when activating the block. So I don't know about the feasibility of the wish. (But since we're talking about a future architecture, hey, who knows. I want it to have an integrated dry-ice thingy for when I want to suffocate in my bedroom.)
 
Dave Merrill said:
Color me thick, don't get it.
Replaced when?
Why is that better than bypassing it?
Click to expand...
Lookup blocks cpu usage.
When added to a scene, a block might take up to 6.8% if it's a drive, 10.5% for a Reverb on High, etc... when a shunt will take about 0.2%.
1750338676592.png
So in a block, it would be nice to have as "Bypass Mode" the Shunt option.
not sure how this can be done programatically in the DSP world but I guess it would be by de-registering the block from the signal path.
Of course this could have as side effect (get the pun?) the fact that killdry, gapless switching and who knows what else, won't work anymore...
The current gen is good already as is :)
 
Vio said:
Lookup blocks cpu usage.
When added to a scene, a block might take up to 6.8% if it's a drive, 10.5% for a Reverb on High, etc... when a shunt will take about 0.2%.
View attachment 156100
So in a block, it would be nice to have as "Bypass Mode" the Shunt option.
not sure how this can be done programatically in the DSP world but I guess it would be by de-registering the block from the signal path.
Of course this could have as side effect (get the pun?) the fact that killdry, gapless switching and who knows what else, won't work anymore...
The current gen is good already as is :)
Click to expand...
Got it. I sometimes switch blocks to their least CPU intensive channel if they're bypassed in a scene, similar idea.

My understanding though is that the reason bypassed blocks still use CPU at all is so they can be enabled more quickly and with fewer artifacts. My guess is that if it was practical to shunt them instead, that's what bypass would have done.
 
You must log in or register to reply here.
Back
Top Bottom