Skip to content

Clock gets stuck, sometimes #1

@hlolli

Description

@hlolli

Hi, thanks for this great library. I want to use the clock to reference schedules. I set Abletonlink.startUpdate to 10ms and on each function callback I send the timestamp from beat (of beat,phase and bpm that coma available as parameters). I printed to console an example of this (excuse the noise and ignore "offering:" part of the printout).


"offering: " 658.126638
"offering: " 658.147352
"offering: " 658.168396
"offering: " 658.189242
"offering: " 658.209964
"offering: " 658.230772
"offering: " 658.251438
"offering: " 658.272136
"offering: " 658.292854
"offering: " 658.313632
"offering: " 658.334332
"offering: " 658.355062
"offering: " 658.375954
"offering: " 658.396834
"offering: " 658.417746
"offering: " 658.440108
"offering: " 658.460968
"offering: " 658.48173
"offering: " 658.500564
"offering: " 658.521474
"offering: " 658.543846
"offering: " 658.562602
"offering: " 658.583232
"offering: " 658.604882
"offering: " 658.625718
"offering: " 658.648232
"offering: " 658.669106
"offering: " 658.689856
"offering: " 658.71058
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808
"offering: " 658.775808

this lasts for on avarage 30 secs, then it start counting normally again. I wonder if there's some concurrency issues with the clock and nodejs. Must add that I'm not doing anything special when this occours. No steps to reproduce but to just start console.logging the beat value from .startUpdate and wait until it clogs.

Im using
Node 7.0.0
abletonliink 0.0.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions