What does that even mean? Why would OSS make it slower? Why would it be an overkill?
This is not Producthunt, you have to give at least some kind of explanation for your claims.
"Smart, invisible regex" sounds like a lot of bs... could you give a more technical explanation?
Also the Whisper model doesn't really have a context window, it already segments the audio with a certain amount of overlap between the chunks, I really have a hard time understanding what you are trying to say here.
This is just plain wrong. I have my own Whisper App in the AppStore (on iOS, with very limited memory capacity) and there are no problems at all with longer Audio / Video files.
This reflects my experience 1:1... even telling 2.5 Pro to focus on the tasks given and ignore everything else leads to it changing unrelated code.
It's a frustrating experience because I believe at its core it is more capable than Sonnet 3.5/3.7
The biggest problem rn is Apple's blocking of JIT for everything but browsers. This means neither UTM nor the more modern emulators can run at close to full speed.
I'd like to see this changed. This seems like the real "Gatekeeper".
JIT (Just-In-Time) compilation is a technique that allows certain programs to run significantly faster by compiling code at runtime, rather than ahead of time.
Apple enabled this for iOS 14+, but killed it again with iOS 17. It's basically the reason why we currently don't have full speed VM's on iOS / iPadOS devices.
While Sideloading / Altstore / Sidestore allows you to install any IPA, this still doesn't enable JIT for these apps. There are currently some workarounds that involve running certain software on your local network (search SideJITServer on Github).