Conversation
|
Why not to use sqlite? Is embeddable database and available out of box everywhere. |
|
@Starmel I saw there's a SQLite file above the directory where .wav files are. That's what you mean? Because from code I assume that Apple is silently using SQLIte as a store, but it can ... change? |
sqlite3 recordings.sqlite "select * from recordings;" |
|
@Starmel I want to get JSONs checked into the repo, for versioning. I know the SQLite is there, and I saw we're using RecordingStore which I think is Swift's way of saying "some data store". Is Apple guaranteeing that it's going to stay to be SQLite across OSXes? If so, perhaps saving JSONs is indeed unnecessary. |
|
RecordingStore Is just a class which uses sqlite. Is not an apple framework to work with data. To work with sqlite used popular library. I don't think there any compatibility issues can be. |
|
@Starmel OK. This is great. Sounds like we're already using SQLite explicitly! Let me think how to get what I want. I think I could just write a Python script to dump the SQLite from OpenSuperWhisper to my directories. Originally I was thinking of this:
Users that want to save the transcripts to git repos would check this, and have .JSONS go to git, and .wav perhaps to a backup. |
|
@Starmel perhaps we need a trigger of some sort? e.g.: post-recording trigger script. |
|
Probable this can help you to make trigger and catch event when transpiration ready. https://developer.apple.com/documentation/foundation/distributednotificationcenter |
|
@Starmel I'm thinking about this one - would you be OK with adding post-record hook (script call) ? I'd be able to do whatever I want if we had it. |
2 participants
I want to have a tech-independent way to save metadata as JSON and perhaps read it with some scripts.
POC version of MR here -- those changes [done with OpenAI Codex] look very similar across 3 files. Perhaps we should refactor this chunk of code to the separate function?