Clock is all messed up #169
Comments
|
I'll have a look. |
|
Oh wow, I can confirm, the shortcut breaks the clock. |
|
There was a duplicated function |
|
Just tested & seems fixed. Can now adjust bpm as regular. Unfortunately, bpm doesn't seem steady. Bpm seems to speed up over time or is outputting a higher bpm than stated (maybe 171 when set to 170)? This could be an issue that has been there for a while, just don't remember it being so bad before. |
|
So very weird. Everything seems ok now. Ran through a bunch of tests and as soon as I soon as I put a |
|
Testing atm. If I tap to bpm it seems pretty stable-ish. |
|
How do you tap to tempo? |
|
I have a node script that detects bpm from midi signal. |
|
Ahhh. Just noticed that you can now send Midi clock from Orca out.
As you can see in the pic above, 104 in Orca is actually 104.17.
Changing from 104 to 105. Orca actually then sends 105.63. This would explain why things would get out of sync for me. |
|
120 to 121 is then 121.96 (basically 122). |
|
Maybe the faster the bpm the more unstable? Here's 201 outputting 202.69. |
|
It's normal I think that has the time between frames get shorter, it becomes more inaccurate. I don't know how I could make this more reliable with my current programming skills. |
|
No worries. Just something that's good to know. :-) Being able to sync to Orca or for Orca to sync up to something else makes this not that big of a deal. Just something that one needs to know when recording and working with multiple setups. |
|
It only took a whole year almost before Orca got clock in and clock out, BUT WE DID IT ✊ |
|
For sure. ✊ |
Just downloaded the latest version of Orca and the clock is all messed up. Can't change bpm and frames go crazy when using the
cmd + >/cmd + <.The text was updated successfully, but these errors were encountered: