Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
pix_film does not re-send still frames for subsequent pix_ objects. #172
When loading a video file into pix_film and selecting a certain frame to display, modifications to [pix_invert] or [pix_contrast] will produce strange results unless the still frame is addressed again with a message into [pix_film's] right inlet. [pix_film]'s behavior displaying still frames should equal that of [pix_image]. See attached example patch.
* umläute <firstname.lastname@example.org> [2017-11-20 14:21]:
this is actually a feature. see `[pix_buf]`'s help for a bit of explanation.
Thank you! Are you referring to the sentence "All images use a pull system, so as long as nothing is modified in the pix "upstream", the pix_buf is still valid."? Is this the reason subsequent pix transformations do not work?
however, it should behave consistently with `[pix_image]`.
it's easy to reproduce. the cause is known. a solution is not hard to implement.
but as the sf bug report says, it's unclear what the proper solution to the problem is.
the reason why it is not solved yet is simply performance.
now, pix-based effects are becoming less and less important, as for any serious stuff you probably want to use a GPU shader anyhow - making any automatic copy even more useless.