After the upload is completed by default Publitio will only store Uploaded video.
It will not create any version or process it.
The reason for this is many users use Publitio only to store files and processing files would take up more space than needed.
In order to get a playable version of the video, you will need to open the link for the video.
On that first request, Publitio will start processing video.
If a video was exported in streamable mp4 format for example with h.264 codec video will work in a few seconds.
MOV files uploaded from iPhone will start working in a few seconds.
If you have uploaded mp4 file optimized for desktop viewing Publitio will need to encode that video to streamable mp4 and processing time can be from few seconds to few hours it all depends how long is video.
VIdeos with a length of 90min could take up to 90min to process.
We are working on an update that will enable you to decide what to do with uploaded videos.
To understand video upload and process check following video
Comments
3 comments
Why is Publitio not saving the different versions of the videos, but rather deleting those version after a while. This means the end user is seeing a message "the file does not exist" and there is no version at alla available. I know all the versions have been working in the beginning.
Why the automatic process is not starting after a request from the user?
Hi Anna, our system purges old unused versions from time to time in order to save storage space. Any missing versions should be auto-recreated on access. For this to work you need to have URL-based Transformations enabled at https://publit.io/dashboard/settings/api and for each individual file.
I am experiencing the same issue it seems as Anna. where people are getting served "Oops... We're having trouble playing this video" or "Processing..." messages after MONTHS of use without problem.
It's highly frustrating and damaging to our sites reputation. Is there a solution so that files aren't purged or at the LEAST I can be notified of their purge so I can force them to reprocess? Basically is there some way to guarantee that someone using our site won't have to wait to view content?
Please sign in to leave a comment.