I don’t know if anyone has had this issue before (looked in the forum and found nothing about it).
When I select a track on which I loaded a M4L device, my framerate decreases of about 10-15 fps. It’s like looking at the interface demands a lot to GPU or CPU.
As you could see, my M4L device doesn’t have much visual in it…
(the 3 outputs are 3 bpatchers)
i have a similar issue in Max5. when a patch window with 2 live.gain’s and 4 live.meter’s as only graphic objects is visible my openGL fps drops by 20%.
The GUI objects seem to take some GPU performance and I would recommend to use as less visual object as you can inside your M4L device when using jitter.
But, even more, I noticed today that if I completely hide my live set to the dock, I increased my framerate by 10 fps!
Good to know and I’m happy to share it to you!
"But, even more, I noticed today that if I completely hide my live set to the dock, I increased my framerate by 10 fps!"
Same here, for a long time. AND with or without M4L ! I think it’s an old issue with Live…
Log in to reply
C74 IN YOUR INBOX
C74 RSS Feed | © Copyright Cycling '74 | Terms & Conditions
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.