If you're also getting a 500: https://web.archive.org/web/20250106075631/https://nickfa.ro...
I just restarted the webserver. It's running on OpenBSD HTTPd + MediaWiki + SQLite, and keeping it up has been a perpetual thorn in my side. Oh well. I need to figure out some alternative setup probably.
OCRing Music from YouTube with Common Lisp
11–20 of 20 posts
Re: OCRing Music from YouTube with Common Lisp
#12Earlier quoted context omitted.
I just restarted the webserver. It's running on OpenBSD HTTPd + MediaWiki + SQLite, and keeping it up has been a perpetual thorn in my side. Oh well. I need to figure out some alternative setup probably.
Is your VPS on OpenBSD.Amsterdam by any chance? (The 46.23. . address seems familiar.)
Re: OCRing Music from YouTube with Common Lisp
#13Earlier quoted context omitted.
Is your VPS on OpenBSD.Amsterdam by any chance? (The 46.23. . address seems familiar.)
Yep, that's it. The host is (for the most part) fine, but there's either some problem with httpd or the PHP worker pool where it just dies after some number of requests.
The service is indeed great, Mischa does an excellent job.
Yeah PHP on httpd can be flaky, I'd wish for a lighter solution for wikis.
Re: OCRing Music from YouTube with Common Lisp
#14to compare two images, i1 and i2
l1 = length(gzip(i1))
l2 = length(gzip(i2))
l12 = length(gzip(concatenate(i1, i2))
ncd = (l12 - min(l1, l2))/max(l1, l2)
Here is a nice article where I found out about this long ago.https://yieldthought.com/post/95722882055/machine-learning-t...
From the article:
"Basically it states that the degree of similarity between two objects can be approximated by the degree to which you can better compress them by concatenating them into one object rather than compressing them individually."
[1] https://en.wikipedia.org/wiki/Normalized_compression_distanc...
Re: OCRing Music from YouTube with Common Lisp
#15Re: OCRing Music from YouTube with Common Lisp
#16Instead of doing a diff, curious if Normalized compression distance (NCD)[1] will yield a better result. It is very simple algorithm: to compare two images, i1 and i2 l1 = length(gzip(i1)) l2 = length(gzip(i2)) l12 = length(gzip(concatenate(i1, i2)) ncd = (l12 - min(l1, l2))/max(l1, l2) Here is a nice article where I found out about this long ago. https://yieldthought.com/post/95722882055/machine-learning-t... From t…
It probably would have added the overhead from compression which in my case would have been detrimental.
Re: OCRing Music from YouTube with Common Lisp
#17Instead of doing a diff, curious if Normalized compression distance (NCD)[1] will yield a better result. It is very simple algorithm: to compare two images, i1 and i2 l1 = length(gzip(i1)) l2 = length(gzip(i2)) l12 = length(gzip(concatenate(i1, i2)) ncd = (l12 - min(l1, l2))/max(l1, l2) Here is a nice article where I found out about this long ago. https://yieldthought.com/post/95722882055/machine-learning-t... From t…
Oh interesting, I remember comparing images before, I think I was doing a diff as well, so I suppose this would have worked? Nice to know! They were very small images though. It probably would have added the overhead from compression which in my case would have been detrimental.
Re: OCRing Music from YouTube with Common Lisp
#18honestly this would be better with an AI model
> honestly this would be better with an AI model In the article the author tried Tesseract which uses ML and has some neural network models, and also tried ChatGPT. I have come to the same conclusion as the author when doing OCR that needed 100% accuracy. When you know the font, spacing and the layout is fixed, old school statistical analysis of the pixels works a treat.
It's a bit more effort to set up since you actually have to set it up. But at least it's done right.
Re: OCRing Music from YouTube with Common Lisp
#19Earlier quoted context omitted.
I just restarted the webserver. It's running on OpenBSD HTTPd + MediaWiki + SQLite, and keeping it up has been a perpetual thorn in my side. Oh well. I need to figure out some alternative setup probably.
Modify your DNS to put cloudflare or bunny in front of it and you'll be good. Don't stop self-hosting :)
Re: OCRing Music from YouTube with Common Lisp
#20Instead of doing a diff, curious if Normalized compression distance (NCD)[1] will yield a better result. It is very simple algorithm: to compare two images, i1 and i2 l1 = length(gzip(i1)) l2 = length(gzip(i2)) l12 = length(gzip(concatenate(i1, i2)) ncd = (l12 - min(l1, l2))/max(l1, l2) Here is a nice article where I found out about this long ago. https://yieldthought.com/post/95722882055/machine-learning-t... From t…
Oh interesting, I remember comparing images before, I think I was doing a diff as well, so I suppose this would have worked? Nice to know! They were very small images though. It probably would have added the overhead from compression which in my case would have been detrimental.