fromfilename: Configurable extraction patterns

[fohrums]

Recommendations for manual editing imported tracks

A) the use of the plugin fromfilename (although I can't get it to work)
B) simple option to just edit

Option A
Upon importing a track (with option to skip matching from sources, because there isn't any), this plugin will provide you the option to set the format-pattern to define which goes where.

Because fromfilename plugin doesn't have any 'configuration' option like other plugins have, there isn't a way to verify the format used within the filename to embed the tags from.
But if you look at the beetsplug/fromfilename.py it has sections for field
extraction patterns for which could possibly define the format-pattern in this following scenario:

File (w/out any tags):

1. Mack 187 & Akoza - Introduction.flac

Format:
$track. $artist - $title

Option B
same as above but by not defining the fromfilename this instead will allow you to edit the general tags yourself:
-artist
-title
-album
-track/total
-disc/total
-comment
...etc

as also suggested from #154 @dokterbob recommended an similar 'Apply and edit' option, except mine includes what could be edited and that it should be up to the user to define what they want to have the option to edit from.

[sampsyo]

Configurable patterns for the plugin would be a great idea.

I don't quite see the difference between #396 as currently proposed and Option B. The proposal would work like #164 (which admittedly has been neutered by the Google Code shutdown), allowing you to edit any tag you like.

[brutus]

I started using beets today, so I guess just patching the PATTERNS list from https://github.com/sampsyo/beets/blob/master/beetsplug/fromfilename.py to include my usual patterns, could work. But I'm not familiar with the code base.

Would be nice if fromfilename would be configurable trough the YAML file — like an option that let's us add additional patterns. And that the results would be used directly — a lot of my tracks aint on musicbrainz.

BTW: using unicode chars (like – or —) in the pattern definition throws an error: SyntaxError: Non-ASCII character …, even when ur'…' is used.

[sampsyo]

Would be nice if fromfilename would be configurable trough the YAML file — like an option that let's us add additional patterns.

Yep, that's the idea.

BTW: using unicode chars (like – or —) in the pattern definition throws an error: SyntaxError: Non-ASCII character …, even when ur'…' is used.

Indeed, because paths are bytes. If we make this configurable, we'll have to handle that.

[pimpsky]

Was this ever implemented? I'm guessing not because the issue is still marked as open.

[sampsyo]

I don't believe so!