Closed rafaellehmkuhl closed 1 month ago
I haven't experienced that as an issue or bug yet, but I do recognize this behavior as intentional. What might have happened to Brian is one of the following situations:
1- If you select an unprocessed video, the download will be a ZIP containing the video's chunks. Downloading the chunks could be useful if the cockpit cannot process the video. 2- If you select multiple unprocessed videos, the download will be a ZIP containing all selected video chunks in the root directory, with files named by hash. 3- If you select multiple videos and among them there are both processed and unprocessed videos, the download will consist of two ZIP files: one for the processed .webm and .ass files, and another for the unprocessed ones.
I haven't experienced that as an issue or bug yet, but I do recognize this behavior as intentional. What might have happened to Brian is one of the following situations:
1- If you select an unprocessed video, the download will be a ZIP containing the video's chunks. Downloading the chunks could be useful if the cockpit cannot process the video. 2- If you select multiple unprocessed videos, the download will be a ZIP containing all selected video chunks in the root directory, with files named by hash. 3- If you select multiple videos and among them there are both processed and unprocessed videos, the download will consist of two ZIP files: one for the processed .webm and .ass files, and another for the unprocessed ones.
Got it.
So it's an UX problem, not a bug in the software.
Maybe a solution is to add a confirmation dialog saying that the user is downloading chunks instead of the video, on those situations?
Maybe we should also differentiate more clearly the processed and unprocessed videos on the Video Library.
On top of that, we can change the ZIP filenames for something more descriptive.
Now processed videos are named Cockpit-Video-Recovery - 2024-05-14T094324.981.zip
and unprocessed are named Cockpit-Temp-Video-Chunks-88f8f692.zip
More info on that: Brian said he had clicked the process button already. Maybe the download button was available while the video was being processed?
Yes, this might have happened. The button should disabled while the videos is processing.
That was a problem faced by Brian Austin (BR):