Does it make sense to have this setting as well?
Or even a manual setting possible?
The Videofilter "resample fps" allows to enter a manual value or even recognizes (real) 30 fps (screen capture) and chooses to put in that custom value, not 29,97. Is this possible with the audio filter?
Quote from: Mick on August 03, 2022, 07:24:56 AMDoes it make sense to have this setting as well?
In general, an ability to pass an exact rational instead of a floating point value (with a very high precision, but still) to the time stretching filter would be nice, IMHO. But contrary to pal2film and film2palm converters there is little demand in this functionality.
"resampleFps" and time stretching audio filters have very different use cases. The natural companion of time stretching audio filters is the "changeFps" filter. I wonder what may be the reason to slow down the audio track of a screen capture.
How would you prepare recordings made with 29,97 or 30 fps that you would like to include into a 23,976 or 24fps timeline with according sound?
Just use "resampleFps", no need to touch the audio track.
If you really want to slow down the video but keep each and every picture, then you would need to use the "changeFps" filter AND modify the speed of the audio track by newFps / oldFps = 24000 * 1000 / (30000 * 1001) = approx. 0.799200799 in case of 30 fps to film conversion.
How to modify that audio from your example in Avidemux?
Select an audio encoder (i.e. not copy) of your choice, open audio filter configuration dialog for the audio track you want to manipulate, select "Custom" for "Frame rate change" and input 0.799299799 into the "Tempo multiplier" spinbox. You need a recent Avidemux build for that, so please use the latest nightly.
Please note that digits from the 8th position on are not retained, this is a known bug.
I updated to 220802 and see what you mean. Nice improvement with the audio filter page! Thank you.
Quote from: eumagga0x2a on August 04, 2022, 08:13:43 PMPlease note that digits from the 8th position on are not retained, this is a known bug.
Should be fixed (https://github.com/mean00/avidemux2/commit/1420534016c0a39106f799fc6c55b21f723d91a6) on git master now. It may happen that one or two rounds of future nightlies will be built not off the git master but from a different branch, created to facilitate testing of a possible replacement for RubberBand library. In this case this fix will be present in later nightlies.
Quote from: Mick on August 04, 2022, 10:32:01 PMNice improvement with the audio filter page! Thank you.
All kudos for this feature go to szlldm.