dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: RE: Enqueing all types.

RE: Enqueing all types.

From: TP Diffenbach <>
Date: Fri, 19 Dec 2003 09:51:17 -0500

Easy. When an mp3 is loaded, read it's associated cfg file, if any. To
associate cfg files to mp3s, we could:
  look for a .cfg in the same directory with the same file name as the mp3,
  look in the mp3's id3 information for the file name of the .cfg, or
  directly encode configuration options in an id3 tag.

If we did not find a .cfg associated with the file, we'd look for a .cfg in
the directory with the same name as the directory; we could keep ascending
to parent directories until we found a .cfg (and obviously this would
benefit from intelligent "caching", or really remembering whether we'd
already looked above a certain directory).

I'd thought about writing this patch, but frankly bass and treble settings
and all that graphic equalization stuff are mysteries to me, so I tend to
leave them alone.
-----Original Message-----
From: []On
Behalf Of Michael Hentschel
Sent: Friday, December 19, 2003 8:41 AM
Subject: Re: Enqueing all types.

Damn it! You're right...
But how would you have configs for specific files? Rockbox searching for a
cfg for every mp3 started?


"Daniel Stenberg" <> schrieb im Newsbeitrag
> On Fri, 19 Dec 2003, Michael Hentschel wrote:
> > But inserting .cfg in a playlist would be a nice workaround for eg.
> > individual soundsettings for certain audio files. Definitely you don't
> > to adapt the volume for every mp3 (easier done in MP3Gain, even
> > but I often would like to tweek the bass-boost, etc. for single mp3s.
> > Developers, are there any technical reasons against such a feature?
> Shuffle for example?
> I'd personally rather have config files for specific files/dirs and keep
> songs in the playlist.
> --
> Daniel Stenberg -- --
Received on 2003-12-19

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy