-
alus_ joined the channel
-
alus_ has quit
-
alus_ joined the channel
-
jams has quit
-
alus has quit
-
alus_
alus_ is now known as alus
-
klang has quit
-
jwatk03 joined the channel
-
IsaacX has quit
-
jwatk03 has quit
-
euskir joined the channel
-
euskir
hello from Argentina
-
ruaok
hi!
-
greetings from California!
-
euskir
I know the place, nice....
-
ruaok
I've never been to .ar :-(
-
euskir
we have a lot of places quite "Californian"...
-
that's why we have such god wines :D
-
good I mean...Sorry God
-
ruaok
heh. I prefer .ar wines over .ca wines any day.
-
euskir
yes Gallo it's just begining... 9.9
-
ruaok
As in E&J Gallo? That's not wine.
-
I live smack in the middle of wine country.
-
We practically have it coming out of our asses. :-)
-
euskir
well, Iwas trying to be friendly... I didn't know you were a wine expert
-
ruaok
I wouldn't call myself and expert, but around here its hard to avoid. :-)
-
euskir
I know it's like the people here living in Mendoza or San Juan states (provinces here)
-
I was exploring rooms, testing Colloquy...
-
euskir has left the channel
-
euskir joined the channel
-
euskir has left the channel
-
Knio
Knio is now known as Knio-sleep
-
alus has quit
-
alus_ joined the channel
-
alus_
alus_ is now known as alus
-
alus has quit
-
MacIntyre has quit
-
bkdelong_ joined the channel
-
yalaforge joined the channel
-
yalaforge
yawn
-
yalaforge wonders what to do with this morning
-
ruaok
run naked through the streets
-
yalaforge
lol
-
too cold :-)
-
ruaok
we just went for our inaugural soak in our new hot tub.
-
what an ordeal getting that installed, but its finally done.
-
yalaforge was reading the playlist mailing list
-
yalaforge
not pleasant either
-
ruaok
nope.
-
painful, indeed.
-
yalaforge
I'm glad someone explained me the point in XML
-
very embarrassing that I didn't get it after all those years ;->
-
ruaok
eh?
-
which point?
-
yalaforge
that you can add elements later and don't break existing parsers :-)
-
ruaok
oh.
-
ya. :-)
-
I learned SGML 4-5 lives ago.
-
Horribly complex, but pretty cool.
-
xml is all the best of SGML.
-
yalaforge
much simpler
-
ruaok
so when xml came around, I was sold, right off the bat.
-
yalaforge tried to write a DSSSL stylesheet in the old days
-
yalaforge
pure horror
-
ruaok
I never even heard of that. What timeframe was that?
-
yalaforge
it was quite popular 7-10 years ago
-
it's a lisp dialect
-
ruaok
ick.
-
yalaforge
people tried to use it for XML, too
-
with emphasis on 'tried'
-
ruaok
I was never fond of lisp, ml or prolog.
-
duerra has quit
-
yalaforge hates prolog
-
yalaforge
lisp is kind of cool for toy problems
-
duerra joined the channel
-
ruaok
I used to have Turbo Prolog, but that was the ONLY language I never managed to write a meaningful program in.
-
yalaforge
anyway, I think I'll hack on mb_index today
-
ruaok
:-)
-
yalaforge
in the evening I think I'll have updating via XML packages implemented
-
ruaok
I was just thinking the same. I want to finish the last set of codings for libtp.
-
yalaforge
testing takes much, much longer
-
ruaok
Go to bed, debug it in the morning.
-
yalaforge
:-9
-
:-)
-
ruaok
sounds like we're in similar places.
-
I can't wait to go back to python.
-
And my first goal is to replicate the tag editing features in easy tag.
-
yalaforge really has to install easytag
-
Just have a solid tagging app, and then load the cool identification features on top.
-
apt-get install easytag
-
yalaforge
whoo. could it be so easy :-)
-
ruaok
its not the greatest program, but it conveys some important features.
-
:-)
-
ok, I'l off to coding.
-
yalaforge
ok, have fun!
-
ruaok
s/l/m/g
-
ruaok loves regexp
-
du auch!
-
yalaforge
danke
-
ruaok
yalaforge: you still around?
-
yalaforge
yup
-
ruaok
can I bounce an idea off you?
-
yalaforge
sure
-
ruaok
ok, think libtunpimp.
-
pipeline architecture.
-
yalaforge
ok
-
ruaok
we used to have an analyzer that did metadata read and TRM at the same time.
-
since picard will do more album oriented lookups, the need for TRM is less.
-
Thus metdata read and TRM have been decoupled.
-
yalaforge
so you want to split the thread, too?
-
ruaok
yes.
-
yalaforge
sounds sensible
-
ruaok
keeping functional blocks seperate
-
that's all pretty much past tense.
-
the question I have is this...
-
It used to be that a track through libtp had a certain path, and all the transitions were obvious.
-
pending -> trm lookup -> (rec, unrecog, error)
-
but now we have:
-
readmetdata -> unidentified or TRM
-
but the read metadata doesn't yield any info to make this decision.
-
The caller needs to direct the flow of the track.
-
Is this track TRM bound?
-
Or just readmetadata -> recognized or unrecognized?
-
does the problem make sense?
-
yalaforge
I'd readmeatadata, then query the web service
-
if unrecognized, then TRM
-
ruaok
well...
-
kinda.
-
yalaforge
that way it stays a linear pipeline
-
ruaok
you have to add a number of tracks and then perform that album lookup on those number of tracks.
-
so where do some tracks go while new tracks are being added?
-
yalaforge
you need a thirds state (recognized, unrec., accumulating)
-
right?
-
ruaok
now I am wondering if I make too mcuh of this.
-
seems like its getting complicated.
-
yalaforge
hm ...
-
ruaok
The read metadata should move a file to either recognized or unrecognized.
-
The caller should watch the messages for tracks that appear unrecognized.
-
And move them along by doing:
-
1. nothing.
-
2. clustering into an album and doing and album lookup while it stays in unrecognized.
-
3. set to pending for TRM generation.
-
Yes, that makes sense.
-
The tagger will need to get modified to look for unidentified files that have no TRM.
-
For those files, just move them to pending and keep chugging.
-
ruaok looks like the problem solved itself by explaining it.
-
:-)
-
Thanks for listening. :-)
-
yalaforge
np :-)
-
lol