Tempo Change Bug

Hi there,
I think I´ve discovered an annoying bug.
I´m using Sonar 7 Producer Edition for years and decided to give the new Sonar Platinum a try - installed the Demo.
Since then I get this bug:
When I change the tempo in Sonar 7 this takes proper effect on all Midi data but NOT on the metronome sound!
Whatever I do, it stays at 120 BPM. Maybe pretty interesting if you want to record experimental stuff or polyrhythmic songs, but
for me it really sucks!
After deinstalling Platinum and the Command center the problem still remains.
 
Many thanks to Cakewalk.

I doubt it's a SONAR issue. Nothing like this has ever been previously reported to my knowledge. Kind of sounds like your click has been rendered as a wave file rather than being generated live by the metronome. Or the opposite: you changed tempo in a project that's all audio, so only the metronome changed while the audio continues to play at the original tempo because autostretch is not enabled.

I reinstalled Sonar 7 and saved the dll´s of the VSTi´s before deleting the old version. After reinstallation I dropped them back to the VSTPlugin-Folder and did a reboot. 
 
Now everything works again.
 
@brundlefly (I remember that old movie, was great!):;
 
No, there was nothing in the project instead of one single keydown Midi event. The click wasn´t rendered either.
 
Couldn't believe it myself. Turned speed to 20 BPM: locator went real slow, still 120 bpm click.
Put it to 500: still 120 bpm. Turned click from wave to midi-click: same behaviour.
By that time the behaviour within Platinum was fine. But that didn´t help much, since Platinum didn´t get my VSTi Miroslav Philharmonic (IK-Multimedia) working.
 
Unbelievable. My conclusion: Platinum Demo ruins existing Sonar 7 Producer Edition - Beware and never change a running system.

I just tested this with Platinum. The metronome followed tempo changes as expected when enabled for playback, recording, or both. SONAR 7 is over eight years old...maybe there's some conflict with the X series versions if the two exist side-by-side. In the future when making changes to your system, I recommend creating a Windows system restore point. 
 
And another heads-up for the future - I'm glad dropping the DLLs into the VSTplugins folder worked, but some instruments make changes to the system and require an actual re-installation.

Check your Windows "Restore" points. Sonar should have created a restore point before it installed the demo OR you can check the dates and find an automatic Winsows Restore point that you can revert back to (so look for the one JUST before you installed the Sonar demo).
 
I create my own manual Win Restore points before installing anything on my DAW using descriptive names and a date so I know what I did, when and thus am able to restore to a point in time I KNOW I had a working config.
 
eg: Dec11 Install Sonar Demo
 
System Restore is different than a full on System Image backup because it retains all new files created. What it does is revert the system programs and settings back to a previous state. This means you do not lose any files created between the time you create the restore point and the time you engage the restore point.
 
To access Windows Restore click on your Start Menu. In the "Search Programs and Files Field" type "Recovery" and click on the option that says "Restore Your Computer to an Earlier Time".
 
Aftter that click on the button that says "Open System Restore".
 
Follow the instructions in the dialog that pops up and choose the appropriate restore point to revert back to BEFORE you installed the offending program (in this case the Sonar Demo).
 
As I said there should have been an auto restore point created before the Demo was installed but you will also likely see auto restore points created by windows anyway that you can choose from.
 
As far as the issue described in the OP... I have no idea why that would happen but I've never installed the demo.
 
Cheers.

williamcopper

Paul P
 I guess it may be complex to accomplish, but uninstalling a demo shouldn't destroy the existing version.

Great word "Shouldn't"  ... sadly, not a true word.   edit -- or said better, true as a moral imperative, but not a good thing to rely on in software.

What I meant was that I'd be pretty angry if my current setup was destroyed after uninstalling a demo (unless this outcome had been clearly stated in large bold capital letters just below the 'download demo' button).