milliseconds in timestamp don't appear to be working

tonyfyeah

HI - trying to fire off scene changes on my Fractal FM3 at specific timestamps in songs. I have everything working, but no matter what I do, I can't seem to get the millisecond field in the "midi@xx:yy:zz:" command to actually make a difference. If for instance a song section starts somewhere between 1:24 and 1:25 in a song, and I want a scene change to occur close to or on the downbeat, no matter where I put the MIDI command within 1:24, it's always noticeably early (doesn't matter if it's 01:24:005, or 01:24:999:, it's always the same). And then if I just try 01:25:00: - it's noticeably late. Anyone else having this issue in trying to get somewhat accurate firing of MIDI commands to external gear? Am I doing something wrong?
-Tony

tonyfyeah

Nevermind - just realized the format is xx:yy.zzz not xx:yy:zzz (a period not a colon between y and z) ! Oops

gdgross

one suggestion I might have for peter/the developers is, turn off the blue text highlight if the format isn't correct.

I've made this mistake several times myself with pdf page changes, but good to remember, since I'll be adding midi out in future as well - some to my FM9 (go team fractal!) and some to the lights

Lishy

gdgross this already happens.

gdgross

Lishy not for me - here's a screen grab I just took and you can see the blue text, and incorrect format, in the last line:

Lishy

gdgross if it’s still blue it’ll still work. Ive just tested this with midi messages and using your last format.

gdgross

I can confirm that it only works on my iPad when I have the period preceding the milliseconds. The colon definitely doesn't work for me.

maybe it treats midi differently than pdf messages?

peter

The syntax highlighting rules are more lax than the actual parsing rules. I experienced slowdowns during editing when using the complex rules for highlighting. That's the reason for simplified rules.

gdgross

peter Thanks Peter :-D