Audio Evolution Mobile Studio

NoiseHorse

Bravo! Thank you for making Audio Evolution so awesome!

vlaoladis

@dwrae said:

@vlaoladis said:
Thank you so much for such fast replies!
If you to reproduce the bug or collect logs - I will be happy to help

I tried all sorts of things, but I cannot get it to crash. I don't have SWAM violin, so if you could check if it happens with another AUv3, I'd appreciate it.

What I tried:

• Create an instrument track with Electric AU
• Record a couple of bars of notes
• Automation: add curves for a couple of parameters
• In the AU display, MIDI, add two CC's that I can control from my nanoKontrol 2
• Play and move the faders on my nanoKontrol vigorously
  No crash here

Hi @dwrae! Thank you for the updates and taking a look at my bug.
I couldn’t reproduce this bug in another synth from end to end. But I have an idea why it may happen.
I will split the bug into two parts.

Part 1. Parameter fluttering

Video #1

This is reproducible on any synth so I used a free J6 for demo. As you can see I

• setup a pretty short loop
• use "touch" AU automation option
• move the fader very slowly so the loop cycles multiple times

I guess you override the automation line with new values only when the fader moves, without catching finger up / down events.
But movements of my finger don't have a constant speed and there are tiny "gaps" where AEMS uses the old values from the previous cycles. And these gaps are so small that the result curve becomes very fluttery. Of course I magnified the effect by using a short loop. But even in the regular production it makes this "Touch" function unusable when you want to override a part of your automation - the "overridden" part will always be that flattery. And that's may be the 1st piece of a puzzle

Part 2. SWAM MIDI + AU automation feedback

Video #2

This is SWAM specific.

• here I also use a short loop
• MIDI CC#1 is mapped to the "Vibrato" parameter by default
• I automate MIDI CC#1 manually and then enable "Touch" option in AU (for example if I want to automate another parameter manually)

I guess that's a SWAMs feature that it displays the AU parameter movement when this parameter is tweaked by MIDI. Very convenient during the live playing I must say. But when I enable the "Touch" function in AEMS it reads this movement as an AU automation. So we have two automation lines and they are not the same - it looks like the AU line is a bit smoother. And here I don't know:

• either AEMS adds values from both automation lanes and overflows the result value limits
• or this feedback interferes with the fluttering issue from the Part 1 and creates a microscopic undisplayable flutter that crashes both AEMS and SWAM

God, that remind me the times when I worked as a manual QA

dwrae

@vlaoladis said:
I will split the bug into two parts.

Thanks for the very detailed information. The automation is recorded based on events that the AU sends. So if it would have sent an event when starting to touch the slider, then I guess it would have been OK. Recording automation in a loop will cause undesired effects since the automation events will be put in a list and afterwards, those events are merged with the existing events. So the 'overwrite' part happens afterwards and I don't see this changing soon I'm afraid.

Regarding the CC's, I think you should use either MIDI CC's to control a parameter and not both MIDI and automation if they control the same thing. If SWAM will send parameter automation when a parameter is controlled by MIDI CC, then you will a double effect. Here, SWAM should have an option to send parameter change events to the host when MIDI CC is used since there is no way that the host knows it controls the same thing.

dwrae

Audio Evolution Mobile Studio 6.9.6 for iOS has been released:

• Long-pressing a Soundfont in the instrument selection dialog now opens a menu where you can choose to delete the Soundfont.
• Added a search field to the automation parameter selection and MIDI CC selection dialogs.
• Calculation of the pre-computed graphics file for audio clips now happens in the background. For long audio clips, this could mean that the waveform is not displayed directly after importing or recording and that 'Loading...' is displayed in the clip.
• Loading a project name with international characters didn't work. Solved.
• Values are now displayed underneath the graphic EQ sliders for iPads.

vlaoladis

@dwrae said:

@vlaoladis said:
I will split the bug into two parts.

Thanks for the very detailed information. The automation is recorded based on events that the AU sends. So if it would have sent an event when starting to touch the slider, then I guess it would have been OK. Recording automation in a loop will cause undesired effects since the automation events will be put in a list and afterwards, those events are merged with the existing events. So the 'overwrite' part happens afterwards and I don't see this changing soon I'm afraid.

Regarding the CC's, I think you should use either MIDI CC's to control a parameter and not both MIDI and automation if they control the same thing. If SWAM will send parameter automation when a parameter is controlled by MIDI CC, then you will a double effect. Here, SWAM should have an option to send parameter change events to the host when MIDI CC is used since there is no way that the host knows it controls the same thing.

Hi @dwrae, thank you for the reply!
Understood your point about AU automation.

Regarding the CC's, I think you should use either MIDI CC's to control a parameter and not both MIDI and automation if they control the same thing.

That would be totally enough for me in this case, but there are two things that are making this usecase not very usable for me as well.
1. It looks like MIDI CC values are also merged together when I want to re-input them for some part of the track. Is it possible to add an override mode or something like this for this case?
2. Only AU automation list shows an asterisk mark for edited parameters. MIDI CC list doesn't have this feature, and I have a pretty complex controller with the mapping I never remember. So I can't find the correct parameter without checking each one. Could you please add the asterisk mark for the MIDI CC list as well?

dwrae

Audio Evolution Mobile Studio 6.9.8 for iOS has been released:

• Added an option 'By BPM' to the time stretch dialog where you can enter a source and target BPM.
• Added an option 'Ignore MIDI volume (CC 07)' to the MIDI input dialog.
• Added an option 'Ignore pitch bend' to the MIDI input dialog. This can help with faulty MIDI keyboards that erroneously send pitch bend messages.
• Added an option 'Solo exclusive mode' to the Mixer channel settings.
• Solved a possible crash when loading a project with AudioBus active.
• The setting 'Ignore other MIDI CC's was not saved. Solved.
• The time stretch button in the piano roll editor did not work anymore. Solved.
• Available memory display in the instrument selection dialog now gets updated every second which is more reliable since Soundfonts are loaded in the background.
• Wheels on/off state in the virtual keyboard is now remembered.

NoiseHorse

That bpm timestretch is well thought out, just when I thought AEM couldn’t get any better. Thank you as always!

anickt

I was fooling around with AEM for the last few hours and found a lot to like. I’ll take some time this weekend to further check it out but so far, so good. Anyone else have any input good or bad? 😎👍🏼

wim

@anickt said:
I was fooling around with AEM for the last few hours and found a lot to like. I’ll take some time this weekend to further check it out but so far, so good. Anyone else have any input good or bad? 😎👍🏼

Only good. If I was going to regularly doing any DAW stuff on the iPad I think I'd work to overcome my little bit of disorientation over the interface and workflow and use it over other DAWs just because it has most of what's needed under one umbrella. I can't say anything bad about the UI and workflow. It's fine. It's just not natural to me right off the bat.

I find that by the time something I do is worthy of being fully DAW'ed (which is rare these days) I just don't feel like using the iPad for that. Everything else, but not that.

anickt

Thanks @wim
I do find the workflow fine in some aspects and puzzling in others. Familiarization will help I think.

I swear by Caustic, NS2 and FLSM but each has something missing. By the time my ideal app comes out I will be dust!

watari_banzai

Couple of questions, if you please…

Is it still limited to a single midi fx per track?

Also, afaik, you can only view the mixer, arrangement, piano roll, and audio editing views individually and can’t for example see the piano roll together with the arrange window. How much of a hindrance is that when composing/arranging?

dwrae

@watari_banzai said:
Couple of questions, if you please…

Is it still limited to a single midi fx per track?

I don't recall it was ever. There are 3 AU MIDI slots per track.

Also, afaik, you can only view the mixer, arrangement, piano roll, and audio editing views individually and can’t for example see the piano roll together with the arrange window. How much of a hindrance is that when composing/arranging?

It depends. There are many users with phones who handle this fine. Rest assured though this is going to be resolved in the next UI update for tablets.

anickt

@dwrae said:

@watari_banzai said:

Also, afaik, you can only view the mixer, arrangement, piano roll, and audio editing views individually and can’t for example see the piano roll together with the arrange window. How much of a hindrance is that when composing/arranging?

It depends. There are many users with phones who handle this fine. Rest assured though this is going to be resolved in the next UI update for tablets.

@dwrae When is this new update expected? I spent a good amount of time with AEMS over the weekend and am quite pleased with it. I have some observations but will hold off until after next update if it’s soon.

@watari_banzai For me there is no hindrance in the current implementation.

dwrae

@anickt said:
@dwrae When is this new update expected? I spent a good amount of time with AEMS over the weekend and am quite pleased with it. I have some observations but will hold off until after next update if it’s soon.

I'm afraid I cannot give a time frame since it depends on a lot of factors.

anickt

@dwrae said:

@anickt said:
@dwrae When is this new update expected? I spent a good amount of time with AEMS over the weekend and am quite pleased with it. I have some observations but will hold off until after next update if it’s soon.

I'm afraid I cannot give a time frame since it depends on a lot of factors.

@dwrae No problem. Thanks!

[Deleted User]

The user and all related content has been deleted.

anickt

@Mountain_Hamlet said:
A really quick question ( well, actually three )
just trying out this beast. I deleted the audio on a track and when I try and drag another piece of audio onto this empty track it says I can’t because I have exceeded the number of tracks. But, I am still only working within the three tracks - not creating a new track.
Is it not possible to drag audio onto an already created track?
Secondly, how do I delete a channel entirely?
What are the meters calibrated too ( ie are they rms and peak or something else )?
Thanks in advance.

Long press on a track and you should get a pop-up with an option to delete the track. Importing audio automatically creates a track so you need to delete the previous track to import audio in your situation. Not sure about your other question. The user manual for this app is pretty good.

I’ve been using this for several weeks now and it’s replaced any other DAW I’ve been using. Haven’t run into anything that can’t be figured out and a trip to the manual now and then can be helpful.

dwrae

@Mountain_Hamlet said:

What are the meters calibrated too ( ie are they rms and peak or something else )?

They are peak meters. If you cannot use more than three tracks, you probably have installed the app once years ago when it was free to download with an in-app purchase to unlock it. Normally you can drag audio onto an existing track.

[Deleted User]

The user and all related content has been deleted.

anickt

@dwrae Any issues with iPadOS 26 and AEMS? Thanks

anickt

In my opinion this is the best DAW on iOS. And it’s been working fine on iPadOS 26.

dwrae

@anickt said:
@dwrae Any issues with iPadOS 26 and AEMS? Thanks

I am currently moving places, so no time to check it out unfortunately until late next week.

anickt

@dwrae said:

@anickt said:
@dwrae Any issues with iPadOS 26 and AEMS? Thanks

I am currently moving places, so no time to check it out unfortunately until late next week.

No problem. I’m using AEMS with iPadOS 26 with no issues so far. Thanks

FizzyLizzy27

Does this support MIDI plugins? Could I use Fugue Rubato and send the play heads out to other tracks?

dwrae

@FizzyLizzy27 said:
Does this support MIDI plugins? Could I use Fugue Rubato and send the play heads out to other tracks?

It supports AU MIDI. You cannot send MIDI from one track to another though.

cube48

Wow, I’ve revisited recently this DAW and it is really the best one on iPad OS! I purchased it ages ago along with other big names but none of them really made it for me. Now I played around with AEM and went through this whole thread. Really great work and support from the developer!

The only last piece that is missing to being perfect is recording into plain MIDI track to sequence external synth.

Is there a technical barrier that prevents MIDI thru when the MIDI track is set to rec-armed state? How am I supposed to record the performance when I’m not hearing it? Are there any workarounds except external physical MIDI splitting/merging?

It is possible to record the data but ‘deaf’ only. Playback of the recorded notes works.

I’d like to record MIDI notes live AND hear it in realtime. Routing the audio from the external synth to rec-armed audio track is no issue but the synth has to be triggered straight from the MIDI controller.

dwrae

@cube48 said:
Wow, I’ve revisited recently this DAW and it is really the best one on iPad OS! I purchased it ages ago along with other big names but none of them really made it for me. Now I played around with AEM and went through this whole thread. Really great work and support from the developer!

The only last piece that is missing to being perfect is recording into plain MIDI track to sequence external synth.

Is there a technical barrier that prevents MIDI thru when the MIDI track is set to rec-armed state? How am I supposed to record the performance when I’m not hearing it? Are there any workarounds except external physical MIDI splitting/merging?

It is possible to record the data but ‘deaf’ only. Playback of the recorded notes works.

I’d like to record MIDI notes live AND hear it in realtime. Routing the audio from the external synth to rec-armed audio track is no issue but the synth has to be triggered straight from the MIDI controller.

Hi there,

I assume the recording part in "recording into plain MIDI track to sequence external synth" is not the issue here. I have to admit that on Android, the MIDI thru option was implemented but on iOS it is not present yet. There are probably other ways to achieve this like having an other app (like AUM) route the MIDI and setting the MIDI input in AEMS to that app. I'll add the MIDI thru to the todo list and will try to find out if AUM can do this.

cube48

Big thanks for both, for considering the MIDI thru feature implementation and for the sideways MIDI routing tip in AUM, I’ll give it a shot.

vlaoladis

Hi @dwrae.
I have a small fresh UX question. I’m arranging a new project in AEM. I’ve recorded loops in loopy pro, then imported them into AEM, arranged accordingly to the desired track structure and then started polishing. An during this process I noticed several user experience issues that actually make the whole process quite annoying and painful.

1. I bought vocal studio IAP to slightly fix timings in my loops. It is integrated very nicely and it was a very pleasurable experience. But when I finished it I decided to apply fade ins/outs to remove clicks between the clips. But it seems to reset the result of vocal studio changes so I have to repeat everything from the scratch. And I don’t see any options to “bake” or “commit” the changes made in the vocal studio destructively into the clip itself.
2. I also don’t see the option of applying fade in/out to the whole batch of clips. That’s strange, I don’t remember I faced such issues before, but right now I was pretty confused when I selected all the clips, used triple dots button under one of them to open the context menu and fades were applied only to this exact clip
3. Also when you edit the fade in/out time the input field is hidden behind the onscreen keyboard. And if you hide it you won’t be able to return it back until you close the modal fade settings window and open it again

System: iPad Pro M4 OS 18.7.1

dwrae

@vlaoladis said:
Hi @dwrae.
1. I bought vocal studio IAP to slightly fix timings in my loops. It is integrated very nicely and it was a very pleasurable experience. But when I finished it I decided to apply fade ins/outs to remove clicks between the clips. But it seems to reset the result of vocal studio changes so I have to repeat everything from the scratch. And I don’t see any options to “bake” or “commit” the changes made in the vocal studio destructively into the clip itself.

Undo would have hopefully done it. But yes, applying 'offline' fades/cross-fades modifies the actual audio in the clip and therefore the VTS clip is replaced. Only applying real-time automation could be used here.

2. I also don’t see the option of applying fade in/out to the whole batch of clips. That’s strange, I don’t remember I faced such issues before, but right now I was pretty confused when I selected all the clips, used triple dots button under one of them to open the context menu and fades were applied only to this exact clip

True, that's still on the todo list I'm afraid.

3. Also when you edit the fade in/out time the input field is hidden behind the onscreen keyboard. And if you hide it you won’t be able to return it back until you close the modal fade settings window and open it again

The downsides of using JUCE I suppose, but I changed some code that will move the dialog. This requires some thorough testing before release though!