Skip to content

Higher PPQN resolution support and better swing feel!
Compare
Choose a tag to compare
@midilab midilab released this 22 Jan 10:55
· 34 commits to main since this release
v2.0.0
de055fa

Engine rewrited to perform higher PPQN resolutions and better swing styles.

// avaliable resolutions
// [ uClock.PPQN_24, uClock.PPQN_48, uClock.PPQN_96, uClock.PPQN_384, uClock.PPQN_480, uClock.PPQN_960 ]
// not mandatory to call, the default is 96PPQN if not set
uClock.setPPQN(uClock.PPQN_96);

BREAKCHANGES:
If you are comming from uClock version < 2.0 versions keep attention to the breakchanges so you can update your code to the new API interface changes:

setCallback functions name changing:

setClock96PPQNOutput(onClock96PPQNOutputCallback) is now setOnPPQN(onPPQNCallback) and his clock depends on the PPQN setup using setPPQN (clockPPQNResolution). For clock setup you now use a separeted callback via setOnSync24(onSync48Callback) or setOnSync24(onSync48Callback)
setClock16PPQNOutput(ClockOut16PPQN) is now setOnStep(onStepCall) and its not dependent on clock PPQN resolution
setOnClockStartOutput(onClockStartCallback) is now setOnClockStart(onClockStartCallback)
setOnClockStopOutput(onClockStopCallback) is now setOnClockStop(onClockStopCallback)
setOnClockStartOutput(onClockStartCallback) is now setOnClockStart(onClockStartCallback)

Tick resolution and sequencers

If you have write a sequencer using setClock16PPQNOutput only its ok to just change the API call to setOnStep, but if you were dependent on setClock96PPQNOutput you migth need to review you tick counting system depending on wich PPQN clock resolution you choose.

Assets 2
Loading