From 84ba2014c9bcbebaeb95f4b652599064d3647454 Mon Sep 17 00:00:00 2001
From: Harry van Haaren <harryhaaren@gmail.com>
Date: Thu, 29 Sep 2016 19:49:45 +0100
Subject: [PATCH] Removed setBpm() retriggers looper playback

Although this allows loops to go out of sync, I think its more
"musical" than the re-trigger noises of scrubbing the BPM dial...

In short - in a live performance I do not expect musicians to
change tempo in a song - between songs it possible, and then
triggering a scene will bring everything back into sync.

This needs a better solution, but right now I'm not sure how
to best do that. The other changes in the patches that changed
this behaviour are valuable, so commiting to get closer to a
solution - but I'm not comfortable with the retrigger noises.
---
 src/timemanager.cxx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/timemanager.cxx b/src/timemanager.cxx
index def7d32..db728bf 100644
--- a/src/timemanager.cxx
+++ b/src/timemanager.cxx
@@ -74,9 +74,10 @@ void TimeManager::setBpm(float bpm)
   barCounter  = 0;
   beatCounter = 0;
   beatFrameCountdown = -1;
+  /*
   for(int i=0;i<observers.size();i++)
       observers[i]->resetTimeState();
-
+  */
 }
 
 void TimeManager::setBpmZeroOne(float b)