KVR Audio

ENV1 · Post by **ENV1** » Fri Jan 22, 2016 2:13 pm

The problem is described in more detail on the image.

Shortversion: REAPER applies CC events from MIDI items outside the loop.

To me this seems wrong, but maybe there is some reason i hadnt thought of.

(Could be a bug, but could also be a preference im not aware of.)

click for fullsize

Dandruff · Post by **Dandruff** » Mon Jan 25, 2016 3:27 pm

Preferences/Audio/Playback: Resest MIDI CC ...

ENV1 · Post by **ENV1** » Mon Jan 25, 2016 5:08 pm

Nope, unfortunately this doesnt work.

It probably should, because this seems to be the right preference, but whether anything under 'Reset MIDI CCs/Pitch on:' is checked or unchecked doesnt make a difference, i.e. the issue persists either way.

Check this new screenshot.

Its always the last CC in the last preceeding MIDI item that is used in the loop, even if the playcursor doesnt actually go across any of the items preceeding the loop.

click for fullsize

Any other ideas?

EvilDragon · Post by **EvilDragon** » Mon Jan 25, 2016 5:14 pm

This looks like MIDI CC chasing as it should work. If you don't want the preceeding CC data to influence your current loop, put CC events in the item(s) you're looping so that they are set to the values you want.

Dandruff · Post by **Dandruff** » Mon Jan 25, 2016 5:34 pm

As EvilDragon said: Put a CC to the item at playback start point. Not a bug but how MIDI is working.

ENV1 · Post by **ENV1** » Mon Jan 25, 2016 5:58 pm

EvilDragon wrote:This looks like MIDI CC chasing as it should work.

I see. Strange implementation though, because in my view this would only make sense if the playcursor actually went over the item before it reached the loop, (i.e. then it would be expected), but not if the playback is started way afterwards, in which case i would expect reaper to ignore everything that came before and go by the items within the loop only.

EvilDragon wrote:If you don't want the preceeding CC data to influence your current loop, put CC events in the item(s) you're looping so that they are set to the values you want.

Thats what i was hoping to be able to avoid.

But unless this behavior can be turned off somehow, (can it?), i dont see how i could get around it...

Groundhog #31684 · Post by **Groundhog #31684** » Wed Jan 27, 2016 7:30 pm

That's chasing working properly, I know what you mean about it being a bit inconvenient when you've already laid stuff down with CCs and you just want to jam with a control later on. You can mute the previous item(s) with the CCs which will stop the chasing happening. It only takes a couple of seconds.

Chasing like this is necessary though, you wouldn't want it chasing the loop end if you don't record any CCs at the start or the next time you play the project it will sound completely different until the first CC is encountered. Having a manual intervention like muting clips is therefore probably a good thing.

keyman_sam · Post by **keyman_sam** » Thu Jan 28, 2016 3:34 am

This chasing thing is pretty annoying. How do I turn it off? I've had the same behavior but didn't know it had a name. I just assumed it was a bug.

The scenario for me was this: Say I mapped modwheel to volume to create a crescendo. If I create a clip with this crescendo, I can't play anything before it without holding the modwheel. EVEN if I set CC1 to some value so I can hear strings without holding the modwheel, it will reset it on playback, forcing me to hold the modwheel or transmit the CC to hear any sound whatsoever. Super annoying.

ENV1 · Post by **ENV1** » Thu Jan 28, 2016 4:43 am

Groundhog #31684 wrote:You can mute the previous item(s) with the CCs which will stop the chasing happening. It only takes a couple of seconds.

Actually thats an excellent idea.

Thanks.

Groundhog #31684 · Post by **Groundhog #31684** » Thu Jan 28, 2016 12:51 pm

keyman_sam wrote:This chasing thing is pretty annoying. How do I turn it off? I've had the same behavior but didn't know it had a name. I just assumed it was a bug.

The scenario for me was this: Say I mapped modwheel to volume to create a crescendo. If I create a clip with this crescendo, I can't play anything before it without holding the modwheel. EVEN if I set CC1 to some value so I can hear strings without holding the modwheel, it will reset it on playback, forcing me to hold the modwheel or transmit the CC to hear any sound whatsoever. Super annoying.

That one isn't chase, it's CC reset and the good news is that you can turn that off in with the Preferences dandruff mentioned.

Groundhog #31684 · Post by **Groundhog #31684** » Thu Jan 28, 2016 12:52 pm

ENV1 wrote:
Groundhog #31684 wrote:You can mute the previous item(s) with the CCs which will stop the chasing happening. It only takes a couple of seconds.
Actually thats an excellent idea.

Thanks.

You're welcome!

ENV1 · Post by **ENV1** » Thu Jan 28, 2016 3:15 pm

BTW, anyone happen to know what happened to the 'Theme Editor' item under 'Appearance'?

Version 5 doesnt seem to have it, so while i can use the V4 theme i cannot set the meters to interlaced unless i load a .ReaperTheme saved with 4 that already has the option enabled.

Is there any special reason why this is currently omitted from 5?

Will it ever REAppear?

EvilDragon · Post by **EvilDragon** » Thu Jan 28, 2016 3:19 pm

Theme editor can now be ran from Actions list. It was moved there.

ENV1 · Post by **ENV1** » Thu Jan 28, 2016 3:25 pm

EvilDragon wrote:Theme editor can now be ran from Actions list. It was moved there.

Got it.

Thank You.

REAPER CC Events - Unexpected Behavior