Hi Adrian, 

Finally coming around to putting my collection on a larger hard drive and 
wanted to check something before I dive in and do this...

You say that '-A' "just trusts all the metadata on the files, including 
MBIDs". Is this true if I were to take my collection with NO existing 
associated database and attempt to start a new Beets database?

Basically, I have now manually copied over my entire file structure to a 
new location, now I want to do a clean install of ubuntu server and Beets 
and start a new database. So the question is, is the MBID stored in the 
file metadata or the Beets database? So when I import (with -A), it'll 
automatically track the correct MBIDs that I've already selected from a 
previous import into (essentially) a different Beets instance/database.

Many thanks,
Jonathan

On Saturday, June 6, 2015 at 11:26:18 PM UTC+1, Adrian Sampson wrote:
>
> If I were you, I would probably use a non-autotagged import (-A). This 
> just trusts all the metadata on the files, including the MBIDs, and doesn’t 
> try to look up anything again in MusicBrainz. If you like, you can then 
> later use `mbsync` to do lookups based on those IDs. 
>
> Another alternative would be to use `max_rec` to downgrade matches that 
> have mismatched album IDs: 
> http://docs.beets.io/en/v1.3.13/reference/config.html#max-rec 
> and then a quiet import (properly configured) would automatically skip any 
> bad matches. 
>
> Adrian 
>
>
> > On Jun 6, 2015, at 3:09 PM, Jonathan Thomas <[email protected] 
> <javascript:>> wrote: 
> > 
> > Hi, 
> > 
> > Sorry if this is mentioned elsewhere, but is there a way to force Beets 
> to re-import an album using the same MBID that was assigned to it on first 
> import. I'm asking because I plan to move my entire library to a different 
> directory soon, and I also plan to move to another drive further down the 
> line. When re-importing, I don't want to have to confirm the matches, I 
> have already chosen the correct MB release previously. I know a quiet 
> import will help me avoid a long import process, but I don't want to risk 
> Beets assigning the albums to the wrong releases. 
> > 
> > Thats a long winded way of me asking, can Beets let me keep the MBID 
> when reimporting? 
> > 
> > I guess something like: 
> > beet imp -f /path/to/my/album 
> > 
> > Would be great 
> > 
> > Cheers, 
> > Jonathan 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "beets" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"beets" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to