gossamer axe wrote:
Yeah (.flac, .rm, .wav, .mp3, etc), I usually
keep all of the audio for a given artist/theme
in the same directory regardless of file type.
That way I have a better chance of finding
things when I look for something specific.
On the left pane in Amarok, where your artists and albums are listed, you
can set to list just what you want. So if you put mp3 in the search bar, it
will only display mp3's. Same for FLAC. There's no way to only load mp3s,
Amarok loads all music files when it searches, but you can specify what to
show. Those other files will still be in the database, but you can then
create playlists of just mp3s. I believe that you could also create a smart
playlist, that would just bring up files with an *.mp3 extension or have mp3
in the name. Is this what you were looking for?
I was thinking your explanation above was what I
had to do if I wanted to limit what Amarok sees
and then what I have for play lists and so
forth. Basically the solution for this situation
seems to be to have audio files for a given
artist in directories and then in subdirectories
by audio file type and then check off the
subdirs I want included by Amarok. While that is
a bunch of work I think I can make it happen
without too much stress. Amarok is a good program.
What bothers me is I automatically assumed that
the program would do this because filtering,
selecting and qualifying are what computer
programs do best. I should only have to think of
the correct selection criteria to get the output
that suits my needs.
I was very surprised that I couldn't do (by
analogy) what Perl folks are always doing by
taking something with a name/in a list and
manipulating that name/list to limit/qualify
what comes out the other end.
Thanks, this confirmed what I was thinking had
to be done.
rb (I'm not a programmer so maybe I am expecting
too much) w
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
