Sorry, I think I found answers...
1. Yes, I think so!
2. I've removed conditions and it seems to be ok.
3. I've used 'albumtype:single [path]' to fix my issue.
Many thanks
On Friday, April 21, 2017 at 7:24:40 PM UTC+1, Jonathan Thomas wrote:
>
> Adrian, I was silly enough to lose my config in the transfer and I'm
> struggling to get the minor details correct, could I ask for help with
> three things, please?
>
> Here's three lines of my new config...
>
> asciify_paths: yes
>
> paths:
> default: artists/$albumartist_sort/$year $album%aunique{albumtype label
> catalognum albumdisambig}/$track $title
> comp: compilations/$album%aunique{albumtype label catalognum
> albumdisambig} $year/$track $artist - $title
>
> 1. Is the asciify_paths line correct - the docs don't mention how to turn
> it on, so I assume it's ''yes"? I know that there's the stuff I can put in
> the path itself but would rather do this, if my understanding of its
> implementation is correct.
>
> 2. The aunique is causing some albums folders to look like "2014 Sonic
> Highways [2014]", even though I've deliberately removed 'year' as a
> disambiguator (as it's part of the path). The weird thing is that there's
> nothing for aunique to do with this particular album as there's not a
> similar album. Other albums in the same 'Foo Fighters' folder are fine,
> except "2011 Medium Rare [2011]", again, there's no similar albums for that
> either.
>
> 3. If I wanted to append " - Single" to the path of every albumtype =
> single, how do I do that? I've looked at the '%if{condition,text}' but
> struggle without example code. Here's my interpretation, can you let me
> know if this will work, please?
>
> default: artists/$albumartist_sort/$year $album%aunique{albumtype label
> catalognum albumdisambig}%if{albumtype=single, - Single}/$track $title
>
> Many thanks for your time.
>
> Jonathan
>
>
>
>
> On Tuesday, April 18, 2017 at 2:58:52 PM UTC+1, Adrian Sampson wrote:
>>
>> When beets tags files, when you have the import.write config option on
>> (the default), it puts the MBIDs into the files’ tags. So if you were to
>> delete your database and re-import everything with -A, it would pick those
>> MBIDs back up again.
>>
>> So it sounds like that’s probably what you want! Good luck.
>>
>> Adrian
>>
>>
>> On Apr 18, 2017, at 5:39 AM, Jonathan Thomas <[email protected]>
>> wrote:
>>
>> 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]>
>>> 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].
>>> > 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.
>>
>>
>>
--
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.
