Simple button conundrum...
-
There is some strange behaviour with this configuration.
When you set it to a sync value , then to ms you get a certain value . If you go back to sync and then to MS you get another value ? Same with the other way around ?
-
@lalalandsynth It's normal behaviour, because you cannot directly transalte ms (0-2000+) to sync (0-18) and vice versa.
1/4 (5th sync position) => 5ms
250ms => 1/64T (250 is greater than 18...)
You need to re-calculate the approaching value usingEngine.getMilliSecondsForQuarterBeatsWithTempo()and consort...That is said, what is the difference with
Engine.getMilliSecondsForQuarterBeats()?
The API says "current tempo"... So it is the host tempo I imagine? -
Yes, but its strange that it goes from a 1/4 to 8 ms , then you do the same thing again and it goes to 5 ms , that is very unexpected behaviour. If you look at the start of the example I dont change anything , just hit the button again and get different results.
-
@lalalandsynth You're right I noticed that once too… it is maybe because of some rounding somewhere in the process… dunno…
-
@ustk How to apply this on a label instead? So that when tempoSync is activated the label changes from ms to n/n? Thanks
-
Update, tried again using
Engine.getQuarterBeatsForMilliSeconds(double milliSeconds), the numbers get to 0.00nnnn. I'm sure it's possible to get the tempo format value to the label just like in the knob. Just need to know how. -
@Sawer What about
Engine.getTempoName()? -
@d-healey
Looks like this function doesn't work anymore. Tried also assigning it to a variable but nothing. Not in the autocomplete list as well. -
@Sawer You're not using the latest version of HISE?
-
@d-healey I am. Is that function working at your end?
-
I am. Is that function working at your end?
Yes, on the latest develop branch.
It was added back in February.
-
@d-healey Ok, will upgrade today.
-
@d-healey Update and working! Thanks
