First of all, when you 'play' the music you are creating, can you hear ALL of what you say should be there, i.e. the trigger note and the triggered (created) notes. If not, then there's something seriously wrong regarding what you think is happening, and what is actually happening.

I assume everything is on the same channel, or you are monitoring all channels that something might be using?

I assume that your reference to 'midi notes' is referring to midi data, i.e. the set of bytes for turning a specific note ON, followed (maybe later) by a set of values for turning the note OFF. You are monitoring at a specific point in the signal chain, and at that point the trigger note has alreadt been created, and now the triggered notes have also been created. I assume that the creation of the triggered notes has not interfered with the previously creater trigger note - I think you say that you can see the data for that. Just not the triggered data?

How are you creating the triggered data withing the existing midi chain. You need to be doing this while NOT interfering with the midi chain.

If all the systems you've tried are doing the same thing, then maybe the triggered data is NOT being created (as you expect it be) or it is no longer 'associated' with the original input trigger data?

Any extra info you can provide as to the mechinics of what you're doing would be a help.

Geoff

Oh, what sort of Delta Time are you adding into the stream to preceed each of the Triggered items? Nothing too long I hope, else you might be still waiting for it to happen?

Geoff

Hello Geoff,
Thanks for replying. Below, I have tried to answer as best as possible the questions you have asked.

First of all, when you 'play' the music you are creating, can you hear ALL of what you say should be there, i.e. the trigger note and the triggered (created) notes. If not, then there's something seriously wrong regarding what you think is happening, and what is actually happening.

When the Virtual Instrument is being played, a MIDI keyboard is being used. Various trigger notes are pre-mapped across the keys on the MIDI keyboard. So, various keys on the MIDI keyboard are serving as trigger notes. When a key (trigger note) on the MIDI keyboard is hit you will hear a series of notes associated with that key (trigger note) but not the key (trigger note) itself.

Prior to playing the Virtual Instrument, Logic is placed in record mode on a track. And when recording is engaged and a key (trigger note) is hit the triggered notes or pattern associated with the key (trigger note) can be heard but are not recorded on the track. Only the key or (trigger note) is recorded. Once recording is stopped. It is only the key (trigger note) that appears in the recording. After recording, playback of the recording can be engaged and it is the trigger notes that have been recorded on the track and they will cue the associated series of notes associated with each trigger note.

I assume everything is on the same channel, or you are monitoring all channels that something might be using?

Yes, all on the same channel.

I assume that your reference to 'midi notes' is referring to midi data, i.e. the set of bytes for turning a specific note ON, followed (maybe later) by a set of values for turning the note OFF.
Yes.

You are monitoring at a specific point in the signal chain, and at that point the trigger note has alreadt been created, and now the triggered notes have also been created.
Yes.

I assume that the creation of the triggered notes has not interfered with the previously creater trigger note - I think you say that you can see the data for that. Just not the triggered data?
Yes.

How are you creating the triggered data withing the existing midi chain. You need to be doing this while NOT interfering with the midi chain.

Not sure about this. The developer of the Virtual Instrument, Output, has done this. There are numerous other Virtual Instruments from Native Instruments, Spectrasonics, Ujam… that operate the same way—trigger notes that create a series of notes.

If all the systems you've tried are doing the same thing, then maybe the triggered data is NOT being created (as you expect it be) or it is no longer 'associated' with the original input trigger data?
Yes, this is what I am trying to figure out>.

Thanks for the extra information, although I still cannot offer any answers - yet.

As you have, it seems, been able to record some of the data, it would be useful if you could attach this info. If you've been able to save it as a midi file, this would be ideal. Please note that a midi file is NOT one of the allowed attachment types (Yes!) so it will be necessary to use PKZIP or similar to compress the midi data into a .zip type file, as .zip IS an allowed attachment file types.

Geoff

Do you have a direct link to Output's website? I'm able to find it for sale on some websites, but am trying to find out more real info about it, and their company and plugin names are about as generic as you can get in the audio world 😀

Hi Jason,
It is output.com They have several additional virtual instruments: Exhale, Analog Brass & Winds, Analog Strings.... as well as effects plugins: Movement, Portal, Substance.

I'm not sure how exactly your virtual instrument is set up in Logic, but see if this video will solve the issue, or at least point you to some ideas.

He takes the MIDI FX version of his plugin and assigns it, and is able to record that way using the "Record MIDI To Track Here" under the track plugin dropdown menu. His method requires the plugin to have a MIDI FX version.

https://youtu.be/i3vpjuGpxyQ?si=Bxlul4TFdaNgcZZz&t=298

Jason--Thanks for the link to the video. I appreciate your help!
I am away from my home studio now, but will give it a try as soon as possible and let you know the results.

This section seems wrong?

Prior to playing the Virtual Instrument, Logic is placed in record mode on a track. And when recording is engaged and a key (trigger note) is hit the triggered notes or pattern associated with the key (trigger note) can be heard but are not recorded on the track. Only the key or (trigger note) is recorded. Once recording is stopped. It is only the key (trigger note) that appears in the recording. After recording, playback of the recording can be engaged and it is the trigger notes that have been recorded on the track and they will cue the associated series of notes associated with each trigger note.

This section suggests that you ARE recording the triggered notes, but I assume this is wrong?

This section refers to data in tracks, but midi data at this stage knows nothing about tracks, so if you are recording data, where is it going? How are you assigning it to a 'track', and which track. Maybe the data IS stored as midi, but not in any place you're looking? This is why I was asking about seeing a copy (midi file of stored/recorded data) that you've saved

Clarification required re what you mean here.

Geoff