weird results when checking ape files

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

weird results when checking ape files

joshd
I've started using FTF to check some lossless audio files (flac and ape) but I've gotten some very odd results i can't figure out. It seems to happen only with ape files, while flac seems to read normal.
Very often with ape files the program will say the file is "OK", but the readout will display a *negative* bitrate and an "Actual bitrate" of 320, which is a lossy (mp3) bitrate. (see pic)
But the message says the file is "OK" (not fake) and when i check the spectrum analysis it looks lossless to me (no obvious cutoffs). So why is it producing these weird results and what do they mean? Thanks for any help you can provide.
Reply | Threaded
Open this post in threaded view
|

Re: weird results when checking ape files

Fake No Funk
Administrator
That sounds strange, indeed :) could you e-mail such a file to me?
Please email to "info <at> fakinthefunk <dot> net"
Reply | Threaded
Open this post in threaded view
|

Re: weird results when checking ape files

joshd
the ones i have are too big to email. they're mostly cd-length single files. i can try to find some separate tracks that do the same thing but don't have any small ones handy. Here's some pics of another file i just checked, different than the last one but similar result. It says "Everything Looks Fine!" but outputs this weird negative bitrate/320 result almost all the time with .ape files. No problem with flac. And again the spectrum looks ok (lossless) to me.

I'm on OS High Sierra if that helps at all, just dl'd the latest version of FTF for Mac a couple days ago.

Anyway, here's the pics:



Reply | Threaded
Open this post in threaded view
|

Re: weird results when checking ape files

Fake No Funk
Administrator
Thanks, but I'd need a sample file to debug the code :-) therefore I asked to send me such a file via mail...