I’ve accepted your statement about the integral nature of the Aeros and playing tracks at different times. You are the designer :-). Nevertheless, I do no share your opinion that Headrush is confusing by providing this.
About restart after stop: Your proposal is not working. I’m not talking about long pauses with time for muting tracks in between. It’s more about short stops of 1 or half a bar.
And: In Aeros 2x2 mode there are currently three (!) options to restart all tracks: a) start/stop all, b) click on track 1 and c) click on track 2, while b and c restart th respective track in overdub mode. What I’m asking for is very close to this. Restart the one you click in play mode and restart the other one in muted mode. Why not including a song setting as described earlier to make this feature possible.
Sorry for insisting: The looper me and my colleagues are looking for is not the one with the highest number of tracks and overdubs. Start/stop/restart variablility is one of the most important features on our priority list.
You are very right I forgot the play and overdub from stopped, excuse me
I don’t believe there would be a way to achieve what you are asking for without a MIDI controller, the short amount of time makes an immediate mute necessary.
Maybe one last possibility, may not work. You can start and stop playback from the mixer screen, once you are ready to stop the playback, be sure you are in the mixer screen with the track you want muted selected, then hit Stop All, and then hit the button to mute the selected track on mixer (mute is always immediate from mixer screen). This may feel a little clunky but is a possible workaround without needing a MIDI controller.
We haven’t mapped the Aeros for MIDI responsiveness, but this is our next task.
Thanks again for discussing this. And here one last trial from my side to convince you of a significant improvement.
Please ask 10 musicians what effect they would expect after stopping a part (e.g. Always in the last bar of a blues chorus) and then clicking on e.g. track 2.
a) starting all tracks and overdubbing track 2 after each and every chorus or
b) start playing track 2 solely.
Bet, at least 8 out of 10 would opt for b). And to make all of them happy, simply make a song setting “restart track after stop: Play/Overdub”
About consistency: If track 2 is muted while part is playing. Currently, a click on track 2 restarts track 2 in play mode (obviously not in overdub mode).
If you do the same thing while part is stopped (for song dynamic purposes), track 2 restarts recording in overdub mode (and by the way, spoils an undo option by doing so). Can you explain this consinstency breach?
I definitely see some applications for the as-is behaviour. However, it’s not the majority. My proposal: Provide a song setting as mentioned above. Thanks in advance.
I don’t fully understand you here
I ask that you please only use “overdubbing” when recording a layer on top, right now I’m not totally sure if the track you’re talking about has a base layer or not
Have they already recorded both the A and B (part 1 and 2) in this scenario, or only the A?
It’s not really a question of consistency, the Play/Stop all is the only command meant to only playback, the RPO buttons will always give a command to change the current state of the track.
You will need to be a little bit more clear about this use-case, as I’m still not seeing the rationale.
Hi Brennan, about your question: Yes, both tracks 1 and 2 are recorded before stopping. Then I want to restart only track 2.
About RPO button and consistency: I’m fine with this “core principle”. However this workflow refers to a continuously playing a track:
R - P - O - P - O - P - …
However, there are some more events in between, that must be handled consistently as well, like Mute (M) and Unmute (U).
R - P - (O - P - ) M - U - O - P - …
After M there must come a U (which is the same like P, by the way) on single click. Or would you ever expect a track to directly switch into O-mode after M on single click?
Same for Stop and Restart. After (S) there must come a restart R (which is the same like P again) on single click.
R - P - (O - P -) S - R - O - P - …
What Aeros does now is overdub (instead R) of after stop:
R - P - (O - P - ) S - O - P - …
and this generates one more layer after every stop!?!? This does not make sence in two ways. Consistencywise and in a musical way. After building up our musical stuff we want to perform a song (with musical pauses :-)) and not build higer stacks again and again.
Thanks for taking this important thing onto your next sprint Backlog.
Hey there I find it highly unlikely we will add more toggles to the buttons, that would highly overcomplicate things and it is not the route we are thinking of going towards.
There is no way to “start” parallel tracks at different times on the Aeros. This is an integral part of all DAWs and the Aeros. We are not considering changing that core-functionality of the Aeros. I’m sorry, but I cannot consider adding something to the dev list until it makes sense to do so. Changing the buttons to play mode won’t change the fact that the Aeros isn’t made to do this.
There is no looper that can maintain separate parallel tracks in sync while also doing this.
Hi Brennan. This is a total misunderstanding. I do NOT talk about about starting parallel tasks at different times!! When I say start I mean “START SOUNDING”. Please ask a colleague to read this. Or read my last two posts again considering this :
T1 is recorded, T2 is recorded, then stop all (example: blues at bar 12)
Click on T2 sould start both tracks, however, only T2 sounding. T1 should start muted. Everything is in sync.
Two reasons why this is important:
Currently Aeros start/stop all starts sounding both tracks. This is fine: “restart all” is what is expected. So T2 or T1 should do something different. See 2.
Single click on RPO button after stop all should restart the respective track in play mode instead of overdub (as Aeros does currently). Nobody wants to add additional layers by restarting a track after stopping the song. The other track sould start muted and in sync.
This is what each and every multitrack looper I’ve ever used does: RC300, RC505, Ditto X4, EHX22500, Headrush. For good reasons. It’s what musicians need.
This is important and very close to what Aeros does. If you still think this is against the Aeros logic let’s have a call. Probably, my English is that confusing.
