Topic: After updating to v2.13, the Tempo = Lock does not work.

[MusicMan]

Hi

Regarding the setting:
Menu 2 > Style Setting > Behavior change > Tempo. When set to "Lock", after changing to a different style during playback, the tempo reverts to the default tempo of the currently selected style.

This problem is now occurring after updating to v2.13.
It worked perfectly in v2.0.

Is there a bug in the Tempo =Lock setting in Genos v2.13.

Thank You for any comments.

[Lee Batchelor]

Hi Musicman,

I tried the Lock and Hold settings on my Genos. In both cases the tempo stays at the same tempo. I'm using V2.13. I don't think it's a bug in the software. There must be another setting somewhere that is causing this issue.

Are you accessing the styles directly from the Styles button and not through a registration?

[RONBO]

hello Musician

You could be right about a glitch in Lock setting.

However, I set my Genos to the Hold setting to keep the tempo the same from one style to another. That is what I am believing that you wish to achieve.

I have also like you applied the new upgrade

Regards

Ron

 

[Stijn]

Hi,

My Genos is updated to version 2.13.
I just checked the Temp Lock setting and it's working just fine.

When I change the Style the tempo stays the same, whether the Style is playing or not.
Resetting the Style to its default tempo is done by pressing the + &- Tempo buttons simultaneously.

Stijn

[MusicMan]

hello Musician

You could be right about a glitch in Lock setting.

However, I set my Genos to the Hold setting to keep the tempo the same from one style to another. That is what I am believing that you wish to achieve.

I have also like you applied the new upgrade

Regards

Ron

Hi Ron

Thanks for responding. I am selecting Styles from the STYLE button, not from registration. This always worked perfectly before the update to v2.13.

egards

[MusicMan]

MusicMan here.

The problem seems to be resolved by a restart.

After updating to v2.13, I restarted once and Tempo Lock did not work. This 2nd restart seems to have fixed the problem.

I should have tried restarting before posting, but thanks to all who responded.