Resolume Forum

Hello,
on a 240Hz Monitor as the sole display on a macbook m3max, on high performance mode, the maximum fps i can reach is 150-160hz.

Cpu at 7%, GPU around 70%.

It doesnt matter if I play a clip, if the comp is xga or 4k, 8 or 16bit, or if there is an active output or not. Max FPS is 160Hz.

Is this by design?
How to deactivate vsync on mac?

Will I have better luck with a fast windows machine?

With Wire, FPS in an empty patch are fluctuating between 100 and 150hz, so tends to be slower.

Maybe it would be helpful to acticate Game Mode for Resolume? Can this be done?

Thx for help

In the current design Resolume can't reach framerates as high as 240fps, it might be possible in the future if your hardware can deal with it.

What kind of content do you have which would require it to run at 240FPS?

Its a research project, I dont need high resolutions at the moment, just high frame rates. 240fps would be the minimum.

Zsoltan,
on another note, your software, I just discovered it, amazing... does it manage to framesync several Resolume servers?
Lets say I have a 20min 8k Mapping Show running on four servers, would they all run framesynced together, even after 15 minutes?
I remember, when i just Column triggered the content via OSC, after some minutes, the servers would start to desync from another, so only way to keep them in sync was to sync the playhead via OSC.

xergon wrote: Wed Sep 04, 2024 03:26 would they all run framesynced together, even after 15 minutes?

For framesync, you'd need SMPTE, and GPU genlock.

Playhead sync has it's own issues. Basically you have the file on free run on the machine, and receive OSC to set the playheads, with a little bit of delay, just enough to cause frame jumps, and audio issues.
SMPTE is really recommended.

xergon wrote: Wed Sep 04, 2024 03:04 Its a research project, I dont need high resolutions at the moment, just high frame rates. 240fps would be the minimum.

You wont be able to reach 240fps no matter the settings or device you're using. Our theoretical maximum is 200fps doing nothing. In practice however the limit is lower. There are some timing inaccuracies and minimum maintenance routines being executed, so 160 is a more realistic limit in practice.
This is due to an unfortunate design decision that will take significant effort to erase...