Hello forum
I’m new to the Aeros, coming to it from my Pigtronix Infinity Looper. I’m attracted to the Aeros mostly for the four outputs… routing loops independently for discrete processing is very appealing to me.
There are two reasons why I hope to retire my Pigtronix pedal. The first is the decreasing quality of its software support; I use a decade old version of its editor (on a decade old laptop) just to access certain functions like “set fade time” that are no longer accessible.
The second reason, and the main reason, is the slight click sound that occurs when a loop starts or ends. It doesn’t have to be this way! A start/stop can actually be a 20ms fade in/out!
In my initial usage of the Aeros, the latter problem remains an issue. The minimum time I can allow for a track to “fade in” is 1 second. Can this not be reduced to 20ms? 50ms? So my starts are clean? The same for “fade outs”, if I effectively want a noiseless stop?
Secondly: one of my favourite features on the Infinity was the ability to “fade to end of loop”. When you send a stop command, it begins a fade, ending at the end of the loop. Could this be possible on the Aeros, short of me estimating a value in seconds and setting it for each song?
(Also worth noting: the Infinity originally had a feature where you could “set the fade time”, allowing a loop to fade out over multiple repetitions. Could this be implemented on the Aeros as well?)
Aside from these requests, the “send a MSB before a program change” feature is… not a dealbreaker but I wish you guys would give the user the option of removing that odd and unique-to-this-pedal protocol. I theoretically could rig something up to send two commands when I want to change songs, hands-free, but it seems strange and unnecessary— every other pedal in the world just gets a PC and changes their preset accordingly, why not the Aeros?
I apologize also if this post is made in the wrong thread!
I hope these features can be implemented!
Thank you!