Problems with RGB Matrix

[Flo]

Hi!

I play around with the RGB Matrix at the moment - and I think there are some bugs:
- The animation seems to have some problems handling the fade times. As soon as you enter a fade in time it stops. Fade out times work, but seem to be calculated in the wrong way.
- I had it two times with the "Balls" setting that one ball had a speed of 0 and so remained in one place all the time. Maybe it would be good to code a minimum speed in this pattern?

Generally in my eyes the matrix has a lot of potential. One thing I would really welcome: If you could define a list of colors (not just only one or two). So e. g. with Stripes every stripe would use the next color, with Balls every ball would have its own color from the list, with Circles every new circle would have the next color of the list...

[plugz]

Hi,

- The animation seems to have some problems handling the fade times. As soon as you enter a fade in time it stops. Fade out times work, but seem to be calculated in the wrong way.

It would be nice to have more details here. I guess you're talking about the preview area in the RGB Matrix Editor. (when editing a matrix in the Function tab) Yes, the behaviour looks pretty erratic here. I usually test-run (with the "play" button) and visualize what's happening in the fixture monitor.

- I had it two times with the "Balls" setting that one ball had a speed of 0 and so remained in one place all the time. Maybe it would be good to code a minimum speed in this pattern?

Maybe a duration of zero could create a super-quick matrix. For now it creates a blank matrix. I don't know what's best.


FYI I've just fixed an issue with the duration (fadeIn+hold) calculation when playing with the speed dial in the RGBMatrix Editor, but I don't know if it will fix the issues you encounter...

[mspeder]

Hello

I'm having also some difficulties with RGBMatrix timeouts (running latest 4.9). Pb seems to be showing both in preview and in "run" mode.
I see two issues when running the matrix in "single shot" mode.
- fadeout on last step is not executed (meaning after last step "hold" time, fixtures are all going black instead of slowly decreasing
- once last step "hold" time is passed, if some fadeout from previous steps are still running they are stopped

To me this all seems related to the same root cause : when in single shot mode, when the last step has reached end of its hold duration everything is shutdown, instead of honoring the remaining fadeouts.

When the rgbmatrix is converted to a sequence, the behaviour of the sequence is correct (all fadeout honored correctly).

Any idea ?

Thanks !

Matthieu

[plugz]

Hi,

Yes, I've encountered this issue too, I'll check this out.