-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
✨ Reencode task for worker #59
Conversation
Do we really want to do this in the backend?. |
Yes and no. I think it makes sense to do this in the frontend too, but I think we should have to option in the backend as well. a) to make sure the file is in the right format and b) to handle cases where the conversion in the frontend is not possible (e.g. files larger than 2GB, browsers without wasm) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with merging transcription at the worker since it is an improvement from the status quo :). However I would like to investigate transcoding at the frontend in the future.
fair points :) |
Ah we probably also need a way to inform the frontend, that the audio file changed. -> Future |
5d35a14
to
801d3e8
Compare
801d3e8
to
186c0bd
Compare
186c0bd
to
4c1af0a
Compare
4c1af0a
to
5d8722f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
load_audio
should probably be moved to the ffmpeg-python
package at some point aswell
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
load_audio
should probably be moved to the ffmpeg-python
package at some point aswell
Reencode everything to 128k cbr mp3 and m4a