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.
What I mean is, are you specifically seeing the bug occur immediately
after a new device joins?
My "feeling" is that whenever it has happened, it has always been on
start, when the devices joined for the first time. But it has been very
random to get any solid evidence or see any pattern. We will continue
doing tests so if I see anything I will report.
enrike
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
