12 Mar
2019
12 Mar
'19
1:21 a.m.
Hi Enrike,
On 11/3/19 4:48 pm, enrike wrote:
This sounds like a bug. If you can get me a patch that replicates it reliably I'll file an issue on GitHub.
I will try but its going to be difficult because it just happens very randomly and I dont see any pattern at all to guess where it might come from. Just in case it is an initialization issue with the BPM argument in the sync-jams object, I am passing a set-state /BPM 60 message on loadbang after a 1 sec delay. So far I have not seen it again but it pops very very randomly so it might be coming from anywhere else.
Do you have some evidence to point to this being the case? It would be good to know if there is a bug in the initialisation code.
Cheers,
Chris.
--
https://mccormick.cx/
Sign up to my newsletter to hear about tech I'm building.
https://mccormick.cx/subscribe