Greetings all! New Aeros person here. I was excited to see the loop decay option in the beta, as I use loop aging/decay heavily with my Ditto X4. I’ve been trying it out and am noticing that the decay only seems to work if I switch from overdub to play and then back to overdub. If I leave overdub activated through several layers, no decay occurs.
It’s not the behavior I would have expected from the feature. All the other looper I have with loop decay automatically fade the loop as each layer is added to the overdub.
This is part of how the Aeros works when an overdub is left on over the loop indefinitely. The Aeros never runs out of space when doing this because the same file is being recorded and merged to over and over, meaning the autodecay is not being enacted since it only enacts when new layers are created.
Thanks for clarifying that is expected behavior with this implementation. I have to say that I find it a bit disappointing as it limits the Aeros’ use for ever evolving ambient soundscape looping, which is what I do. As I mentioned, the Ditto X4 has a better implementation for this use case, as does the Infinity loopers and the Line 6 Helix loopers to name a few. Maybe that could be put on the backlog for future consideration?
Okay, maybe I’m doing someting wrong, but after my recording I safe the file.
the next time, I open it, the volume is increased. I take a old record and it’s okay….then I go back….and the record again is increased. The sound is horrible and the wave is a thick fat line.
I went back to the previous version and everything is okay.
I hope you understand me and maybe have a solution.
Thank’s
I sent a video to Jay at support. Same with me! Super annoying and about blew my ears out since I practice with in ears. I went back to 4.2.4 and all is well.
Dear Brennan,
I was with a new record. The old records stayed well
Loop decay was turn of. I was recording in 2x2 mode
Mono or stereo makes no difference and I dit the same, when I recording in the previous version
Thank you, it appears the issue has been identified and we are hopeful a fix will be ready for you all soon, this seems to have fixed any distortion/overly loud playback introduced by 4.3.0.
I haven’t been around here much, lately (life and all that). Did I read somewhere that you’re going to have more adjustment options for fade in/out times in a future release? Hope so, as with my really long soundscapes, I have to wait a reaaaaal long time for them to fade in when starting (can’t really use that, esp when it’s taking a minute or two).
I am curious as to what the rationale is for not doing it at the song level, though. That creates a lot of menu diving if one has some songs with and some without. Is it possible to have it so that can be toggled with a MIDI command, at least? That way I can load the song, and hit a button.
This is headed towards much complexity and we do not want to go this route,
MIDI control is likely going to be the case, yes we will be looking into how we can make it as manipulable as possible without constantly changing it from the settings but it is not the priority at this time.
I agree with billvencil. The Decay function as currently implemented is not useful In fact, this does the same as the FADE function, no need to duplicate a feature with another name. Any new users coming from other units will be expecting Decay to work in continuous overdub mode. I doubt anyone will have a use for the current implementation. Hope this gets fixed soon. Until then, I will be keeping my DITTO X4 in the board, sadly.
