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

pix_film: Ambiguous rightmost outlet bangs randomly on Win10. #161

Open
musger opened this Issue Nov 15, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@musger

musger commented Nov 15, 2017

Loading somefile.avi into [pix_film] on Win10 and playing back via [auto 1< will output bangs at the right outlet before the file end is reached. The help patch decribes these as possibly being an "illegal frame" being decoded. Nevertheless playback does not stop. This makes it very hard to differentiate a bang issued when the end of the file is reached from a bang because there has been an "illegal" frame and will not allow any subsequent message logic making use of that outlet.
The file is attached in zipped format as github does not allow .avi

somefile.zip

@umlaeute umlaeute added the bug label Nov 16, 2017

@umlaeute umlaeute added help wanted and removed help wanted labels Dec 5, 2017

@umlaeute

This comment has been minimized.

Owner

umlaeute commented Dec 5, 2017

given that this is backend-specific, we'd need to know which backend you were actually using to play back the film?

@umlaeute umlaeute referenced this issue Dec 5, 2017

Open

make filmDS consistent #180

0 of 7 tasks complete
@musger

This comment has been minimized.

musger commented Dec 19, 2017

How do I find out which backend I am using? Upon loading my videofile into pix_video Pd/Gem prints on the console:
[pix_film]: DirectShow support
[pix_film]: QuickTime support
Image loading support: QT SGI jpeg tiff
GEM: GLEW version 1.5.4
GEM: Start rendering
[pix_film]: opening C:/vid/somefile.avi with format 1908
[pix_film]: loaded file: C:/vid/somefile.avi with 464 frames (320x240) at -1.000000 fps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment