Obsolete
Status Update
No update yet.
Comments
na...@google.com
am...@google.com
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.
lb...@gmail.com
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.
am...@google.com
Thanks - Good catch, I'll get the documentation updated. (The previous sentence is quite explicit, but we must have missed this one.)
lb...@gmail.com
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.
ar...@google.com
am...@google.com
Re #5, we can track this here. I have renamed the title of the issue to capture this.
0j...@gmail.com
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?
sa...@google.com
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.
Description
They should include all kinds of permissions that the user grants via special confirmations dialog and screens .
On this case, I present that it doesn't exist for notification-access, but I've tried and noticed it doesn't exist for many other types.
* Which Developer Preview build are you using? See Settings > About phone > Build number (for example OPP1.170223.012 or OPP1.170223.013).
OPP1.170223.012
* What device are you using? (for example, Nexus 6P)
Emulator
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
1. Go to "notification access" screen in the settings, and enable it for "Pixel Launcher"
2. Go to the app info screen of "Pixel Launcher", and try to find the notification access there, so that you could disable it.
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
UI, permissions
* What was the expected result?
To be able to see the "notification access", notice that it's enabled for this app, and also be able to disable it, as was written that it does exist.
* What was the actual result?
Doesn't appear there.
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)
Attached video showing the issue.