Does that need any further explanation really? If it says Rate: 0.5 and BPM: 120, I would expect the MIDI clock to be at 60, not 120. If it says Rate: 0.9 and BPM: 120, I would expect the MIDI clock to be at 108, not 120. If it says Rate: 1.1 and BPM: 120, I would expect the MIDI clock to be at 132, not 120. If it says Rate: 1.5 and BPM: 120, I would expect the MIDI clock to be at 180, not 120. Etc. Imho it just plain sucks to have your delay effects nicely synced to the tempo, only to see your syncing get screwed on using anything but 1.0 rate. Make it optional if you have to (for backward compatibility), but PLEASE fix this asap, now it just feels like completely broken, and makes the Rate: unusable for any project with any tempo synced parameter (and imho /all/ things should be synced to tempo; since were talking about /music/ here: rhythm is an essential element of that). I would be really surprised to hear from anyone that the current behavior is the *expected* behavior.
--------------------- Cześć! Jestem Michał. Jestem tutaj zupełnym żółtodziobem, natomiast mam w zamyśle bezustannie uczestniczyć, w istnieniu niniejszego portalu.
MEGA BUMP. C'mon guys! That whole big "Rate" slider in the middle of your screen is /completely effing useless/ whenever you use *anything* related to a proper MIDI clock speed. Doesn't anybody in here use tempo-synced delays, for example? I can't believe I'm the only one missing this feature.
The playrate slider only affects the audio output of Reaper. It is a little misleading for the midi folks. What folks may be asking for is a midi playrate, sort of a secondary BPM scaling control. Am I right to presume this ? We could add that as a secondary effect of the Playrate slider. Should this affect the tempo track ? The playrate does not. It's like a tempo trim that simply varipitches the audio output, i.e. plays everything a little slower.
Playrate control does slow the midi down - its like slowing down the "master clock" if you will. I think the OP is looking not for an additional fader, but for the transport BPM to display the new post-varispeed values - ie 120BPM should display as 108 when varispeed is at .9 For me the drag is that since varispeed slows the midi down and lowers the pitch of the audio, Virtual instruments end up out of tune with recorded tracks. What I'd like to see is the Virtual instruments optionally send audio to their tracks before varispeed is applied, so that their output is shifted in pitch to match the shifted audio...