[fixed] Graphical Tempo automation issue

Hi all,

I’m trying to compose something in Renoise with a lot of tempo automation, but I’m finding that all the points I put in have decimal values instead of BPM values. The first point I put in was fine, showed up in the value box under the envelope as 134.000, but after leaving the automation window and going back in, the values changed from BPM values to decimals. How can I please get BPM display back in the automation window? Is it a setting I have to enable that suddenly got disabled?

I’m on a MacBook Pro running BootCamp Windows 7 x64. I have a Mid-2012 MacBook Pro (non-Retina) with an i7 processor and 8GB of RAM, upgraded from the stock 4GB.

I’m not sure what else I need to provide in terms of information, so please tell me what you need to know and I will provide more information if needed.

Thank you.

Bug confirmed in 3.1 (on Windows 10 here). Thanks for reporting.

Steps to reproduce:

  • New song.
  • Go to the master track BPM automation envelope and create a few points.
  • Switch to a different track, then back to the master track again.
  • The envelope points have now changed from showing BPM values, to showing values in the range 0.000 to 1.413 instead.

Awesome. Thanks for all your help, dblue. You and the team do a grand job. Let’s hope it’s easy to fix!


After further testing, I believe I have found out that this also happens with the Instrument MIDI Control plugin. Values appear as either a 0 or a 1. This therefore appears to be becoming a more general automation bug. I have tried searching this forum for similar reported issues but this thread is the only one that comes up when searching for ‘automation’ or ‘envelope’ in this forum. Can I change the title of the first post, or do I have to submit an official bug report for that?

Renoise 3.1 - Win7 64

This also happens to the LPB and TPL values.

Hey, is there any estimate on when this fix will be released? I’m kind of dependant on this feature and must resort to the BPM global command until it’s fixed… cheers.