Vex Flow Tick Resolution

[texto...@gmail.com]

Hi,

I have a question regarding the tick resolution VexFlow uses:

Is there any specific reason why the tick resolution is 16384?

In tables.js looking into the implementation of  durationToTicks.durations it seems that 16384 ticks represent a whole note,

16384 / 2 a half note, etc.

I first thought it would have something to do with the MIDI standard which apparently uses 120 ticks per sixteenth note

and a PPQ (Pulse Per Quarter note) of 480 (120x4). But 16384 / 16 = 1024 ticks for a sixteenth note is significantly greater than 120 ticks per sixteenth note

which is already used to capture fine nuances during performances.

Can somebody (maybe Mohit) chime in shine some light on this?

Thank you!