Watermark AI-generated audio files
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
@nextcloud/integration
We could watermark all the audio files generated by the task processing providers. If we do it at the task processing level, it saves us the effort of implementing it in all providers.
- Audible watermark: We could insert a little bit of audio at the end or the beginning of the file. Something short saying "this audio file was generated by AI".
- Inaudible watermark
- We can store information as ID3 tags inside the file. We could store a comment
- Just like for images, there might be a way to embed something inaudible in the audio itself. I have no idea what the technics are and if there are Php libraries for that
This could be done right before storing the images in appdata, when the task results are set by the provider.
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
Start at the task-processing path where provider task results are set, immediately before generated files are stored in appdata. Compare the proposed audible and inaudible approaches and identify how all generated audio providers would be covered. Done means an agreed watermarking approach is implemented centrally for generated audio files and its behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- audio-video-rtc, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100