Hey Steve! I’ve been looking for a solution to automate clip triggering in Resolume based on timecode inputs, since while you can sync to SMPTE in Resolume, you still have to manually trigger the clip you want playing. As a result I am looking to setup the following logic in BMTP:
If xx:xx:xx.xx < MTC < yy:yy:yy.yy
Then send midi note or osc value “z”
Only send message once as we do not need to “keep triggering” the clip in Resolume
With this translator, I can create a playlist of parameters, so each song has its own “x < MTC < y, trigger z” to automatically trigger Resolume clips.
Your work on this “timecode log” here suggests this might be a pretty quick thing to advise on!
Hi Steve, thanks for the quick reply! I’m sitting here working through this right now. I’ve had a few Bome boxes over the years going back to 2017
I am receiving SMPTE from a DAW on stage, converting to MTC on my local machine, and want to trigger events. I’m not entirely sure if the quarter frame or full MTC makes a difference for my purposes, in that I am “just triggering” the launch of a video clip in Resolume using a midi note, and the SMPTE from the on-stage DAW takes over the sync. Also, since I am wanting to “trigger the event” any time I jump into this MTC range, it is less about hitting a specific quarter-frame, and more about triggering the event for any message that is received within a MTC range.
Well, we have to know what the current MTC is and we can look at that by:
Counting quarter frame messages
Looking at MTC full frame message
I would need to know which type of MTC message that your DAW sends when it jumps to a given location. Then we would have to convert that into a generic numerical format and compare to see if it is within the target range. We would also need to determine whether the message within that range has already triggered a clip.
The format of message for MTC is Binary Decimal encoded which is why it is best to somehow convert both the target range and the incoming location to a standard binary format.
This should be possible but writing something like this would be out of scope for free support as it would likely take a number of hours. I have a project that looks at quarter frame messages and puts into BCD format but nothing that converts to a standard binary format for comparison.
This project simply sends keystrokes to a given application every time a quarter frame 0 message is sent.
The work here would be to
Build the standard format number from the current BCD fomat
Set up low and high parameters in standard format to compare with
3 ) Compare the values upon every quarter frame message
If within range, look for a flag if the message has already been sent
If not sent, send the clip launch (note) and set the flag.
Is there a support page that explains in more detail the syntax for Rules in Bome? It feels like this is where the majority of the work will be done.
In my case, the MTC is coming from Timecode Expert by TXL20, and I believe the format is just: “F1 xx”, as per the log:
‘1680: MIDI IN [IAC Driver Bus 2]: F1 28’
I’ll have a look at your example .bmtp and report back if I find any solutions myself.
