Single CCs (now with video) (SOLVED)

[Tod]

I have found that this is a Kontakt bug, not a Reaper bug, and wanted to post this in case anyone else runs across it.

EvilDragon gave me this link.
https://www.native-instruments.com/f...events.345041/

I've complained about this before, and it's so irritating I need to bring it up again. Please fix.

These midi editor pictures are midi for my Pedal Steel Guitar in Kontakt

This only works part of the time.


This works all of the time.



This only works part of the time.


This works all of the time.

[MonkeyBars]

what is the bug? what do you mean by works

[sockmonkey72]

If you put a ReaControlMIDI before the PSG and examine the log, are the single CC messages being sent? Does the problem occur with other plugins (best, not from NI)? Does the problem occur with the same plugin in other DAWs?

[Tod]

Originally Posted by MonkeyBars

what is the bug? what do you mean by works

These are CC events that control the pitch of my steel guitar.

The ones that work part of the time have 1 CC event before the note is played.

The only way to get it to work all the time, every time is to draw several events under the notes.

One CC event before the note should work which is why I call it a bug.

I have this Steel Guitar on the market, here is one of the demos.
https://youtu.be/j_Ypn79rt_s

[Tod]

Originally Posted by sockmonkey72

If you put a ReaControlMIDI before the PSG and examine the log, are the single CC messages being sent? Does the problem occur with other plugins (best, not from NI)? Does the problem occur with the same plugin in other DAWs?

Thanks for your reply sockmonkey, yes ReaControlMIDI shows the events are working.

Simple CC event tests with the Steel Guitar also work okay.

It's when the midi is more complex, like the midi track used to create that Steel Guitar in the demo I posted above, that's when things become ify.

[Tod]

Here's a video showing the problem and you can clearly see the bug in this video.

https://youtu.be/t0dfH2_0Fig

Now I have to be absolutely honest. It wasn't until I was putting this video together that I found another factor. This is a midi program with key-switches and as I was putting this video together I accidentally put a CC4 event in front of the key-switch, and it played properly.

This is good, but does not mean this is not a bug, it is still a bug with important reasons to try and fix.

[Tale]

Originally Posted by Tod

It's when the midi is more complex, like the midi track used to create that Steel Guitar in the demo I posted above, that's when things become ify.

But does ReaControlMIDI then still shows events are working? Because that would suggest that it might not be a REAPER bug, but rather a Pedal Steel Guitar (or Kontakt) issue.

[Tod]

Originally Posted by Tale

But does ReaControlMIDI then still shows events are working? Because that would suggest that it might not be a REAPER bug, but rather a Pedal Steel Guitar (or Kontakt) issue.

Hi Tale, I didn't put ReaControlMIDI on this time because as I mentioned above it showed all the midi data before.

I'm the one who wrote the script and created this Steel Guitar, all the key-switch does is tell witch group in Kontakt is to be used and the velocity of the KS tells what the pitch amount will be..

I can't see how selecting the group before the CC-event would cause this you'd think it would be the other way around. I mean if the group to be played is selected and then CC-event is played.

I guess it's not that big of deal if in deed it will work with the cc events played before the key switches, we'll just have to wait and see.

[Tale]

Originally Posted by Tod

I guess it's not that big of deal if in deed it will work with the cc events played before the key switches, we'll just have to wait and see.

Oops, I seemed to have missed that it worked with the CCs before the key switches. But it might still be useful to look at the MIDI log, both when it works and when it fails Maybe you'll be able to spot the difference that way.

[Justin]

aha, I think I duplicated this, investigating now!

[Tod]

Originally Posted by Justin

aha, I think I duplicated this, investigating now!

Thanks for checking this Justin.

[Justin]

Originally Posted by Tod

Thanks for checking this Justin.

ah, the thing I found is that if "Sync MIDI editor transport to project transport" is unchecked, playing back the preview from the MIDI editor doesn't respect CC ramps, which isn't ideal.

If that's not what you're seeing (e.g. this is from project playback), can you make me a minimal project that reproduces? (ideally with reasynth or something so I don't have to be dependent on another VSTi, using MIDI parameter modulation if necessary)

[Tod]

Originally Posted by Justin

ah, the thing I found is that if "Sync MIDI editor transport to project transport" is unchecked, playing back the preview from the MIDI editor doesn't respect CC ramps, which isn't ideal.

If that's not what you're seeing (e.g. this is from project playback), can you make me a minimal project that reproduces? (ideally with reasynth or something so I don't have to be dependent on another VSTi, using MIDI parameter modulation if necessary)

Okay Justin, for what it's worth I do have "Sync MIDI editor transport to project transport" checked.

I'll see what I can do with Reasynth, I tried it the other day for testing this, but couldn't figure out how to get it to respond to CCs. I'll give it another try.

[Tod]

Originally Posted by Justin

ah, the thing I found is that if "Sync MIDI editor transport to project transport" is unchecked, playing back the preview from the MIDI editor doesn't respect CC ramps, which isn't ideal.

If that's not what you're seeing (e.g. this is from project playback), can you make me a minimal project that reproduces? (ideally with reasynth or something so I don't have to be dependent on another VSTi, using MIDI parameter modulation if necessary)

Hi Justin, I'm not sure what you want. I was able to get Reasynth set up and working with CCs as well as parameter modulation.

ReaSynth responds perfectly with the CC event. It don't even need a CC event at the front, it responds directly with the envelope, which is great and expected.

I'm just not sure how to duplicate the problem I'm having with My Steel that's using keyswitches.

To recap what's happening with my steel guitar.

> The key-switch comes before the note(s) being played.

>The key-switch determines which CC controller (1 of 4) is being used for the tuning, and for now lets just call it CC1 .

>If the event for CC1 comes after the key-switch but before the note(s), then it doesn't work.

>But if CC1 is before the key-switch, then it works.

Is there something I'm missing or don't understand?

[Justin]

Originally Posted by Tod

Hi Justin, I'm not sure what you want. I was able to get Reasynth set up and working with CCs as well as parameter modulation.

ReaSynth responds perfectly with the CC event. It don't even need a CC event at the front, it responds directly with the envelope, which is great and expected.

I'm just not sure how to duplicate the problem I'm having with My Steel that's using keyswitches.

To recap what's happening with my steel guitar.

> The key-switch comes before the note(s) being played.

>The key-switch determines which CC controller (1 of 4) is being used for the tuning, and for now lets just call it CC1 .

>If the event for CC1 comes after the key-switch but before the note(s), then it doesn't work.

>But if CC1 is before the key-switch, then it works.

Is there something I'm missing or don't understand?

Can you make a screenshot of this one that also shows where the key-switch event is (or -- is it the E1 note?)?



I suspect in that case, it goes CC, key-switch, note. So then the plug-in ignores the CC, gets the key-switch (where it starts listening for the CC), then gets the note.

REAPER doesn't keep sending the CC if it hasn't changed, unless you have manual CC events inserted.

[Tod]

Originally Posted by Justin

I suspect in that case, it goes CC, key-switch, note. So then the plug-in ignores the CC, gets the key-switch (where it starts listening for the CC), then gets the note.

REAPER doesn't keep sending the CC if it hasn't changed, unless you have manual CC events inserted.

Okay here is another screenshot showing all 3 scenarios.


The E1 is the keyswitch, the C2 is the note being played.

Does this help?

[Justin]

Originally Posted by Tod

Okay here is another screenshot showing all 3 scenarios.


The E1 is the keyswitch, the C2 is the note being played.

Does this help?

Does the CC lane have events that are before the current view, or are the events visible the first events?

Can you show me the midi_logger output of the top and bottom scenarios? and while you're at it, make me a minimal .rpp of each of those? (or put the two items in one .rpp).

[Tod]

I made a light error in the picture above, this is the way it should have been.



I've included a Reaper project file that has the 3 scenarios in the picture. It also has a midi_logger.
https://stash.reaper.fm/45233/Test%2...r%20Justin.zip

[Justin]

Originally Posted by Tod

I made a light error in the picture above, this is the way it should have been.



I've included a Reaper project file that has the 3 scenarios in the picture. It also has a midi_logger.
https://stash.reaper.fm/45233/Test%2...r%20Justin.zip

Then it makes sense that that wouldn't work -- the CC gets sent first (the plug-in ignores it), then the E1 gets sent (so the plug-in starts looking for that CC).

Ideally, the plug-in should track the CC, and use the last-known value of it when it receives the E1. (if this is your Kontakt script that should be possible I would think?)

[Tod]

Originally Posted by Justin

Ideally, the plug-in should track the CC, and use the last-known value of it when it receives the E1. (if this is your Kontakt script that should be possible I would think?)

Yes, I could probably setup a variable or array for each of the 4 keyswitches. Haha, I'm looking at the script right now to see how that might work.

I'm going to give this some thought Justin, and thank you for sticking with me.

[Tod]

I've found that the bug is indeed a Kontakt bug and I wanted to post this in case anyone else has this problem.