Hi list,
experiencing some weird issues with Gem 0.94.git v0.94 on MacOS 12.4 as well. Upon trying to create a gemwindow I am getting [gemmacoswindow]: unable to switch to current window (do you have one?), cannot render! Seems to be https://github.com/umlaeute/Gem/issues/257 Following some advice to a different, but possibly related error, I replaced [gemmacoswindow] with [gemglfw3window]. This made the window appear and render.
What is the difference between [gemglfw3window] and [gemglutwindow]? In one of the two, the origin of the coordinate system seems to be off in fullscreen more and and contents are rendered smaller, possibly related to https://github.com/umlaeute/Gem/issues/261 in the other one, there is often flickering.
I tried to make Gem output on a second screen (extended desktop) next. When I use the [fullscreen 1] message, th OS will change the resolution of that second display to that of gemwin's "dimen" setting. But whenever I want to edit the patch and focus the patch window, the fullscreen gemwindow on the external display is minimized to the dock, and the resolution of that external display changed back by the OS setting it to as it was before. Makes it impossible to work. Without the fullscreen message, the title bar of the Gem window is always visible.
Can anyone perhaps test and confirm, possibly also explain, this last issue?
Thank you! Peter
On 12/28/21 21:33, Johnny Mauser via Pd-list wrote:
Hi Dana and all,
I upgraded my personal computer to a new arm Mac and can confirm, that Gem is not running properly out of the box. I don’t know whether I made a mistake, or it is the general situation, or what’s going on..
MacOS 12.1 Pd 52.1, Gem 0.94
Trying to create a Gem window leads to console showing: "[gemmacoswindow]: failed to init GLEW: your system only supports openGL-1.0“
that's https://github.com/umlaeute/Gem/issues/257 et al.
the solution is to replace the [gemmacoswindow] within the gemdefaultwindow.pd abstraction (which is used within [gemwin]) with [gemglfw3window] (or [gemglutwindow]).
When I open the backendinfo window from the help-patch of pix_video the [AVF-videoplugin $0] object could not be created. AVF-videoplugin
that's a separate (minor) issue, that just indicates that there's a lack of documentation for the AVF backend of [pix_video]. it doesn't indicate any malfunctioninig of [pix_video] per se (it doesn't indicate the opposite either; it is just orthogonal)
gfdmsy IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list