This is just an idea, nothing special. But it may make the foobar2000 program directory more synoptical.
(maybye it was here before.. , I don't know)

It would be welcomed to create a "plugins" subdirectory in foobar2000 program directory and then one or both of these changes:

1. change naming conventions of plugin files to something like this:
foo_in_xxx.dll (input plugins)
foo_dsp_xxx.dll (DSP plugins - yes, they are named this way now, fine ) )
foo_out_xxx.dll
foo_gen_xxx.dll
etc...

2. create subdirectories for every kind of plugin type in "plugins" directory and move them there (like XMMS in Linux):
"input"
"dsp"
"output"
"general"
etc...

(maybye You can also create "Input" section in foobar2000 Preferences/Playback and move all input plugins' settings there)

If You think this is bad idea, forget it and call me stupid or anything :-))

Your idea is good in intentions, but is trivial compared to the project. It would help develop some sort of hierarchy of order, but in reality, most people download a plugin, throw it in the foobar2000 directory and load it up within the foobar2000 program. After that, I'm not sure anyone spends much time focusing on the foobar2000 directory.. Of course I could be completely wrong.

Personally, I like being able to see all the plugins, configuration files, database.foo, etc in the same directory. I guess it's all a matter of opinion.

abhatia

Not to mention, the way the API is designed, a plug-in is not limited to providing just one type of service. I already designed one plug-in with both input and disk writing services. (Unreleased)

Aww, release that! :B

If you insist.