Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Euclidean rhythms problem when set via I2C and Mapping
#2
Oh thanks I got to test that.
It does work here…but: I always use an I2C/Multi track (also for trigger16 outputs) and there it works fine also outside of a pattern.
Might be the trigger16 track in your case which I‘m gonna try.

Generally the rules are that it should work from every screen. Another rule is that it affects the current or last playing pattern or the selected pattern if you are in the pattern screen. One quirk is there which is being updated with the next firmware (and I think already discussed here) and that is if you are in a pattern then the faders for another pattern are indeed not working. But that is not your issue currently.

Another thing is when you load your project then it loads the last ‚beats‘ from the pattern and these change only with the first change of the faders.
I do rely here on what the faderbank is sending out. There is no way that I can request an update of all faders.
There is also a 10 second delay with the 16n faderbanks where they start to detect any I2C followers and from then it works which might be your delayed bpm change that you mention.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply


Messages In This Thread
RE: Euclidean rhythms problem when set via I2C and Mapping - by XORadmin - 05-26-2024, 07:31 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)