Am 02.07.2010 17:50, schrieb jida...@jidanni.org:
So they spread the word forget ffmpeg.
There is a reason for everything and there is even documentation for
(nearly) everything. People who keep themselves informed should know
about both and not render premature justice.
So that's why
OK, but still maybe the package Description shouldn't be as upbeat as it
currently is.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
Am 05.07.2010 13:35, schrieb jida...@jidanni.org:
Just say This version of ffmpeg is NOT compiled against ...
or This package differs from the default compilation in that ...
There is no such thing like a default compilation but anyway, the
package descriptions could be improved to reflect
On Mon, Jul 05, 2010 at 08:14:26 (EDT), Fabian Greffrath wrote:
Am 05.07.2010 13:35, schrieb jida...@jidanni.org:
Just say This version of ffmpeg is NOT compiled against ...
or This package differs from the default compilation in that ...
There is no such thing like a default compilation
Having said this, I do think that the description could and probably
should be improved.
Word.
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
[Dammit, this didn't go to the bug and submitter by accident.]
Am 02.07.2010 15:34, schrieb jida...@jidanni.org:
The reason may be documented in /usr/share/doc/ffmpeg/README.Debian.gz
but it is very hard to tell.
I fail to see what is difficult to understand in this sentence from
Am 02.07.2010 15:59, schrieb Fabian Greffrath:
However, I agree that the error message
Encoder (codec id 86017) not found for output stream #0.0
should be improved to at least call the encoder by name.
Which will be done by the attached patch. Would you please try it out?
- Fabian
diff
All I know is it seems to the average user that ffmpeg can't even make
.mp3s, a rather common format.
So they spread the word forget ffmpeg.
So that's why your patch should at least say
***Probable causes:...
There's only a small chance that the user will be nurd enough to dig
out the README
