Isn’t this possible since a few years now with AUv3 and MIDI output recording from Instrument types? Béla Balazs gave a WWDC talk about this with GarageBand on iOS in either 2017 or 2018, but I can’t seem to find the video now.
Peter, are you using either the AU’s midiOutputEventBlock <https://developer.apple.com/documentation/audiotoolbox/auaudiounit/2866003-midioutputeventblock> or scheduleMIDIEventBlock <https://developer.apple.com/documentation/audiotoolbox/auaudiounit/1387576-schedulemidieventblock> to trigger MIDI from the plugin’s own virtual keyboard? If you’re not, using this may solve your problem, and will have the added benefit that users will also be able to record their performances using the plugin’s keyboard. You can use the current "Audio Unit Extension App” Xcode templates as a reference point for this, particularly the MIDI Effect example, which illustrates sending note-on and -off events from the DSP Kernel’s `process` block (search for `sendNoteOn` in the generated project). Of course, in an Instrument, you won’t be able to use the process block to send MIDI for exactly the reason that Markus mentioned, so you’ll need to use a different mechanism to connect your keyboard UI to the AUAudioUnit’s `midiOutputEventBlock`. Best regards, Kevin > On Feb 23, 2024, at 12:32, Markus Fritze via Coreaudio-api > <[email protected]> wrote: > > In your case you do not have a generator plugin, but rather an instrument or > effect and these plugin types are only processed by Logic Pro when needed, > meaning: when Logic knows that there is something to process, e.g. MIDI or > Audio going in. This is an optimization – active many years – to avoid > wasting CPU cycles on plugins processing „nothing“. Such a plugin can’t > trigger itself. > > > Markus > >> On Feb 23, 2024, at 09:20, support (One Red Dog Media) via Coreaudio-api >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi >> I’m experiencing a bug with my AUv3 when hosted within Logic Pro (both Mac >> and iPadOS). When a project containing my plugin is re-opened, the plugin’s >> own virtual keyboard does not trigger the synth’s audio engine. It appears >> silent or suspended. When the Logic transport is started, or MIDI is sent >> from an external instrument, or MIDI is sent from Logic’s own virtual >> keyboard, my plugin “wakes up” and the audio engine is behaving as expected. >> During the suspended phase, the plugin’s UI behaves as expected.I’ve managed >> to get the Xcode debugger connected to my AUv3 and observed that the render >> callback is not called until the transport starts or MIDI received. >> This is the last major bug, so any help will be appreciated in understand >> what the fix is. >> Thanks >> peter >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Coreaudio-api mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/coreaudio-api/mfritze%40apple.com >> >> This email sent to [email protected] <mailto:[email protected]> > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Coreaudio-api mailing list ([email protected] > <mailto:[email protected]>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/coreaudio-api/rknelson%40apple.com > > This email sent to [email protected] <mailto:[email protected]>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
