FFAStrans 1.4.0.1 Loudness Analyzer Issue
FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hello,
I have been testing the latest version of FFAStrans and have been facing an issue with the Loudness Analyzer. I am analyzing the loudness of dual mono tracks and then determining the loudness level of each individual track. However, it is only returning the level of one track and is unable to read the second track.
Below is the return value of the loudness analyzer on version 1.3.1. This is how it should appear. Below is the return value of the loudness analyzer on version 1.4.0.1. As shown above, the 1.4.0.1 version only returns the loudness level of track one, instead of both tracks. The input file and workflow were exactly the same when tested on both versions.
I also attempted to analyze each track with separate loudness analyzers but it seems that FFAStrans would still return a null value for track 2.
I have attached some screenshots of the logs and a mediainfo of an example source file.
Is anyone familiar with this issue and have any ideas of a fix/workaround?
I have been testing the latest version of FFAStrans and have been facing an issue with the Loudness Analyzer. I am analyzing the loudness of dual mono tracks and then determining the loudness level of each individual track. However, it is only returning the level of one track and is unable to read the second track.
Below is the return value of the loudness analyzer on version 1.3.1. This is how it should appear. Below is the return value of the loudness analyzer on version 1.4.0.1. As shown above, the 1.4.0.1 version only returns the loudness level of track one, instead of both tracks. The input file and workflow were exactly the same when tested on both versions.
I also attempted to analyze each track with separate loudness analyzers but it seems that FFAStrans would still return a null value for track 2.
I have attached some screenshots of the logs and a mediainfo of an example source file.
Is anyone familiar with this issue and have any ideas of a fix/workaround?
- Attachments
-
- SourceFileMediainfo.txt
- (5.29 KiB) Downloaded 269 times
-
- LoudnessAnalysisFullLog_V1.4.0.1.png (259.97 KiB) Viewed 7021 times
-
- LoudnessAnalysisExtra_V1.4.0.1.png (233.36 KiB) Viewed 7021 times
-
- AudioTracksLog2_V1.4.0.1.png (236.97 KiB) Viewed 7021 times
-
- Nodes.png (59.74 KiB) Viewed 7021 times
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hey Warran,
thanks for the exhaustive error description. I played a little around and also saw that there seems to be something fishy with the whole loudness analyzer trackmapping. Unfortunately i am not yet sure what exactly goes wrong so i cannot yet suggest a workaround. Anyway it is very possible that IF you want to workaround instead of waiting for a fix, you can probably come away with something like extracting the first 2 audio channels to wav
thanks for the exhaustive error description. I played a little around and also saw that there seems to be something fishy with the whole loudness analyzer trackmapping. Unfortunately i am not yet sure what exactly goes wrong so i cannot yet suggest a workaround. Anyway it is very possible that IF you want to workaround instead of waiting for a fix, you can probably come away with something like extracting the first 2 audio channels to wav
emcodem, wrapping since 2009 you got the rhyme?
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hello,
I'v got the same issue in our setup unfortunatly.
Our workaround was firstly to set "Discrete tracks" param to "Same as source" and it was fixed for stereo input but of course this is not the best for dual mono. In our workflow we handle stereo as independent channels therefore it is important for us also.
Another workaround could be Command executor processor with ffmpeg audio manipulation script (https://trac.ffmpeg.org/wiki/AudioVolume) using loudnorm variables in workflow (as we did before using this marvelous Task automation Engine).
Finally we've rolled back to 1.3.0.2 as it most stable for us.
I'v got the same issue in our setup unfortunatly.
Our workaround was firstly to set "Discrete tracks" param to "Same as source" and it was fixed for stereo input but of course this is not the best for dual mono. In our workflow we handle stereo as independent channels therefore it is important for us also.
Another workaround could be Command executor processor with ffmpeg audio manipulation script (https://trac.ffmpeg.org/wiki/AudioVolume) using loudnorm variables in workflow (as we did before using this marvelous Task automation Engine).
Finally we've rolled back to 1.3.0.2 as it most stable for us.
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hello,
v1.4.0.3 build did not fix the issue unfortunately.
v1.4.0.3 build did not fix the issue unfortunately.
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Yeah sorry, it is because i forgot to notify @admin, my bad... sorry.
emcodem, wrapping since 2009 you got the rhyme?
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Should be fixed in the newest 1.4.0.4
emcodem, wrapping since 2009 you got the rhyme?
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
No worries but the thanks goes to @admin (if it was fixed)
emcodem, wrapping since 2009 you got the rhyme?
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hi Emcodem,
Did have a try with "Discrete tracks" set on "Source channels to tracks" and "Set real peaks to" to %my_sound_var%. Different loudness still when get mp4 file with stereo aac and convert to mxf xdcam. Only first track get loudness from variable...
Re: FFAStrans 1.4.0.1 Loudness Analyzer Issue
Hm so for standard R128 loudness correction, you would select "Set levels to" %my_sournd_var% instead of the real_peaks, maybe thats your issue?
emcodem, wrapping since 2009 you got the rhyme?