Skip to main content
Recent Posts
General - (fb2k) / Re: [Feature Suggesion] Current Playing / Selected Tracks Available as Titleformat
Last post by jazzthieve -
If I understand you correctly about current playing alternative version of playing track I already have a method in place that does that but I don't think it's for everyone. You need Columns ui and library tree component (the older columns ui version, not the jscript version of the same name) although I guess perhaps with default ui and popup panels library tree could work too (untested).

First, a screenshot:

This show all versions in library of current playing track "Last Train to Transcentral" by The KLF. It doesn't show the artist or title just because I have limited width on that panel and only want necessary information to show.
For this to work you first need to strip down the title of the track to its 'absolute form', meaning stripping away stuff like "remix", "remasterd", "12 inch version", "DJ whoever mix", "live in wherever version"....basically anything that's not part of the actual title and relegate that information to a different tag which I call "Track Info". I also use an additional tag called "track type" which can either be acoustic, remix, demo or live.

The library tree has a filter field and when formatted like this
Code: [Select]
%artist%-%title% IS $nowplaying{%artist%-%title%}
It will show all titles which are the same (hence the purpose of splitting up track info from the actual title). You can set view format to whatever you like to be shown, %track info% and/or %rating% seems logical.

An extra step I devised that proved very helpful for me for identifying same track but which have slight different spellings is using masstagger and use "format value" with this formatting pattern:
Code: [Select]
$crc32($lower($ascii(%artist% $replace(%title%,$char(32),,$char(33),,$char(34),,$char(39),,$char(40),,$char(41),,$char(44),,$char(46),,$char(47),,$char(58),,$char(59),,$char(63),,$char(96),,$char(145),,$char(146),,$char(147),,$char(148),))))
Destination field name: FOO_ID

Basically what this does is formatting all artist-title to an integer and in the process remove all spaces, punctuation marks and other often occurring marks. This ensure for example tracks which are named the same but are not 100% identical (Example: KLF - What Time is Love? or KLF - What Time Is Love) will still be shown as the same in library tree.

If you then use as filter in library tree
Code: [Select]
%FOO_ID% IS $nowplaying{%FOO_ID%}
Then this will yield more trustworthy results without the track titles needing to be 100% identical.
Opus / Re: Which has better quality?
Last post by ThaCrip -
in short... putting hardware compatibility aside, Opus is basically the best lossy encoder right now. but I think anything higher than 2xx kbps is overkill in general for MP3/AAC/Opus (and the like) as it defeats the purpose of using lossy encoders. that answers your questions.

a bit more details...

in terms of lossy encoders at this point in time I think only three are worth using...

-MP3 (LAME) (the safest choice due to everything that works with lossy files supports it)

-AAC (Apple AAC) (the all around best choice given it's widely supported and it beats MP3 at lower bit rates. say roughly around 128kbps and lower. it's just a more efficient version of MP3 one could say.)

-Opus (the best choice if hardware support is not a big concern and your planning on using bit rates around 96kbps and lower. while Opus is great in the 128kbps+ range I feel it loses it's advantages over AAC once you get into the 128kbps+ range and your probably better off using AAC due to the bonus of much better hardware support)

but at the 384kbps bit rate you mentioned... your probably best off just using lossless formats instead (if sound quality is of super high importance) as the whole point in using lossy encoders is for efficiency sake to get similar audio quality to the lossless file but at a much lower bit rate. those who use 320kbps MP3 (and the like), unless they have to for a specific reason, is just a waste of storage space.

or to give you some suggestions given some basic scenario's...

-If you got storage space to burn and are paranoid about sound quality = use lossless audio.
-If you want to use lossy audio but are a bit paranoid on sound quality = use AAC @ 256kbps (Apple AAC CVBR mode). I think this is what iTunes uses.
-If you want efficient use of storage space but still maintain solid sound quality  = use AAC @ 128kbps (Apple AAC @ q64 TVBR)
-If you don't mind trying some of the latest tech and are more concerned with maximum efficiency = use Opus @ 96kbps (maybe a bit lower depending on your preferences (64kbps is respectable for the bit rate) but I just suggested 96kbps since that scores very well around here and you can be confident sound is not really sacrificed at that rate).

if you don't want to overthink things... I suggest you use Apple AAC @ 128kbps (q64 TVBR) and forget about it. you can't go wrong with that choice.
General - (fb2k) / [Feature Suggesion] Current Playing / Selected Tracks Available as Titleformat
Last post by Anselm -
I'm a working open format dj and use foobar for a lot of organizational and preparational tasks. Having implemented my own structures on tagging I found ways to make these usable for various filters in Facet, yet I'd absolutely love to have filters that allow me to show alternative versions of the now selected or playing track (when preparing playlists).

Basic idea from my pov would be a chance to allow title formatting variables to be related to absolute tracks eg. now playing, currently selected... and use the existing methods to strip down the title tag from remix/version information or use my mood mashes (eg. #riser #bigroom #chill) to gain a filtered view on my library in a second Facets instance.

For example I have this track:
Artist: Artist;Artist2
Title: Title (XYZ Remix)
Album: #bigroom #riser #house #tech

and I could create filters that search for:

1) Artist Title;Artist2 Title
2) XYZ
3) #bigroom #riser #house #tech

automatically during playing back a track in foobar or having it selected, a suggestion tool that totally relies on what I tagged before.

As an idea on how they could be designed I'd suggest something like
$nowplaying(title) <- if thats even possible...
3rd Party Plugins - (fb2k) / Re: foo_enhanced_spectrum_analyzer
Last post by Porcus -
I like it. I don't view spectra that often, but I have had this and foo_musical_spectrum side by side, and I am not sure which I prefer for general visuals.

But foo_musical_spectrum has a couple of features which I at least sometimes would miss from your component. For your consideration:
- octave / "piano key" view. Sometimes more instructive than Hz numbers. Can be "tuned" by setting the pitch for A4 (defaults to 440 Hz).
- "transposition by semitones". Who has a Bb instrument? ;-)
(When I have run tests for infrasound or ultrasound - I have at least a couple of musical pieces with possibly amp-draining infrasound down to 6 Hz - I have tuned/transposed transposed to circumvent its C0-A11 range.)
3rd Party Plugins - (fb2k) / Re: foo_enhanced_playcount - Record all song plays and scrobbles (JScript)
Last post by MordredKLB -
Releasing v3.0.1

  • When no lastfm plays recorded by the component, [%lastfm_playcount%] now shows a blank value instead of 0 meaning it operates identical to [%playcount%] - Thanks to @annalise for reporting
  • Fixed a bad regression where changing file tags would cause all plays and scrobbles of that song to be lost. This allowed me to clean up some code and ensure this can't happen again as there's now a single code path for generating hash strings
General Audio / Re: Questions on "loudness wars" and/or bad CD engineering - doing a FLAClibrary
Last post by mitchco -
I've read the term "pump" being used here and elsewhere and it certainly describes the gawd-awful artifact that I find so irritating, but I don't know enough of the vocabulary to identify it in a way others readily understand.

Is there a primer on the common vocabulary used for this stuff?

Thanks for your patience!

Ex recording/mixing engineer here. I wrote an article on this with some definitions and a few listening samples at:

While folks have made references to declipping tools and can help, the sad reality is that over compression/limiting can occur at all stages of recording, mixing, mastering... Even on every individual multi-track channel, going to tape, plus tape compression, and coming back from tape for mixing, each with different compression ratios, attack, release times, plus on sub groups, plus on the overall 2 channel mix, let alone mastering or remastering... Impossible to undo the damage done... The best one can hope for is an older recording that has not succumbed to the loudness war, but if it is new material... Good sounding quality recordings, mixes and masters have become a lost art over the past 25 years :-(

SimplePortal 1.0.0 RC1 © 2008-2018