these might be true in RB too, but right now I'm using PT x64, preparing a show for streaming, and I've noticed two things I've never seen before in all the years of using PT and RB in exactly the same way:

Before I describe the problem, I should describe my setup, and how I use it. My gear is rack mounted, and it all goes to a mixer, which then goes to an audio interface for streaming. The only thing that connects the gear together is serial MIDI cables used for sending embedded patch changes and continuous controller messages in each sequence to set up the patches and FX for each song so I can move through my set hands free.

I go to a lot of trouble to make sure that the volume of each device and each track and each song is consistent, much like mastering an album... through many iterations I play and record the set, making tweaks at each pass.

I noticed today that two things are causing unexpected variations:

1) if I move the master volume slider in PT, somehow it is changing the master volume on my vocal processor. Which blows my mind, since the only thing that slider should affect is the backing tracks. CC7 is the controller I use to change the output volume for the TC Helicon vocal processor. Maybe a change was made in the program so that a CC7 controller is executed across all MIDI channels when the master volume slider is moved? But it's messing me up.

2) The other new problem is that MIDI controllers embedded throughout each song to turn FX on and off have started randomly changing locations in the song.

When I enter a location for an event to occur, PT (sometimes) changes the number to something wayyyy outside the range of the song, so the change never executes at all because the song ends before that bar is reached. I click on the event to edit it, and as soon as I click on it, the event editor shows the correct number... but as soon as I start the song again, it reverts back to some crazy large bar number. Even when I find it, I can't fix it because PT changes it back to the incorrect value for some reason.

I have actually seen this in the past, but not very often. Maybe because I've had PT open all day every day for practicing it's more likely to happen?

This usually happens near the end of the song, when I'm turning reverb off so I can talk to the audience. It might have something to do with running chord wizard, because that creates a section of bars (the song) that are mapped to a different tempo than the rest of the bars in a song? Since I'm picking a bar near where the tempo might be dramatically different, is there any way the algorithm could get it wrong? (grasping at straws here)

Anyway, my workaround is to close the program, reopen and make changes. but.... potential is high to make last minute edits to the CC events, and fail to catch it before a show.




Last edited by Pat Marr; 03/19/21 04:14 PM.
https://www.dropbox.com/sh/ey71h8ep047758h/AAC12jNM0Hz9Q8zsh5iDeqNHa?dl=0