Vdmx to Madmapper via Syphon

Support
1

Hello, for the past couple of years I’ve been sending VDMX via Syphon to MadMapper for my projects. For some time now, I’ve been having problems when switching between windows. Micro-cuts were appearing when changing windows, but now, after updating, the image freezes. This major problem started after updating to Tahoe 26.1. I’m working on a MacBook Pro M4 with 48GB of RAM. The problem is that when I switch from VDMX to MadMapper, the image freezes or the frame rate drops drastically. I also tried using Arena simultaneously and didn’t have this problem. I’ve run different tests with older versions of MadMapper, from 5.6.0 to 5.7.1, and of VDMX, from 1.1.7 to the current 1.2.3. I hope you can help me find a solution. The problem also occurs when I send files via Syphon from VDMX to Arena; the same image freezing happens.

2

513455026-dc399436-3d47-4d85-82e6-e814267ea424
513455026-dc399436-3d47-4d85-82e6-e814267ea4241426×1444 111 KB

From DL,

The best work around for this at the moment is to disable this option in the VDMX preferences. This will let the user specify a specific frame rate for rendering, which is probably what they want when they are primarily sending video to other apps via Syphon or NDI, or recording video to disk.

For users who are outputting video directly to monitors, they’ll get smoother output, and don’t have to bother thinking about the render FPS when they use the canvas driven by displays option.