2005-04-29, 01:46
hi,
i listened to some sid's tonight, and started wondering what the name of one of the tunes were..
the result, hvsc (high voltage sid collection) documents/stil.txt support (limited to one tune per .sid right now..)
work mostly done by lala, due to his parsing class
a few problems
- it's "a bit" slow (that's what you get when you choose a lousy custom file format). i could probably make a lousy-to-xml converter to speed things up a bit, if i feel like it later.
- since i use lala's parsing class, it needs the documents/stil.txt to be in a local directory (it uses fstream's, could probably be replaced by a stringstream+memory cache+streambuf later on), or even better, i could replace the whole parser.
- in order to be able to perform the lookup the sid's need to be in the original hvsc paths, and artist/stuf.sid must be in a directory of the form "whateverprotocol://whateverdir/hvsc/artist/stuf.sid", since it needs to be able to identify the hvsc root dir.
- i were surprised to notice that there is no comment field in xbmc's tag structure. since there is a lot of comments in stil.txt, i was a bit disappointed.
is this something that could/would be integrated into cvs?
spiff
i listened to some sid's tonight, and started wondering what the name of one of the tunes were..
the result, hvsc (high voltage sid collection) documents/stil.txt support (limited to one tune per .sid right now..)
work mostly done by lala, due to his parsing class
a few problems
- it's "a bit" slow (that's what you get when you choose a lousy custom file format). i could probably make a lousy-to-xml converter to speed things up a bit, if i feel like it later.
- since i use lala's parsing class, it needs the documents/stil.txt to be in a local directory (it uses fstream's, could probably be replaced by a stringstream+memory cache+streambuf later on), or even better, i could replace the whole parser.
- in order to be able to perform the lookup the sid's need to be in the original hvsc paths, and artist/stuf.sid must be in a directory of the form "whateverprotocol://whateverdir/hvsc/artist/stuf.sid", since it needs to be able to identify the hvsc root dir.
- i were surprised to notice that there is no comment field in xbmc's tag structure. since there is a lot of comments in stil.txt, i was a bit disappointed.
is this something that could/would be integrated into cvs?
spiff