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

add self._move.close()to MovieStim3._uload, #1917

Merged
merged 1 commit into from Jul 30, 2018
Merged

add self._move.close()to MovieStim3._uload, #1917

merged 1 commit into from Jul 30, 2018

Conversation

tjwilli58
Copy link
Contributor

@tjwilli58 tjwilli58 commented Jul 29, 2018

add self._mov.close() to MovieStim3._uload, move self._unload() in MovieStim3.stop after logging code.

Calling self._mov.close() seems to prevent invalid handle error in call to
ffmpeg_reader in moviepy module.

See
https://stackoverflow.com/questions/43966523/getting-oserror-winerror-6-the-handle-is-invalid-in-videofileclip-function

…vieStim3.stop after logging code.

Calling self._move.close() seems to prevent invalid handle error in call to
ffmpeg_reader in moviepy module.

See
https://stackoverflow.com/questions/43966523/getting-oserror-winerror-6-the-handle-is-invalid-in-videofileclip-function
@peircej
Copy link
Member

peircej commented Jul 30, 2018

Thanks. For future commit messages (the pull request text doen'st matter) could you try and make sure you follow the information here regarding BF, FF...
In your case the commit should have been BF: to indicate that this commit would need copying to other (release) branches as a fixed bug. Thanks.

PS I don't think the reordering aspects are probably important but well done for tracking down the _move.close() call :-)

@tjwilli58
Copy link
Contributor Author

Sorry about that. I was intending to, but after reading through the github tutorial, creating a fork, and getting to the point where I actually could make a pull request, I simply forgot. (My first PR)

@tjwilli58 tjwilli58 deleted the fix-movie3 branch July 31, 2018 01:23
@peircej
Copy link
Member

peircej commented Jul 31, 2018

No worries. Thanks for the PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants