Aeros firmware 3.1.x

[JusDandy]

I also did the same procedure on a Windows 10 PC and no way to update. What am I doing wrong?

[sharifkerbage]

Which file format is the SD card?

[mbeck]

Quick note as you’re working on next functionality: would be great to have mixer level and pan controls over the dry audio input, as well as the looper tracks. That would also give you dry kill functionality, as requested elsewhere, by setting dry volume to 0.

Reiterating that ideally we’d see MIDI functionality for every command being implemented going forward. Thanks!

[persist]

@JusDandy

Please help! I followed instructions for trying Beta 3.1x. Downloaded to my Mac. Renamed to aeros.bin. Transferred to SD card and inserted into the Aeros and turned on. Doesn’t change firmware. Went to updates section - no way to update.
.

@JusDandy

I also did the same procedure on a Windows 10 PC and no way to update. What am I doing wrong?

Make sure your card is not locked. Your SD card should be formatted as MS-DOS (FAT32)

[Euan]

I don’t see any mention of a facility to have songs displayed in order on the selection screen. This a real disappointment. To be honest, I’m close to giving up on the Aeros because it’s becoming impossible to use live when you can’t quickly locate the next number in your set.

[LaurentB]

@DavidPackouz

• All track actions are now on down press of the button for more accuracy. This includes, record, re-record (on an undone track), overdub, play, mute, cancel mute, unmute, cancel unmute.
• Made Next Part command (lower left button) on press (not release) while recording for more precise recording in freeform with 2x2 mode
  …
• Base track for Sync Length setting is now the shortest track in the song part instead of the longest in freeform mode for additional flexibility

Sounds exciting… Will try that ASAP. So regarding my requests, it should fix:

• Attach all time sensitive commands (i.e. recording) to on-press events only
• Align new track duration on the shortest one (first) in 6x6 (freeform mode)

Apart from that, still no file hash… ¯\(ツ)/¯ why ?

[LaurentB]

@yanarchy

Maybe I missed something but is it possible for next updates to receive a warning (or even better a direct download link) by email? That’d avoid to have to constantly check the forum.

Maybe something like a document to keep track of the releases, that you could “watch” (with the “watching button” displayed at the bottom of a topic)…

[Thovy64]

There is a click when you loop. I do the same loops with a jamman and I can’t hear the connection between the end and the beginning of my loops. With the air it is a disaster.
Are you planning to do something?

[BrennanSingularSound]

@Jzzb8ovn

I’d also love to see midi control of track volume functions and muting My current midi controller could do this if the CC numbers etc were available

Noted!

@LordRadish

Sometimes, when I’d hit overdub, I’d see the waveform overdub for just a bit (the yellow), but for some reason, it wouldn’t be yellow for most of it, almost as thought the overdub ended prematurely

This is a UX issue, not to worry the audio is not affected by this, we are working on optimizing the waveform the Aeros makes, but it’s handling quite a few levels adaptively, and that gets more complicated to show accurately as you add more and more overdubs, we’re working on that.

@LordRadish

Second, there’s a huge volume spike where I’m assuming the crossfade is occurring

This is related to something that we believe we’ve found the problem for, hopefully there will be a solution soon and this may be related to the length of the crossfade as well.

Stay tuned on that!

@LordRadish

• are there particular settings that are optimal for this in the main settings?
• What if I don’t want to go straight to OD on my other tracks? Often, I may get that seamless drone on the first track, but I want separate non-overdub things to bring in and out on the subsequent tracks… do I just have to double-tap quickly?

1. I don’t understand this question could you re-phrase this for me, please?
2. You can’t have the cake and eat it too, so to speak,

Yes you will have to tap twice to convert the overdub to a play command, but don’t confuse that for a double-tap.

What I mean by that is that the Aeros reads any second tap within 500ms (it may be 300ms now, but I’m positive it’s 500) as a double-tap which is a mute command.

Because of this, if you double-tap too quickly, the Aeros won’t register the second tap since muting at that point is not allowed.

While writing this I realized this could possibly be improved by creating a corner-case logic for a double-tap that it instead causes a change of state for the upcoming command. I can ask dev about that. For now, time your taps with a small (half-second) pause, if possible, to change an upcoming overdub to a play command. Obviously, this is only possible if you have at least Sync Length on, if in freeform mode.

@AMackie

After the second overdub I stopped the drone and pressed play. As you can hear there is a clear drop at every start of the loop, even though this should be seamless (as I understand it).

We have found the issue causing this and are working on a solution, stay tuned.

@Quad

Is there a way to disable the clicks in all cases?

Seems like I have the right settings to disable it already.

Thank you for reminding me let me ask.

@Quad

• Before first track is recorded, adjusts to midi clock BPM changes
• After track is recorded, the BPM doesn’t change.

This is correct

@Quad

Update the documentation

How so? To specify that BPM only changes once before recording something? Do you mean on the Aeros manual?

@Quad

Change the Tempo indicator from “100 BPM” to “100 BPM (Warning: MIDI at 120BPM)” if the midi bpm and the song bpm are not the same.

• Bonus points for making locked be a icon, red text, or something very obvious.
• IMHO this is a good way to handle “alerting without getting in the way with a popup message”
• Same warning for time signature (although there are some good uses cases where time signature sync would need to be disabled by user preference per song)

We do plan on making a visual system for this that includes red flashing as well as separate internal and external BPM and time signatures.

@Quad

Change the Tempo indicator from "100 BPM to “100 BPM (Locked)” if the BPM will never change due to MIDI.

That’s a thought, we could do something like that

@Quad

Note: There is a roadmap feature to allow stretching recorded tracks. I’m guessing that this feature will take quite some time to ship … and even when it does, many will not want/like the (sonic or other) tradeoffs that are likely.

It will most likely not be any time soon, especially given the difficulty of not compromising audio like you say, we will get there when we get there, so to speak.

@Quad

Does MIDI Time Signature change work?

I tried a few tests and have not seen the time signature change when loading new songs on the BB. Using the latest BB firmware.

Depends when you change the time signature, if the song is blank and you open a song different than the one currently open on the BB, it will send a time signature message, we hope to optimize this at some point.

@sharifkerbage

Is there any MIDI messages for Track Levels? If is not, is there any plan to add it soon?

No, but we have gotten requests, so it may be in there eventually, stay tuned on that.

@sharifkerbage

Having the Aeros as MIDI clock slave, when I change the bpm on my iPad, it doesn’t show up on the stop screen of the Aeros, but the Aeros actually change the tempo, but it’s not showing up as a BPM Value on the Aeros.

Interesting what app are you using on you iPad?

@sharifkerbage

• I don’t see any control for MIDI Clock on the Aeros, that’d be really useful (for not say necessary)

We have plans to implement this, it is on the dev list

@booneroo

I’d like to have a global setting to ignore a bpm mismatch. Or, even better, have Aeros as master only for bpm when loading a saved song. Or a quick toggle for that setting when loading a saved song. I’m not too familiar with midi so I’m in the dark as to what is possible.

We plan on making a simple touchscreen button that can turn off and on sync for both CC and clock independently, stay tuned on that

@mbeck

Quick note as you’re working on next functionality: would be great to have mixer level and pan controls over the dry audio input, as well as the looper tracks. That would also give you dry kill functionality, as requested elsewhere, by setting dry volume to 0.

Reiterating that ideally we’d see MIDI functionality for every command being implemented going forward. Thanks!

Noted.

@audiosampling

Well, I don’t think it is a valid test. Because of the nature of the signal you use. It’s a static tone, without any modulation.

This is true, but our soundscaper guys benefit from seamlessness, I agree with you however that most instrument signals are not devastatingly affected by this. We have found the problem, and are working on a solution.

@AMackie

After some further testing, I got the following result. Looks like the visual error can also be a (visual) amplification instead of a dropout (as demonstrated in the previous “screenshot”).

Yes, we are aware of this I answered this above^

@Euan

I don’t see any mention of a facility to have songs displayed in order on the selection screen. This a real disappointment. To be honest, I’m close to giving up on the Aeros because it’s becoming impossible to use live when you can’t quickly locate the next number in your set.

We’d hate to see you go, but please know it’s on the dev list, we can only focus on so much, we hear your issue, too

[Quad]

@BrennanSingularSound

How so? To specify that BPM only changes once before recording something? Do you mean on the Aeros manual?

Yes. Would also be good to update the release notes in the first posting here (perhaps the one on the device as well)

[Quad]

@BrennanSingularSound

a visual system for this that includes red flashing

Ooh. That reminds me, some of the flashing in the UI is pretty “strong”. Would be great to soften that and have limits as to the speed (If you create a very, very short loop …watch out for seizures).

@BrennanSingularSound

@Quad

Does MIDI Time Signature change work?

I tried a few tests and have not seen the time signature change when loading new songs on the BB. Using the latest BB firmware.

Depends when you change the time signature, if the song is blank and you open a song different than the one currently open on the BB, it will send a time signature message, we hope to optimize this at some point.

Please add to docs and changelog in the first post in this thread…

@audiosampling

Well, I don’t think it is a valid test. Because of the nature of the signal you use. It’s a static tone, without any modulation.

The true test is if there aren’t similar artifacts when you take the separate signals and put them into a professional DAW. The Aeros shouldn’t be held to a higher standard than that (and not much lower).

[BrennanSingularSound]

@Quad

Ooh. That reminds me, some of the flashing in the UI is pretty “strong”. Would be great to soften that and have limits as to the speed (If you create a very, very short loop …watch out for seizures).

Noted!

@Quad

Please add to docs and changelog in the first post in this thread…

I believe its in docs now, but I’ll ask David about editing the thread

@Quad

Is there a way to disable the clicks in all cases?

Seems like I have the right settings to disable it already.

Is this with the BB or on its own?

I’m trying to replicate this, but I’m not hearing any click unless there’s a count in

You have the click routed to neither output and the click after recording first track setting is off?

[Quad]

@BrennanSingularSound

Is this with the BB or on its own?

I’m trying to replicate this, but I’m not hearing any click unless there’s a count in

You have the click routed to neither output and the click after recording first track setting is off?

With the BB and with the the routing to nowhere and click after recording off as well.

This is pretty disturbing as either of those settings should override anything that ever happens elsewhere in the code. Is this code messy? Just saying…

• Record a track with BB running (I’m using a 6/8 if that matters)
• Stop Aeros
• Press Overdub with time left in the pattern on the BB.

[Quad]

Recorded waveform started reading zero signal before the end of the first loop. By that I mean the display looked just like nothing was being recorded. But upon playback of first track the audio was there and the zero reading showed up at the same point. Same for overdub. This was 2x2 in 6/8 with BB running.

Pretty sure when the display dropped out on recording was much earlier than the l 1.25 measures it showed upon replay.

Upon recording the last overdub, I saw the live recording drift to the left off screen as time went on!

I also saw the white bars between the two tracks not lined up.

This seems to be a new issue for this beta release?

IMHO, 2D layout can be deceptively simple, and pretty buggy without the right representation.

I have no way to reproduce this. I had been playing around with the above stuff trying to break it then cleared it and started playing. I think I changed from 4/4 to 6/8 after clearing the song and started via the BB midi after I saw the time signature update.

[Quad]

Bug: The scroll wheel doesn’t work in the song list any more.

Feels like the Play/Stop button is active in more places in the UI. Haven’t found a place where its felt off.

[Thovy64]

@BrennanSingularSound

I’m sorry, the sound is not hi quality but here are 2 exemples of loops seam anomalies (pop or fade trouble). If I record the same kind of loops with a simple Solo XT jam man, the sound of loops is continue, the seam is inaudible.
Exemple 1
Exemple 2

[LaurentB]

@DavidPackouz

• Base track for Sync Length setting is now the shortest track in the song part instead of the longest in freeform mode for additional flexibility

Ok it seems to work. See updated topic…

@DavidPackouz

• All track actions are now on down press of the button for more accuracy. This includes, record, re-record (on an undone track), overdub, play, mute, cancel mute, unmute, cancel unmute.
• Made Next Part command (lower left button) on press (not release) while recording for more precise recording in freeform with 2x2 mode

Doesn’t work . See bug report… @DavidPackouz please do something…

[booneroo]

Hard to tell if this is the same problem I’m having… Did you change the bpm on BB after recording and erasing the initial track? Seems the BB keeps forcing the bpm on a track that’s already set. I think even if something has been recorded and deleted, for some reason the bpm setting remains and subsequent initial tracks are off if bpm or time sig changes.

From the Dev responses above, they appear to be aware of it and working on it. The toggle solution mentioned above would be invaluable.

[BrennanSingularSound]

@Quad

With the BB and with the the routing to nowhere and click after recording off as well.

This is pretty disturbing as either of those settings should override anything that ever happens elsewhere in the code. Is this code messy? Just saying…

• Record a track with BB running (I’m using a 6/8 if that matters)
• Stop Aeros
• Press Overdub with time left in the pattern on the BB.

This is now fixed, we are probably looking at a subsequent beta very soon

@Quad

This seems to be a new issue for this beta release?

noted.

@Quad

I have no way to reproduce this.

this all happened in one-go? Or in several takes? Was there any effect on the audio or this is purely UI?

@Quad

Bug: The scroll wheel doesn’t work in the song list any more.

Feels like the Play/Stop button is active in more places in the UI. Haven’t found a place where its felt off.

Fixed.

@Thovy64

I’m sorry, the sound is not hi quality but here are 2 exemples of loops seam anomalies (pop or fade trouble). If I record the same kind of loops with a simple Solo XT jam man, the sound of loops is continue, the seam is inaudible.

I believe this will be solved with another issue we have found that was reported above.
It seems like the same problem.

@LaurentB

Doesn’t work . See bug report… @DavidPackouz please do something…

I also believe this is related to a bug we have found already, the solution is imminent hopefully. More on this soon, but know we’re likely to post another beta very soon.

[Euan]

@BrennanSingularSound

@Euan

I don’t see any mention of a facility to have songs displayed in order on the selection screen. This a real disappointment. To be honest, I’m close to giving up on the Aeros because it’s becoming impossible to use live when you can’t quickly locate the next number in your set.

We’d hate to see you go, but please know it’s on the dev list, we can only focus on so much, we hear your issue, too

The code must already exist, because until the last release you had an alphabetised list. All you need is a switch in configuration between the two listing options.