Audio Evolution Mobile Studio

Robin2

@espiegel123 said:
@Robin2 : in loopy pro Add MIDI is for adding controllers or AU that can send midi

Thanks @espiegel123.

As such, Digistix 2 or iBassist could show up there as an option in Loopy Pro without that indicating that they are AU MIDI plugins, but just that they are available as MIDI sources? Correct?

dwrae

@dwrae said:

@espiegel123 said:
@Robin2 : in loopy pro Add MIDI is for adding controllers or AU that can send midi

I just checked: iBassist is definitely not a AU MIDI effect. It can show up as MIDI input though when you run it standalone, but I didn't manage to send MIDI events from it to either AEMS or CB3. I just tried to see what happens if I force iBassist to be detected as AU MIDI and it just 'consumes' MIDI that is already on the track since it is not outputting the MIDI. It doesn't output any MIDI from itself either in this case.
When I use it as AUv3 instrument, then MIDI from iBassist can be recorded onto the track.

But even if it did work as AU MIDI, you wouldn't be able to route the MIDI to other tracks in AEMS.

Scrap that. For some reason, when forced as AU MIDI, it now started to play using the instrument selected on the track. It still won't help you with the MIDI split though (although you could do that afterwards by splitting the recorded MIDI into separate tracks based on the MIDI channel).

Edit: I figured out why it didn't work the first time. It only records when the additional Rec button in the AU display is also enabled. When just pressing play with Rec disabled, it would play as well.

dwrae

Ok, so in next release, iBassist (and perhaps others, I only found Koala sampler) will be available as AU MIDI option. It is a bit weird though, since you cannot play your actual instrument when active since it doesn't pass on MIDI, so it only 'generates' MIDI.

espiegel123

@dwrae said:
Ok, so in next release, iBassist (and perhaps others, I only found Koala sampler) will be available as AU MIDI option. It is a bit weird though, since you cannot play your actual instrument when active since it doesn't pass on MIDI, so it only 'generates' MIDI.

I think people use this ability so that iBassist ad s sequencer can be driving better bass samples than iBassist has.

Robin2

@dwrae said:
Ok, so in next release, iBassist (and perhaps others, I only found Koala sampler) will be available as AU MIDI option. It is a bit weird though, since you cannot play your actual instrument when active since it doesn't pass on MIDI, so it only 'generates' MIDI.

Seems i was wrong all along @filo01 - my sincere apologies.

filo01

Thank you all so much for moving this in the right direction! Really looking forward to the next release of AEMS, @dwrae.

@dwrae said:
Ok, so in next release, iBassist (and perhaps others, I only found Koala sampler) will be available as AU MIDI option. It is a bit weird though, since you cannot play your actual instrument when active since it doesn't pass on MIDI, so it only 'generates' MIDI.

It is not as unusual situation as it looks like. For example I'm also using Riffler for generating bass riffs and use it as a MIDI driver for GM Bassalicious2. And I'm sure there many other apps with this (wanted) behaviour.

wim

Loopy Pro takes a more "liberal" approach to listing plugins that may or may not output MIDI. It lists all plugins, some of which may not output midi at all. You may notice, if you scroll down far enough that some have a question mark on their icon. The question mark means Loopy isn't sure if the plugin does or doesn't.

The upside is not being restricted based on the 4-letter app type the plugin developer choses. The downside is people sometimes being confused that midi out isn't working.

I wish that all host apps allowed all plugins and left it to us to discover if they work or not, but can understand why most don't.

Artem

@dwrae said:

So, what do you guys expect what will happen (to PDC) when you put an effect with a large latency on an instrument track and arm it to play live?

I expect that in this case the PDC will not work, of course. 😄
My request only applied to the PDC when playing an instrument track in the context of a project:
When I work on the sound of an instrument and use plug-ins, I need the project to be synchronized during playback. Exactly how it works in Logic Pro.
Even if you can implement PDC only when the track is frozen, it will be much better than the complete absence of PDC for instrument tracks.

zah7

@dwrae said:

@senhorlampada said:
@dwrae not sure if I asked already. Is there any option to arm a track to record and it just starts recording as soon as audio signal comes in? (some record threshold thingie)

tried searching the documentation and could not find it. Thanks

No, I don't think you will find that often in a DAW, perhaps I'm wrong.

So maybe someone else knows if any DAW is capable of starting recording upon receiving a signal that exceeds a specified dB level? That thing would come in handy.

yellow_eyez

@zah7 said:

@dwrae said:

@senhorlampada said:
@dwrae not sure if I asked already. Is there any option to arm a track to record and it just starts recording as soon as audio signal comes in? (some record threshold thingie)

tried searching the documentation and could not find it. Thanks

No, I don't think you will find that often in a DAW, perhaps I'm wrong.

So maybe someone else knows if any DAW is capable of starting recording upon receiving a signal that exceeds a specified dB level? That thing would come in handy.

BM3 does (I think. )

wim

Loopy Pro has threshold recording. Most people don't think of it as a traditional DAW though.

As @yellow_eyez mentioned, BM3 has it for its sampler. While recording to the timeline doesn't use threshold recording, you can record to the sampler and then place the audio into the timeline.

zah7

@wim said:
Loopy Pro has threshold recording. Most people don't think of it as a traditional DAW though.

As @yellow_eyez mentioned, BM3 has it for its sampler. While recording to the timeline doesn't use threshold recording, you can record to the sampler and then place the audio into the timeline.

I sort of achieved it in AUM paired with Neon Recorder. Additionally, Fac Envolver triggered ‘Start Play’ in AUM, which gave me a metronome.

wim

@zah7 said:
I sort of achieved it in AUM paired with Neon Recorder. Additionally, Fac Envolver triggered ‘Start Play’ in AUM, which gave me a metronome.

I'm not trying to push Loopy Pro, but Loopy Pro has a unique capability as an audio threshold recorder in AUM. It can set the tempo and start AUM transport based on auto detecting your first loop. That may not be the workflow you're after but I'll describe it anyway.

With Link and Link Start/Stop enabled in both AUM and the Loopy Pro AUv3 plugin, you can reset the clock in Loopy so that it has no tempo. Then you can set threshold recording on in Loopy and the first loop recorded will set the tempo and start the transport. AUM will start with the matching tempo. It works great.

yellow_eyez

@wim said:

@zah7 said:
I sort of achieved it in AUM paired with Neon Recorder. Additionally, Fac Envolver triggered ‘Start Play’ in AUM, which gave me a metronome.

I'm not trying to push Loopy Pro, but Loopy Pro has a unique capability as an audio threshold recorder in AUM. It can set the tempo and start AUM transport based on auto detecting your first loop. That may not be the workflow you're after but I'll describe it anyway.

With Link and Link Start/Stop enabled in both AUM and the Loopy Pro AUv3 plugin, you can reset the clock in Loopy so that it has no tempo. Then you can set threshold recording on in Loopy and the first loop recorded will set the tempo and start the transport. AUM will start with the matching tempo. It works great.

It’s true when I say I’m not either but no daw really had it besides Lp - Loopy pro is maybe my favorite up and coming daw thanks to threshold recording, and the new features

Cubasis will always remain #1 for me on iOS 17 and as long as I keep my air m1 but LP is going to be a very close second with templates I seen

senhorlampada

@wim said:
Loopy Pro has threshold recording. Most people don't think of it as a traditional DAW though.

As @yellow_eyez mentioned, BM3 has it for its sampler. While recording to the timeline doesn't use threshold recording, you can record to the sampler and then place the audio into the timeline.

Yeah... I'm used to recording on BM3 and SP-404 that way. Good when recording instruments.
Forgot about Loopy Pro having that.
May end up recording synced on LP and sending the stems later to AEMS
Thanks for reminding me

dwrae

@Artem said:

@dwrae said:

So, what do you guys expect what will happen (to PDC) when you put an effect with a large latency on an instrument track and arm it to play live?

I expect that in this case the PDC will not work, of course. 😄
My request only applied to the PDC when playing an instrument track in the context of a project:
When I work on the sound of an instrument and use plug-ins, I need the project to be synchronized during playback. Exactly how it works in Logic Pro.
Even if you can implement PDC only when the track is frozen, it will be much better than the complete absence of PDC for instrument tracks.

Ok, I have implemented a different PDC method which works for both audio and instrument tracks and, unlike the previous version, does not 'eat' some audio of the start of a clip. I need to do some finetuning, but it will be available as a BETA option in the new app's Settings dialog until I'm sure it works well. Note for people receiving the next beta: it won't be in this version yet since it was already uploaded. It was a bit too easy, so I probably forgot some use case that will fail!

BTW: to test, I modified my Delay plug-in such that the delay time also becomes the latency. When set to 100% mix and no feedback, audio should be heard without the delay. So with a 2 second delay time, things become obvious whether the PDC works or not.

Artem

@dwrae said:
Ok, I have implemented a different PDC method which works for both audio and instrument tracks and, unlike the previous version, does not 'eat' some audio of the start of a clip. I need to do some finetuning, but it will be available as a BETA option in the new app's Settings dialog until I'm sure it works well. Note for people receiving the next beta: it won't be in this version yet since it was already uploaded. It was a bit too easy, so I probably forgot some use case that will fail!

BTW: to test, I modified my Delay plug-in such that the delay time also becomes the latency. When set to 100% mix and no feedback, audio should be heard without the delay. So with a 2 second delay time, things become obvious whether the PDC works or not.

This is really good news! Can I email you to test it?

dwrae

@Artem said:

@dwrae said:
Ok, I have implemented a different PDC method which works for both audio and instrument tracks and, unlike the previous version, does not 'eat' some audio of the start of a clip. I need to do some finetuning, but it will be available as a BETA option in the new app's Settings dialog until I'm sure it works well. Note for people receiving the next beta: it won't be in this version yet since it was already uploaded. It was a bit too easy, so I probably forgot some use case that will fail!

BTW: to test, I modified my Delay plug-in such that the delay time also becomes the latency. When set to 100% mix and no feedback, audio should be heard without the delay. So with a 2 second delay time, things become obvious whether the PDC works or not.

This is really good news! Can I email you to test it?

Sure, but there is no beta version ready yet with this feature. I would first have to fix a thing or two tomorrow and then upload it.

Artem

@dwrae said:

@Artem said:

@dwrae said:
Ok, I have implemented a different PDC method which works for both audio and instrument tracks and, unlike the previous version, does not 'eat' some audio of the start of a clip. I need to do some finetuning, but it will be available as a BETA option in the new app's Settings dialog until I'm sure it works well. Note for people receiving the next beta: it won't be in this version yet since it was already uploaded. It was a bit too easy, so I probably forgot some use case that will fail!

BTW: to test, I modified my Delay plug-in such that the delay time also becomes the latency. When set to 100% mix and no feedback, audio should be heard without the delay. So with a 2 second delay time, things become obvious whether the PDC works or not.

This is really good news! Can I email you to test it?

Sure, but there is no beta version ready yet with this feature. I would first have to fix a thing or two tomorrow and then upload it.

Ok, thanks!

MrStochastic

AEM looks like the most active dev iOS daw

It is really nice to see how responsive and active @dwrae is.

The more familiar I get with it the more I like using it.
But now that I've begun using the midi tracks, some editing questions pop up.

I've been recording improvisations into it using SWAM instruments and it does a good job with that and recording all of the controller messages, etc.
So what I'd like to do is leave everything in place but just fix some pitches. I don't want it quantized; I'm not playing on the grid; I just want to move notes up or down without changing their position. Shouldn't there be a way to move note pitches and keep them in their exact, unquantized location? The only way I can do it now is to turn off quantized but then it's too easy to shift the timing while dragging the note.

dwrae

@MrStochastic said:

AEM looks like the most active dev iOS daw

It is really nice to see how responsive and active @dwrae is.

The more familiar I get with it the more I like using it.
But now that I've begun using the midi tracks, some editing questions pop up.

I've been recording improvisations into it using SWAM instruments and it does a good job with that and recording all of the controller messages, etc.
So what I'd like to do is leave everything in place but just fix some pitches. I don't want it quantized; I'm not playing on the grid; I just want to move notes up or down without changing their position. Shouldn't there be a way to move note pitches and keep them in their exact, unquantized location? The only way I can do it now is to turn off quantized but then it's too easy to shift the timing while dragging the note.

I'm afraid there currently isn't such an option. On desktop, it would be easy to use a modifier like shift or ctrl, but on mobile it would require an extra button/mode somewhere. I will think about what the best solution is here.

Kewe_Esse

@dwrae said:

@MrStochastic said:

AEM looks like the most active dev iOS daw

It is really nice to see how responsive and active @dwrae is.

The more familiar I get with it the more I like using it.
But now that I've begun using the midi tracks, some editing questions pop up.

I've been recording improvisations into it using SWAM instruments and it does a good job with that and recording all of the controller messages, etc.
So what I'd like to do is leave everything in place but just fix some pitches. I don't want it quantized; I'm not playing on the grid; I just want to move notes up or down without changing their position. Shouldn't there be a way to move note pitches and keep them in their exact, unquantized location? The only way I can do it now is to turn off quantized but then it's too easy to shift the timing while dragging the note.

I'm afraid there currently isn't such an option. On desktop, it would be easy to use a modifier like shift or ctrl, but on mobile it would require an extra button/mode somewhere. I will think about what the best solution is here.

Fwiw, 4pockets get around this sort of thing by using multiple assignments for a single button (eg. press, swipe down and long press). There are little indicators on the corner of the buttons to visually show this availability. See example:

I don’t dislike it! But I did have to read manual a bit, didn’t find it immediately obvious.

dwrae

@Kewe_Esse said:

@dwrae said:

@MrStochastic said:

AEM looks like the most active dev iOS daw

It is really nice to see how responsive and active @dwrae is.

The more familiar I get with it the more I like using it.
But now that I've begun using the midi tracks, some editing questions pop up.

I've been recording improvisations into it using SWAM instruments and it does a good job with that and recording all of the controller messages, etc.
So what I'd like to do is leave everything in place but just fix some pitches. I don't want it quantized; I'm not playing on the grid; I just want to move notes up or down without changing their position. Shouldn't there be a way to move note pitches and keep them in their exact, unquantized location? The only way I can do it now is to turn off quantized but then it's too easy to shift the timing while dragging the note.

I'm afraid there currently isn't such an option. On desktop, it would be easy to use a modifier like shift or ctrl, but on mobile it would require an extra button/mode somewhere. I will think about what the best solution is here.

Fwiw, 4pockets get around this sort of thing by using multiple assignments for a single button (eg. press, swipe down and long press). There are little indicators on the corner of the buttons to visually show this availability. See example:

I don’t dislike it! But I did have to read manual a bit, didn’t find it immediately obvious.

I'd rather have two buttons showing a lock/unlock symbol and arrows pointing left/right on one and up/down on the other

MrStochastic

@dwrae said:

I'm afraid there currently isn't such an option. On desktop, it would be easy to use a modifier like shift or ctrl, but on mobile it would require an extra button/mode somewhere. I will think about what the best solution is here.

If you can it would be great help! I really like how solid and stable AEM is. Audio editing has been smooth and easy.

stormbeats

@dwrae I used Audio Evo in it’s early days on iOS and it has really come along far since then. A lot of improvements and good work you have done Any plans to release a MAC / desktop version ?

purpan2

@stormbeats said:
@dwrae I used Audio Evo in it’s early days on iOS and it has really come along far since then. A lot of improvements and good work you have done Any plans to release a MAC / desktop version ?

It’s not a specific version, but it does run pretty well on silicon Macs. (edit: a few things are compromised, like track settings.)

And I’m eagerly waiting for news of the new version of this great DAW!

dwrae

@purpan2 said:

@stormbeats said:
@dwrae I used Audio Evo in it’s early days on iOS and it has really come along far since then. A lot of improvements and good work you have done Any plans to release a MAC / desktop version ?

It’s not a specific version, but it does run pretty well on silicon Macs.

And I’m eagerly waiting for news of the new version of this great DAW!

Thanks. In the next days I hope to roll out the next release:

What's new in version 6.7.3:

• Many actions can now be done during playback, most of them without a pause, some with a short pause.
• Changed the colors of the piano roll and drum pattern editor into a dark mode.
• Added a 'Multi-instrument' option when creating a drum pattern track: in this mode, you can assign an audio file or a sound from a Soundfont to a drum 'lane'. This makes it possible to use your own sounds in the drum pattern editor. Each drum lane now also features its own audio processing chain, meaning that it has its own effects grid, volume, panning, ADSR, pitch shift and basic reverb controls. You can use the iOS drap & drop mechanism to import drum sounds as well (max. file size 4MB).
• A free drum sound pack consisting of 80 high quality drum samples for use with the multi-instrument drum pattern editor can be downloaded. It features a wide range of kicks, snares, hihats, toms, etc. sorted by different genres: 80's Retrowave, Acoustic, EDM, Foley, Hip Hop, Industrial and Reggaeton.
• Optional in-app purchase to extend the free drum sound pack with 420 more high quality drum samples.
• Added multi-output support for AUv3 instruments. Additional outputs can be sent to mix busses.
• New Settings screen to match the app's style.
• Multiple mixer controls can now be adjusted simultaneously.
• Added an 'Import Soundfont' option to the instrument selection dialog (although Soundfonts can always be copied directly using the Files app to the AudioEvolution/SoundFonts folder).
• Added a 'Share' option to the file pop-up menu in the file browser.
• Added an option 'Draw grid on top of clips' which now defaults to 'off'.
• Changes to tempo markers can now be undo/redone.
• The audio input dialog now makes it possible to select between different inputs of the device itself, so you can for example select the iPad microphone even if a headset is connected.
• The state of the AU button in the instrument display is now remembered and stored with the project.
• When editing notes outside the current clip area, the clip will now be automatically expanded.
• Added a Quantize option to the pop-up menu of selected notes in the piano roll editor.
• Added a 'Select all' button to the piano roll editor in Edit mode.
• The mixer can now be scrolled when dragging in the volume slider area.
• The available memory is now displayed in the instrument selection dialog. The app will now refuse to load Soundfonts when the available memory is lower than 250MB to prevent out-of-memory crashes.
• Added an 'Auto split' option to the audio clip pop-up menu.
• Added an option 'MIDI loop recording'.
• Added an option to test the new plug-in delay compensation that works for both audio and instrument tracks (non-armed) to the BETA section of the new settings dialog.
• The size of the AU MIDI view is now remembered and stored in the project (half/full size) and the option 'Open AU in full screen' has been removed from the Settings.

• Minimum iOS version is now iOS 12.

• Solved a crash that could occur when MIDI was received while adding or removing a track.

• Replacing an effect with the display active of the target effect block could cause a crash. Solved.
• A split point could be erroneously added when moving your finger beyond the display edge. Solved.
• Long-tapping a position on the arranger screen and selecting Paste could paste at the wrong location. Solved.
• MIDI parameter control settings for Evolution One were not set when loading a project. Solved.\n"
• Solved a timing issue for MIDI events being recorded from a AU MIDI processor.
• Marquee selection in the piano roll did not handle scrolling correctly. Solved.
• Selected events in the piano roll could be moved to a negative offset. Solved.
• MIDI clock messages weren't always sent correctly on iOS14+. Solved.
• Pasting a MIDI clip with multiple MIDI channels would reset all the MIDI channels to one and the same channel. Solved.
• Could not overwrite Evolution One preset. Solved.
• Solved an issue with rendering tracks with the iSymphonic AUv3 (and perhaps other AUv3 instruments).
• MIDI remote control presets could not be saved for Lowtone. Solved.
• Cut (ripple) from the More menu did a regular cut. Solved.
• When selecting a clip edge for trimming without actually moving, the clip would still get trimmed on release. Solved.
• When recording Flowtones or Lowtone using an external keyboard, notes would get duplicated. Solved.
• Punch in/out positions are now remembered, but are recalculated when they would not become in view when enabled.
• Note velocity is now drawn behind notes such that they are not cut off.
• AudioShare stopped working in iOS18. Solved.

Cambler

Wow, kudos @dwrae ! Great update.

purpan2

That’s a massive amount of work - thank you!

NoiseHorse

Thank you so much for this update. I’m buying every In App purchase you’ve got. Looking forward to your new drum loops!