#beets

does beets provide a way to copy/move my .cue files together with the audio files in the same dir?

q2: how can i best configure my ripper to deal with multi-disc albums? put them in separate directories or in one? and if in one, include disk number in the file name?

tom[]: You might want to take a look at: https://github.com/beetbox/beets/issues/111

And there's an FAQ about the second thing: http://docs.beets.io/en/v1.4.3/faq.html#import-...

tnx sampsyo

sampsyo: regarding the "…import a multi-disc album?" faq, it talks about a heuristic and "or just putting all the tracks into a single directory to force them to be tagged together" as two options. is either preferable?

or should i just suck it and see?

Freso: you were right in your assumption yesterday, that beets wantet to tell me that the MBIDs don't match. I looked into the files and they actually already had an MBID in them that i didn't know about

tom[]: I'd give the heuristics a try, and if they fail, force it by making a single directory.

i have a big rip project ahead. ~1k albums. i want to get the workflow as robust as i can

atm i'm using xld to rip, which is working surprisingly well

tried dbpoweramp but it was rather hands on

abcde was a struggle

tom[]: You may want to check our whippper (the no-gstreamer will get merged soon).

If you want to CLI/automated things more.

*out

(IIRC, XLD is gui?)

xld is gui

i'm happy to use the cli

bit abcde wasn't easy to use because of perl mods that aren't well maintained for osx

Mhm. whipper is Python. And under active development.

i'll check these out

interesting

Freso: do you run osx?

No, Linux. You'll likely have to make some adjustments. :)

However, if whipper doesn't work for you under OS X, I'm pretty sure the devs would love to know!

(#whipper is a thing, btw.)

They're working hard on getting a 1.0 ready. First big issue is removing gstreamer code/dependencies.

That one is basically done, just needs to be merged into master.

i see picard in there. do you use beets autotagger also?

Freso: do you use beets after importing with that shell script?

Hello is anybody online?

louisallaway: everybody

louisallaway: somebody

If so can beets go through a huge unorganised (9000 file) music library and organise it?

automajically

louisallaway: Do you have a backup in case things go south?

Yeah

I need to update it before I do this though.

Did you read through all of https://beets.readthedocs.io/en/v1.4.3/ ?

(It's not as ... long as it seems.)

Oh well.

Oh well.

Did you read through all of https://beets.readthedocs.io/en/v1.4.3/ ?

Ah

(Wb. And it's not as long as it seems.)

le Docs!

Once you can say "yes" to both of these, I'll say "yes" to your question. ;)

What part of the docks should I read?

All of it.

Ok.

(start with the "Getting Started" guide)

I did that before starting to use beets the first time.

But that might just be me. :)

Beets works on linux?

louisallaway: you might as well. processing 9k discs will take a lot longer than the reading

I really think it helped having an idea of what beets was and wasn't capable of before getting started.

9k songs, not disks

oh

well then

making backups and starting over isn't so hard

louisallaway: I've used beets on Linux for years. IMO, it works perfectly fine under Linux!

Starting over isn't exactly an option. A fire destroy'd all of the CD's a few years ago.

(And I think sampsyo, the lead dev, is also only Linux. And most of the non-lead devs are too. Maybe a couple on Mac OS X. We don't really have any "core" people on Windows.)

louisallaway: Well, starting over from a backup. :)

(I'm actually macOS + Linux, a little bit of both.)

Ie., in case you misset some setting and beets ends up deleting all your files.

Ok

sampsyo: macOS, eh? how modern!

:)

I need to redo my backup brb

I try to keep up with the times.

So 10.3?

Debian-style?

I am a windows user, I installed beets on the linux subsystem