MIDI Clock Jumping to 20 or 500 BPM

[Zoltán]

This might help meanwhile https://forum.cockos.com/showthread.php?t=254027

[manymanyhaha]

Thank you for the suggestion, really appreciate it. Unfortunately that does not work with Region Playlist in Reaper, which is what I am using to get a randomized playlist.

Don't recall what it was but there was another reason why I wasn't using Link when I've had this setup in Ableton. When I remember, will update here.

[manymanyhaha]

Hey, its is May and don't think I've expressed how much I despise 500 bpm yet this month

[SeanBannister]

While this is still a problem for me, I was able to make it happen less often by separating my midi clock and midi data. I use loopMidi as my virtual midi port and it allows you to setup multiple ports, I've now setup one called "clock" and another called "data" in Resolume I have the data port set to "Midi input" and the "clock" port set to "Clock input".

Without doing this if I was to change decks and then column via midi commands it would loose midi clock consistently. With this setup it doesn't happen.

It just happens in a heap of other cases, like swinging the BPM quickly.

[manymanyhaha]

Appreciate the tip but already have it set up like that.

Wish I could say 500bpm was growing on me but it still grates like I am sure me repeating this annoyance is grating to the resolume folks.... . As I've said before, at least have it not stop at 500bpm. 20bpm is infinitely more tolerable than 500, imho

[manymanyhaha]

I hate 500 bpm. Just curious why 500 bpm? Do people actually go beyond like 200 bpm?

[manymanyhaha]

I actually kind of like when it goes to 500 bpm and then settles at 20 bpm, it has this brief speed up effect. But when it settles at 500 bpm, so annoying..............

[mowgli]

Many years later and this is still a problem.
Will it ever be fixed?
What's the point of having MIDI clock-in capabilities if they are rendered useless by this bug?

I find some consistent behaviour. Everything is fine to start off with, but if I stop my MIDI clock, Resolume jumps to 500. The only way to fix it is to go to preferences and toggle Clock input off and then on again. I wish this was it but sometimes the clock jumps to 500 for no obvious reason.

I've been trying to integrate Resolume and my Eurorack synth for years now but this kind of bug makes the setup completely unreliable to perform anywhere other than experimental kind of events which is a big shame!

I haven't looked into it but I'm wondering if it would be possible to make a botch fix using Wire?

[manymanyhaha]

Yep, I gave up on controlling Resolume BPM with midi. Useless.

[mowgli]

New version and this issue appears to be getting worse...

The thing is that toggling MIDI clock in the preferences on and off fixes the problem which makes me think that fixing this with a botch could be easy...I'm only guessing and I'd much rather that it was properly fixed in any case.

The weirdest thing is that things like rearranging clips in the grid messes up the MIDI clock.
Stopping the MIDI clock source also messes it up.

I can not express how utterly frustrating this is.
The amount of amazing things that I'm just not doing in public because the functionality that is supposed to be there doesn't work!

It's not like it's a feature request, it's a request to make things that are supposed to already be there work as intended!