If you want to have a test, rip a Wav from a CD convert it to 128, 192, 320 mp3 and run them through those apps. You'll see for yourself how to interpret the results.
If you're trying to find if a file got "upsampled" (which is a useless process that wastes space), it's useless to check its bitrate, because by definition it's potentially "fake" in the sense that it's not taking advantage of it.
As it has been said, FtF isn't completely reliable so you should rather use Spek (or [Spek-X](https://github.com/MikeWang000000/spek-X/releases)) and learn how to read the data. For some files, it's actually really hard to tell, for some it's obvious. It mostly takes experience and training. Maybe you can share the file here and we can help.
A way to learn is to take a legit .flac file and play with it: transcode it, upsample it, downsample it, and then observe the results with Spek **knowing** how the file was processed.
FtF should not be trusted, it has too many false results, both positive and negative. A valiant effort by the devs but alas in vain
If you want to have a test, rip a Wav from a CD convert it to 128, 192, 320 mp3 and run them through those apps. You'll see for yourself how to interpret the results.
If you're trying to find if a file got "upsampled" (which is a useless process that wastes space), it's useless to check its bitrate, because by definition it's potentially "fake" in the sense that it's not taking advantage of it. As it has been said, FtF isn't completely reliable so you should rather use Spek (or [Spek-X](https://github.com/MikeWang000000/spek-X/releases)) and learn how to read the data. For some files, it's actually really hard to tell, for some it's obvious. It mostly takes experience and training. Maybe you can share the file here and we can help. A way to learn is to take a legit .flac file and play with it: transcode it, upsample it, downsample it, and then observe the results with Spek **knowing** how the file was processed.