Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
1
3rd Party Plugins - (fb2k) / Re: MusicBrainz64
Last post by KthugS -
It's interesting. Since the first time I ripped a music CD a long time ago, the album artist tag field has always been filled in, so I thought it was natural.
Really interesting, I was missing something very basic  :))
I will update to 2.4
Thank you very much
3
General Audio / Re: Can lossy high resolution outperform lossless at standard resolution?
Last post by Kraeved -
Turn the volume way up during a very quiet passage from a CD (like a reverb tail) and the hiss (or distortion, if not properly noise-shaped) you hear is the limitation of 16-bit audio … the point is that 24-bit audio has the advantage of a greater dynamic range than 16-bit, and this is achieved with a higher signal-to-noise ratio.

The advantage comes while editing. As for playback, how many bits can you hear?

If you’re a subjectivist then any form of lossy encoding is very suspect (and virtually always audible)…

I remember subjectivists who, ignoring the research of optical illusions, saw signs of civilization in low-resolution spots on Mars that resemble a face. Okay, there is Pi. It is used, for example, to build bridges and dams. The decimal expansion of Pi is infinitely long, namely 3.1415926535897932384626433… Downsampling 192 kHz and higher rates at least by a factor of 4 is as lossy as rounding Pi up to this length, which is still sufficient to serve the purpose. Expecting someone to hear the difference is like expecting someone's eyes to see millions of bacteria, fungi and viruses that compose our skin microbiota. It's just that the word lossy, uttered without specifying the scale of the loss, first brings to mind the worst artifacts of the MP3 childhood, whereas in this case it's just the operation that was not done in the studio for marketing reasons, although those anxious folks somehow accept without worries the fact that the studio reduced 64-bit or 32-bit float to 24-bit integer before delivery. No doubt in the future they will worry about this too.

Neither of these philosophical camps have ever left any space for something like lossy WavPack.

I had. But then I found a few cases when WavPack hybrid failed. You called those cases anomalies. But in the course of your explanation, you outlined ways how this encoding mode can be improved, which is what I now pray for, even in my own signature. Until then, WavPack lossless only, which looks advantageous against FLAC, which has difficulties with the preservation of non-audio data. Peace of mind, you know.
4
3rd Party Plugins - (fb2k) / Re: MusicBrainz64
Last post by marc2k3 -
album artist is only written when it needs to be. When you have an album where the artist is identical for every single track, it's not written because it's pointless.

https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Encouraged_Tag_Standards#ALBUM_ARTIST

Everyone one should be using %album artist% title formatting in library viewer grouping/playlist headers etc where the artist will be used if album artist is not present. That is documented here...

https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Title_Formatting_Reference#.25album_artist.25

And while most players don't have anything quite like title formatting, they usually follow the general rule. Even steaming piles of poop like itunes and WMP do (or did - I've not tested for years :P)
6
3rd Party Plugins - (fb2k) / Re: [fb2k v2] Playlist Attributes (foo_playlist_attributes)
Last post by Cannonaire -
I think there might be something wrong with the new version. As soon as I update it on my portable install (I have it backed up), upon playback it starts duplicating one of my DSP settings and adding it over and over to my DSP list (in this case, a VST I am using). Is anyone else experiencing this issue?

I don't use Playlist Attributes to apply DSP effects to any playlist since I select DSP chains based on whether I am listening to speakers or particular headphones.
8
3rd Party Plugins - (fb2k) / Re: MusicBrainz64
Last post by KthugS -
X
"The whole purpose of this is to unify tag display/search across foobar2000 regardless of file format."

This has been my wish for a long time.
And in the meantime, I directly modified the tag to do so.
However, when I tried to edit something with mp3tag, the FLAC file was fine, but
In the case of mp3 files, some fields such as MBID field and ORIGYEAR were changed unintentionally.
The 'User-defined field mappings' option didn't help me either.
So, after using mp3tag, I had to edit the tag once more with foobar2000.
It was a real hassle, but this is what I ultimately wanted.
So I really agree with "The whole purpose of this is to unify tag display/search across foobar2000 regardless of file format."

I have one question
Does MusicBrainz64 intentionally omit the 'ALBUM ARTIST' field?
While testing after deleting some or all tags, I found that the 'ALBUM ARTIST' field was missing.
I thought it was a conflict with the existing MusicBrainz Tagger, so I deleted MusicBrainz Tagger and foo_musicbrainz.dll.cfg, but 'ALBUM ARTIST' is still missing.


Your Components are always useful thank you
9
3rd Party Plugins - (fb2k) / Re: [fb2k v2] Playlist Attributes (foo_playlist_attributes)
Last post by cwb -
I honestly shouldn't have posted the question concerning the placement of the dialog boxes, because it really is quite unimportant. Sorry for having wasted yours and my own time with it.

*******************************

As far as the issue with going from a playlist that has edited DSP settings, through your component, to a playlist that has no edited DSP settings. Things have improved.

But I am hesitant to try to relate it because I suspect that my use of DSP settings is probably not common, and I can live with it.

But very briefly:

I use the component vlevel with two of my playists through Playlist Attribute's edited DSP settings. It happened that when I pressed stopped, and moved to another playlist that has no edited DSP settings, under certain conditions, vlevel was activated in the playlist with no edited DSP settings.

Now in your newly released 1.0.4, when I switch from the vlevel playlist to a playlist with no DSP settings, vlevel is no longer activated in the DSP manager, but another of my DSP chain presets is, this time it is "Tempo Shift - Normal", which happens to be set to 0.00. Which makes it essentially "Off".

As it is I can live with things as they are, But it would be interesting to know what happens with other's who use your component for DSP settings applied to specific playlists. What, if anything, happens in the DSP manager window for them when they go from an edited DSP playlist to a no DSP's applied playlist. Can they post if anything happens when they double-click a file to play it, or if they select a file and then press play, or select a file and add it to Queue, and then press play.

As it is @fbuser  I'm fine with it, and I thank you for your component. Thus far, I have only used a very small percentage of your component's capability.