OSC client and os.clock() question

Renoise Tool Development
1

Hi,
i tried to send OSC messages with a delay to the OSC server of renoise like that:

client:send(renoise.Osc.Bundle(os.clock() + delay_in_ms, messages))

… but it doesn’t have any effect, the messages are allways triggered instantly.
Actually it doesn’t matter at all what number is used for the clock value, could be 1 or 78987827, no difference.
Tried it under win7 64bit (2.8.1) and linux 32bit (2.8.0).
Is it a bug? doing something wrong?
It would be nice to have timing offsets for OSC messages, cause i suppose the clock of the OSC server would be more stable than using timers in lua.
Thanks in advance

2

Yes, we’re currently not making use of the OSC message timestamps in Renoise. For what exactly do you need them?

3

I’m writing a note repeat tool with mpc grooves. Basically i’m using renoise’s midi clock to re-retrigger the notes, but the resolution ain’t fine enough to represent the grooves properly at 16th or even 32th level. So what i tried is using timers for the addional “sub-midi-clock-ticks” delays, which seems to work, but i didn’t have time to check the timing more in depth yet. Will see if its good enough for “day-to-day” use. I do also have a unfinished “live” arpeggiator with scales and chords mappings and some extras laying around that works the same way.
So, i think two things would be great for scripting midi stuff in renoise:
1: the osc timestamps
2: a way to delete scheduled osc messages
Obviously you’ld still have to process the incoming midi in lua, but it might keep the timing issues down to a minimum.