[Question] It's ok to make beets copy the files instead of moving it?

[edassis]

Hi,

Basically, it's as the title says. I need to copy the files because of the way I structured my workflow for now, moving them is not an option.

I take a look into drop2beets code, and from the comments I understood that file operations made by it can trigger events in the file watcher. So, I'm asking to clarify my understanding about this. This can cause the same file to be re-imported? Some sort of infinite loop in the import process?

I'm analyzing if I can use it to watch my downloaded files and import it. As I'm using docker containers, it's not trivial to call the beets binary directly, so a file watcher could be a solution.

Thanks.

[martinkirch]

Hello !
As long as files are left there untouched, nothing should happen. drop2beets is triggered by file events, that is when renaming, writing, moving or deleting them.
In that case I'd suggest you do not let beets write tags, with the write option:

import:
    write: no

[edassis]

I think I don't get it. beets writes the tags into the file that has been imported into the beets library. Not in the original file, sitting in the download folder.

drop2beets will be watching the download folder, correct? Not the beets' library. So, why enabling the beets write option can be a problem?

[martinkirch]

Sorry i've misread.

you're right. Copying should be fine.