If you use an ffmpeg approach for the conversion, that typically requires installations at a lower level than Python (or other programming language) modules/libraries can offer. That is, the programming languages typically only offer wrappers over the OS-level ffmpeg utility. So, Cloud Functions would need to use something other than ffmpeg, which is not ideal since that's the gold standard. You'll also need to watch the max configurable timeouts (10 minutes for event-driven functions, and 60 minutes for other functions). Overall, 2nd Gen Cloud Functions could certainly work, but if you're doing other pipeline-type processing anyway, a low-code step in Kubeflow is a good way to go.
Thanks for the video. Question: Why not using a simple Google Cloud Function (version2) for the first conversion from mp4 to wav?
If you use an ffmpeg approach for the conversion, that typically requires installations at a lower level than Python (or other programming language) modules/libraries can offer. That is, the programming languages typically only offer wrappers over the OS-level ffmpeg utility. So, Cloud Functions would need to use something other than ffmpeg, which is not ideal since that's the gold standard.
You'll also need to watch the max configurable timeouts (10 minutes for event-driven functions, and 60 minutes for other functions).
Overall, 2nd Gen Cloud Functions could certainly work, but if you're doing other pipeline-type processing anyway, a low-code step in Kubeflow is a good way to go.