-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Specifying pix_fmt on FFMPEG call #27
Comments
Thanks for this. What you describe seems to be what user @chunder made in a branch just a few days ago: Do you confirm that this is what you want ? Or do you think it would be a better idea to make it an option ? I asked the user for a merge request. |
This should work for me. I will test it soon. On Fri, Mar 28, 2014 at 12:14 PM, Zulko notifications@github.com wrote:
|
Ya, I added this because my libx264 mp4s were not displaying on a couple of browsers (Chrome and IE I think). I found this ffmpeg ticket that is considering making yuv420p the default for libx264, since most players expect that. http://trac.ffmpeg.org/ticket/658 I'll turn it into a pull request shortly. |
Any word on this? Would be immediately useful to myself and my labmates. |
Aw, sorry we didn't come back to you. Here is an update. Now the export of .mp4 videos is yuv240p (almost always) by default in Now for the details. A few days ago @chunder merged a pull request that makes yuv420p the default for all video written with the libx264 codec (that is, the default codec every time you export to mp4). I have plans to change
The advantage being that you can process the |
Thanks for the update. I construct my movies like so --
Will this take advantage of the new codepaths? |
I'll keep you posted.
|
I probably don't need the to_RGB, and checking some other code I wrote, I mp.fromarray(images,fps=30.0).to_videofile('/path/to/my/movie.mp4') That would be a PIL-like syntax that would be *incredibly *convenient. On Mon, Apr 7, 2014 at 1:50 PM, Zulko notifications@github.com wrote:
|
That is where I am going:
,fps=30.0).to_videofile('movie.mp4') While we are at it, if you have a better idea for the class name... What I meant in the previous clip is that I expected that people from https://www.youtube.com/watch?v=fT_n61iXQiE
|
I started using moviepy because I can composite by hand in PIL or ndimage, Why don't you just use On Mon, Apr 7, 2014 at 2:07 PM, Zulko notifications@github.com wrote:
|
Something I forgot to mention: if you generate all the numpy frames in
Here any newbie can tell me that these objects are instances of the |
I'm closing this thread (unless you still have unresolved issues ?). Thanks for the feedback ! |
This works perfectly for me now. On Thu, Jun 19, 2014 at 3:22 PM, Zulko notifications@github.com wrote:
|
The newer versions of FFMPEG default to a pixel format which is incompatible with Apple's Quicktime player. It would be convenient to offer the option to specify the pixel format, i.e. to add the flag
-pix_fmt yuv420p
to the ffmpeg call in ffmpeg_tools.py:ffmpeg_movie_from_frames.
There is a note that
ffmpeg_movie_from_frames
is almost deprecated. I can add the option, and propagate the keyword argument up toto_videofile
and issue a pull request, but is this the most appropriate place to add the change?The text was updated successfully, but these errors were encountered: