The latest spec can be found here, https://github.com/mrRay/ISF_Spec/
(and we are working on new reference pages for the ISF sharing site overhaul which is in development…)
As for the clock time, currently there isn’t a uniform for this, nor is there an easy way to pass in an absolute running (non-normalized) clock time from VDMX; your best bet is to use the various measure / beat time data-sources through a standard float input.
We’ll keep this in mind for the next version of the ISF spec; two initial details that come to mind would be…
Though we designed ISF for VDMX, other apps now support it as a standard; This would add a burden of including a BPM based clock for host applications (for apps that didn’t have such a clock, we’d need to define some standard fallback behavior that hosts could implement)
In VDMX you can have multiple clock plugins; which one should be used for this uniform? If we are going by the concept of multiple clocks being possible, perhaps this would be better off as a special type of float input that is declared in the JSON? Then VDMX could show a pop-up button that lists the possible clocks to sync to, like you’d get in the LFO / Step Sequencer / etc controls. Of course this goes back to the first point, not all apps have multiple clocks…
Yes the idea of a “Sync” command seems great !
As I am modifying an tesseract and creating my first shaders a lot of questions come to my mind ^^
And will work on some Float input to apply LFO and seq