Thanks #147
-
|
Amazing initiative, thank you for building it open source! I’ve noticed the GB usage is slowly increasing. Could you explain why that is and what this data is being used for? Best, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Thank you for your kind words. If you’re referring to this: This shows the number of KB (or GB) of audio data processed by Murmure this month. Data that would have been sent to the cloud if you were using a cloud-based solution like WisprFlow. With Murmure, voice data is processed entirely on your device. Nothing is sent externally and nothing is stored except for the last five transcriptions. You can also change this in the settings to keep them in memory (RAM) only instead of saving them to disk. If you hover over the indicators, you’ll see a short explanation of what each one represents: |
Beta Was this translation helpful? Give feedback.
-
|
Amazing, yes, that’s exactly what I was referring to you answered my question doubts I had about the local storage on my machine. The tool runs smoothly, with very little latency. It’s extremely handy and has already saved me a lot of time!! I’m convinced that the future of development will be more speech-based and we’re getting there quickly. Have fun building it! Maybe you should add a small tooltip icon like that because I didn't realized it could be hovered. |
Beta Was this translation helpful? Give feedback.
Thank you for your kind words.
If you’re referring to this:
This shows the number of KB (or GB) of audio data processed by Murmure this month. Data that would have been sent to the cloud if you were using a cloud-based solution like WisprFlow.
With Murmure, voice data is processed entirely on your device. Nothing is sent externally and nothing is stored except for the last five transcriptions. You can also change this in the settings to keep them in memory (RAM) only instead of saving them to disk.
If you hover over the indicators, you’ll see a short explanation of what each one represents: