see no reason why we shouldn't.
I think the best way to do it would be to add a "progress_callback" parameter to "write_videofile". This parameter would be a function which will be run that would be run inside the main loops of "write_audiofile" and "write_videofile".
progress_callback("audioclip", current_frame, current_frame_number, total_frames_number)
progress_callback("videoclip", current_frame, current_frame_number, total_frames_number)
This would enable to do a lot of things such as sending the progress back to a web client, and even get a preview of what is being written down, as it is being written down.
Another related issue #278
write_videofile and we have a update for that in PR #380 (and #300 for write_images_sequence)Implemented in v1.0. See #1020
Most helpful comment
I think the best way to do it would be to add a "progress_callback" parameter to "write_videofile". This parameter would be a function which will be run that would be run inside the main loops of "write_audiofile" and "write_videofile".
This would enable to do a lot of things such as sending the progress back to a web client, and even get a preview of what is being written down, as it is being written down.