The landing page is difficult to read due to the strong red background.

Thank you. I have heard this : P - It will change soon.

I learned this as a young developer writing status pages. I had a colour-blind colleague, so text on green/yellow/red.

Typically white text works better on red.

Reds people choose are usually between dark and light, which doesn't contrast particularly well on anything because for good contrast you need a dark color vs a light color.

Green, yellow, red or whatever hue is fine, as long as it's dark or light enough. Colorblind and non-colorblind people can see how dark or light a color is (luminance), but they might not agree on the hue. That's why WCAG contrast checks require luminance contrast and not hue contrast.

It's best to use a contrast checker because it's not always intuitive how dark or light a color is e.g. yellow and lime are almost as light as white.

Does it support speaker diarization?

Timecode drift is an interesting issue, think I faced this recently while translating a Google Meet transcript into an incident report timeline.

The elapsed-time timestamps didn't correlate well with other data sources. I figured it was a mistake on my end, and just brushed it off.

What is your tech stack to make this? Is it end to end swift?

Swift 37.0% C++ 26.5% C 19.8% Rust 4.7% Shell 4.4% Objective-C 1.7% Other 5.9%

What language do you have the model architecture and implementation in? Feel like it would be the biggest proportion of the codebase, curious if you did it in Swift?

How does it compare to MacWhisper?

MacWhisper crashes at about an hour of context. This uses, smart, invisible regex in the text generation pipe. Makes this fast. + bonus, there is no context limit

I am a MacWhisper Pro user, and I successfully transcribed and translated a 15-hour course inside the app without any issues

> MacWhisper crashes at about an hour of context.

This is not true. (I've been a MacWhisper user since 2023. I have two bugs during that time, which the author addressed quickly.)

I've done 3+hours with MacWhisper without issue? One downside is the transcription is not real time - can Scriber Pro do realtime?

I haven't worked in a while with transcription, but whisper.cpp itself (which I assume is the underlying tech behind MacWhisper) does realtime transcription on my MBP with an M1 Pro chip. When I first started writing my last completed novel, I fired it up and just started telling the story to test it out. Realtime.

That was back in 2023. I assume things work better now.

Smart invisible regex makes it fast and prevents it from crashing? What does that mean?

"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.

Whisper will fail > 99%* (edit, most of the time) of the time at lengths over 90 minutes and fairly high over one hour.

This is absolutely not my experience. I regularly (weekly at least) use whisper for 90-120 minutes pieces of content and only rarely have problems.

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.

I've never had whisper complete a single attempt a anything over 75 min

I’ve used whisper-cop on 5-hour podcasts without problems.

Would also love to hear what you mean by “smart invisible regex,” sounds like AI slop to me.

Can't really declare that without declaring which whisper model in particular you are referring to, as there are a number of them

What do you mean context limit?

Neither whisper nor MacWhisper have any context limit

> Smart invisible regex

I've never heard a regex person speak this way of a regex.

Please tell me you didn't vibecode the regex... one of the areas it's still not good at