I create rackspaces for individual songs. When I do that, I enter the song’s BPM and “override global BPM” in the rackspace properties. It would seem logical that whenever I select that rackspace it would change the global BPM. In rackspace view, it works as expected. On that same note, it would seem that if I create a song in setlist mode that does NOT override global bpm, you would think the system would default to the rackspace’s global bpm designation, but it does not. I stays with whatever BPM was in place prior to the change. The net effect, although not tragic, is that I have to globally overwrite the BPM for both the rackspace AND the song if I want that BPM to be accurate in both modes. Wouldn’t it make sense that if on the song doesn’t override the global, but the underlying rackspace does, it should match the rackspace? Or is there some impact I’m not considering?
Songs and rackspaces are independent. All tempo options/overrides need to be configured separately.
@npudar is right.
However, I think I can help you out with this little script to sync the rackspace BPM to your songs: Use rackspace tempo as song tempo
Fair enough. And thanks Florian, but I think I want to keep the rack bpm fixed as that’s the frequently exported part (and I’ll want to preserve BPM there).
No worries, just thought it would be nice if there was a hack to avoid that data entry upon song creation.
Sorry, @Phinnin, I didn’t express it correctly. I guess it does exactly the way you want it: manually set the rackspace tempos and have the songs automatically use that.
No I got what you meant there. Was I was hoping for was a situation where if a song didn’t override the global BPM, that the rackspace’s override would kick in. This would prevent me from having a create a rackspace (or importing one) and then having to create a song for it, and then have to reapply a global BPM override to match the rackspace. Instead, if a song has no global override, the bpm won’t change upon activation from the previous song.