#beets

sup

hrm..

I'd give this primary type "album"

secondary type "compilation" ?

oops

not #musicbrainz

hello

sampsyo: happy 4th!

sampsyo: have you guys changed from sqlite + custom ORM to sqlalchemy or similar yet?

That would be nice as sqlite really should only be used for dev or small things and doesn't handle over 10,000 song entries well

meh 10,000 records isn't that much

ThomW: Its probably way more, sqlite is just extremly slow at it

5,731 all artists

hm I'm having no trouble at all

1,314 album artists

4,067 albums

308 genres

30,997 songs

Those are my states from subsonic

subsonic isn't really reliable in my experience

beet stats takes 2.8 seconds, but that isn't too suprising since it does sum up everything

its better for me compared to beets because beets uses sqlite which is slow, not sure what subsonic uses but its probably relational

subsonic uses Hbase

35k songs, counted in almost an minute by beets: http://pastebin.com/v2mSCHSu

querying is the problem

DjSlash: interesting that it takes so much longer for you

756.23 GB (~ 2,311 hours)

why isn't beets relational though?

ThomW: might be due that machine being a P4 :)

lol

its using a relational database with relational data

DjSlash: gl with your energy bill

sqlite is a rdbms sec^nd

ThomW: yeah... but beets isn't using it in a relational way

I think it is

exploring the schema

that it doesn't have REFERENCES ON doesn't really matter

hmm replaygain is causing crashes with gstreamer0.10 on import

while beet replaygain uses gstreamer1.0

which is also weird

ThomW, do you have bpd enabled?

nope

oh, and if I remove 'replaygain' from plugins import does work

and I already installed python-gst* from apt

because loading both 0.10 and 1.0 in the same process doesn't work / crashes (not sure how beets handles plugins..)

ive noticed i think that beets used both 0.10 and 1.0. i could be wrong though. I think the replaygain and chromaprint use different versions

the chromaprint page tells you to install python-gst0.10-dev and replaygain mentions gstreamer 1.0

ah indeed, beets -> chroma -> pyacoustid -> audioread -> gst0.10

i ran into that the other day when trying to use replaygain, but instead opted to have it use mp3gain instead of gstreamer

I've got almost everything in FLAC

I don't think mp3gain works on FLAC

ThomW: you're correct

i have the same problem actually

i have gst1 and plugins-good installed, and whenever i try to use it as backend for replaygain, it can't initialize and i verbose mode doesn't provide much additional insight

sampsyo: i noticed that beet -h and beet help do not produce the same result, i.e. beet -h omits plugin commands. is this by design?