[Partially Solved] MIDI Input Issues

[Jimmy NaNa]

I made a post yesterday about a specific plugin but I think there is a larger issue at play with MIDI, inputs, VSTs and combinations thereof.

I'm on an up to date version of Windows 10, up to date version of CbB. Interface is Steinberg UR-RT2.

1. Using MeldaProduction MAutoPitch on an audio track, i set MIDI input to on, assign the correct MIDI track to it. In MAutoPitch you turn off all the notes in the scale so that it only corrects to the MIDI track notes. This works fine for the time I'm in the session. When I close and re-open the session, MAutoPitch starts randomly adding notes back to the scale by itself. It corrects if I delete the plugin and reassign all the settings. Every session close and reopen I need to reset everything.

I contacted Melda, they had no answer. i though the plugin was the issue, and maybe it is, but I got other plugins to avoid this issue.

2. Waves Auto Tune. The MIDI input works. It stays working after reopening the session. However, the settings for things like speed and note transition keep randomly resetting itself to the default after I do the initial audio scan with the plugin. So I can only use the plugin on default settings basically.

3. Waves Auto Tune Real Time. Since this plugin works differently for tuning, I gave it a shot. Except this plugin will not pull in the MIDI track notes for correction no matter what I do. Waves confirmed the plugin settings were correct. It will only tune algorithmically to the scale you have set. MIDI input connection does not work at all seemingly.

Solution:

There's a learn mode on the Waves Tune Real Time plugin. For all the functions you need to right click on the button to enable it.

The documentation doesn't state this, but it seems that it is being automatically enabled for the target pitch button.

I right clicked the target pitch button, clicked "clear" which seems to turn learning mode off.

Then I re-enable the target pitch button and it's holding the pitch to the midi track now.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

The strange thing is that Izotope Vocal Synth 2 MIDI input works flawlessly to my observation. However the latest version of Nectar 3 crashes CbB, so I had to roll back to the previous version. Nectar doesn't use MIDI input, but it seemed that when pitch correction module was on, the issue happened. So all this has some relation to pitch correction VSTs.

4. Another MIDI issue I've frequently had is that when I unfreeze a MIDI instrument track it will crash immediately upon playback. The only way to get it working again is to create a new instrument midi track and copy the midi to it without playing, then deleting the track that causes the crash.

Just me, or is this a problem for others? Is there a fix?

 

Edited January 29, 2023 by Jimmy NaNa

[reginaldStjohn]

Try clearing "zero controllers" and see if that makes a difference

[Jimmy NaNa]

1 hour ago, reginaldStjohn said:

Try clearing "zero controllers" and see if that makes a difference

Thanks for the reply, unfortunately that did not change anything.

[bvideo]

13 hours ago, Jimmy NaNa said:

4. Another MIDI issue I've frequently had is that when I unfreeze a MIDI instrument track it will crash immediately upon playback. The only way to get it working again is to create a new instrument midi track and copy the midi to it without playing, then deleting the track that causes the crash.

Does this happen with more than one particular synth? There have been unfreeze problems before related to at least one specific synth (sektor).

[Jimmy NaNa]

8 hours ago, bvideo said:

Does this happen with more than one particular synth? There have been unfreeze problems before related to at least one specific synth (sektor).

It's happened with multiple. One off the top of my head that frequently does it is Applied Acoustics AAS player, which is the most basic synth ever haha. I would say there are some that it never happens with, like Superior Drummer 2.0. However, I had a weird issue with SD2 for the first time this week. The track was playing hits that weren't on the midi track at all. Not a muted section, nothing. It wasn't even a rhythm block I had in there and deleted. Just random hits. When I froze the track it even rendered it as audio. Had to delete the whole track and copy over the midi to a new instance to get rid of it.

[scook]

Often when unexpected MIDI data is playing in a track the data is coming from another plug-in.

This is caused by one or more plug-ins having Enable MIDI Output selecting in their plug-in properties

and having the input on the track playing the unexpected data set to All Inputs - MIDI Omni.

 

By default, any soft synth capable of sending MIDI data will have Enable MIDI Output selected.

 

[Jimmy NaNa]

26 minutes ago, scook said:

Often when unexpected MIDI data is playing in a track the data is coming from another plug-in.

This is caused by one or more plug-ins having Enable MIDI Output selecting in their plug-in properties

and having the input on the track playing the unexpected data set to All Inputs - MIDI Omni.

 

By default, any soft synth capable of sending MIDI data will have Enable MIDI Output selected.

 

Hmm, interesting. I suspect there may be some conflicts going on. Just weird that specifically never happened until I started using these Midi input Tuning plugins.

I also tested Waves Tune in a blank session with only one audio track and one midi track with no other plugins or tracks and the issue of it not pulling the midi notes persisted.

Edited January 26, 2023 by Jimmy NaNa

[scook]

Can't help with Waves except to mention only the VST3 format is supported, and based on other posts here they seem to provide excellent support for their products.

[Jimmy NaNa]

11 minutes ago, scook said:

Can't help with Waves except to mention only the VST3 format is supported, and based on other posts here they seem to provide excellent support for their products.

Yeah, been using all VST3. They've been very responsive, so hoping they can figure it out. Thanks for the assistance!

[Jimmy NaNa]

On 1/26/2023 at 10:49 AM, scook said:

Can't help with Waves except to mention only the VST3 format is supported, and based on other posts here they seem to provide excellent support for their products.

I think I just figured it out.

There's a learn mode on the Waves Tune Real Time plugin. For all the functions you need to right click on the button to enable it.

The documentation doesn't state this, but it seems that it is being automatically enabled for the target pitch button.

I right clicked the target pitch button, clicked "clear" which seems to turn learning mode off.

Then I re-enable the target pitch button and it's holding the pitch to the midi track now.

This would be something I'd think Waves Support should've suggested trying.