py file and adding these two lines just underneath from _future_ import. If you're having trouble with "couldn't share context", consider opening up your. This fixed my "Couldn't share context" error. STOPPED, FINISHED, PRESSED, RELEASED, FOREVER) Pyglet.options=False # script continues as normalįrom psychopy import locale_setup, sound, gui, visual, core, data, event, loggingįrom nstants import (NOT_STARTED, STARTED, PLAYING, PAUSED, # Trying to fix pyglet 'shared environment' error py file with notepad / wordpad / coder view / code writer and added two lines to the top of the script (here in bold):įrom _future_ import absolute_import, division I used PyschoPy's Builder View to compile the task. This error was resolved by specifying an option for pyglet. Updating my drivers didn't fix the problem, perhaps in part because the hardware is kind of old. I don't know anything about Python, so I hope these are helpful to the equally clueless.Īpparently this can be an issue with graphics drivers on some machines. Here for posterity are the two major bugs I'd encountered and how they were resolved. I spent a lot of time wrangling with these errors, and I experienced a lot of stress wondering whether I'd fix them in five minutes or five months. In this process, I ran into a couple of bugs on these machines that I hadn't encountered while developing the tasks on my Win10 Dell Optiplex 7050s. I'm reluctant to try to upgrade them since, as shared computers, other members of the department have stuff running on them that I'm sure they don't want to set up all over again. Those cubicles are equipped with Dell Optiplex 960s running Windows 7. My department has a shared research suite of cubicles. I thought I'd try making the jump to PsychoPy as a way to make my materials more shareable, since not everybody will have a $750+ E-Prime or DirectRT license or whatever. Similarly I’ve tried using and without any success.I'm a new assistant professor trying to set up my research laboratory. Below are some of the more common problems and their workarounds, as well as advice on how to get further help. However, this recreates the problem of “pyo server not created” which I struggled with for some time. have contributed either bug reports and/or fixes. I have seen the same problem here on the forum, and the solution suggested is to change the audio library from to. So it isn’t exactly a fix that works for me. However, this means that the microphone doesn’t record. The only “fix” I’ve found is to not set a duration for the mic. That is, it records when it is supposed to and stores it. Important to note is that the microphone component otherwise seems to be working fine under these conditions. I had someone else run it on their computer (Win 10), and the same problem occurred. It always occurs in the transition from the loop which uses the mic to the following loop that doesn’t, and it occurs almost every time I run it. I.e., as soon as I put a duration (3 sec) for my mic component, this error message started popping up. The error started occurring after I activated my microphone. Standard Standalone? (y/n) If not then what?: YĪt most run-throughs (though not all), I get the uninformative error message “Python has stopped working”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |