1
Support - (fb2k) / Re: foobar2000 for Mac: bugs & wishes
Last post by Guildencrantz -I can't reproduce what your screenshot shows. What version of macOS are you on?
I’m on macOS 12 (Monterey).
I can't reproduce what your screenshot shows. What version of macOS are you on?
We have an ancient code here that needs to be dusted off first, whereas you are in a hurry to attach wings to it so that it flies even faster, although it is already faster than LAME anyway.
Dear developers, I listen to your every word with great attention and I am taken aback. Why do you use compilation flags which impact on quality you find difficult to assess? Since when did chasing fractions of seconds become more important than quality? We have an ancient code here that needs to be dusted off first, whereas you are in a hurry to attach wings to it so that it flies even faster, although it is already faster than LAME anyway. If there is even the slightest chance that the quality could deteriorate in at least one frame by at least a bit, such compilation flag should be omitted. Aren't there other projects that can be turned into a proving ground? Helix MP3 encoder should be approached with care, in the spirit of restoration, as the title of the topic suggests.It isn't that easy. @maikmerten already explained that compilers of different origin may change the output more as setting flags inside one and the same enviroment.
For example, what's the difference between object.container.album.musicAlbum and object.container.genre.musicGenre. Obviously, one has to do with Albums and the other has to do with Genres, but I can't tell what they're specific functions are. Also, which object.container do I use for single tracks? I saw something about object.item, is that a thing?
A class is used to assign a type to an object. It also identifies the minimum required set of properties that shall be included in the object’s metadata and the allowed properties that may be included. Classes are organized in a hierarchy with certain classes being derived from others as in a typical object-oriented system.
<spec type="object.container">%releasetype%</spec>
<spec type="object.container.album.musicAlbum">%album%</spec>
LACE/NoLACE is post-processor that works after SILK decoder and can be optionally enabled at decode time. In other words, there's no difference on the encoded bitstream
I do indeed have fast-math enabled on both x64 compiles. I too recall a lame issue, I think with a particular Intel compiler option, but I don't recall which option, and it was in any case some many years ago.Thanks John. Maybe it was even only a bug in some compiler version.