So this is mostly just a bug report, not request for help, but if anyone has guidance on messages I can watch for in Console to give more insight into what’s going on, it would be appreciated. My solution for now is to just not call Screen(‘CloseMovie’), which leaves all of the RAM used by the end of the experiment (I play 9 clips totalling about 30 minutes), but at least avoids crashes.
Unfortunately, this is for an fMRI study, and I really can’t change my setup at this point.
I’ve searched through as much of the documentation/help forum as I could find, and my guess is that the answer is basically here… that is, I’m pairing a buggy OS with an unsupported GPU. When I try digging through Console at the time of the hang, nothing jumps out, but I also don’t know what to look for. For 2) in particular, the command line will still display what is being typed, but ctrl-c doesn’t have any effect, and script/function names aren’t interpreted-for instance, typing ‘sca’ and hitting return only has the effect of having ‘sca’ followed by a new line appear in the command window. There are no errors or warnings printed to the Matlab console (and wrapping the call in a try/catch doesn’t change anything), and I don’t get any other indicators (spinning beachball of death), but 1) the next line of code (flipping a blank screen) never runs, and 2) Matlab stops interpreting keyboard input. mov files, but not all, that I’m playing using PsychToolbox, the command Screen(‘CloseMovie’) causes Matlab to hang indefinitely.
Matlab for mac os catalina pro#
Hardware: MacBook Pro (16-inch, 2019) 2.6 GHz 6-Core Intel Core i7 16 GB 2667 MHz DDR4 AMD Radeon Pro 5300M 4 GB + Intel UHD Graphics 630 1536 MBįor certain. Here are the details of my particular setup:
0 kommentar(er)
