Live data from Hacker News

Transcribe.cpp

workshop.cjpais.com

31–40 of 180 posts

Re: Transcribe.cpp

#31
> Maintainer supported bindings in 4 Languages

Nice. Here's the Python one: https://github.com/handy-computer/transcribe.cpp/tree/main/b... - looks like it's not yet available as a binary wheel on PyPI with the dependency included (the library on PyPI right now uses ctypes to call a separately installed library) but that's planned for a future release.

Re: Transcribe.cpp

#32
post #6

I saw that metal is almost x10 faster than vulkan? Why so much gap?

It very much depends on the hardware! An M4 max is being compared against a Ryzen 4750U with an integrated GPU!

The M4 max has probably 10x the compute and memory bandwidth hahaha

Re: Transcribe.cpp

#33
post #24
post #17

What's the easiest way to add speaker separation to this?

Hey! It’s actually in progress right now, probably will come this week :)

Awesome! I found the in-progress diarization PR here: https://github.com/handy-computer/transcribe.cpp/pull/85

Looks like it's using IBM's Granite-Speech-4.1-2B-Plus https://huggingface.co/ibm-granite/granite-speech-4.1-2b-plu... and/or MOSS-Transcribe-Diarize https://huggingface.co/OpenMOSS-Team/MOSS-Transcribe-Diarize

Re: Transcribe.cpp

#34
post #31

> Maintainer supported bindings in 4 Languages Nice. Here's the Python one: https://github.com/handy-computer/transcribe.cpp/tree/main/b... - looks like it's not yet available as a binary wheel on PyPI with the dependency included (the library on PyPI right now uses ctypes to call a separately installed library) but that's planned for a future release.

Yes, I’ve put a PR up on pypi for extra storage for CUDA but it has not been accepted yet afaik

If there’s any issues or improvements on the bindings I would love help to make the DX the best it can be

Re: Transcribe.cpp

#35
post #11

Congrats on shipping this. I love handy on my Mac, my phone for STT in situations where it’s not possible/poor performance of the native Model for STT(e.g apple’s thing is not upto scruff, like mistranslating words corresponding to a domain). Noob question: How do you think about funding from a foundation(i have no clue if you need it or not, I do hope you have a way to get paid one way or another because handy is am…

Thanks! What an excellent question, I’m not sure I have a good answer. I kind of became an open source maintainer by accident as Handy became popular

Certainly I am very lucky that quite a few people donate to Handy, and also some people and organizations who sponsor the work I do

To be honest I just love contributing to open source and wish to continue to do so. So anyone who supports this is good to me. Organizations which believe in OSS and push it forward are typically most aligned with me

Of course you can always email me (contact@handy.computer) and we can discuss in more detail

Re: Transcribe.cpp

#36
post #33
post #24

Earlier quoted context omitted.

Hey! It’s actually in progress right now, probably will come this week :)

Awesome! I found the in-progress diarization PR here: https://github.com/handy-computer/transcribe.cpp/pull/85 Looks like it's using IBM's Granite-Speech-4.1-2B-Plus https://huggingface.co/ibm-granite/granite-speech-4.1-2b-plu... and/or MOSS-Transcribe-Diarize https://huggingface.co/OpenMOSS-Team/MOSS-Transcribe-Diarize

Yep, but I am in the process of also porting NVIDIAs Sortformer for multi speaker diarization as well :)

I’m not sure how many specific models will be supported as the library is more focused on transcription specifically. But the models which support diarization natively must be supported I think. And parakeet multitalker was the primary driving force for this change

Re: Transcribe.cpp

#37

Congrats on delivering good value to the people. I have used transcribe.cpp a few weeks ago to do near realtime offline stt on a 10 year old phone, writing simple adhoc app for my use case, it's crazy what is happening right now.

Ha amazing, love to hear it

Re: Transcribe.cpp

#38

Spot 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…

>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. 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 t…

[deleted]

Re: Transcribe.cpp

#39
What's the best local TTS model right now? I'm running parakeet on a mac which transcribes all my uh's and aahs. I'm running whisper on linux/cuda and I by far prefer that one over parakeet.

Re: Transcribe.cpp

#40
post #39

What's the best local TTS model right now? I'm running parakeet on a mac which transcribes all my uh's and aahs. I'm running whisper on linux/cuda and I by far prefer that one over parakeet.

> parakeet on a mac which transcribes all my uh's and aahs

You should be able to fix this by playing with the mic speech floor. It happens when to much ambient stuff slurps in.

It's actually gaslighting you, you don't say that many ums and ahs ;)

Post reply on HN