Try applying a slight negative amplification in a program like Audacity. You will see that the previously clipped peaks are actually not clipped, they were simply floating point values above 0.000, and programs such as Audacity show that as clipping.I learned something today.
On the other hand, sometimes clipping is just clipping.
"Hotel California" from HDTracks after -3dB amplification
Anyway OP, it's nothing worth worrying about.
Last post by probedb -
dbPoweramp also have their own forum, might get a quicker answer?
Ah, so it decides the blank path is a relative path and expands it out to the foobar2000 installation directory. I'm sure the behaviour could be improved in a few places.
Just out of curiosity. Did you try to play the distorted track on Windows 10? If that plays fine, we can assume that the file is fine, and that either the soundcard or the audio settings on that win XP are set in a way that is prone to make distortions.Yes I did it and the file sounds as bad as in Win10.
I didn't ask before but, do you have a control panel on the taskbar related to the audio settings?? Realtek, soundblaster, cmedia... Some of them had "enchancers" and other settings that could be additionally boosting the audio, causing the distortion.All these enhancing settings are disabled. When Winamp creates the WAV file it "plays" quickly the original file, you can hear nothing. It seems a kind of internal process and Winamp uses only its own things, I don't think it uses features of soundcard. In WinXP DFX installs a plugin in Winamp but in Win10 DFX seems a kind of "audio driver" or similar. That's why I need old WinXP to create the files. Of course, after creating WAV+DFX I have to disable DFX when playing that file.
I have found this in DFX support page: If you are hearing distortion, or your overall sound level is too low, at some point in your system, a gain stage is set incorrectly. It's probably not a problem in your Internet audio player or DFX, but an adjustment you need to make. The only thing I can do regarding this is to decrease Winamp Pre-amp button before creating a WAV+DFX file, but every original WAV file has its own level, so I will go crazy doing this.
Also, I'm wondering why WavGain shows -9.68dB and -11.28dB and Audacity shows no clipping. Why am I hearing distortion? What kind of distorion is this?
DFX has a small built-in graphical spectrum analyzer. In WinXP its bars shows much higher levels than in Win10 for the same file. I will post some screenshots later since I'm not in my computer now.
Also, I wonder if the distortion is different if you try to listen with some headphones connected to the line out.I think the distortion is not related to headphones, amplifier, etc. I have played the file in other audio systems and could hear the same distorion.
I am fairly sure that the the frontend's so-called verify option does nothing to verify whether new audio equals old audio. Because I could use FLAC itself to tell that the MD5s fail to match.
And that is an issue with the frontend; if FLAC fails (for example due to full drive), then the front-end does nothing to check it.
Anyway, I have no sourceforge account, but I replied where the developer announced the front-end, so I assume that no-one responsible is interested.
Try applying a slight negative amplification in a program like Audacity. You will see that the previously clipped peaks are actually not clipped, they were simply floating point values above 0.000, and programs such as Audacity show that as clipping.
Standards-compliant MP3 decoders will handle these values correctly, hence there is no clipping on playback. You don't have to make any changes to the files.
We've covered the same subject in an earlier thread: https://hydrogenaud.io/index.php/topic,113646/topicseen.html
Just to mention it, the FLAC frontend is not safe. It has been eating some of my files, even with the verify option
Good to know! Thanks!
...even though this particular problem would not effect me, since I never use the source folder/file(s) as the destination folder/file(s) to be safe.
And I doubt that it's a problem caused by FLAC Frontend. It's more likely that it's a bug of libFLAC itself, because the frontend doesn't encode anything. It's only a GUI for libFLAC.
Thus, I'm pretty sure that you could cause the same effect with CUEtools using libFLAC with the -f (force overwrite) parameter.
Nevertheless I'have to admit that FLAC Frontend isn't very stable on Windows PCs. It crashes always during the seconds operation.
After closing the cmd-window of the first operation you won't be able to complete a second operation successfully.
Maybe you should file a bug report here:
/usr/bin/rec WARN formats: mp3 can't encode to 32-bitMP3 doesn't use a bit depth, it simply tries to pack everything as efficient as possible.
Is the popping in the audio (in the file) or is it a artifact of the playback chain?
I've been getting the error "bass.dll is missing" every time I start TAC. I close the error twice, and TAC force closes. If I open TAC again, it opens fine. I'm on Windows 10. I've completely uninstalled TAC and reinstalled it and still this problem. Anyone else or any ideas?hi
i have the same issue but only under w10 , under w7 runs without error
i have the portable installation , i tried to run as administrator under w10 and i don't get errors
i run version 0.9.9 built 3899 i guess it's the last
hope it could help you