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
Programmatically controlling LosslessCut / API / CLI #980
Labels
Comments
mifi
changed the title
Controlling LosslessCut
Programmatically controlling LosslessCut / API / CLI
Jan 14, 2022
This was referenced Jan 14, 2022
Closed
4 tasks
4 tasks
5 tasks
Merged
this was closed by accident |
there's now a new http api |
mifi
added a commit
that referenced
this issue
Oct 15, 2023
- add closeCurrentFile action - allow export confirm also via action - upgrade electron
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggested ways to programmatically control LosslessCut. Feel free to add suggestions in comments below.
command line arguments
API / actions / macros
I could imagine some API that allows automating actions in LosslessCut, internally and externally. This could be tied to custom keyboard mappings #254
Run a custom command from segments
See also afterExport event #974 #1347
Ability to press a button in losslesscut and have it run a custom command line (or more commands, e.g. one cmd per segment) and with ability to inject information about the current segments into this command. I think this requires some coding in one way or another by the user.
I think such a «hack» can currently be achieved by creating a custom bash script. Losslesscut will auto save a project
.llc
file with json5 containing information about each segment. You could create a bash script that you trigger by a keyboard shortcut (outside losslesscut). Then this script will then read the.llc
file and run the desired commands. The workflow would be:The text was updated successfully, but these errors were encountered: