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
macOS Raycast Extension #38
base: main
Are you sure you want to change the base?
Conversation
Update main
Renamed previous event from "change-device" to "set-media-device". Added handler for deep link requests within the Recorder component. Currently supports commands for start/stop recording and opening the dashboard. This shouldn't interfere with the auth process. Testing auth functionality is still recommended.
update from origin
update from origin
@ItsEeleeya is attempting to deploy a commit to the Cap Software Inc Team on Vercel. A member of the Team first needs to authorize it. |
The extension is here To test, make sure Cap is built with |
There will be a Form view that opens up once you invoke the Start Recording command, letting you select the input devices and then start your Cap. |
Solves #28
Added deep-link support.
The Raycast extension will be able to use these to send commands to Cap.
Currently, you can start/stop recording with specified media devices, as well as open your account's Dashboard.
I'm not sure if this will interfere with the auth process. This should be tested.
To test on macOS, make sure you first build a debug version of the app via
pnpm tauri:build --debug
and then "install" it. (Putting the resulted.app
into yourApplications
folder.Read more about it here
Then run the app via
pnpm dev
The structure of the deep-link scheme is like
caprecorder://:command?parameters
Copy and paste the URI below into a browser to try it out:
caprecorder://start-recording?mic_in_label=MacBook%20Pro%20Microphone&vid_in_label=FaceTime%20HD%20Camera
The URI must be encoded. You can also use
none
as the value for a media device label to disable it.P.s: I'm not sure where to create the extension. Should it be under the packages directory?