Skip to main content

Recent Posts

1
A very horrible thing with float 32 file is they can be encoded in different "normalized" fashions. If the decoder misinterpret the format, the result will be horrible full scale square wave-ish like crap which may destroy your equipment. I experienced this nightmare several times, sometimes in foobar2000, sometimes in Audition.

Of course, in DAWs if people find the decoded waveform looks like crap, they won't hit the play button, but that's not the case with typical audio players.

https://forum.cockos.com/showthread.php?t=85641
2
MP3 - General / Re: Lame 3.100 has been released
Last post by saratoga -
I don’t know how he compiled, is there any reason we shouldn’t use tmkk?
All builds sometimes create different files, even the x86 and x64 version from the same bundle. From the null test results I am unable to tell which particular build has more differences than the others, plus I can't ABX them. Therefore I am going to use tmkk's version for the speed.

I learnt about the term "non-deterministic" in x264 but I think the situation is a bit different, since individual lame.exe always create identical mp3 files.

I wonder will the same lame.exe create different mp3 files when using different processors, like Intel vs AMD? Who wants to try?


It's been discussed in detail before, but basically floating point numbers have rounding error, so each of the many ways you can compile a mathematical operation may give slightly different results due to how the numbers round. If you need deterministic output, you're probably looking for a lossless codec.
3
3rd Party Plugins - (fb2k) / Re: foo_wave_seekbar
Last post by Wemppu -
Do give it a try, see if it helps you - foo_wave_minibar-1.26.fb2k-component

Thanks @Zao !
This is a big step forward to see whole playlist in browser window as single page.
However as you can guess most usable version would be display on foobar app window module ;)

Playing in these contests is following playlist by press enter and then music stops, select next, wait team to be ready and press enter.
If selecting next would give picture of next track waveform too I would be sold.

But yes, since there is lot of waiting for next team and standalone images are in same order than playlists there is time to see starting levels of next track. Therefore this is working solution to me. Thanks!
4
In my little world of Linux/Unix and Windows command line, I use the utility sox (the command name is actually soxi), and that is how I normally determine what kind of data/sample rate in a wav/mp3/flac/etc file.   The utiiliies that I write also automatically display the data type/rate.   My own 'normal' data type is 32bit float (or 24bit signed int for flac), even though I normally produce 16bit to send to others.  So, the best bet that costs NO money is to use the command line soxi.   Also, I happen to know that Audacity (free GUI audio software) displays the data type also ( i use Audacity once in a while.)   A wonderful (almost lossless) tradeoff is to use 24bit signed flac, which ends up being not far different from a 16bit wav file in size.

John
5
MP3 - General / Re: Lame 3.100 has been released
Last post by eahm -
Confirm Rarewares-x86.mp3 is the only different one with bit-compare.
6
There are a few of these out on the 'net by now. I can only speculate that more artists use software that work with such files, and more often than before an artist will upload a file without having to worry whether to save bandwidth by going mp3.

But why? Of course there will always be someone who on purpose will upload the biggest files they can, but I know that not all of my files were intended to be uploaded in that format ...
Is it so that these DAWs do not even tell you that these are not your "usual" WAV files? (What does Audition do? I'm too lazy to download a trial version just for this.)

Just curious.
7
MP3 - General / Re: Lame 3.100 has been released
Last post by bennetng -
I don’t know how he compiled, is there any reason we shouldn’t use tmkk?
All builds sometimes create different files, even the x86 and x64 version from the same bundle. From the null test results I am unable to tell which particular build has more differences than the others, plus I can't ABX them. Therefore I am going to use tmkk's version for the speed.

I learnt about the term "non-deterministic" in x264 but I think the situation is a bit different, since individual lame.exe always create identical mp3 files.

I wonder will the same lame.exe create different mp3 files when using different processors, like Intel vs AMD? Who wants to try?

Among the attached files, Rarewares-x86.mp3 is the only file which is different from others. However, if the original audio files are longer, all files are more likely to be different.

8
I just wanted to mention a limitation of your experiment.
It does exactly what it was supposed to do; control PSS splitters with the only means available to do so at this time. Recommending undocumented components that a handful of people on the planet use (and probably even fewer understand) is going off-topic here.
9
Validated News / Re: Opus 1.2 is out!
Last post by alter4 -
Could anybody compile recent revision, I would like to test this fix
https://git.xiph.org/?p=opus.git;a=commit;h=b30f45b9a8bfc7b97afb75042bf2ab16a2150972
Thanks
10
MP3 - General / Re: Lame 3.100 has been released
Last post by sanskrit44 -
@john33: thank you for the updated flac and lame versions at rarewares. will there also be a latest ogg lancer build as well?
You're welcome. :) I may get round to the Lancer builds, but I don't believe the code's been updated in a long while, so I'm not sure there will be any benefit.
hm, i think there have been some minor changes (not qualitywise though) to ogg lancer indeed. anyway, after flac & lame it would be great to see a lancer update, too :)