#beets

/

      • misterswag has quit
      • lad1337 joined the channel
      • lad1337 has quit
      • lad1337 joined the channel
      • lad1337 has quit
      • lad13371 joined the channel
      • lazka has quit
      • nyloc joined the channel
      • _nyloc_ has quit
      • lad13371 has quit
      • jankowiak joined the channel
      • k03ll has quit
      • tuxiano joined the channel
      • lad1337 joined the channel
      • tuxiano has quit
      • lad13371 joined the channel
      • lad1337 has quit
      • jswagner has quit
      • jswagner joined the channel
      • jswagner has quit
      • lad13371 has quit
      • jswagner joined the channel
      • thunderrd has quit
      • thunderrd joined the channel
      • lad1337 joined the channel
      • lazka joined the channel
      • lad1337 has quit
      • lad1337 joined the channel
      • JayPee joined the channel
      • lad13371 joined the channel
      • JayPee
        Just started using beets; possibly stupid question:
      • what if I want to query on a single word?
      • i.e. beet ls boo
      • will return stuff that has both "boo boo boo" and "boopity boopity" in it
      • what if I just want the former?
      • lad1337 has quit
      • (I suppose I could do beet ls ' boo '; but meh.)
      • Mineo has quit
      • Mineo joined the channel
      • jbd joined the channel
      • slush
        JayPee: "boo boo" works too
      • but there isn't a easy way to query for a single word, unless you use regex's
      • tuxiano joined the channel
      • tuxiano has quit
      • lad13371 has quit
      • k03ll joined the channel
      • thunderrd has quit
      • thunderrd joined the channel
      • tuxiano joined the channel
      • tuxiano has quit
      • sampsyo
        JayPee: A regex that matches only the full field would look something like ^this$
      • jankowiak has quit
      • k03ll has quit
      • k03ll joined the channel
      • NOTICE: [beets] sampsyo pushed 2 new commits to master: https://github.com/sampsyo/beets/compare/86bf8b65bad0...e2908017a411
      • NOTICE: beets/master 8b35ec9 Bruno Tournay: Fixed ignored new fields when showing/detecting a model change
      • NOTICE: beets/master e290801 Adrian Sampson: Merge pull request #560 from brilnius/fix_modify_with_new_field...
      • NOTICE: [beets] sampsyo pushed 2 new commits to master: https://github.com/sampsyo/beets/compare/e2908017a411...057ff66ad6ea
      • NOTICE: beets/master ecace62 Adrian Sampson: changelog/thanks for #560
      • NOTICE: beets/master 057ff66 Adrian Sampson: show_model_changes: special display for new fields...
      • daks
        hello
      • sampsyo: irc is simpler to debug problems than twitter :)
      • so i got an album with artist as ARTIST
      • i have done 'beet modify artist:ARTIST artist=ARTIST'
      • and the same with albumartist=
      • now i want files to move from the directory ARTIST/album to artist/album
      • but i don't understand how to do it
      • sampsyo
        daks: hey there
      • indeed, twitter is a poor IRC :)
      • daks
        for sure :)
      • sampsyo
        since albumartist is an album-level field, use:
      • beet modify -a albumartist=foo
      • daks
        oh
      • i don't understand why but i'll try
      • sampsyo
        it's a bit confusing; it would be great to find a way not to expose that distinction to users
      • BrainDamage
        sampsyo: what do you think about checking if an album's items all contain the same field and then add that property to the album too?
      • sampsyo
        yes, that might be a good idea
      • we do a similar thing for the `update` command
      • daks
        oh ok it's because the db has information about tracks AND album?
      • sampsyo
        yes
      • daks
        which has no sense for files
      • BrainDamage suggestion seems good
      • sampsyo
        BrainDamage: it would be great if we could move that logic (propagating item-level field changes to albums) into a function and use it in both `update` and `modify` (and the `mbsync` plugin, which also does the same thing)
      • daks
        with -a beet move does the job, thanks
      • adding this to my beets-cookbook document
      • it's a great software but sometimes user interaction is hard
      • when using beet modify
      • is beet write necesary after?
      • sampsyo
        depends on your configuration (if you have import.write set, then modify does it automatically)
      • daks
        i didn't change this config, is it the default one?
      • sampsyo
        yes
      • daks
        default queries are case insensitive it seems?
      • yes they are, but regex aren't (but much much slower)
      • thanks for your help, going back to library organization
      • sampsyo
        :)
      • pprkut
        sampsyo: would you have an idea why importing a cd with about 30 tracks would take one hour?
      • sampsyo
        Nope. Do you have echonest enabled?
      • pprkut
        I have no system or network load, I'm really stumped by this :(
      • I do have echonest enabled
      • sampsyo
        Uploading to them takes literally forever
      • pprkut
        yeah, but it hasn't started uploading yet
      • sampsyo
        (And waiting for the analysis results to come back)
      • Oh?
      • Any clues in the verbose log?
      • pprkut
        I'd have to rerun it for that, right?
      • is running import with -v enough or should I add something else?
      • hmm, getting connection timeouts from the lyrics plugin. That could be it
      • lad1337 joined the channel
      • sec^nd has quit
      • sec^nd joined the channel
      • jbd has left the channel
      • lad1337 has quit
      • stillaftermath joined the channel
      • stillaftermath
        Hey all, I've sorted all my music using beets but accidentally reversed two tags (I put $artist - $track when I meant the other way around) - The FAQ and help command says that I should be able to fix this easily by running a beet move $/Music (my destination folder), but I fixed it in the config, did that, and it just chugs for a minute or two, exits out, and doesn't rename anything
      • Is there something I need to add to it to tell it to process already imported media or something?
      • oloP
        stillaftermath : try with the origin folder
      • or no folder at all
      • just "beet move"
      • stillaftermath
        Oh, beet move might be the trick, it's reporting back that it's moving 2000-and-change items
      • and nope, negative.
      • By origin folder you mean the -d switch, as in beet move -d ~/Music?
      • oloP
        yes
      • stillaftermath
        trying that now
      • oloP
        but beet move should do the trick, I use it all the time
      • k03ll has quit
      • stillaftermath
        Aha! yeah, worked with the -d switch
      • One more q - The import process is very slow (pausing for seconds and sometimes minutes before returning options or deciding on the course of action) - I'm betting this is due to one or more plugins. My current line is "plugins: discogs fetchart embedart lastgenre duplicates"; any of those known right off the bat to be bad for that kind of thing?
      • I know musicbrainz itself can sometimes be all bitchy with request throttling and such.
      • I'm thinking it's discogs because it gets much worse on albums that return a ton of potential matches
      • misterswag joined the channel
      • oloP
        I don't know, try without it and you'll see
      • stillaftermath
        Yeah will do, just asking in case one of them was a known problem child
      • Thanks for the help mate
      • oloP
        You can try on the same album by reimporting it to see if there is a big difference. Just change the path to the one that is already in your library
      • Beets won't really reimport it but will update it intead.
      • instead
      • derwin
        you can also set up the musicbrainz vm
      • and unthrottle your requests, heh
      • lazka has quit
      • JanC has quit
      • JanC joined the channel