For information, with MadMapper 2.5 you can set the maximum ArtNet FPS in preferences. The default value is 44.
MadMapper will not send ArtNet DMX packets if nothing has changed in the video, so if you're using a Syphon input at 60 FPS, MadMapper will send a maximum of 60 ArtNet DMX packets per second. If you're using a movie at 30 FPS, it will send 30 packets per second.
Using more than 44 FPS ArtNet can be useful with LEDs, since some LED controllers can control lights much faster than 44 FPS (Advatek Pixelite is limited to 100 FPS and we tested with 400 universes at 100 FPS and got great results).
In general working at 25 / 30 / 50 or 60 FPS is great. The ideal is the your whole chain, from the input to the light, is working at the same FPS. For instance if you use a movie at 60 FPS and set the maximum ArtNet to 60, MadMapper will send 60 FPS, but if you are then using an ArtNet->DMX node, you then getting to DMX electrical protocol which is limited at 44-45, then it's better to work with a movie at 44 or lower or you'll skip too many frame. Ideally in this case working with content at 44 FPS would be optimal.
But if you're sending Modul8 syphon output to LEDs using an Advatek Pixelite, Modul8 will be locked on the screen (60FPS), so MadMapper will receive 60 FPS, MadMapper max ArtNet FPS must be increased to 60 FPS or more (1000
, MadMapper will then send one ArtNet packet for each Syphon frame, the Pixelite will send the 600 FPS on LEDs. In this case, it will be perfect.
To get more than 60 FPS, you need MadMapper not to be synced on your screen. MadMapper graphic engine is displaying on the previews and on the outputs, if you have no projector in your project and you collapsed your previews, MadMapper will no more be blocked by your screen refresh rate and you can go to higher FPS
It's a bit tricky, but that's a hacker feature, and hackers must suffer, normal people will enjoy a simple and easy life