▲ | mastazi 3 days ago | |||||||
From the website > Recording system audio is still very clunky: audio routing hacks, third-party tools that aren't meant for the task - too many steps. I really love the idea because I'm one of the people who previously had to use those hacks! But I wonder what are the privacy implications? Maybe the OP could clarify that this: > RM2000 Tape Recorder just listens. Whatever your Mac is playing, it can record it instantly means that nothing is retained unless explicitly recorded by the user, right? There isn't cache somewhere that captures last X minutes of audio or anything like that? | ||||||||
▲ | marcelox86 3 days ago | parent [-] | |||||||
version 1.0.1 does keep a cached file undeleted (due to an oversight)....and has a lot of other bugs. version 1.0.2 doesnt! On the other note - right now RM2000 Tape Recorder uses the ScreenCaptureKit API. This is the worst API i've ever used - every app i've tried out that uses it (Polycapture, QuickRecorder, Ayazaka) has had EXC_BAD_ACCESS problems with it, and sometimes it causes `replayd` to consume 5% of cpu even after the recording is done. I plan to move all the recording into a CoreAudio API, which is not only stable, but also has the added benefit of being more privacy conscious - it only uses the "record system audio" macOS permission instead of the "record the ENTIRE screen" permission. right now, the app does the bare minimum of trying to record the screen. it captures a 2 x 2 window of the screen, and it throws away all the video buffers regardless. i've always felt like im actually doing something that apple wouldn't like and they just didn't see it. moving to the new API is one of my top priorities, and it still lets me keep the minimum requirement at macOS 14.6+ | ||||||||
|