Direct midi recording from mixer doesn't work

[gentleclockdivider]

Niot sure what I am doing wrong here , but clicking on the new icon (enable midi capture ) from within the mixer does nothing
No new midi file is created

Just a simple setup , monosequencer into midi out ( assigned to vst on mixer track 1 )

[levendis]

Works here.
[mono step seq] --> [MIDI output] (set to <mixer track name>)
The MIDI Input selector of the Track is set to Track Input.

The new file is created in the MIDI pool upon disengaging the MIDI capture button.
i also placed a MIDI arp VST on the track and its output was then what became content of the capture.
If the track receives no MIDI events, for the duration of an enabled capture button, then nothing is created in the MIDI pool.

[colin@loomer]

Works here.

...

The new file is created in the MIDI pool upon disengaging the MIDI capture button.

Thanks. I haven't had a chance to look into this yet as I'm first investigating a few other bugs. But I should mention that the other catch with writing to the MIDI pool is that the transport needs to be running for capture to work. Stopping the transport should also create the file (same as when the MIDI capture button is clicked off.)

[levendis]

… I should mention that the other catch with writing to the MIDI pool is that the transport needs to be running for capture to work. Stopping the transport should also create the file (same as when the MIDI capture button is clicked off.)

Thanks for the extra specificities.

It may be useful to have the MIDI capture function available as destination for the [mixer parameter] module.

[colin@loomer]

It may be useful to have the MIDI capture function available as destination for the [mixer parameter] module.

Yeah, that's a great idea. And as a controller mapping destination, also.

[gentleclockdivider]

Still no luck
I load micrtonic vst using only the onboard sequencer ( no architect sequencer ) and that midi output is captured .
But non of the architect sequencers is captured , unless I am totally misunderstanding this feature and it's only meant to capture vst midi outputs and no arch.sequencers
Here's the verry simple set up

[colin@loomer]

Still no luck
Here's the verry simple set up

That setup looks fine to me. I've fixed that other bug you reported, so I'll take a look at this one right now...

[colin@loomer]

Just to confirm, ABL3 does output MIDI? (You can check this by looking at the plugin properties under INPUT/OUTPUT. It'll say how many MIDI outputs the plug-in supports.)

[gentleclockdivider]

Some more info about this issue , it seems that certain plugins only will pass through midi when there is an effect applied afterwards
In my case ( see screenshot ) I used abl3 , recording midi didn't work , but when I inserted KLanghelm vumt ( ballistic VU meter ) the midi was recorded
Strange , shouldnt the midi output be taken directly from the architect's sequencers ?

[colin@loomer]

Strange , shouldnt the midi output be taken directly from the architect's sequencers ?

Not if there are plug-ins on the track. MIDI data flows more or less the same way as audio does:

audio input > plugin A > plugin B > audio output
midi input > plugin A > plugin B > midi output

So it'll capture whatever the MIDI the last MIDI outputting plugin outputs. If plugin B output MIDI, it'll record that.

If you want to route from the graph directly to a track for MIDI capture, either:
(a) create another MIDI output module and use that to route directly to a track that you use exclusively for MIDI capture.
or
(b) just create a MIDI capture track and set its MIDI input to the previous track.

[gentleclockdivider]

Strange , shouldnt the midi output be taken directly from the architect's sequencers ?

Not if there are plug-ins on the track. MIDI data flows more or less the same way as audio does:

audio input > plugin A > plugin B > audio output
midi input > plugin A > plugin B > midi output

So it'll capture whatever the MIDI the last MIDI outputting plugin outputs. If plugin B output MIDI, it'll record that.

If you want to route from the graph directly to a track for MIDI capture, either:
(a) create another MIDI output module and use that to route directly to a track that you use exclusively for MIDI capture.
or
(b) just create a MIDI capture track and set its MIDI input to the previous track.

O.k. but this still doesn;t explain why I need to insert an effect in order to record the midi output directly from that track ( abl 3 )

Example B is a good workaround

[colin@loomer]

O.k. but this still doesn;t explain why I need to insert an effect in order to record the midi output directly from that track ( abl 3 )
Example B is a good workaround

No, you're right: it doesn't. I'll look into it...

[colin@loomer]

Think I've fixed this now (in the sense that I've written a whole bunch of tests to check combinations of audio routing and MIDI routing, and they all pass.)

[colin@loomer]

Just to confirm, I have fixed it (which is an upgrade from my previous comment that I think I've fixed it!)