Skip to main content
Recent Posts
4
Support - (fb2k) / Re: %CONTENT GROUP% mapping error
Last post by incifinci -
Nem hiszem...
Misunderstanding -- it was addressed not to you. Sorry.

I understood you. But today millions of foobar users, because of Id3 fog, use TIT1 for very, much more important purpose: really, as written, as musical category -- symphonic, concerto, chamber or solo. You argue with some technical needs, and force to remove this chance from us. Do you plan to give us some as strong, as TIT1, in exchange? Not some TXXX one and its Vorbis Comments pair, but some exactly so strong and populated one. NO. You only remove, once forever, from us and all future users.

You forget: tags and programs and standards must serve music. Not inversely.
5
3rd Party Plugins - (fb2k) / Re: foo_dsp_xgeq
Last post by Rollin -
Maybe not bug, but:
If by accident you give multichannel signal (e.g. 4.0, 5.1, 7.1) to this equalizer when it is in "Stereo" mode, this will result in horrible noise.
6
3rd Party Plugins - (fb2k) / Re: foo_dsp_effect
Last post by mudlord -
the iir might also have the GUID bug, thanks for reminding me to double check everything.

As for the EQ, I'm not in the mood to implement another graphic EQ. I thought xnor already did a decent EQ.

EDIT: double checked the IIR filter, works fine here. Not sure what you mean. You might be getting confused with another component.
7
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by Hugg Niceman -
The spectrum analyser is the only visualisation that's built into Columns UI – if you had others with Columns UI before they must've been third-party components. Do you still have your old foobar2000 installation available to double-check how it was set up there?

Thank you for the reply. I do not have my old installation still. It was a few years back on my old PC. I suppose I must have been using the Default UI, but I know I had used Columns UI at some point there, I loved the way the albums and stuff had that separator between them, made the UI look a lot better. But I am most likely mistaken since this is the case. I appreciate you trying to help out on that. I might just have to sacrifice my visualizations for the vastly superior UI from Columns UI.
9
General - (fb2k) / Customize playback preview
Last post by fabiospark -
About playback preview this is what I understand:
- now it is part of main FB and not a separated component anymore
- I can't customize the drop down list of lengths
- I can't define a percent length

Is all that correct?

Thanks.
10
Support - (fb2k) / Re: %CONTENT GROUP% mapping error
Last post by thomian -
But today some guys want to say me, that I am stupid, and I must to use TIT1 in absolutely other way...
Nem hiszem, hogy hülye vagy. Thanks for your detailed explanation. I can follow your thoughts. Sorry, I did not want to offend you.
To my knowledge, both, the Windows Media Player and Microsoft Groove, never supported the grouping tag. I don't think, that these players could be authoritative for this issue. Not only at Microsoft, but most software developers never realized, that some music needs a more differentiated description, than just "Artist - Song". For classical music you have to distinguish between performers and composers, between ensembles, conductors, singers and soloists. And Title description includes work and movement and for large-scale works like an opera even subsections like acts. Furthermore the opus number, and other stuff. At least four tags are essential for classical music: artist, composer, grouping & title. You have different but comparable problems with jazz music etc... The ID3tag consortium adressed all these issues by providing at least three tags for Title naming TIT1, TIT2, TIT3 and three tags for Artist names TPE1, TPE2, TPE3, which was a usable solution for nearly all cases. Unfortunately software developers never gave full support for these fields and focused on "artist" and "song". Instead they even misused some of these fields for other purposes. For example, the ID3tag consortium did not provide a field for the "album artist", so people startet to put this information into the TPE2 field, which originally was meant to hold the name of the band, orchestra or ensemble involved. foobar denied to participate in this "misuse" for a long time and mapped this field to %band% instead of %album artist%. But that's another story... For genre information the ID3tag documentation provided the TCON field, that was named "content type". No mention about genre. This about foggy descriptions of ID3tags... It's a string variable and may hold any user-defined genre, subgenre or music type of this planet.

But again... I don't want to argue, how to use the grouping field "correctly". People are free to fill it with the information they need. No need to change anything.

I just argue that %grouping% would be a better field name than %content group%, as it is more standard and practicable as explained in my previous posts. Hope that this will be fixed.
SimplePortal 1.0.0 RC1 © 2008-2018