Improve documentation on path format

[FichteFoll]

The README does not mention which variables are replaced in the path format interpreted by this plugin. From reading the source code, I have determined this to be the following:

• artist
• albumartist
• album
• albumpath
• filename
• basename

As well as all functions provided by beets by default.

I was especially interested in filename and basename, because the readme wasn't clear enough (to me) on whether the matched files will be copied into a directory specfied in the paths setting or whether that will be the path for each individual file. Especially considering that the file extension is specifically not considered for the template and merely appended.

Also a mention of the default pattern would be useful. That should be $albumpath/$filename.

[alfureu]

I second this. Is there any way to put the extra files inside of a custom made folder defined by inline and path? All the extra files land where the albumpath is, but it does not take insto consideration the full albumpath, just the first part of it.

[daniellwdb]

I second this. Is there any way to put the extra files inside of a custom made folder defined by inline and path? All the extra files land where the albumpath is, but it does not take insto consideration the full albumpath, just the first part of it.

Been a while but +1 for this, this plugin does not respect full album paths so it's not possible to create subdirectories when using buckets