#beets

/

      • cucumber joined the channel
      • choki joined the channel
      • freakout has quit
      • freakout joined the channel
      • choki has quit
      • Vacuity_ joined the channel
      • Vacuity has quit
      • Miblo has quit
      • Miblo joined the channel
      • storrgie has quit
      • storrgie joined the channel
      • NOTICE: [beets] jrobeson pushed 1 new commit to master: https://github.com/beetbox/beets/commit/8d7a6260741abaabfbb2736d4566bfe2946406d9
      • NOTICE: beets/master 8d7a626 Johnny Robeson: Move timeout config getter to library from dbcore...
      • asdil12 has quit
      • asdil12 joined the channel
      • fredmorcos joined the channel
      • choki joined the channel
      • fredmorcos has quit
      • Freso
        discopatrick: The beatport importer should not be active on Discogs and vice versa…
      • discopatrick
        Freso: are you agreeing that there is a conflict? i had problems that were solved by only using one of the plugins at a time.
      • i didn't get around to reporting it on github yet
      • ToM` has quit
      • untitaker_ joined the channel
      • Freso
        discopatrick: I've never even looked at the beatporter one, so I wouldn't know.
      • choki has quit
      • squirrels
        Is it possible to update all entries in the database that were not updated since e.g. the last 7 days?
      • 'beets info -l' shows only the date when the song was added to the db. Therefor, I expect the answer will be: no. (?)
      • DexterLB joined the channel
      • cobra2
        squirrels: beet list added:$(date -d '7 days ago' +%Y-%m-%d)
      • squirrels: so there is the query you need to pull the songs that you're looking for. now you can either use that to re-import or update.
      • squirrels
        cobra2: thanks, I will try this
      • cobra2
        squirrels: beets = teh shit.
      • squirrels
        but it seems the date of the last update is not saved
      • this would be usefull, ot update only the entries that weren't updated for a long time
      • cobra2
        what version of beets are you using?
      • squirrels
        let me check
      • 1.3.18
      • i mean: update != added
      • cobra2
        1.4.0
      • squirrels
        oh... really, than i need to update
      • cobra2
        i don't ever use the update feature.
      • i'm running the latest git.
      • and python3
      • squirrels
        i didn't know that python3 is already finished
      • :)
      • *beets for python3
      • cobra2
        well, 'beet update added:$(date -d '7 days ago' +%Y-%m-%d)'
      • worked just fine for me.
      • squirrels
        yes, it seems to work
      • thanks
      • cobra2
        i'm not familiar with 'beet info' is that a plugin?
      • squirrels
        yes, it's a plugin
      • cobra2: is 1.4.0 already stable?
      • cobra2
        no, it's not stable. I've been using it without fail for a couple months now.
      • squirrels
        ok, then I will stay with my current version
      • Kabouik has quit
      • Kabouik joined the channel
      • watsonalgas has quit
      • jrobeson
        uggh.. i want it to be done soon!
      • cobra2, somebody on the mailing list wanted a better syntax for querying by date. and your suggestion wouldn't work to well on windows as far as i know :(
      • cobra2
        jrobeson: i moved from that horrible OS 15 years ago. I couldn't even tell you how to find the date in msdos anymore.
      • jrobeson
        i never did know how to do it :)
      • but beets still supports it
      • so, we'd probably like to have something like date_added:"7 days ago" or whatnot
      • not just for windows, but in general of course
      • cobra2
        i usually use epoch. I thought '* days ago' was really user friendly
      • jrobeson
        thought? as in the past tense?
      • i'm confused
      • also i just woke up
      • cobra2
        hehe
      • '* days ago' for date in unix is easier than unix epoch for dates to newer users who might not be as familiar with ho wmany seconds have passed since 1970.
      • jrobeson
        but avoiding al the date formatting in the process, that's the unfriendly part
      • cobra2
        it would be nice if there was a way to invoke that in python.
      • jrobeson
        you wrote added:$(date -d '7 days ago' +%Y-%m-%d), and i just want added:'7 days ago'
      • cobra2
        well, here is the math for 7 days ago in seconds. -(60*60*24*7)
      • jrobeson
        that's just as bad :)
      • cobra2
        jrobeson: import datetime
      • now = datetime.datetime.now()
      • now.strftime("%Y-%m-%d")
      • errr.... str(now)
      • jrobeson
        oh you meant that date math for being inside the program earlier?
      • cobra2
        yeah,
      • just for refrence.
      • but this might be an easier way to get dates.
      • jrobeson
        () is valid in my fish shell
      • cobra2
        i'm in a python3 shell.
      • discopatrick
        what can i do if i've imported an album, and i think it was misidentified and tagged incorrectly?
      • jrobeson
        that is i'd be writing (right now) like : beets ls (date stuff)
      • reimport it
      • i always have it set with timid, so i can pick
      • beet import -t /path/to/files
      • but i have timid: yes in my config, so i don't use -t
      • discopatrick
        nice. i'm using the 'move' import setting - if i run this on an album that's already in the collection, i guess it will just move it to the new path after it's tagged?
      • jrobeson
        i have move too
      • discopatrick
        ok great.
      • cobra2
        if it's already in there.... you can reimport with a query that returns the album.
      • discopatrick
        i've run my initial import on my itunes directory in quiet mode... it's managed to do 33% on it's own, which is pretty good...
      • i think i'll lower the accuracy settings a bit and make another pass
      • cobra2
        probably would be a good idea to enable timid mode for sure. That way you don't get too many crazy fubar files.
      • discopatrick
        fubar? you mean tagged incorrectly?
      • watsonalgas joined the channel
      • jrobeson
        would they really be fubar? i hope not
      • discopatrick
        ...me too!
      • i guess, once something is tagged incorrectly, it can be harder to find
      • but most incorrect taggings will be something small like wrong version of an album or something
      • so no major damage done
      • i'm keen to have this first import done as automatically as possible. so i'm happy to leave timid off
      • it seems a lot of my failed imports on my first run were due to missing tracks on an album. i believe i can give missing tracks less importance when beets is scoring the match?
      • jrobeson
        sampsyo, you about?
      • thunderrd_ has quit
      • thunderrd_ joined the channel
      • discopatrick
        so if i do match: ... ignored: missing_tracks - it should score matches highly, even when i've got tracks missing?
      • jrobeson has never tried that
      • jrobeson
        i've been through a lot of beets internal code, but I haven't actually used it too heavily :(
      • like i've never wanted to tweak those settings
      • discopatrick
        gotcha
      • i'm going to try it anyway!
      • to be honest, this is still a "dry run"... i'm working on a copy of my itunes folder, not the original one... so once i've decided on the secret settings sauce, i'll do it all over again
      • any plans to make beets work with AccurateRip or a similar service?
      • cobra2
        what does accuraterip do?
      • discopatrick: this is kinda what I do on large libraries that have decent tags. I import everthing as-is to a database. make a backup of that so i have something to revert. Then reimport with 'beet import -L $QUERY"
      • i usually go through the foldernames with grep to see if anything got matched with strings from my inline filters.
      • discopatrick
        cobra2: yep, always good to have something to revert to. as a programmer, i'm really into change control... it would be great to be able to keep the library in a git repo (unfortunately the library is in binary format, and not human readable)
      • cobra2
        i find that importing a large library (400GB+)is just too tedious at one go.
      • discopatrick
        come to think of it, it's a sqlite db isn't it
      • cobra2
        sqlite3.
      • discopatrick
        accuraterip creates a checksum of the audio, and then verifies it against an online database. you can check whether you have any glitches or pops in your rip.
      • cobra2
        i'd love to see a postgres or mysql plugin for database myself since i have a machine already running databases for the house here.
      • linux user?
      • discopatrick
        accuraterip is meant for cd rips, but i can see how it could be applied to any type of file. the point is, you want to know whether most other people have the same checksum as you, or whether yours is slightly different
      • these days i am a linux/osx user, yes
      • there is some talk of bringing an accuraterip-like feature to musicbrainz
      • cobra2
        there is something for chromaprint or something like that which serves a similar function.
      • discopatrick
      • chromaprint is audio fingerprinting, which is slightly different, i believe
      • cobra2
        that seems more of a whipper (cd ripper) feature than a beets feature to me.
      • discopatrick
        audio fingerprinting is how shazam works, i think. it can match audio even with noise in the background.
      • accuraterip is a bit for bit comparison
      • cobra2
        gotta go be a dad for a while be back in an hour or so.
      • discopatrick
        well, i don't think it has to be limited to cd audio only
      • no worries :)
      • cobra2
        i guess little man isn't ready for bed yet.
      • Vacuity_ has quit
      • Vacuity joined the channel
      • discopatrick
        hmm... what to do if an import hangs?
      • hasn't moved on in about 30 mins
      • it's in quiet mode
      • hasn't shown any new information in that time
      • hmm... just terminated the terminal tab