[FFmpeg-user] documentation in spanish

[juan carlos Rebate]

http://trac.ffmpeg.org/wiki/StreamingGuide Nor it is clear, it does
not explain why use the -y flag, in the second example not explain
anything, just indicates this;

And here is what another person did:

ffmpeg -f dshow -i video="screen-capture-recorder":audio="Stereo Mix
(IDT High Definition" \
-vcodec libx264 -preset ultrafast -tune zerolatency -r 10 -async 1
-acodec libmp3lame -ab 24k -ar 22050 -bsf:v h264_mp4toannexb \
-maxrate 750k -bufsize 3000k -f mpegts udp://192.168.5.215:48550
I understand you're using directx to capture web cam, but does not
explain why, does not explain how each command works either as acts
According to this article it posed this example was published because
someone else wanted, but not explained whether this works or not, or
does not explain the errors that this could cause.
this sort of thing I mean when I say that the documentation is confusing





2016-03-06 19:43 GMT+01:00 juan carlos Rebate <nerus492 at gmail.com>:
> moritz I do not want any front-end, these are often very poor and
> basic, the command line is not complicated, the question is that the
> documentcion is unclear, little concise, should build a clean
> documentaion
>
> 2016-03-06 19:28 GMT+01:00 Moritz Barsnick <barsnick at gmx.net>:
>> On Sun, Mar 06, 2016 at 17:33:22 +0100, juan carlos Rebate wrote:
>>> is not wrong, if you look at the section vera protocols;
>>>
>>> ffmpeg -i somefile.ogg -c copy -listen 1 -f ogg http://server:port
>>> this is to send a local file via http,therefore I would say to convey
>>> the same way
>>>
>>> ffmpeg -i rtp://239.0.0.5:8208 -c copy -listen 1 -f mp4 http://localhost:80
>>
>> Juan Carlos, this is a big misunderstanding, on several sides. Indeed,
>> the example says that, and it doesn't say anything about caveats and
>> restrictions. Yet it is an example regarding HTTP serving, not on the
>> complete chain of actions. (It's an *example*, so I don't even think it
>> should.)
>>
>> The bigger misunderstanding is your deduction that your command line
>> should work. Just as running ffmpeg is complicated and complex, so is
>> the whole topic of multimedia conversion. If you want something to take
>> the complexity and the problems away from you, you will need some sort
>> of front-end which tries its best at that. ffmpeg on the other hand
>> allows you to access almost any detail of the conversion process, and
>> will error out in various scenarios, and most often give good error
>> messages. In your case, it gave a good error message, and it means:
>>
>> Whatever your input (from rtp:// is), it cannot by muxed into the "mp4"
>> format.
>>
>> If you show us the command line and the complete, uncut console output,
>> we can try to help in making your command work, or explain why it can't
>> work. (And not in Spanish, sorry.)
>>
>>> States, the other countries were allowed to dupe the smokescreen of
>>> the United States
>>
>> Sorry about the lack of Spanish documentation. It is hard enough to
>> find people to improve the English documentation. Please do understand
>> that none of this is done professionally, i.e. as a job with a regular
>> pay. Instead almost all of it is volunteer work by extremely committed
>> people. If you can help out or if you know someone who could, you and
>> they are very welcome!
>>
>> Constructive feedback is of course also welcome.
>>
>> By the way, the documentation you are looking at is very much of a
>> reference, not necessarily an introduction. There are other better
>> sources of introduction, like the initial chapters of the docs, or the
>> ffmpeg wiki.
>>
>> Moritz
>> _______________________________________________
>> ffmpeg-user mailing list
>> ffmpeg-user at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user