Audio Evolution Mobile Studio

Kewe_Esse

When I map from hardware to an AU, (eg from novation launchcontrol to any synth param) ‘show midi control’ and ‘midi learn’ have made this type of exercise remarkably easy.

dwrae

@bargale said:
Ill add my full input later on today but i wanted to say that if you do add auv3 midi learn and record to timeline, please raise the midi cc resolution, right now it's too low for editing, if you can make it sample accurate like the audio editing, itll be much better

I'm not sure I understand. MIDI events in AEMS are stored as 64-bit doubles (seconds), with a higher resolution than audio frames.

dwrae

@Kewe_Esse said:
When I map from hardware to an AU, (eg from novation launchcontrol to any synth param) ‘show midi control’ and ‘midi learn’ have made this type of exercise remarkably easy.

Doing MIDI learn is not the issue here.

Kewe_Esse

Best example: AUM

2 instances: mapping per instance

Project specificity: yes

Other app mapping view screens: yes, eg AUM (instance mappings listed in the AU window, project mappings in the midi routing and midi control windows)

Same CC to multiple params: proportional changes to each param per CC

Precedence: I suppose personal approach would be: save project template with USB midi mappings, then use whatever unassigned controls for AUs… not sure if I understand this question properly

Jumpercollins

AUM and apeMatrix do midi best with a matrix page for midi connections as everything is laid out in front of you for the user.

espiegel123

@dwrae said:

@bargale said:
Ill add my full input later on today but i wanted to say that if you do add auv3 midi learn and record to timeline, please raise the midi cc resolution, right now it's too low for editing, if you can make it sample accurate like the audio editing, itll be much better

I'm not sure I understand. MIDI events in AEMS are stored as 64-bit doubles (seconds), with a higher resolution than audio frames.

I think he is asking that recorded automation resulting from midi control be stored as higher resolution values than midi’s 128 discrete values (for 7-bit midi) so that editing automation isn’t restricted to midi’s slow granularity.

dwrae

@espiegel123 said:
I think he is asking that recorded automation resulting from midi control be stored as higher resolution values than midi’s 128 discrete values (for 7-bit midi) so that editing automation isn’t restricted to midi’s slow granularity.

Aha. Well, it's not the MIDI values that are stored, but the parameter values, so also there, this isn't restricted to 128 values.

espiegel123

@dwrae said:

@espiegel123 said:
I think he is asking that recorded automation resulting from midi control be stored as higher resolution values than midi’s 128 discrete values (for 7-bit midi) so that editing automation isn’t restricted to midi’s slow granularity.

Aha. Well, it's not the MIDI values that are stored, but the parameter values, so also there, this isn't restricted to 128 values.

That’s great. I figured that would be the case but wanted to clarify.

[Deleted User]

@dwrae said:

@janpieter said:
@dwrae will sidechaining stay only for the ToneBoosters in DAW plug-ins?

According to the code at least, sidechaining should work on all AUv3 effects. Do you have an effect where it doesn't work?

I’ll go check immediately. I actually always thought it wasn’t implemented as such. Great news for me!

headmademusic

@dwrae said:

Actually, I'd like to discuss the MIDI learn thing or in broader terms, controlling an AUv3 parameter by MIDI. What would be the best example of another app doing this already? I don't see how I can pop-up a menu on a control of an AUv3 since I don't own or cannot access the AUv3 UI. It's just being 'displayed', but the app itself does not take part in handling the UI.

AUM is my prefered workhorse and make the midi stuff real well.

Furthermore, what would you expect to happen if there are two instances of the same AU?

One assignment per instance.

Would the MIDI-to-parameter connection be project specific?

Yes mostly and used with templates for jam sessions.

Do other apps have a certain place where all mappings are listed? If settings were global (not project specific), you might forget about a parameter mapping and wonder why things sound odd when you adjust a MIDI control.

No, because I work with individual settings in every project.

What would happen when you map the same MIDI CC to multiple parameters?

I would find this very useful and set each minimum and maximum value individually and reverse.

The MIDI remote setup was created to make it easy to setup MIDI remote control for volume/panning/etc of multiple tracks.

I dont use that function.

USB MIDI fader devices usually are set up by increasing MIDI CC or MIDI channel, so you would only have to enter the first MIDI CC and tell if the other faders use an increasing MIDI CC or MIDI channel. What would have precedence when using both MIDI remote control and the MIDI mapping of AU parameters?

MIDI mapping of AU parameters

Thank you very much for your openness and the fast implementation of so many little things

bargale

@dwrae said:

@bargale said:
Ill add my full input later on today but i wanted to say that if you do add auv3 midi learn and record to timeline, please raise the midi cc resolution, right now it's too low for editing, if you can make it sample accurate like the audio editing, itll be much better

I'm not sure I understand. MIDI events in AEMS are stored as 64-bit doubles (seconds), with a higher resolution than audio frames.

Oops, it was my mistake as I forgot to turn off grid snapping.
Instead, I hope you could add a long press to select multiple cc values at once for quicker and easier edits, same as what midi notes have.

bargale

@dwrae said:

Actually, I'd like to discuss the MIDI learn thing or in broader terms, controlling an AUv3 parameter by MIDI. What would be the best example of another app doing this already? I don't see how I can pop-up a menu on a control of an AUv3 since I don't own or cannot access the AUv3 UI. It's just being 'displayed', but the app itself does not take part in handling the UI.

drambo let’s you expose the au parameter by pressing map and pressing, moving stuff in the plugin ui and afterwards you can midi learn and map the parameters to midi cc

I think it’s the most efficient way, as there are no uncalled for menu diving

Furthermore, what would you expect to happen if there are two instances of the same AU?

One assignment per instance as someone above said

Would the MIDI-to-parameter connection be project specific?

yes + adding mapping presets save and recall will up it a notch

Do other apps have a certain place where all mappings are listed? If settings were global (not project specific), you might forget about a parameter mapping and wonder why things sound odd when you adjust a MIDI control.

i don’t think there is one app that shows all mappings at once but it might be helpful to have a general midi mappings mode to see how is everything mapped in the project and it should only show the already mapped parameters

What would happen when you map the same MIDI CC to multiple parameters?

instead I think it’s better to use macros, map few parameters to one macro in aem and map a midi cc from a controller or a midi au to this macro, Beatmaker 3 does it best by allowing you to choose minimum and maximum values for each plugin parameter mapped to the same macroand allows to switch polarity so min will become max and vice versa

The MIDI remote setup was created to make it easy to setup MIDI remote control for volume/panning/etc of multiple tracks.

why would it affect it? I think it should stay and be a general mapping setting, unrelated to a specific project

USB MIDI fader devices usually are set up by increasing MIDI CC or MIDI channel, so you would only have to enter the first MIDI CC and tell if the other faders use an increasing MIDI CC or MIDI channel. What would have precedence when using both MIDI remote control and the MIDI mapping of AU parameters?

not sure what is the question, why would anyone need precedence?

No one will use the same fader to control both channel fader and a plugin au parameter by sending the same midi cc on the same midi channel simultaneously

thanks again for being so approachable

MisplacedDevelopment

Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI. Did a quick test copying MIDI from MultiTrackStudio and it pasted fine into AEM. I noticed that dragged audio overwrites existing audio clips without rippling or offering to crossfade but it is simple enough for the user to make sure there is suitable space before dragging, or just drag to an empty track and then move the new clip to its destination.

Thanks for these recent updates @dwrae, I look forward to seeing what this new feature is you are cooking up!

Kewe_Esse

@MisplacedDevelopment said:
Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI.

Nice! Thanks @dwrae

FPC

Watching this thread with interest. The Dev seems amazing and I'm wondering if this will replace Cubasis 3 for me.

I've owned it for years on Android but never used it because I was a Caustic devotee at the time.

dwrae

Thanks! So to make it official:

Audio Evolution Mobile Studio v5.3.2 for iOS released:

• Added support for dragging & dropping audio/MIDI files using Slide-over.
• Added support for pasting audio and MIDI from the iOS system-wide clipboard: use the track's pop-up menu and select 'Paste using iOS pasteboard'.
• Latency compensation only worked for audio tracks. Solved.

Please beware of the following bug that has been fixed internally but not in time for this release:
When you have more groups/busses than tracks, pressing a track's input button will crash the app.

bargale

@MisplacedDevelopment said:
Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI. Did a quick test copying MIDI from MultiTrackStudio and it pasted fine into AEM. I noticed that dragged audio overwrites existing audio clips without rippling or offering to crossfade but it is simple enough for the user to make sure there is suitable space before dragging, or just drag to an empty track and then move the new clip to its destination.

Thanks for these recent updates @dwrae, I look forward to seeing what this new feature is you are cooking up!

You on a beta? Cause it doesn’t work with the latest release on my device

dwrae

@bargale said:

@MisplacedDevelopment said:
Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI. Did a quick test copying MIDI from MultiTrackStudio and it pasted fine into AEM. I noticed that dragged audio overwrites existing audio clips without rippling or offering to crossfade but it is simple enough for the user to make sure there is suitable space before dragging, or just drag to an empty track and then move the new clip to its destination.

Thanks for these recent updates @dwrae, I look forward to seeing what this new feature is you are cooking up!

You on a beta? Cause it doesn’t work with the latest release on my device

There is currently no one on a beta. Does regular copy/paste from the iOS clipboard work?

MisplacedDevelopment

@bargale said:

@MisplacedDevelopment said:
Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI. Did a quick test copying MIDI from MultiTrackStudio and it pasted fine into AEM. I noticed that dragged audio overwrites existing audio clips without rippling or offering to crossfade but it is simple enough for the user to make sure there is suitable space before dragging, or just drag to an empty track and then move the new clip to its destination.

Thanks for these recent updates @dwrae, I look forward to seeing what this new feature is you are cooking up!

You on a beta? Cause it doesn’t work with the latest release on my device

Which part are you unable to do? Latest version is 5.3.2, does that match yours? Update may not have arrived everywhere yet.

Telstar5

@dwrae said:

@DanSebPage said:
Cubasis has been my DAW of choice for a while now, but there's a few things it doesn't have: Time signature changes, Plugin Delay Compensation and ghost/clone patterns (tweak midi data in one pattern, and all others update to match). I notice AEM has the first of these, but does it have the other two?

Secondly, Cubasis is very good at utilising multi-core processors. Is AEM coded to take advantage of multi-core processing too?

It has plug-in delay compensation and I have no idea what the ghost/clone thing does, so that's likely a no. Multi-core processing is still on the todo list.

@DanSebPage : It seems to have time change capabilities

Telstar5

The user manual is absolutely first rate . Reminds me of Auria Pro in that regard.

ipadbeatmaking

@dwrae said:
Thanks! So to make it official:

Audio Evolution Mobile Studio v5.3.2 for iOS released:

• Added support for dragging & dropping audio/MIDI files using Slide-over.
• Added support for pasting audio and MIDI from the iOS system-wide clipboard: use the track's pop-up menu and select 'Paste using iOS pasteboard'.
• Latency compensation only worked for audio tracks. Solved.

Please beware of the following bug that has been fixed internally but not in time for this release:
When you have more groups/busses than tracks, pressing a track's input button will crash the app.

This is impressive!!! Very nice 👍

bargale

@dwrae said:

@bargale said:

@MisplacedDevelopment said:
Latest update allows MIDI and audio to be dragged onto the timeline from outside the app and also lets you use the system clipboard for audio and MIDI. Did a quick test copying MIDI from MultiTrackStudio and it pasted fine into AEM. I noticed that dragged audio overwrites existing audio clips without rippling or offering to crossfade but it is simple enough for the user to make sure there is suitable space before dragging, or just drag to an empty track and then move the new clip to its destination.

Thanks for these recent updates @dwrae, I look forward to seeing what this new feature is you are cooking up!

You on a beta? Cause it doesn’t work with the latest release on my device

There is currently no one on a beta. Does regular copy/paste from the iOS clipboard work?

You’re too quick too handle, I didn’t realize there’s another update
It works perfectly fine, you’re killing it with these updates

cokomairena

This is awesome!!!

Jumpercollins

@dwrae Quality update thank you. Hope the DAW gets more exposure now it’s a hidden gem.

Paa89

@dwrae big ups on the frequent updates.
I know this might be far stretched but work flow would be faster and fun in my humble opinion if we had these:
Mixer button: tap on that it opens the mixer in same view as timeline, showing you volume fader of all tracks and including master, with pan ect and a button for FX grid.
Double tap on midi region, it opens up under the tracks in timeline and user can make it full screen if needed.
I believe an interface similar to these pictures would really improve work flow instead of having to tap on “Next” continuously

dwrae

@Paa89 said:
@dwrae big ups on the frequent updates.
I know this might be far stretched but work flow would be faster and fun in my humble opinion if we had these:

The Cubasis way.

Yes, the app in its current design is not really suitable for this. When I port these views to JUCE it will become a lot easier. Planned, but might take a year.

dwrae

@Jumpercollins said:
@dwrae Quality update thank you. Hope the DAW gets more exposure now it’s a hidden gem.

Thanks! Next up will be a little side project.

Jumpercollins

bargale

@Jumpercollins said:

Latest few updates are fire