Fakin The Funk? 6.0.0.162 + Portable + Repack

Так она и умеет делать анализ, тем более на её спектрограмме проставлены пороговые метки, соответствующие реальному битрейту.

Только визуальный анализ спектрограммы.

программа проверяет соответствие спектра битрейту, указанному в тэгах файла и, исходя из этого делает заключение.

FakinTheFunk_4.1.0.146_x86_Portable

Вопрос не в том, что проблем стало меньше. Вопрос в том, зачем ВООБЩЕ видеть проблемы там, где их нет и быть не может.

Мало того, что на тучу MP3 -b320 -q0, сделанных из фирменных флаков посредством LAME 3.100, прога сказала 192-256. Да, мало ей того. Она еще и на вторую часть Mike Oldfield - Tubular Bells сказала 160k, а на первую часть 320k.

Fakin The Funk 6.0.0.164 Portable

Loudness normalization
This version offers the ability to analyze the loudness normalization values (similar to ReplayGain) and will write them to the ReplayGain tags of your files. The audio data is not changed; only Id-tags are written. You will need a player that supports the ReplayGain tags to apply these values.

Fakin‘ The Funk offers this ability; you can (de-)activate it in the settings-dialog, tab [Replay options]. It is called „apply loudness normalization values when playing a file“

It’s not the older ReplayGain algorithm that is used, but the newer „EBU R 128“ one. See https://tech.ebu.ch/docs/tech/tech3343.pdf for details.

You can either activate the option „Calculate loudness after analyzing files“ in the settings dialog. This will run the analysis directly after adding files to your collection.

Or you can use the right-mouse menu „Analyze loudness…“ in the listview to analyze all selected files or in the treeview to analyze all files of the selected folder.

In all cases you have to specify a target loudness in [db].

Even though EBU recommends a target value ob -23, it seems to me that ReplayGain was targeting something like -18 db. It’s up to you; you can easily change this value – but then you will have to reanalyze all files to make the change effective!



Performance on large collections
On large collections, when there are a lot of subfolders, building the treeview can be rather slow. Therefore, the settings dialog offers the option „disable treeview on large results“ in the [Display options] Tab.

If you perform a search e.g. for artists or filenames (see search-tipps at the forum (click here)), the tree will be automatically build properly as soon as there are less than 3,000 folders to show

Note:
This setting is only available when there are at least 5,000 files in your database



Hide treeview
If you don’t need the treeview at all, you can simply disable it in the settings dialog, Tab [Display options]. If disabled, all files will be shown in the Listview. Please also refer to the search tipps at the forum (click here).

This settings was available also in the last version, but internally the tree was still built which resulted in a bad performance on large collections; this is fixed.



Bugfixes
Replacing single files
Replacing single files by drag&drop (see Settings dialog) worked only properly if the file that you dropped onto was also selected. This is fixed; the file you drop onto will now be replaced, regardless which one is selected. In addition, an info-box will show the filename that will be replaced.
Additionally, not only the tags from the source file will be copied, also the embedded images.
320 bps
Under some reare circumstances, 320 kbps mp3 files were reported as 321 kbps. This is fixed.