volume detect

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

volume detect

juan carlos rebate
hello moritz, sorry for taking a long time to answer, I have not had
time to do it, I write to comment that the command you mention does not
work, says -filter: v "volumedetect" invalid argument, this command is
not the only one that has stopped work since version 4.0 has been
released, the worst is that the documentation does not indicate it as
obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
server ffserver 3, it could not be done either, since it would indicate
to me an invalid argument, for example, if I wanted to broadcast a
pre-recorded source:

ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument

but the documentation keeps saying that this can be done in that way,
although it is not true since version 4 of ffmpeg, I have already found
4 things that do not work as they should in version 4

_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

Carl Eugen Hoyos-2
2019-01-30 21:39 GMT+01:00, juan carlos <[hidden email]>:

> hello moritz, sorry for taking a long time to answer, I have not had
> time to do it, I write to comment that the command you mention does not
> work, says -filter: v "volumedetect" invalid argument, this command is
> not the only one that has stopped work since version 4.0 has been
> released, the worst is that the documentation does not indicate it as
> obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
> server ffserver 3, it could not be done either, since it would indicate
> to me an invalid argument, for example, if I wanted to broadcast a
> pre-recorded source:
>
> ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument

The ffm format does not exist anymore because ffserver was
removed (the format was only relevant for ffserver).
This is not related to the volumedetect filter.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

juan carlos rebate


El 30/01/19 a las 20:51, Carl Eugen Hoyos escribió:

> 2019-01-30 21:39 GMT+01:00, juan carlos <[hidden email]>:
>> hello moritz, sorry for taking a long time to answer, I have not had
>> time to do it, I write to comment that the command you mention does not
>> work, says -filter: v "volumedetect" invalid argument, this command is
>> not the only one that has stopped work since version 4.0 has been
>> released, the worst is that the documentation does not indicate it as
>> obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
>> server ffserver 3, it could not be done either, since it would indicate
>> to me an invalid argument, for example, if I wanted to broadcast a
>> pre-recorded source:
>>
>> ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument
> The ffm format does not exist anymore because ffserver was
> removed (the format was only relevant for ffserver).
> This is not related to the volumedetect filter.
>
> Carl Eugen
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".

Yes, I know that ffserver disappeared, but backward compatibility should
follow, right?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

Carl Eugen Hoyos-2
2019-01-30 22:11 GMT+01:00, juan carlos <[hidden email]>:

>
>
> El 30/01/19 a las 20:51, Carl Eugen Hoyos escribió:
>> 2019-01-30 21:39 GMT+01:00, juan carlos <[hidden email]>:
>>> hello moritz, sorry for taking a long time to answer, I have not had
>>> time to do it, I write to comment that the command you mention does not
>>> work, says -filter: v "volumedetect" invalid argument, this command is
>>> not the only one that has stopped work since version 4.0 has been
>>> released, the worst is that the documentation does not indicate it as
>>> obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
>>> server ffserver 3, it could not be done either, since it would indicate
>>> to me an invalid argument, for example, if I wanted to broadcast a
>>> pre-recorded source:
>>>
>>> ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument
>> The ffm format does not exist anymore because ffserver was
>> removed (the format was only relevant for ffserver).
>> This is not related to the volumedetect filter.

> Yes, I know that ffserver disappeared, but backward compatibility
> should follow, right?

Unfortunately not.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

juan carlos rebate


El 30/01/19 a las 21:24, Carl Eugen Hoyos escribió:

> 2019-01-30 22:11 GMT+01:00, juan carlos <[hidden email]>:
>>
>> El 30/01/19 a las 20:51, Carl Eugen Hoyos escribió:
>>> 2019-01-30 21:39 GMT+01:00, juan carlos <[hidden email]>:
>>>> hello moritz, sorry for taking a long time to answer, I have not had
>>>> time to do it, I write to comment that the command you mention does not
>>>> work, says -filter: v "volumedetect" invalid argument, this command is
>>>> not the only one that has stopped work since version 4.0 has been
>>>> released, the worst is that the documentation does not indicate it as
>>>> obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
>>>> server ffserver 3, it could not be done either, since it would indicate
>>>> to me an invalid argument, for example, if I wanted to broadcast a
>>>> pre-recorded source:
>>>>
>>>> ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument
>>> The ffm format does not exist anymore because ffserver was
>>> removed (the format was only relevant for ffserver).
>>> This is not related to the volumedetect filter.
>> Yes, I know that ffserver disappeared, but backward compatibility
>> should follow, right?
> Unfortunately not.
>
> Carl Eugen
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".
well, if there is no backwards compatibility, the documentation
referring to obsolete options should also disappear.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

Carl Eugen Hoyos-2
2019-01-31 1:03 GMT+01:00, juan carlos <[hidden email]>:

>
>
> El 30/01/19 a las 21:24, Carl Eugen Hoyos escribió:
>> 2019-01-30 22:11 GMT+01:00, juan carlos <[hidden email]>:
>>>
>>> El 30/01/19 a las 20:51, Carl Eugen Hoyos escribió:
>>>> 2019-01-30 21:39 GMT+01:00, juan carlos <[hidden email]>:
>>>>> hello moritz, sorry for taking a long time to answer, I have not had
>>>>> time to do it, I write to comment that the command you mention does not
>>>>> work, says -filter: v "volumedetect" invalid argument, this command is
>>>>> not the only one that has stopped work since version 4.0 has been
>>>>> released, the worst is that the documentation does not indicate it as
>>>>> obsolete. for example, if I wanted to transmit using ffmpeg 4.1 to a
>>>>> server ffserver 3, it could not be done either, since it would indicate
>>>>> to me an invalid argument, for example, if I wanted to broadcast a
>>>>> pre-recorded source:
>>>>>
>>>>> ffmpeg -imput.mp4 http://ip:8090/feed1.ffm say invalid argument
>>>> The ffm format does not exist anymore because ffserver was
>>>> removed (the format was only relevant for ffserver).
>>>> This is not related to the volumedetect filter.
>>> Yes, I know that ffserver disappeared, but backward compatibility
>>> should follow, right?
>> Unfortunately not.

> well, if there is no backwards compatibility, the documentation
> referring to obsolete options should also disappear.

Didn't it?

Please cut the mailing list footer when replying, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: volume detect

Carl Zwanzig
On 1/30/2019 4:08 PM, Carl Eugen Hoyos wrote:

>> well, if there is no backwards compatibility, the documentation
>> referring to obsolete options should also disappear.
> Didn't it?

Having just checked, ffm is not listed in the formats page
(https://ffmpeg.org/ffmpeg-formats.html).


OTOH, the ffserver doc page itself doesn't say that the program has been
removed (https://www.ffmpeg.org/ffserver.html), nor does the main doc page
(https://www.ffmpeg.org/documentation.html). ffm also appears in the
ffserver sample config page, which google finds quite easily.

The removal is mentioned part way down the main page under April 20, 2018
and on the wiki page (https://trac.ffmpeg.org/wiki/ffserver).

This might be considered an incomplete job of removing ffserver as searches
will still find it and it's options. Adding a few more "no longer available"
messages to the various doc pages should take care of that. (I'd offer to
add them, but have no idea how or where.)

Later,

z!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".