I think it would be a great feature for the equalizer if it was able to automatically load feq preset files that are located in the same folder as the track that is currently played.

One scenario where this would be beyond useful: I listen to many concert recordings which all might or might not have different shortcomings - like boomy room acoustics, dull treble range, overemphasized midrange etc.

It'd be great if I was able to figure out a preset that compensates for these problems and put it into the same folder as the recording, with the effect that this preset is automatically loaded every time a track of this concert is played back.

Discuss.

I think this will need more changes in foobar than in EQ itself as foobar handle the song file access (that will trigger the preset existence check).

The problem I see is that people will start to ask for all DSP settings to be stored in the preset file.

I would be happy with some flexibilizations I already asked for.

Err.. no.

Or better solution - posibility to store equalizer settings for each song as an APE tag. Although I don't use equalizer, I think it would be nice feature.

Way overkill in the scenario I proposed, but I guess it'd have its merits for compilations and VA stuff.

But better? I don't think so. Think about it, do you really want to store player-specific configuration data in a tag? I don't think this is a sensible thing at all.

if anything, i suppose the fb2k-database would be right location. Just a thought, i don't need this feature(i dont even use the database).

Nah, that'd make it kinda hard to back up a show including a readily tweaked eq preset on a cd and play this stuff on a different comp, for example.. :-|

hmm, thats true - would kinda beat the purpose.

The thing is, fb2k is modular.... the EQ is a plugin.... so such settings should be kinda seperate too(another reason why my previous idea isn't a good idea).

Maybe to store it in seperate files indeed is the best solution, dont know.

But storing a single eq-file per directory would have the following disadvantage: what if you're going to move some of the files out of the directory?

storing a single eq-file for every track would of course be technically the most versatile solution - but it would mean hundreds of eq-files floating around your hd...

apev2-tags would solve this, but this would be a DIRTY solution and misuse of tags.

Ok, i'm nailed - i don't know the "ideal solution"

- Lyx

So is storing replaygain on them and no one is complaining.. anymore

I would call it song-specific configuration. If we can store replaygain info as an APE tag for each song why do not store equaliser settings?

Wrong. Storing replaygain info in the tag is not tag abuse, because the replaygain value will be interpreted in the same way by any decoder / player that supports replaygain.

On the other hand, equalizer settings obviously depend on the implementation of the equalizer (number of bands, frequencies, etc..)

The foobar equalizer already stores presets in separate files (.feq) anyway - I am just asking for the option to have the eq autoload these files when any of them are present in the same directory as the song that is playing right now.


You people are seeing nonexistant problems. The problem at hand is not how and where eq presets are stored - this has been solved already. It's all about loading the presets automatically under certain circumstances.

re:open this topic. 8-)

I not see problems to embed eq-settings and other DSP-settings to tag, but that non-standart method now. maybe anybody make that standart? 8-)

Allowed way - store settings into file on same directory and autoapply settings on playback. Nice, but:
1. No one Eq-settings must be stored. How about surround and other? Want All DSP-settings in one file!
2. Need set filename rules. "Album.dsp" - for entrie files, "same-file-name.dsp" -for each file.
3. Foobar do auto apply this file.

foobar dev & dsp-plugins dev - what you think about this?