From 5dc63bdb7d7fbe2858ef3cdc43960cb4c049bdf9 Mon Sep 17 00:00:00 2001 From: midilab Date: Sat, 29 Mar 2025 14:25:46 -0300 Subject: [PATCH] update breakchanges from 1.x to newer api calls --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1e6feab..af26695 100755 --- a/README.md +++ b/README.md @@ -62,10 +62,10 @@ If you are coming from uClock version < 2.0 versions, pay attention to the break ### setCallback function name changes -- **setClock96PPQNOutput(onClock96PPQNOutputCallback)** is now _setOnPPQN(onPPQNCallback)_ and this clock depends on the PPQN setup using _setPPQN(clockPPQNResolution)_. For clock setup you now use a separated callback via _setOnSync24(onSync24Callback)_ -- **setClock16PPQNOutput(ClockOut16PPQN)** is now _setOnStep(onStepCall)_ and it's not dependent on clock PPQN resolution -- **setOnClockStartOutput(onClockStartCallback)** is now _setOnClockStart(onClockStartCallback)_ -- **setOnClockStopOutput(onClockStopCallback)** is now _setOnClockStop(onClockStopCallback)_ +- `setClock96PPQNOutput(onClock96PPQNOutputCallback)` is now renamed to **`setOnOutputPPQN(onOutputPPQNCallback)`**, and its tick count is based on the PPQN setup using **`setOutputPPQN(clockOutputPPQNResolution)`**. For clock ticks, you now use a separated callback via **`setOnSyncXX(onSyncXXCallback)`**, where XX represents one of the available PPQN values +- `setClock16PPQNOutput(ClockOut16PPQN)` is now renamed to **`setOnStep(onStepCall)`**, and it's not dependent on clock PPQN resolution. +- `setOnClockStartOutput(onClockStartCallback)` is now renamed to **`setOnClockStart(onClockStartCallback)`**. +- `setOnClockStopOutput(onClockStopCallback)` is now renamed to **`setOnClockStop(onClockStopCallback)`**. ### Tick resolution and sequencers