-
Notifications
You must be signed in to change notification settings - Fork 97
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
WIP: adapt Brain.save_movie() API for imageio #155
Conversation
Codec to use with ffmpeg (default 'mpeg4'). | ||
bitrate : str | float | ||
Bitrate to use to encode movie. Can be specified as number (e.g. | ||
64000) or string (e.g. '64k'). Default value is 1M |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add kwargs to the docstring
1fc180b
to
fb5c56d
Compare
Updated. Keeping the specific keywords open would have the big advantage that additional imageio formats would become available, such as *.gif |
bitrate : str | float | ||
Bitrate to use to encode movie. Can be specified as number (e.g. | ||
64000) or string (e.g. '64k'). Default value is 1M | ||
additional keywords : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why additional keywords and not **kwargs :
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fine with me :)
ready to merge? |
If you're happy with the documentation |
ok next time set the PR to MRG so I don't have to ask :) |
Ok, sorry :) |
Following up on #154
imageio
parameters: http://imageio.readthedocs.io/en/latest/format_ffmpeg.html#parameters-for-savingProbably the most sense would make to provide access to all of
imageio
's options. I've saved a couple of movies andimageio
seems to have sensible defaults (variable bitrate, hence I removed our fixed bitrate default). We could keep the existing keyword arguments so we don't break code that used positional arguments. Are there better alternatives? I am not sure how to document in case we just include a**kwargs
in the signature. Should the documentation just include a link toimageio
's documentation?