Re: [FFmpeg-devel] Atempo limits

2018-06-05 Thread Pavel Koshevoy
On Mon, Jun 4, 2018 at 8:54 PM, Pavel Koshevoy  wrote:
> On 06/04/2018 08:35 PM, Ronak Patel wrote:
>>
>> Thanks. Is it okay if I push a patch for this? How high of a limit does
>> the algorithm support today?
>>
>
> I don't think there is an upper limit...  Post a patch here for review.  See
> http://www.ffmpeg.org/developer.html#Submitting-patches-1
>
> Pavel.
>


I've posted a patch myself --
http://ffmpeg.org/pipermail/ffmpeg-devel/2018-June/231004.html
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Atempo limits

2018-06-04 Thread Pavel Koshevoy

On 06/04/2018 08:35 PM, Ronak Patel wrote:

Thanks. Is it okay if I push a patch for this? How high of a limit does the 
algorithm support today?



I don't think there is an upper limit...  Post a patch here for review.  See 
http://www.ffmpeg.org/developer.html#Submitting-patches-1


Pavel.

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Atempo limits

2018-06-04 Thread Ronak Patel
We did consider rubberband, but the audio quality is too poor. The audio has 
echo artifacts in it that makes it sound robotic.

Sent from my iPhone

> On Jun 4, 2018, at 8:32 PM, Lou Logan  wrote:
> 
>> On Mon, Jun 4, 2018, at 10:09 AM, Ronak wrote:
>> 
>> We are looking to use the atempo filter for our audio files. However, 
>> the limit between 0.5 - 2x is too restrictive for us. We would like to 
>> expand the limit to 0.5x - 3x.
> 
> Consider using the rubberband filter instead if atempo is too simple or 
> restrictive.
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Atempo limits

2018-06-04 Thread Ronak Patel
Thanks. Is it okay if I push a patch for this? How high of a limit does the 
algorithm support today?

Sent from my iPhone

> On Jun 4, 2018, at 8:00 PM, Pavel Koshevoy  wrote:
> 
>> On 06/04/2018 12:09 PM, Ronak wrote:
>> Hello,
>> 
>> How are you all?
>> 
>> We are looking to use the atempo filter for our audio files. However, the 
>> limit between 0.5 - 2x is too restrictive for us. We would like to expand 
>> the limit to 0.5x - 3x.
>> 
>> I tried changing the range in atempo.c and the rest of the tempo filter just 
>> worked.
>> 
> 
> Going below 0.5 is likely not going to sound good. Going above 2.0 should be 
> fine.  The reason for current [0.5, 2.0] range is mostly for symmetry. 
> atempo=0.5 followed by atempo=2.0 should sound like original audio.  This 
> should also point you to an alternative solution -- put 2 atempo filters one 
> after another to achieve tempo greater than 2  (atempo=2.0,atempo=1.5), or 
> like this:
> 
> ffmpeg -i /scratch/Music/02\ Feeling\ Good.mp3 -af 
> 'atempo=sqrt(3.0),atempo=sqrt(3.0)' -y /tmp/tempo-3x.wav
> 
>   Pavel.
> 
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Atempo limits

2018-06-04 Thread Lou Logan
On Mon, Jun 4, 2018, at 10:09 AM, Ronak wrote:
>
> We are looking to use the atempo filter for our audio files. However, 
> the limit between 0.5 - 2x is too restrictive for us. We would like to 
> expand the limit to 0.5x - 3x.

Consider using the rubberband filter instead if atempo is too simple or 
restrictive.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel


Re: [FFmpeg-devel] Atempo limits

2018-06-04 Thread Pavel Koshevoy

On 06/04/2018 12:09 PM, Ronak wrote:

Hello,

How are you all?

We are looking to use the atempo filter for our audio files. However, the limit 
between 0.5 - 2x is too restrictive for us. We would like to expand the limit 
to 0.5x - 3x.

I tried changing the range in atempo.c and the rest of the tempo filter just 
worked.



Going below 0.5 is likely not going to sound good. Going above 2.0 should be 
fine.  The reason for current [0.5, 2.0] range is mostly for symmetry. 
atempo=0.5 followed by atempo=2.0 should sound like original audio.  This should 
also point you to an alternative solution -- put 2 atempo filters one after 
another to achieve tempo greater than 2  (atempo=2.0,atempo=1.5), or like this:


ffmpeg -i /scratch/Music/02\ Feeling\ Good.mp3 -af 
'atempo=sqrt(3.0),atempo=sqrt(3.0)' -y /tmp/tempo-3x.wav


  Pavel.

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel