![]() ![]() If you have not, please review our errors guide. Please reach out to us if you would like to implement better progress bars, but get stuck on how to execute them! Uploading reliably Chunk-level granularity is acceptable, so if your asset has 3 chunks, as each chunk is uploaded successfully, your progress can jump from 0% → 33% → 66% → 100%.įiner-grained progress is nice for the end-user, but implementation will be highly dependent on your HTTP library, and therefore out of scope for these guides. We require that our integrations supply basic upload progress to the user. Try profiling a few different strategies from your library and see what works best! Tracking progress We’ll repeat that your HTTP library is likely to have some sort of abstraction to handle connection pooling + parallelism for you, and will be a good resource to lean on. In the C2C Connections tab, go to the three-dot menu on your device, and click Pause. Our server takes that value, compares it against the windows for which a device was paused, and returns an error if your device was paused when the media was created. Instead, when you upload a file, you supply how many seconds ago the file was created. Our API is designed so that you do not have to be aware of when a device is paused or unpaused. Read more on how the paused feature works here. When a device is paused in Frame.io, the user is telling the device not to upload media created while paused. The offset is how we determine when a piece of media was made, and is critical to ensuring that your device does not upload media it is not supposed to. It is critical that you supply a proper offset value. The offset parameter is particularly important to get right, so please make sure to give it particular attention! Offset - handling paused devices When creating a new asset in Frame.io, there are a few advanced parameters that can be passed to modify upload behavior. In this guide we will be using the same test asset we used in the Basic Uploads guide. You will also need the access_token you received during the C2C hardware or C2C Application authentication and authorization guide. If you haven’t read the Implementing C2C: Setting Up guide, give it a quick glance before moving on! The guide is your black-belt training for making a reliable, resilient, and fast uploader. Uploading assets is the bread and butter of every C2C integration, and there’s a number of considerations that need to be taken when uploading assets reliably. ![]()
0 Comments
Leave a Reply. |