Replies: 1 comment 1 reply
|
Thanks for reporting this — it was a real bug, and a bad one. Not your memory and not the context window. Fix is up in #48. What was happening When a recording stops, Logue re-transcribes it with a more accurate batch model and swaps that in for the live transcript. The audio it kept for that pass was capped at 30 minutes — but the swap replaced the whole session regardless of how much the batch pass had actually heard. So the live transcriber had your entire meeting, and the replacement threw away everything past the 30-minute mark, at the moment you hit stop. That's why it looked like a clean cut at exactly 30:00, and why memory usage looked low — the cap was holding the buffer at about 115 MB. What changes
Where that leaves things
Verified end to end against a five-hour two-speaker recording, plus a six-hour read-back test that holds under 4 MB resident. One thing worth saying plainly: the meetings you already recorded lost that text when you stopped, and this fix can't bring it back — the audio is still on disk, but the transcript past 30 minutes is gone. Sorry about that. Anything you record after this ships keeps all of it. |
Uh oh!
There was an error while loading. Please reload this page.
As per title, I've tried recording/transcribing a few meetings to play with Logue, and all the transcriptions seem to stop right at 30 minutes - is this a known limit, configurable, or a function of my system memory somehow (it doesn't seem to be using very much at all, and wouldn't expect it does for a small model, but realize it may be a limitation of the context window)
All reactions