Transcript Detail
Transcript #34866
Playback
Status: completed · Language: en · Source: Behnam · Captured: 2026-08-20 17:39:15 · Open quote, audio containing a speaker, fixed dimensional speaker embedding, close quote. You then compare that embeddin
Open quote, audio containing a speaker, fixed dimensional speaker embedding, close quote.
2026-08-20 17:39:15 - 2026-08-20 17:39:19You then compare that embedding against the embeddings in QDRAFT.
2026-08-20 17:39:20 - 2026-08-20 17:39:23NVIDIA describes TITANET as a speaker representation model intended for speaker verification and diarization
2026-08-20 17:39:23 - 2026-08-20 17:39:28and provides direct methods for extracting embeddings.
2026-08-20 17:39:28 - 2026-08-20 17:39:30And here's the really encouraging part for your machine.
2026-08-20 17:39:31 - 2026-08-20 17:39:33TITANET large is only about 23 to 25 million parameters.
2026-08-20 17:39:33 - 2026-08-20 17:39:36The actual .NEMO checkpoint is only about 102 megabytes.
2026-08-20 17:39:36 - 2026-08-20 17:39:40For comparison, even just the FP32 waits for 23 M parameters are only roughly 23 million times 4 bytes and 92 megabytes.
2026-08-20 17:39:40 - 2026-08-20 17:39:48There will obviously be additional VRAM for activations, CUDA, PyTorch NEMO buffers, batching, etc.
2026-08-20 17:39:48 - 2026-08-20 17:39:52NVIDIA doesn't appear to publish an official TITANET requires XGB VRAM figure, so I don't want to fabricate one.
2026-08-20 17:39:53 - 2026-08-20 17:39:58But this is emphatically not an 8 gigabyte class model.
2026-08-20 17:39:58 - 2026-08-20 17:40:01I would expect TITANET inference itself to occupy well under a couple of gigabytes
2026-08-20 17:40:01 - 2026-08-20 17:40:04and probably substantially less with modest batch sizes.
2026-08-20 17:40:04 - 2026-08-20 17:40:07More importantly, you can run it with very small...
2026-08-20 17:40:07 - 2026-08-20 17:40:10...small batches because Berai isn't latency sensitive.
2026-08-20 17:40:10 - 2026-08-20 17:40:12So on your RTX 3060 Ti 8...
2026-08-20 17:40:12 - 2026-08-20 17:40:14Diarization Windows
2026-08-20 17:39:15 - 2026-08-20 17:39:19
2026-08-20 17:39:19 - 2026-08-20 17:39:20
2026-08-20 17:39:20 - 2026-08-20 17:39:31
2026-08-20 17:39:31 - 2026-08-20 17:39:48
2026-08-20 17:39:48 - 2026-08-20 17:39:53
2026-08-20 17:39:53 - 2026-08-20 17:39:58
2026-08-20 17:39:58 - 2026-08-20 17:40:01
2026-08-20 17:40:01 - 2026-08-20 17:40:01
2026-08-20 17:40:01 - 2026-08-20 17:40:03
2026-08-20 17:40:03 - 2026-08-20 17:40:07
2026-08-20 17:40:07 - 2026-08-20 17:40:12
2026-08-20 17:40:12 - 2026-08-20 17:40:14