I will explain to you what I am doing and how.
I am in the process of making a Step-sequencer with 16 steps.
For each layer, a selection of effects that can be sequenced differently, with a different BPM.
Example of how it works in video:
Each line on the Launchpad = 16 identical effects
Each Pad on the Launchpad = One effect.
Each effect is configured like this:
( 4 effects )
The pads on the Launchpad mainly control bypassed [ B ]
But by pressing a function pad on the Launchpad, they can be used to manipulate other parameters, such as blending modes.
Theright most and leftmost pad controls the BPM at which the sequence will be played.
But with a function pad, they also allow you to load / unload all effects on the line
Or to send a precise patern.
Finally, it is planned to be able to switch to the video grid, to trigger the videos, individually or by column.
And of course the classic tap tempo, deck switching etc. etc..
I also have a Midi Fighter Twister with 16 infinite encoder and LED ring to control different parameters / effects.
And two Launch control XL to control the mixing parameters of each Layer and select the Layers on which the Launchpad and the Midi fighter twister will act.
A sequence is composed of 16 steps / 16 effects.
Each sequence is configured to be "played" on 1 / 2 / 4 / 8 / 16 / 32 / 32 / 64 / 128 BPM.
This means that the entire sequence is read in 1/2/4/8/16/16/32/64/128 bpm.
For some effects a short sequence of 1 2 or 4 bpm is the best choice.
For other effects, a longer sequence is preferable.
For example, with invert RGB effect :
Read on 1 BPM : strobe effect at the beginning of BPM ( Up to 1/2 bpm)
Read on 2 BPM: Strobe effect on the first BPM and nothing on the second.
Read on 4 BPM: Strobe effect on the first two BPMs and nothing on the third and fourth.
From 4 BPM the "strobe" effect is no longer really visible. Each effect being visible on 1/4 bpm, it is no longer really "strobe".
This sequence is interesting on 4 BPM.
Inverrt RGB is Active on the first BPM and Inactive on the next 3 bpm
This sequence is only of interest on 2 BPM ( or 4 bpm maybe)
First inverted BPM RGB is active.
Second BPM inverted RGB is OFF
This sequence can be read on:
1 / 2 / 4 BPM: strobe effect all the time.
16 BPM : as in the previous example, invert RGB is active 1 out of every two BPMs
reading the invert RGB sequence over a longer time than 16 BPM is of little interest. It is effective on short sequences.
Unlike other effect sequences.
To return to the original question of the thread.
I wanted to retrieve the value of the MIDI instruction assigned to the BPM Timeline, to display a Yellow cursor on the Launchpad. To tell me where the sequence is at.
But as it is not possible to retrieve all the values of a Midi instruction, read over a short time, I found another solution.
I first tried to use Waveclock, but it didn't work properly. My Yellow pad shifting little by little.
The only Software MIDI Clock I found is https://midiclock.com/
But the Tap tempo is really zero compared to the one of resolume. He only averages between two Tap
Finally, the most correct solution I found is to recover the BPM value given by the TAP tempo on resolume to generate a timer in BOME.
It's not perfect. But it works.
I monitored throughout the construction of the BOME project and the settings in Resolume, to see how it affected performance, and whether it was viable.
Because at the end, it's a little over 200 effects per Layer. And I was afraid Resolume wouldn't be able to handle it.
And I was quite surprised to see that it was working rather well.
Until recently :B
According to your previous answer, it is the frames per second that determine when the midi instruction will be sent.
For more reactivity on my controllers, I was careful not to overload the Midi instruction channel. So much so that instructions are sent only when I perform an action.
But I realized that by adding more and more BPM SYNCH in the effects, the instructions sent by resolume are slower and slower.
Even though there are no midi shortcuts assigned to these parameters in BPM Synch mode
I tested by duplicating 16 times the layer I'm working on. All MIDI shortcuts are in "Target : Selected Layer" mode which is representative of the project once completed.
If I press one of my Pads, the action is performed immediately in Resolume.
But the return...... Easily about ten seconds of waiting time. If not more.
It is not Viable......
After more than a month of work, programming BOME, and setting Resolume, I am about to enter a deep depression.
I tested it in a new project, to reproduce the problem. With a new midi shortcut file. To start from scratch.
Just one parameter linked to a Midi shortcut. Nothing else.
Then load several dozen effects with all settings in BPM Synch mode.
==> No problem, the Midi returns are almost immediate.
Then I have in this same new project, reload the Midishortcut.xml with all my Midi settings.
This is also visible in the Windows Task Manager. It is enough to have about ten parameters in bpm Synch mode, so that one of the core (Ryzen7 1700 8 Core) is busy @100%.
With a new MidiShortcut.xml this does not happen.
I deduce that in any case, if a parameter is modified, resolume will read the entire midiShortcut.xml file to see if a midi shortcut is assigned to this parameter.
So, obviously, if there are several dozen parameters that are modified at the same time, and the MidiShortcut.xml file is huge, this can only cause problems...
Anyway, is there any way out of this? Is it a bug, or is it normal?
I use an online translator to write ( Deepl). I can read English, but I have a lot of trouble expressing myself.
So excuse me if I'm not always understandable.