![]() Luckily, it's not a problem with the token in your query - it only has 'public' scope and cannot be used for uploading to Vimeo or to access. Depending on the token's scope, someone could use it to access and modify your account, upload videos to your account, and more. I suggest migrating to the Vimeo Node library first, or another library that supports Vimeo's tus implementation, and once that is up and running, evaluate any upload speed issues you may encounter. First off: never disclose your authentication token in public. The library will send the video file all at once, not in chunks, from the client. Internally, the library uses the tus upload method, as implemented by Vimeo. Vimeo provides a NodeJS library that is in active development and supported by Vimeo. The websemantics library does not use tus, instead it uses an older resumable upload method that has been deprecated by Vimeo. If you have an older application defaulting to 3.4, that library will not work for uploading unless the library is modified to include a version header.Īll that being said, the "upload chunk" size you mention only applies to uploads using open source tus. Because no version header is provided, the Vimeo API defaults to the version specified on your app management page. That websemantics library, at current time, does not provide a version header in its requests. Thank you for your assistance in advance. ![]() My request is for you to kindly please assist me with tips and hints to make uploads from the library as fast as directly uploading to Vimeo. Trying to look for the same situation in the library, I have realized that there doesn't seem to be any defined upload chunk size or its somewhere and I can't locate it. However, this was a whole different situation uploading to some other place, not Vimeo. According to the writer, in their case, this problem was because the upload chunk was around 100Kb and the solution was just to change this size to make it bigger, say to 1Mb and the upload became faster. I tried researching about this issue and the closest I got to an explanation is what one writer termed the size of the upload chunk. Here are step-by-step instructions for uploading videos through the API and managing related tasks. With this functionality, you can access all the amazing upload capabilities of through your own front end in your own application. I observed that, when I opened my Task Manager in windows to observe the network performance, I can see that my upload using the library indicates that my upload speed is averaging/locking around 2Mbps while the upload directly is averaging around 20Mbps hence the upload directly on the Vimeo site is around 10 times faster. The Vimeo API includes a full set of features for uploading and managing video files. ![]() I observed a major thing which had me quite concerned and I just had to reach out for assistance. I have run two tests to determine why my implementation of the library is rather quite slow compared to uploading the same video directly onto the Vimeo Platform. However, I need some assistance please in relation to the uploading speed. I am using this library to upload videos from my web app to Vimeo. ![]()
0 Comments
Leave a Reply. |