Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mojave frame rate is bad unless GLUT prefs set to debug mode #207

Open
Benitoite opened this issue Jan 14, 2019 · 7 comments

Comments

Projects
None yet
2 participants
@Benitoite
Copy link

commented Jan 14, 2019

This is occurring on macOS 10.14.3b Mojave but not Sierra. To obtain a reasonable frame rate I have to either select the GEM window and wave the mouse around, or set the window's GLUT preferences to debug mode.

screen shot 2019-01-14 at 8 12 32 am

Example patch:
https://raw.githubusercontent.com/Benitoite/pure-data_patches/master/3cubesTest1.pd

@umlaeute

This comment has been minimized.

Copy link
Owner

commented Jan 14, 2019

i've seen something similar today, on a students Sierra machine (although i don't know whether this was with [gemglutwindow])

@umlaeute

This comment has been minimized.

Copy link
Owner

commented Jan 14, 2019

out of interest: how do you get to the GLUT preferences dialog?

@Benitoite

This comment has been minimized.

Copy link
Author

commented Jan 14, 2019

@umlaeute I can only get it on Mojave. You must select the GEM window first, then access the Prefs in the Pd menu. On Mojave, when the GEM window is selected, the prefs lead to the GLUT dialog as above. On Sierra, it does not.

@umlaeute

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2019

another thing: i'm wondering, whether Gem is being blocked when switching to the GLcontext (that is: for each render-cycle) or if only the window doesn't redraw itself (unless you "damage" it by moving the pointer).

so, could you measure the actual framerate you get?
something like:

[gemhead]
|
[t  b   b]
|        |
[realtime]
|
[print]
@Benitoite

This comment has been minimized.

Copy link
Author

commented Jan 15, 2019

In summary:

[gemwin] test Mojave Sierra
Standard 16.66 fps 19.89 fps
Waving mouse 76.96 fps n/a
Debug mode 19.88 fps n/a
[gemwin 40] test Mojave Sierra
Standard 14.32 fps 40.66 fps
Waving mouse 153.1 fps n/a
Debug mode 40.66 fps n/a

For the test of [gemwin] default:
screen shot 2019-01-15 at 1 15 23 am

Standard window on macOS 10.14.3β Mojave:

print: 61.022
print: 58.872
print: 60.038
print: 61.028

Waving the mouse around with GEM window selected
print: 15.866
print: 15.772
print: 10.317
print: 10.018

GLUT debug mode `on`
print: 49.994
print: 50.059
print: 49.577
print: 51.543

macOS 10.12.6 Sierra

print: 50.349
print: 50.193
print: 48.568
print: 51.956


For the second test: [gemwin 40]

screen shot 2019-01-15 at 1 27 15 am

Standard window on macOS 10.14.3β Mojave:

print: 80.008
print: 60.091
print: 79.989
print: 59.335

Waving mouse around with GEM window selected:

print: 8.036
print: 5.96
print: 4.071
print: 8.064

With GEM window in GLUT debug mode:

print: 25.485
print: 23.646
print: 26.369
print: 25.182

macOS 10.12.6 Sierra

print: 24.181
print: 25.015
print: 24.253
print: 24.921
@umlaeute

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2019

so it's really blocking. :bummer:

@umlaeute

This comment has been minimized.

Copy link
Owner

commented Jan 17, 2019

i did a bit of research, and haven't found anything to fix this programmatically.

for now, i'd suggest to just enable Debug mode in the GLUT preferences and live happy ever after (afaict, the settings are sticky, so you only have to do that once per machine.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.