AUM 1.4.0 update is here!

j_liljedahl

@belldu said:
@j_liljedahl I'm getting hanging notes on the in-app midi keyboard in new AUM (iPad iOS 15.5)
If you start on C4 then slide finger to C5 then release, then C5 will not receive Note Off.
This is with 'hold' set to off and the only way to stop the note is to start / stop transport.

I can't reproduce this, and I didn't change how key on/off handling is done. It could be something in the synth, which instrument plugin are you experiencing this with?

Would also be good to make the keyboard a bit taller or draggable, I think its got smaller vertically.

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.

j_liljedahl

@Apex said:
Love the new long press “node” pop-ups. Very useful.

Will echo what a few others have said: Would like to see MIDI Clock sync (I don’t find Ableton Link to be any better than good ol’ MIDI Clock, especially when dealing with hardware). I understand though that it’s hard to do right.

As mentioned a couple of times, this is on the roadmap. I had hoped to get it into this update but I ran out of time and energy and wanted to get this update out before summer.

IMO, AUM has the best user interface in all of iOS land. Brilliant job.

Thanks!

j_liljedahl

@Apex said:
Slowly making my way thru the new features…..

Noticed that the ‘scroll left/right’ arrow keys are no longer working on my Bluetooth keyboard. Was working in the previous version a day ago. But oddly enough the ‘page left/right’ (command + arrow keys) still works? 🤔

I didn't change this part so that's weird. Perhaps it's the AUv3 focus stealing bug? If you have focussed a text entry in a plugin, the host will stop receiving keyboard shortcuts until the plugin window is closed. I've reported this to Apple a long time ago so hopefully it will get fixed. (The same thing happens in all the other hosts so it's not related to AUM)

Apex

@j_liljedahl said:

@Apex said:
Slowly making my way thru the new features…..

Noticed that the ‘scroll left/right’ arrow keys are no longer working on my Bluetooth keyboard. Was working in the previous version a day ago. But oddly enough the ‘page left/right’ (command + arrow keys) still works? 🤔

I didn't change this part so that's weird. Perhaps it's the AUv3 focus stealing bug? If you have focussed a text entry in a plugin, the host will stop receiving keyboard shortcuts until the plugin window is closed. I've reported this to Apple a long time ago so hopefully it will get fixed. (The same thing happens in all the other hosts so it's not related to AUM)

Unfortunately not a “AUv3 focus” issue. Its super weird cause it was just working, and like I said the “page left/right” still works.???? (maybe specific issue with my Logitech keyboard case??). The keyboard support was one of my favorite things you added recently. HUGE workflow bump for me. No worries…. I can still use my finger to scroll left/right 😆 You’re spoiling us with the awesomeness of AUM.

belldu

@j_liljedahl said:

@belldu said:
@j_liljedahl I'm getting hanging notes on the in-app midi keyboard in new AUM (iPad iOS 15.5)
If you start on C4 then slide finger to C5 then release, then C5 will not receive Note Off.
This is with 'hold' set to off and the only way to stop the note is to start / stop transport.

I can't reproduce this, and I didn't change how key on/off handling is done. It could be something in the synth, which instrument plugin are you experiencing this with?

Would also be good to make the keyboard a bit taller or draggable, I think its got smaller vertically.

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.

I can't reproduce it now either... I'll watch for it again though. I didn't have it connected to any hardware so wasn't a stuck sustain pedal, but agree it could have been another auv3 causing it.

enkaytee

@j_liljedahl Can definitely confirm that Autony midi sequencer no longer appears as a source for an audio channel - looks like it's because it's not listed as an Audio Unit MIDI Processer, but as an Audio Unit Extension. Is this something for the Autony dev to investigate? I'm not sure it they're still active and it would be a real shame if Autony wasn't going to work in AUM any more...

j_liljedahl

@enkaytee said:
@j_liljedahl Can definitely confirm that Autony midi sequencer no longer appears as a source for an audio channel - looks like it's because it's not listed as an Audio Unit MIDI Processer, but as an Audio Unit Extension. Is this something for the Autony dev to investigate? I'm not sure it they're still active and it would be a real shame if Autony wasn't going to work in AUM any more...

Not sure I understand. MIDI Processors are not and have never been listed as audio sources. Any plugin can be a MIDI source, if it declares that it has any MIDI outputs.

EDIT: I assume you mean MIDI source. Yes I can confirm that Autony does not show any MIDI outputs. Perhaps it doesn't return its MIDI outputs at the right time in its initialization procedure, so when AUM asks if it has any MIDI outputs it says it has none.

onerez

Autony not listed as source…. Cality by same company is???? Big Bummer as I love Autony!!!!

j_liljedahl

@j_liljedahl said:

@enkaytee said:
@j_liljedahl Can definitely confirm that Autony midi sequencer no longer appears as a source for an audio channel - looks like it's because it's not listed as an Audio Unit MIDI Processer, but as an Audio Unit Extension. Is this something for the Autony dev to investigate? I'm not sure it they're still active and it would be a real shame if Autony wasn't going to work in AUM any more...

Not sure I understand. MIDI Processors are not and have never been listed as audio sources. Any plugin can be a MIDI source, if it declares that it has any MIDI outputs.

EDIT: I assume you mean MIDI source. Yes I can confirm that Autony does not show any MIDI outputs. Perhaps it doesn't return its MIDI outputs at the right time in its initialization procedure, so when AUM asks if it has any MIDI outputs it says it has none.

There's a new section in the built in Users Guide that lists the init order for AUv3 plugins. For example:

• For AUv3 plugins, instantiate the AUAudioUnit object.
• Set the AU transportStateBlock, musicalContextBlock and MIDIOutputEventBlock.
• Call AU allocateRenderResources, failing if it returns false or if renderResourcesAllocated is not set after the call.

So if Autony creates its MIDI outputs in allocateRenderResources instead of at plugin initialization, it would make AUM not see them.

enkaytee

@j_liljedahl said:

@enkaytee said:
@j_liljedahl Can definitely confirm that Autony midi sequencer no longer appears as a source for an audio channel - looks like it's because it's not listed as an Audio Unit MIDI Processer, but as an Audio Unit Extension. Is this something for the Autony dev to investigate? I'm not sure it they're still active and it would be a real shame if Autony wasn't going to work in AUM any more...

Not sure I understand. MIDI Processors are not and have never been listed as audio sources. Any plugin can be a MIDI source, if it declares that it has any MIDI outputs.

EDIT: I assume you mean MIDI source. Yes I can confirm that Autony does not show any MIDI outputs. Perhaps it doesn't return its MIDI outputs at the right time in its initialization procedure, so when AUM asks if it has any MIDI outputs it says it has none.

Thanks @j_liljedahl - what's changed in the latest version that would affect this so I can try to contact the Autony dev for a fix? Is it just the case that it needs to show MIDI outputs? It used to work fine so I'm hoping it's something that can be sorted as I've used it a lot in projects! BTW - when I said it's not listed as a midi processor I was referring to the choice of AU type that appears in the pop-up when you add an AU to a MIDI channel. As far as I remember it's always appeared in the Audio Unit Extension list, NOT the Audio Unit MIDI Processer list so I didn't know if this was causing problems with the new AUM version.

EDIT: having checked a little deeper, it looks like plugins that I'm pretty sure worked as MIDI generators for Audio channels but which are in the 'Audio Unit Extension' list as described above and as shown in the screenshot below no longer appear as MIDI sources - Axon 2 for example.

Hkor

Really nice update.
A crossfader like in Drambo or ableton live with A/B Chanels would be welcome 🙏

ZankFrappa

This is what it looks like for me in Autony:
The Moogs and Mela are displayed and can be connected, Sunrizer and iSEM are not.

wim

@ZankFrappa said:
This is what it looks like for me in Autony:
The Moogs and Mela are displayed and can be connected, Sunrizer and iSEM are not.

I think you might be looking at that backward. You would want to be checking that the synths can receive from Autony, not that Autony can receive from the synths. However, when you check the synths, you won't find Autony as a source to be connected, so it's definitely borked.

The reason you don't see Sunrizer and iSEM as sources is they don't output any midi.

dalton34gr

A Confirmation That Koala issue is fixed
But SynthMaster 2 is not fixed yet

wormfood

Same issue with Autony, it doesn’t show up as a midi out option for me too. 11” iPad Pro, 15.4.1:

_ki

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

Fingolfinzz

Great update, @j_liljedahl. Lots of very helpful ease of use updates

onerez

@_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

I dont even know if @pagefall is supporting the apps anymore? I think he was ending in December of 2020?

auxmux

It would be disappointing re Autony, it's a great midi AU.

enkaytee

@_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.

RajahP

@dalton34gr said:
A Confirmation That Koala issue is fixed
But SynthMaster 2 is not fixed yet

Seems ok here..
Air 4.. latest iOS..

jolico

@Hkor said:
Really nice update.
A crossfader like in Drambo or ableton live with A/B Chanels would be welcome 🙏

👍

GLacey

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…

RaquNox

@j_liljedahl said:

@Apex said:
Love the new long press “node” pop-ups. Very useful.

Will echo what a few others have said: Would like to see MIDI Clock sync (I don’t find Ableton Link to be any better than good ol’ MIDI Clock, especially when dealing with hardware). I understand though that it’s hard to do right.

As mentioned a couple of times, this is on the roadmap. I had hoped to get it into this update but I ran out of time and energy and wanted to get this update out before summer.

IMO, AUM has the best user interface in all of iOS land. Brilliant job.

Thanks!

This is very very exciting for me to hear. AUM is the best there is for the iPad form factor gui wise. Tipped and will again once that update is out. Btw really appreciate your engagement with customers!

soulianis

Jonatan, thank you very much! This is stunning!

rogp

Love the update. Thanks. AUM is awesome.

GLacey

@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…

Ok, I just realized that this is the long press the node trick.

enkaytee

@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...👍

onerez

@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...👍

This is great!!!!!

auxmux

@onerez said:

@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...👍

This is great!!!!!

Awesome.