Resolume Forum

NxKmn wrote: ↑Thu Jan 31, 2019 07:33 I find the same drop in FPS again.

I see it too on my machines. I've created a ticket, we'll see what we can do. (#12190)

I hope there is a solution.
That it is not related to the functioning of Resolume itself.

I am now in 8 weeks of programming on BOME and Resolume configurations.
I am a complete beginner in programming. Learning to Use BOME was a big piece
To compensate for the lack of Local Variable in BOME, I had to learn to do Bitmapping.
Anyway, a lot of sleepless nights.

Certainly, my use of Resolume is not common, and the solution I thought of to realize the sequencer is particular.
But when I saw the envelopes when R6 was released, I immediately thought of this solution.

This problem is the last obstacle to the realization of my project.
In any case, it will not be functional until a next release.

If you have any news, in the meantime, would it be possible to keep me informed?

Will do

Any news?

I tried another method to reduce the number of effects per Layer.
Send A note assigned to a Resolume parameter in Timeline Mode
The Timeline is set with the parameters "Play forwards" & "Play Once"

Send Note removes the bypass, and sends the cursor to the beginning of the Timeline,
The cursor then moves to the end of the Timeline and gets stuck with the "Play Once" and the effect is automatically bypassed.
Sending the note, and the duration of the Timeline would be set automatically according to a BPM calculated via BOME ( By counting the number of milliseconds separating two "Tap")

The advantage of this method is:
- To reduce the number of effects per Layer.
Previously, 16 steps required 16 times the same effects. Now only one effect is needed. At each step the cursor is returned or not, at the beginning of the Timeline
- To play the effects independently of the BPM of Resolume.

But as often, the theory works, but in practice it doesn't.
The timeline with a Speed of 10 is not fast enough to simulate the duration of one Beat ( If the music has a BPM greater than 120) and below.

I'm desperate...

I don't have any news for you yet, I'm afraid.

According the Midi specifications, the data rate you can use to stay midi compliant is very limited. (about 3125 bytes per second), so realistically what you want to do can't be done via Midi.
Midi needs at least 3 bytes for each message if I'm not mistaken, so with the 127 messages per beat per parameter you need at 120bpm, you'd be maxing the specs out at only 4 (!) parameters.

I think you'd have a better chance with OSC, or making the sequencer outside Resolume.