I want to access direct links to videos of my users. they have PRO or above. also, the access token of each user includes the video_files scope but I still not able to see the download and files fields of their videos.
I have now a PRO account and my users have Pro too.
How do I fix the issue, please? I bought a Pro account only for that.
It's not possible. You can only get the direct file links and download metadata for videos on your own account.
Related
I'm sorry for bothering you guys with something as simple as this appears will be for you. I am trying to help develop a public Roku channel for an awesome minister I know who has 100's of videos. (hoping Naz Vanof or someone who knows a lot about this can help)
I attempted to find information on how to use Vimeo as a json feed provider and didn't find any tutorials. (the online help at Vimeo was no help).
First is there something that needs to be done for each video uploaded to my Vimeo account to prepare them to be used as json? I tried using the provided URL for my Vimeo account on the Direct Publisher feed link and it wouldn't accept it.
I've been searching for two days on this subject and not really getting anywhere and the only place I could see any related content was here (Naz). The videos I am using I have permission for from the developer but they are downloaded from Youtube through the Keepvid online program to my computer then uploaded to Vimeo. Is that an issue?
Sorry for the lack of knowledge but I am excited to get my feet wet on this and have a high aptitude in other fields, I'm just a total newbee in this field. starting two days ago I went through all the tutorials on Roku and did all the prep for establishing the developer account, and learned how to side load and alter channel templates, now I just need to know how to get my URL link to connect and to organize videos on Vimeo. Later I will get deeper with the Brightscript app. But what they have for the template for Direct Publisher would be perfect to get started.
Thanks and sorry again for this base level question.
Direct Publisher accepts two types of feeds, as described in the Direct Publisher Feed Specifications: their own custom JSON format (which is not something Vimeo offers I imagine, based on how new Direct Publisher is) and MRSS feeds (which Vimeo might offer, not sure). If Vimeo doesn't offer either of those, you likely won't be able to use Direct Publisher, unless you create your own in between API layer which transforms what Vimeo offers to what Direct Publisher needs.
According to other sources Vimeo does offer JSON feeds. And I did purchase Vimeo Pro but still could not access my files. I was wondering if the type of encoding on Youtube where I had to get the downloads to upload to Vimeo would interfere with the Direct Publisher feed? They don't support Youtube links so I used a Keppvid program to download from Youtube then upload to Vimeo. Vimeo accepted those downloads no problem. But my URL wouldn't work on Direct Publisher. I talked to Vimeo and they said my account URL should have worked. I'm stuck.
You need to compare the Vimeo feed to Roku's feed specification and figure out what the difference is that is causing it to not work, then load the Vimeo feed into a text editor and alter it to make it compatible. Alternatively and preferably, you would write a script that would do the conversion on your own server so you could have it run once a day and then deliver the feed from your server to Roku's server instead of directly from Vimeo.
The problem with using Vimeo is that housing your video in an external xml document, vimeo uses Ampersand in their URL. Sample:
https://player.vimeo.com/external/213601353.hd.mp4?s=71a24afbe4d4792806a08391263kjhisihe69fe2&profile_id=xxx
This needs to be modified to:
https://player.vimeo.com/external/213601353.hd.mp4?s=71a24afbe4d4792806a0839126c484c175269fe2&profile_id=174
Once you make this change the xml URL will be parsed properly. The URL was having the ampersand stripped which is why it may not have been working. I have tested this with all of our vimeo videos and they work properly now.
Hope this helps.
I would like to access my own videos through Vimeo API and to download low and high definition versions that Vimeo encoded.
I have a Premium account on Vimeo.
I didn't find it in their doc :(
Is there a way? I would like to avoid encoding videos myself in different sizes...
Thanks!
First off, you'll need to be a Vimeo PRO member to get the direct video file URLs.
Using the latest API, do an authenticated GET https://api.vimeo.com/videos/[clip_id]. In the response you'll see an attribute named files that contain the HD, SD, and mobile transcodes that Vimeo generates. These URLs are meant for use with other video players (JWPlayer, or simply with the <video> tag, for example).
If you want to get the URLs to use for downloading (providing a download link on your site, for example) do the same authenticated GET https://api.vimeo.com/videos/[clip_id] to find the download attribute in the response. These URLs expire, and with them you'll see an expires attribute with the date and time.
Note that to get the download URLs, not only must you be authenticated as the clip owner, the API app itself must also be created by the clip owner.
I have a website that has a web page with a html5 video-tag, and the user can supply a URL, and it will play in the video-tag.
The webpage uses JavaScript commands that control the video-tag - for instance, it can pause the video, move to a different point in the video, etc.
It works fine with the cloud. Videos stored on Microsoft Azure can be used, for instance (Azure gives you a way to get a URL to any video on your cloud storage, and streams it too).
However, I have users that store videos on Google-drive, and also on Microsoft One-Drive.
From what I can see, I can play these videos, but only in a page (probably with Google's own player in it) on their site.
It seems that there is no way to get a URL to these videos that I can put in a video tag.
Without the ability to do that, I can't use the javascript commands that work with the html5 video-tag.
Is there any workaround?
Or am I missing something?
Thanks.
For playing videos that are stored in google-drive using your app:
you need oauth2 credentials to access the user's drive, but assuming you have the oauth part covered :
you can create a drive application as a google appengine app and deploy it in a part of your website.
enable the drive-sdk and set the open-url to your website (that you have verified)
-> basically this tells drive to redirect towards your website whenever the user clicks on the video (from his drive)
when drive redirects to your website a json file will be sent, you'll have informations such as fileId from there i think you can execute the method files().get() to retrieve the necessary information for you to play the video
I advise you to take a look at this course in codeschool.
Is it allowed to use the vimeo API to search and download videos from vimeo?
Can you download all type of videos or only a particular category?
If I would like to download all video, do I need a special approval from them (or special account) to be able to do so?
Edit: I would like to know if it's possibile using the current API
Downloading source files through the API is only available under three conditions.
You are the owner of the video
You have a PRO account
You are the owner of the API App.
I have created an vimeo app and idea is to upload video on different peoples account using the app if user gives upload access to the app. Now the problem is no matter what permission i set in my authorization link, app never gets upload access for other user, if i try to authorize the app with same user as app owner then only it get upload access. Is it something that vimeo wont let app to do or is there special tweaks.
By the way i am using oAuth 1.0 and i have vimeo pro account.
Regards
Vimeo upload permissions clarify which types of accounts can upload via your app.
Owner means only you
PRO means only pro users
Plus means only plus users
Basic means only basic users
You can have zero to all of these permissions, and you can verify them on your app page. It's likely that the third party users you are communicating with do not line up with your upload permissions.