Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System audio capture not working from MacBook speakers with macOS 14.5 #101

Closed
htalvitie opened this issue Aug 3, 2024 · 4 comments
Closed

Comments

@htalvitie
Copy link

Have not been able to record system audio at all with screenpipe. Microphone recording works without issues. Running version 0.1.48 on macOS 14.5.

CLI output produces following error early during execution:

[2024-08-03T13:16:58Z INFO  screenpipe_audio::core] device: "MacBook Pro Speakers (output)"
[2024-08-03T13:16:58Z INFO  screenpipe_server::core] Finished record_and_transcribe for device MacBook Pro Speakers (output) (iteration 1)
[2024-08-03T13:16:58Z ERROR screenpipe_server::core] Error in record_and_transcribe for device MacBook Pro Speakers (output) (iteration 1): The requested stream type is not supported by the device., stopping thread
[2024-08-03T13:16:58Z INFO  screenpipe_server::core] Exiting audio capture thread for device: MacBook Pro Speakers (output)
[2024-08-03T13:16:58Z INFO  screenpipe_server::core] Handle for device MacBook Pro Speakers (output) has finished

Above run was produced by executing screenpipe --audio-device "MacBook Pro Speakers (output)".

Have attempted to use BlackHole (as mentioned in #90), but without success.

Wondering, if my issue is the same as described in #70 (comment), i.e. system audio recording not working on macOS 14.4.1?

@louis030195
Copy link
Collaborator

yes system audio is not implemented yet on macos and windows (should work on linux)

yes its like #70

i think we should use this https://github.com/RustAudio/cpal/pull/894/files

or in general the apple screencapture api (which capture system audio) but didnt have time to dig back in

@htalvitie
Copy link
Author

Ok, thanks for the clarification!

I suggest this fact should be mentioned somewhere - for example on the main Readme.md, where you have a list a functionalities & integrations which are completed (and which are not - yet). Otherwise people might try to troubleshoot the issue and waste time. At least I didn't realize this is not yet even possible.

@louis030195
Copy link
Collaborator

I'm going to prioritize this feature

@louis030195
Copy link
Collaborator

@htalvitie this works now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants