Seiten, Taisei

4.5K posts

Seiten, Taisei banner
Seiten, Taisei

Seiten, Taisei

@lekandev

Oh Captain! My Captain!

The cosmos Katılım Mayıs 2020
2.1K Takip Edilen348 Takipçiler
Tairu 👨🏽‍💻
Tairu 👨🏽‍💻@TayCode·
"Am I a munafiq" a frequent question that goes through my mind
English
1
1
3
421
Seiten, Taisei retweetledi
Oladimeji
Oladimeji@uxdimeji·
day 14 of posting my design everyday in march. scholar - imagine you could throw a research topic at Claude, GPT, etc all at once and they all work on it together, fact-check each other, then hand you back a full paper with real sources. will share more screens soon.
Oladimeji tweet mediaOladimeji tweet mediaOladimeji tweet media
English
1
4
8
118
Seiten, Taisei retweetledi
OnyinyeMo the Tech Scribe✨
OnyinyeMo the Tech Scribe✨@Momooinreallife·
@lekandev This is very well worded. As a writer, I am totally onboard with this lol. Fable!!
English
1
1
1
23
Tairu 👨🏽‍💻
Tairu 👨🏽‍💻@TayCode·
There is something Thomas Shelby said in peaky blinders that always stays with me. Lemme see if I can find it.
English
2
0
3
693
Seiten, Taisei retweetledi
مُحَمَّد
مُحَمَّد@niyiokeowo·
It's not much. It's getting there.
مُحَمَّد tweet media
English
6
14
152
2.2K
yazin
yazin@yazins·
here we go again.. a new fastconformer fine-tune: - added RetaSy noisy crowd recordings mapped to canonical phonemes (1.6K train + 183 val samples) - duration alignment (15s→30s max) so long ayahs aren't truncated - audio augmentation (speed, gain, noise, shift, silence) target is 95% on the streaming run, though probably going to require multiple training runs to get right.
yazin tweet media
yazin@yazins

update: the phoneme model works. trained a small ONNX model that runs entirely in the browser, converts recitation audio into phoneme text, then fuzzy-matches against all 6,236 verses of the Quran. no server, no internet. single verse recognition on clean audio is solid (~90%). The hard part turned out to be... well... EVERYTHING ELSE. real usage means short verses (~2sec audio), long verses (80+ seconds), people reciting multiple verses back to back, background noise, different accents. that mix brings accuracy down to ~70%. real-time identification (figuring out the verse while you're still reciting) is even harder: 62%. You only have ~2 seconds of audio at a time, so you're comparing a tiny fragment against full verses. and the matching algorithm punishes that size mismatch, so wrong verses that happen to be similar in length to your fragment outscore the correct ones. i've been iterating on the matching layer for like 3 days. semi-global alignment, beam tracking, partial window scoring. each buys 1-2% and hits a wall. starting to think the next jump needs a fundamentally different approach -- either a better model, different matching paradigm, or both. if you've worked on fuzzy matching against a fixed corpus, audio fingerprinting, or similar problems -- please reach out. constraint: everything has to run client-side in the browser, so no GPU!

English
9
3
58
6.2K