Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ux
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
Kanji 3D Mapping fun hack
(blog.pkh.me)
3 points
by
ux
13y ago
|
0 comments
122.
▲
Learning Japanese the nerd way
(blog.pkh.me)
5 points
by
ux
14y ago
|
0 comments
123.
▲
by
ux
14y ago
Interesting, so you have a way of making the relationship at the end. Now I could start nitpicking about how you decide to make the link to Aphex Twin and not his name (or another nick), and how would you make that decision for any similar
124.
▲
by
ux
14y ago
You mean by having a guy to ask where to find something because you're lost in the store and can't find shit?
125.
▲
by
ux
14y ago
I was actually talking about browsing. The musical content analysis has the goal to provide new ways of representing your music, and browse it.
126.
▲
by
ux
14y ago
Well, it's the same person behind. Even if the artist tried to give a different "personality" to his music over the time, following all his creations is actually a good listening experience. The "hey I just want to listen to the musical evo
127.
▲
by
ux
14y ago
Nice, I'm sure a lot of people would be interested in trying this. But talking to myself, I'm disgusted with all of this, so I'm just maintaining my mess in its current state for now. Still, I like to see such solution, and I'd be really in
128.
▲
by
ux
14y ago
It would be interesting to make an analysis on how MusicBrainz deals with all these problems, I admit I didn't look much into this. But AFAICT it wouldn't really solve the file system problem, except if you decide to name your files with a
129.
▲
by
ux
14y ago
I wonder how often a bit exact copy of one song appears... Sure the songs might have the same title and duration, but some very trivial edits might be done. You need to be extra careful when identifying these songs as identical if you don't
130.
▲
The music classifying nightmare
(blog.pkh.me)
98 points
by
ux
14y ago
|
75 comments
131.
▲
by
ux
14y ago
Feel free to use plugins like Stylish :) Do you have any suggestion for the CSS?
132.
▲
by
ux
14y ago
This really changed a lot, see http://fate.ffmpeg.org/ We now test all the code through valgrind; a single memory leak will complain. There are also static analysis, and various other checks. And BTW, you can't treat warnings as errors. J
133.
▲
by
ux
14y ago
We did some work to improve this a little, see for example: http://git.videolan.org/?p=ffmpeg.git;a=tree;f=doc/examples;... This should be deployed with any new fresh ffmpeg install. The filtering code is still unstable due to what's expl
134.
▲
The FFmpeg/Libav situation
(blog.pkh.me)
150 points
by
ux
14y ago
|
51 comments
135.
▲
GameBoy crackme based on Pokémon universe
(blog.pkh.me)
7 points
by
ux
15y ago
|
0 comments
136.
▲
Fun reverse of a Dune game
(blog.pkh.me)
3 points
by
ux
15y ago
|
0 comments
137.
▲
by
ux
15y ago
I just fixed that paragraph. It will hopefully avoid some confusion. By the way, x264 isn't really a codec, it is just an encoder. I'm also not sure calling H.264 a video format is really correct, it's more like a codec standard to me. But