Summary: | media-video/ffmpeg-0.5_p20373: broken ffmpeg default settings detected (x264) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Denilson Sá Maia <denilsonsa> |
Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | polynomial-c |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Denilson Sá Maia
2010-04-09 18:17:28 UTC
I can confirm this bug. Encoding videos in h264 with media-video/dvdrip is broken because of this. I did some testing, and these are the minimum parameters I was required to pass (instead of passing "-vpre default"): -qcomp 0.6 -i_qfactor 0.71 -g 250 -me_range 16 -partitions +parti8x8+parti4x4+partp8x8+partb8x8 Of course, the values don't need to be the same as these. Not sure if this helps to find the source of the problem, though. Also, while using blender and trying to render the output with ffmpeg and H264, I get this message: "Couldn't initialize codec" Using ffmpeg (in blender) with other codec works well. Tested with media-gfx/blender-2.49b. This same blender version used to work well last year (the same time when standalone ffmpeg was working). This check was added to x264 to prevent applications from inadvertently using the (horribly broken) ffmpeg default settings. Unfortunately, after over a year, ffmpeg default settings are still broken due to the lack of codec-specific defaults (it attempts to force a set of defaults designed for its own encoders onto all other encoders, even when it doesn't make any sense). Don't try to get around it by attempting to cheat the heuristic; the only proper solutions are: 1. Insert the correct default settings manually (crappy solution, but it works). or 2. Fix the application to use libx264 directly instead of libavcodec, bypassing the problematic code. or 3. Fix ffmpeg to suck less. Using the FFmpeg profiles to work around this probably is a good idea, it should give you reasonable settings. (In reply to comment #5) > Using the FFmpeg profiles to work around this probably is a good idea, it > should give you reasonable settings. > should be the solution; not a bug ? |