Recording post-processing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Allow to intercept recording import and manipulate recordings before they are imported, e.g. to generate subtitles, censor chat messages, fix playback issues or re-encode media files.
Proposal:
Introduce a new config option called RECORDING_IMPORT_HOOK. If defined, it should point to an executable that is called once per playback format at an early stage during import.
The hook script is called without parameters, but with the current working directory pointing to a temporary folder that contains extracted recording data. The script is allowed to reads or manipulate any files within that directory, including metadata.xml or media files. If the script finishes successfully, then the import will continue as usual. If the script fails, the import will also fail. All output will be logged.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the recording import workflow and determine where an executable hook can run once per playback format with the extracted recording directory as its working directory. Done means RECORDING_IMPORT_HOOK is supported, successful hooks allow import to continue, failures stop import, and hook output is logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100