Max 8.5 caused slowdown of frame rate in Jitter
I have an extensive patch using Jitter / gl2 among many other things, and when I upgraded to 8.5, my patch went from its usual 30-40 fps down to under 10. I have a performance starting up next week so I reverted back to the previous version 8.3.3. and now the frame rate is back up.
I am wondering if anyone else is experiencing issues with 8.5 in Jitter, and whether or not the new gl3 could be the cause and whether there any adjustments, modifications, etc. required.
Many thanks.
hey Randall, with Max 8.5 we have set the default Graphics Engine to glcore (formerly known as gl3). you can change this back to gl2 in your Max Preferences.
If you have a moment to bundle up your patch (or at least enough of it to exhibit the slowdown) and email it to me please do so I can try to determine why the slowdowns occurs.
Thanks Rob... actually I misspoke, I was already using gl3. Is there anything I need to do?
My patch is so massive I hesitate to send it, particularly since it has many third party externals, input / output devices, tabs galore, communication with networked computers running Max, etc.
It's humming along quite nicely in 8.3.3. right now.
same... 8.5 is way more "slow" than 8.3.3. I tried to make a case, unfortunately I really cant determinate where its comming from..
Imho jit.world by its own is not affected. (free flow render bang)
shader issue? dont know.
I'm still trying to figure out..
M1 Max
Is there some kind of diagnostic we can use to check what's slowing things down?
@RANDALL PACKER - ok sounds like it's unrelated to the graphics engine. If you're able to isolate or narrow down the issue, we'd love to take a look. But we are not aware of performance drops between 8.3 and 8.5, nor are there any general tips for improving performance when upgrading to 8.5 (especially if the graphics engine hasn't changed)
@HERR MARKANT - from what I recall your case was specific to sync state of jit.world in the context of Ableton Live, and you were also able to workaround by toggling the state, so I'm not convinced this is related to Randall's issue, not would I claim that 8.5 is slower then 8.3 (yet). Investigations remain ongoing for this issue, and your reports and findings are appreciated.
Randall, if you want to try toggling jit.world @sync attribute off and on after initializing your context (e.g turn on the rendering, then toggle the attribute), see if that helps.
We'll have to see patches if we're going to have a chance to diagnose.
IMO the best diagnostic to employ is a well organized patch that allows you to enable and disable components while monitoring the jit.fpsgui framerate.
@TAAVET, there are no Jitter objects in your patch from what I can tell, so not sure why you're posting here. Please send a message to support with your patch and node script and system specs and we'll take a look.
ups, sorry. I got carried away..
It would be great if someone could post any news about 8.5 performance issues here (or link to where there is news). I would test myself, but I have a performance starting next week and I don't want to rock what is already a very precarious boat. Thx!
@Rob Ramirez, I was able to resolve the 8.5 slowdown problem. I tore the patch apart and it turned out to be a few Vidvox jit.gl.isf objects. I just needed to update it in the Package Manager, and voila, my frame rate is now back to normal. Many thanks for your help on this.
great to hear, thanks for following up.