AUM 1.4.0 update is here!

Poppadocrock

Checking out the individual app DSP is crucial for me. I can now easily see who the heavy hitters are, and potentially “freeze” aka record that track to audio.

Poppadocrock

@auxmux said:
It would be disappointing re Autony, it's a great midi AU.

Definitely it’s great to just throw out there for finding a good scale, a good synth patch, add extra midi fx, and just get something started.

@enkaytee said:

@enkaytee said:

@_ki said:
Axon 2 is still listed as midi source (both if sending from audio source node or when loaded as midi node).
But i can confirm the Autony problem.

.

To determine the extent of the problem, I simply tested all my midi generating AUv3:

• I checked about 40 ‚Audio Unit Midi Processor‘ AUv3‘s loaded into a midi slot, they all managed to get their output(s) listed in the ‚mid input‘ list of an audio generator.

• I also checked about 20 ‚Audio Unit Extension‘ midi generating AUv3s and all of them (except Autony) get their output listed in the ‚midi input‘ list.

So, it's not a widespread problem, for my rather long list of midi generators it only occured with Autony.

Regards, -ki

Yes - apologies, it's not widespread, I wasn't drilling down far enough in the audio channel to see Axon as a source. I'll try to contact @pagefall to see if there's any hope for a fix.

Update: I've heard from @pagefall and they're going to take a look at the problem...👍

AWESOME THANKS

auxmux

@Poppadocrock said:
Checking out the individual app DSP is crucial for me. I can now easily see who the heavy hitters are, and potentially “freeze” aka record that track to audio.

Yeah, this is a kickass feature.

auxmux

Oh yeah, be sure to use the tip jar. I did! 😄

j_liljedahl

@GLacey said:
I don’t know if it’s a new feature in 1.4.0, but I found out that if I tap and hold the AU instrument plug-in icon in a channel I can replace the plug-in with another AU instrument without needing to reconfigure the channel’s midi input settings. This way the midi input settings remain unchanged.
I’ve been using AUM for 3 years, but I didn’t know this feature…

It’s new in 1.4.0

Synthi

When selecting high quality in mic settings ( mic measurement mode ) the output is muted… bug??? Air 4 iOS 14.6

Tovokas

Absolutely amazing update: the DSP bypass update alone is worth hitting the tip jar!

One note: is there any possibility of modifying the behavior of the File Player so that when you first add it AUM immediately pops up the add file modal in the folder of the project you’re working on? The ‘tap to load’… “tap to load a file”… “AUM recordings”… find the folder dance gets a bit repetitive each time I record. And since you return to the default settings dialog of the player after selecting the file, it shouldn’t be confusing to new users. Thanks again for a great update.

espiegel123

@Synthi said:
When selecting high quality in mic settings ( mic measurement mode ) the output is muted… bug??? Air 4 iOS 14.6

It is my understanding that measurement mode gives you the unprocessed input. Non-measurement has automatic gain control which boosts the signal and has a limiter applied to prevent clipping.

Gdub

@Tovokas
I agree
There is extra taps for no reason, if I choose file player, then I obviously want to load a file
Great update!!

Samu

The more I think about it an audio buffer node would make perfect sense for AUM.
Add an audio-node in an effect slot, set its lenght (1-x bars) and playback mode (loop/one-shot) and add same controls as the file-player.

Since it’s built-in into AUM the recording would also be directly accessible by the file-player, no need for advanced time-stretching.

The AUM pitch-based tempo matching is enough already 😎

With overdub enabled each pass would create a new file.

Since AUM can already record audio I feel it would not take too much time for @j_liljedahl to add an audio-node as an IAP for those who need it. (It would be a no-brainer for the seamless integration alone).

Cheers!

jsmonzani

Yes it got a tiny bit smaller because the kbd settings toolbar moved from right side to top side. Making it larger would eat up another visible fx slot in the channels. But I agree it would be cool if this was a user setting.

After a few hours of tests, the new gap at the bottom of the keyboard is annoying as I often miss keys now (the reduced height doesn't help). I know that this space is used for some iOS bar at the bottom on some iPad pro (I guess) but as my iPad 9th gen isn't plagued with this OS oddity, it's just a waste of space now. Is there a chance to fix this? Thank you

j_liljedahl

@espiegel123 said:

@Synthi said:
When selecting high quality in mic settings ( mic measurement mode ) the output is muted… bug??? Air 4 iOS 14.6

It is my understanding that measurement mode gives you the unprocessed input. Non-measurement has automatic gain control which boosts the signal and has a limiter applied to prevent clipping.

That's correct. You can use the Mic Gain setting to adjust the level.

@jsmonzani said:

Yes it got a tiny bit smaller because the kbd settings toolbar moved from right side to top side. Making it larger would eat up another visible fx slot in the channels. But I agree it would be cool if this was a user setting.

After a few hours of tests, the new gap at the bottom of the keyboard is annoying as I often miss keys now (the reduced height doesn't help). I know that this space is used for some iOS bar at the bottom on some iPad pro (I guess) but as my iPad 9th gen isn't plagued with this OS oddity, it's just a waste of space now. Is there a chance to fix this? Thank you

Unfortunately the gap is needed because of the "home indicator" on modern devices without a physical home button, and as far as I can tell there's no way for my code to know if it is such a device.

jsmonzani

@j_liljedahl said:

Unfortunately the gap is needed because of the "home indicator" on modern devices without a physical home button, and as far as I can tell there's no way for my code to know if it is such a device.

Thank you for your answer, it makes sense!

nuno_agogo

@jsmonzani said:
After a few hours of tests, the new gap at the bottom of the keyboard is annoying as I often miss keys now (the reduced height doesn't help). I know that this space is used for some iOS bar at the bottom on some iPad pro (I guess) but as my iPad 9th gen isn't plagued with this OS oddity, it's just a waste of space now. Is there a chance to fix this? Thank you

for switching between app with slide up gesture this feature is very useful. before version 1.4.0 i had stuck notes when sliding up. so quite useful to me

Synthi

@j_liljedahl said:

@espiegel123 said:

@Synthi said:
When selecting high quality in mic settings ( mic measurement mode ) the output is muted… bug??? Air 4 iOS 14.6

It is my understanding that measurement mode gives you the unprocessed input. Non-measurement has automatic gain control which boosts the signal and has a limiter applied to prevent clipping.

That's correct. You can use the Mic Gain setting to adjust the level.

I mean that the Main AUM output is muted when selecting high quality in mic settings, even if there is no audio inputs in the project!

Synthi

The vumeter at the top don’t change but Pushing the “hi quality “ button acts as a mute button for the speaker output

espiegel123

@Synthi said:

@j_liljedahl said:

@espiegel123 said:

@Synthi said:
When selecting high quality in mic settings ( mic measurement mode ) the output is muted… bug??? Air 4 iOS 14.6

It is my understanding that measurement mode gives you the unprocessed input. Non-measurement has automatic gain control which boosts the signal and has a limiter applied to prevent clipping.

That's correct. You can use the Mic Gain setting to adjust the level.

I mean that the Main AUM output is muted when selecting high quality in mic settings, even if there is no audio inputs in the project!

It is my understanding that when measurement mode is off , the automatic gain system includes the built-in mic and the and the built-in speaker.

uncledave

@Synthi said:

The vumeter at the top don’t change but Pushing the “hi quality “ button acts as a mute button for the speaker output

Try turning up the iPad volume (in Control Center or side buttons). Seems like the normal Automatic Gain compensates somewhat for a reduced volume setting. In Measurement Mode, you get what you get.

boomer

Add MIDI parameter for Tempo (BPM) and Tempo Presets (trigger specific tempo changes via MIDI)

Does this mean that it would be possible to create a tempo track plugin? I.e. something like helium or atom2 could hold automation tracks mapped to this midi parameter and allow for gradual speeding up and slowing down?

GeoTony

I think so… not a helium or atom2 user but assuming I understand your question I just mapped Rozeta LFO to AUM Tempo and CC values of 0 to 127 appear to map to bpm of 20 to 500 (obviously with values in between) . I just used a simple drum pattern and got some interesting results very quickly. The inbetween CC values don’t map cleanly to integer BPM e.g. CC value of 88 produced bpm 352.6 so if you need integer bpm to sync with other apps I think you will have to use the temp presets facility (not tried it!)

j_liljedahl

@GeoTony said:
I think so… not a helium or atom2 user but assuming I understand your question I just mapped Rozeta LFO to AUM Tempo and CC values of 0 to 127 appear to map to bpm of 20 to 500 (obviously with values in between) . I just used a simple drum pattern and got some interesting results very quickly. The inbetween CC values don’t map cleanly to integer BPM e.g. CC value of 88 produced bpm 352.6 so if you need integer bpm to sync with other apps I think you will have to use the temp presets facility (not tried it!)

You can adjust the mapping range, it's not fixed to 20-500.

GeoTony

Ok thanks @j_liljedahl . Great update by the way.

boomer

@GeoTony
You definitely understood my question. Can you elaborate on “interesting results”? Thanks!

wim

@j_liljedahl - feature suggestion: pull-down search box for AU parameters. Some apps have huge lists of parameters and scrolling through them can be a pain.

Tones4Christ

Is there a way to lock sustain on a channel being played with an external midi controller?

wim

@Tones4Christ said:
Is there a way to lock sustain on a channel being played with an external midi controller?

Do you mean lock sustain on from a midi controller for notes coming from that (or another) midi controller? Or lock sustain on from a midi controller for notes coming from the internal AUM keyboard? Or something else?

Also, what kind of control to send the lock? A button, knob, notes, sustain pedal ... ?

j_liljedahl

@wim said:
@j_liljedahl - feature suggestion: pull-down search box for AU parameters. Some apps have huge lists of parameters and scrolling through them can be a pain.

You can use the Control Finder: long press the Parameters button in the top left of a plugin window:

Krupa

I’m loving the hold to replace thing, really nice simple UI/functionality improvement 👌

I had a weird intrusive thought this morning that won’t go away; I’ve long wanted to decouple Gauss from the tempo but it’s not something that will likely happen - would it be at all possible to do this with a host? @j_liljedahl

wim

@j_liljedahl said:

@wim said:
@j_liljedahl - feature suggestion: pull-down search box for AU parameters. Some apps have huge lists of parameters and scrolling through them can be a pain.

You can use the Control Finder: long press the Parameters button in the top left of a plugin window:

Oh yeah, I forgot about that one. Thanks!

GeoTony

@boomer, here is a quick video showing an example…