Infeasible
Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
Thanks for the report!
Unfortunately you can't specify a height or width for video files at the moment, and the 'dv' parameter returns a downsampled version of the video. There is currently no option to retrieve the video in its original resolution.
I have forwarded this to the team and will update here once I hear back.
Unfortunately you can't specify a height or width for video files at the moment, and the 'dv' parameter returns a downsampled version of the video. There is currently no option to retrieve the video in its original resolution.
I have forwarded this to the team and will update here once I hear back.
mi...@gmail.com <mi...@gmail.com> #3
Thanks
The documentation should be updated then?
https://developers.google.com/photos/library/guides/access-media-items#video-base-urls
If specifying a video width or height is not possible the sentense "with your required dimensions:" makes no sense then.
The documentation should be updated then?
If specifying a video width or height is not possible the sentense "with your required dimensions:" makes no sense then.
zj...@google.com <zj...@google.com> #4
Thanks - Good catch, I'll get the documentation updated. (The previous sentence is quite explicit, but we must have missed this one.)
mi...@docketalarm.com <mi...@docketalarm.com> #5
Is there a separate ticket for adding the ability to download full resolution video? Or does this documentation ticket also cover that? I want to make sure I'm tracking the correct ticket so I'll know when that feature is added.
mi...@docketalarm.com <mi...@docketalarm.com> #6
Re #5, we can track this here. I have renamed the title of the issue to capture this.
zj...@google.com <zj...@google.com> #7
Not sure if this works (or is fool-proof), but I tried reverse-engineering this based on the URLs I see in Google Photos directly, and in Picasa. My hunch is, if you pass the attribute "=m37", you might get a higher resolution video. How I tracked this down is:
1. Go to Picasa's API for showing your albums:https://picasaweb.google.com/data/feed/api/user/YOUR_USER_ID_HERE?kind=album&prettyprint=true . Find the album you are looking for, in the element <gphoto:id>xxxxx</gphoto:id>. Note that this album id is different from your Google Photos album id.
2. Now look at your album via Picasa's API:https://picasaweb.google.com/data/feed/api/user/YOUR_USER_ID/albumid/YOUR_ALBUM_ID?kind=photo&prettyprint=true . Find the video you are looking for (you can search by title etc.).You will see the following defined:
<media:content url='https://lh3.googleusercontent.com/dummy-image-url=m18 ' height='360' width='640' type='video/mpeg4' medium='video'/>
<media:content url='https://lh3.googleusercontent.com/dummy-image-url=m22 ' height='720' width='1280' type='video/mpeg4' medium='video'/>
<media:content url='https://lh3.googleusercontent.com/dummy-image-url=m37 ' height='1080' width='1920' type='video/mpeg4' medium='video'/>
Specifically look for those items where the type='video/mpeg4'.
If you observe the URLs you will see that they have the same URL with a different suffix: =m18 for the smallest resolution, =m22 for the medium resolution, and =m37 for the highest resolution. This is what I see in my albums; you might see something else. What I have found, though, is that if I simply append "=m37" to the URL shown in Google Photos API, it seems to neatly bring me a good resolution video.
Product Team,
Is my hypothesis correct? Or am I completely off-base?
1. Go to Picasa's API for showing your albums:
2. Now look at your album via Picasa's API:
<media:content url='
<media:content url='
<media:content url='
Specifically look for those items where the type='video/mpeg4'.
If you observe the URLs you will see that they have the same URL with a different suffix: =m18 for the smallest resolution, =m22 for the medium resolution, and =m37 for the highest resolution. This is what I see in my albums; you might see something else. What I have found, though, is that if I simply append "=m37" to the URL shown in Google Photos API, it seems to neatly bring me a good resolution video.
Product Team,
Is my hypothesis correct? Or am I completely off-base?
mi...@gmail.com <mi...@gmail.com> #8
One more thing - I got the idea of looking at the Picasa API because in the preview page of Google Photos I saw that the small preview of my video was suffixed with "=m18", and I had seen that while I was working with the Picasa API.
ch...@google.com <ch...@google.com> #9
Re #8 Adding "=m37" works for me in a browser but gives me a 404 when calling the API.
Furthermore, requesting 'https://lh3.googleusercontent.com/[video-baseUrl]=dv ' now results in an Error 400 (did work before for low-res videos) - do I just leave that here, or do I open another issue?
Furthermore, requesting '
Description
1 - Put a .p12 file in your repository (it's a private key).
2 - gcloud app preview deploy app.yaml
What is the expected output? What do you see instead?
The app should deploy with the .p12 file.
What is the output of 'gcloud info'?
The deployment fails, looking in the logs, you can see the root cause is the following line:
Uploading ...com/26d9d1c09c438d92f51af97acdf4c041005db637.p12: 0
Invalid MIME type: "x-pkcs12"
Please provide any additional information below.
This error gets raised in the following file / function:
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\lib\googlecloudsdk\third_party\apitools\base\py\utils.py:AcceptableMimeType
The above function checks to see if there is a slash in each mimetype. On compute engine, most mime types are determined by the mimetypes python library, and particularly, mimetypes.guess_type. When you run this function on a .p12 file, it incorrectly returns ('x-pkcs12', None)
, when it should return ('application/x-pkcs12', None). This appears to be a bug with mimetypes, but Google should be able to work around it.