Need help: Midi CC not output / not set? 2.1.24

[alschmid]

Hi there

I’m running 2.1.24 on macOS Sequoia.

I am trying to output Midi CC data via a defined Midi Output to switch scenes on my FM 9.

For that purpose I’ve added a Midi track, added a new Midi region, and then, using the MIDI List Editor, added two CC events, both to channel 16, both CC #34, all using the defined MIDI output.

The MIDI Output works and the FM9 is configured correctly, all tested using another software with exactly the same CC #34 messages to channel 16. So the issue is with VST Live.

Observation: The CC change that I set using the MIDI List editor (see picture, left window) is not shown in the MIDI editor (right window); it is however consistently shown in the MIDI List.

There is no MIDI output from VST Live.
What am I doing wrong?

Thanks a lot!
Alexander

[fkalmus]

hi! could you do a screenshot from your settings in
Devices / Connections / MIDI
to look if everithing okay there too?

[alschmid]

Hi Felician

Thanks for your swift response.
With pleasure. I’ve not set the input, since I don’t need it.

Best,
Alexander

[fkalmus]

Hi! I’m totally in different kind of work currently, but can we try two things to find out what might stop VL sending CC to to FM9?

1. there is a MIDI monitor in Devices, can we check if sent info appears there?
2. what happens is set your MIDI TRACK OUT Ch to 16?
3. …oh, yes… the question of your VSTL version No? (sure Spork, forgotten to ask )

[Spork]

… the MIDI Editor (on the right) does not look correct. Is the MIDI Clip (FM9 Changed) selected? Have you tried the latest release (2.1.27)? You can download it here

/Michael.

[alschmid]

Hi both

So, installed 2.1.27 now, and switched to channel 16 also in the inspector.
There is a new behavior:

I have CC messages at Bars 1.1.1 and 3.1.1:

• When I hit stop multiple times to get back to the beginning of the song and then press play, the Midi message for 1.1.1 is correctly sent, the FM9 switches as expected.
• When the playhead goes across bar 3.1.1, nothing happens. No MIDI is sent (I see this as the FM9 has a MIDI activity LED).
• When I press stop, some MIDI is then sent to the FM9, but seemingly not the correct message. Nothing happens on the FM9.
• When I then press play (playhead being somewhere after 3.1.1), the CC message is sent immediately, MIDI activity LED on the FM9 blinks, and the FM9 switches as expected.

It’s not the FM9. If I send the midi messages from another software, it works as expected, every time.

Here’s what VST is sending:

Note:
18:11:45 I pressed play at bar 1.1.1.
18:11:53 I pressed stop.
18:11:56 I pressed play again after having passed bar 3.1.1.

There seems to be a bug.

Thanks!
Alexander

[alschmid]

Still on 2.1.27.

So, in the meantime I’ve created a midi file in Pro Tools, set some CC#34 messages, exported as MIDI and imported the MIDI file into VST Live.

Same behavior as described above.

Also,

• the MIDI List Editor recognizes the events correctly;
• the MIDI Editor still does not show any events:
  
  

These are the events that should be there according to the Midi List Editor:

Also, I can’t draw any events into the automation lane (CC 34).

In noticed that the MIDI Editor says “No object selected” even though I’ve clearly selected the MIDI region:

Help, please?

Thanks!
Alexander

[Spork]

@alschmid

Help, please?

… that’s really strange! I am sorry. We would need access to the project to analyse it. Do you think it is possible? You could send me a PM where I can download the project. For that you need to create an archive of your project. Use the “Menu / Edit / Save Archive …” option, select an empty folder and finally zip it.

See you,
Michael.

[musicullum]

Tried your first setup with breath lsb at 1, 3, and 43. Send to virtual midi 3 out and observed midi monitor on virtual midi 3 in. All seems correct.

Note the preferences setting “MIDI/Chase Events on Start”, if set, nothing is sent when locating, only when started; when disabled, chased events are sent when locating transport.

AS for your midi file and automation problems, as Micha said it would help to get a (possibly reduced) VST Live project; we could test the midi file separately too.