beetbox / beets

music library manager and MusicBrainz tagger
http://beets.io/
MIT License
12.75k stars 1.82k forks source link

Attachments to items and albums #111

Open ghost opened 11 years ago

ghost commented 11 years ago

This issue was automatically migrated from Google Code. Original author: adrian.sampson (November 17, 2010 23:05:05) Original issue: https://github.com/google-code-export/beets/issues/109

holms commented 10 years ago

@vext01 i believe you will be able to register any kind of filename you want manually in your configuration file. my personal interest is covers, cue files, log files, and maybe whole directory with cover files. usually 300dpi scans being attached with album :)

vext01 commented 10 years ago

@holms what configuration directive am I looking for?

holms commented 10 years ago

@vext01 we still don't have attachments ready? or i'm missing something?

vext01 commented 10 years ago

Any news on this?

sampsyo commented 10 years ago

@vext01 Whenever there's news, it will be posted here! If you're interested in this feature, the best thing you can do is help out.

Profpatsch commented 10 years ago

The easiest way to handle this is to give an option to simply copy any files over that are not recognized (and not clutter). That way nothing gets lost.

sampsyo commented 10 years ago

@Profpatsch Yes, that's what the stopgap copyartifacts plugin (above) does. This ticket concerns a more complete solution, which would keep track of files in the database also.

NeuroWinter commented 8 years ago

Has there been any implementation of this as of yet?

benpye commented 7 years ago

I feel like I'm just repeating the last comment, but I am looking for an organisation solution and beets seems great, however, I would like to keep cue+log files. Is there any workflow that can currently do that with beets or is it going to be impossible without the attachment support? And if the latter, is there any indication that this is a feature that is going to be undertaken.

Stunner commented 7 years ago

@benpye this task is being undertaken, however slowly as is characteristic with all projects in the open source domain. You can find the in-progress plugin for this here, I have been using it for a little while now and I have no issues with it.

tom-- commented 7 years ago

UPDATE: ignore me. i hadn't spotted the wip plugin

~Perhaps a set of regex substitutions?~

~When beets processes a dir, for each file in the dir, if the file is not an audio file processed by core beets functionality, and if the file matches one of the configured regexes, then the plugin copies the file to the corresponding destination of the audio files and applies the re.sub.~

keepfile:
    - ["^artist\.(?:jpg|png)$", "\0"]
    - ["^.+?\.cue$", "\0"]

~Perhaps the substitution strings can include path format variables and functions too.~

~I'm not familiar with Python regexing but do you get the idea?~

eharris commented 5 years ago

It should be noted that the copyartifacts plugin does not support the link or hardlink config options at all, so support for this within beets is still needed.

kassisaf commented 4 years ago

It may be worth mentioning beets-extrafiles here. It was originally created to replace the copyartifacts plugin, which is no longer maintained. Unfortunately it also hasn't been touched in about 8 months now, despite some significant issues.

SE2Dev commented 2 years ago

It may be worth mentioning beets-extrafiles here. It was originally created to replace the copyartifacts plugin, which is no longer maintained. Unfortunately it also hasn't been touched in about 8 months now, despite some significant issues.

I'm fairly certain that at this point, both beets-extrafiles and copyartifacts no longer operate correctly with modern versions of beets. I'd imagine that we're pretty likely to repeat the cycle of creating new plugins as a workaround this issue every time the old ones stop being maintained.

kelvinhammond commented 1 year ago

How do you handle extra files with beets these days?