Transcribe.cpp
workshop.cjpais.com
Transcribe.cpp
1–10 of 180 posts
Re: Transcribe.cpp
#2Re: Transcribe.cpp
#3> I think as we look forward to the future, more inference will start happening locally for one reason or the other. This brings the distribution story front and center. In order to have more applications running inference locally, we need to make running inference easier.
This makes these projects so much more trustworthy and easier to approach:
> Were any of the words here written using AI? Nope. They came from my mouth or my fingers.
Re: Transcribe.cpp
#4Re: Transcribe.cpp
#5Spot on: > I think as we look forward to the future, more inference will start happening locally for one reason or the other. This brings the distribution story front and center. In order to have more applications running inference locally, we need to make running inference easier. This makes these projects so much more trustworthy and easier to approach: > Were any of the words here written using AI? Nope. They came…
>> Were any of the words here written using AI? Nope. They came from my mouth or my fingers.
I have to push back on this a bit, as I believe (quite strongly) that we're shaped by the tools we use; text-to-speech LLMs are still LLMs, and generally their mistakes are shaped by the expectations inherent in their training. This, in turn, shapes the words that appear on the screen. For those who regularly use them, you then learn which word sequences are likely to be accurately transcribed, and this definitively becomes part of your thinking process. Over time, the LLM becomes tangled into your thinking; the use of AI, even in this way, very much can and often does shape the resulting words.
Re: Transcribe.cpp
#6Re: Transcribe.cpp
#7Re: Transcribe.cpp
#8Excellent work, paired with the 500kb TTS model headlining today I can see the full stack coming together.
Re: Transcribe.cpp
#9would love to see a demo handy is fantastic although its still behind the frontier models