You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Could you provide better feedback to the user, when video is being processed? I know it's very hard to display accurate percentage of some process, but at least some simple animation with approximate amount of processed video would be great. It is always better to provide some interesting feedback, users are more likely to wait for long task, when they see something like this (which is something you surely know, but just in case... :) ).
The text was updated successfully, but these errors were encountered:
That would be a nice addition and I had actually planned for it, however I was simply unsuccessful on getting the actual progress data from FFmpeg WASM. There is a bug reported for it which was fixed, but unfortunately Screenity uses an older version, so the issue persists.
My plan is to try to upgrade to the latest version of FFmpeg WASM, as it supports multithreading (so it would improve the speed at which it can process). My previous experience trying to update it to a more recent version though has been pretty poor (I couldn't get any of them to work), but I think the v0.12.8 release seems promising. When I do so I'll likely be able to get the actual progress data.
It would be good, if you succeed with updating the ffmpeg. It's pretty slow now, so even for short videos it takes ages to process. Multi threading could help a lot. Progress is just a very fine bonus.
Hi! Could you provide better feedback to the user, when video is being processed? I know it's very hard to display accurate percentage of some process, but at least some simple animation with approximate amount of processed video would be great. It is always better to provide some interesting feedback, users are more likely to wait for long task, when they see something like this (which is something you surely know, but just in case... :) ).
The text was updated successfully, but these errors were encountered: