Status Update
Comments
jf...@google.com <jf...@google.com> #2
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.
am...@gmail.com <am...@gmail.com> #3
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.
jf...@google.com <jf...@google.com> #4
he...@gmail.com <he...@gmail.com> #5
jf...@google.com <jf...@google.com> #6
sa...@gmail.com <sa...@gmail.com> #7
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...@gmail.com <sa...@gmail.com> #8
ke...@gmail.com <ke...@gmail.com> #9
Furthermore, requesting '
jf...@google.com <jf...@google.com> #10
Undocumented flags are not supported and should not be used directly. If you have a use case for other types of encoded or processed video, please do file a new feature request, describing your use and any technical requirements.
de...@gmail.com <de...@gmail.com> #11
de...@gmail.com <de...@gmail.com> #12
Based on the description in the documentation the dv parameter should download the full quality video. There is no mention of down sampling the in documentation.
In addition it the basic expectation of getting a media item is to have access to its full quality download.Not having this ability makes the api incomplete missing basic functionality most apps require.
Finally access to full quality video would be consistent with the way images download works (full quality with some tagging stripped).
This is why I think this is a bug, the behavior is unexpected, undocumented, and inconsistent with other interfaces.
Thanks!
an...@gmail.com <an...@gmail.com> #13
an...@gmail.com <an...@gmail.com> #14
jf...@google.com <jf...@google.com> #15
Can you confirm if the quality and resolution is of higher quality now?
If you are still seeing this, could you provide an example of the file or the exact codec, resolution and framerate of the video?
an...@gmail.com <an...@gmail.com> #16
I tried using the Google Drive integration with Google Photos, but it was a nightmare because deleting a photo from Drive wouldn't necessarily delete it from Photos. Now I'm hoping to use the Google Photos API.
I tried downloading a video from Google Photos today, but the 50MB video from my phone resulted in a 13MB download. Also, the video was taken at a time as per the filename on my phone: 20181124_140007.mp4 but the EXIF data in the downloaded video had been rewritten by Google Photos and the only timestamp in there was 2018:11:24 16:48:07, which was probably the time that my phone uploaded the video. So now I have a poorer quality copy of my original video with the wrong timestamp.
And it's just this second dawned on me that I've deleted files from my phone to free up space, so the only original copy of those files is on Google Photos and I can't get access to them.
I'm just trying to keep a few files in sync between different devices. It shouldn't be this difficult.
om...@gmail.com <om...@gmail.com> #17
Any solution about this issue ???
fr...@dioshotel.com <fr...@dioshotel.com> #18
Any news about this issue. ?
ma...@gmail.com <ma...@gmail.com> #19
someone work on it?
gi...@gmail.com <gi...@gmail.com> #20
I have recently discovered that my 1080p 60fps videos are now transcoded down to 30fps with high compression - they look terrible. But if I directly download them from the Google Photos Web they are fine. Why is the API transcoding, please?
Here is an example which I share globally for all to see.
Album =
The attachment contains three copies of the video:
- the original file from the phone directly (1080p 60fps)
- the file as downloaded from the Google Photos Web (similar but not identical to the above)
- the file as downloaded from baseUrl with =dv -- this shows only 30 fps and file size is 1/10 of the above
cj...@gmail.com <cj...@gmail.com> #21
This is getting really ridiculous. This API has been the only means of interacting with Google Photos since you all did away with the Google Drive folder a couple months ago and yet we still can't get any traction on this issue that's been open for OVER A YEAR???? What kind of terrible management is going on over there that the person assigned to this hasn't been canned already for not completing their work?
For the love of all things holy Google... PLEASE FIX THIS DUMPSTER FIRE OF AN API!!!!
cl...@gmail.com <cl...@gmail.com> #22
I'm using
com.google.photos.library:google-photos-library-client:1.4.0
to fetch videos. It was working pretty well but for some new videos i got issue IOException with reason 500 from google endpoints:
It describe itself more like this:
java.io.IOException: Server returned HTTP response code: 500 for URL:
this is (partial) output from fields of MediaItem
google.photos.types.MediaItem.base_url=
google.photos.types.MediaItem.mime_type=video/mp4, google.photos.types.MediaItem.media_metadata=creation_time {
seconds: 1570301787
}
width: 576
height: 1024
video {
fps: 29.918403416437823
status: READY
}
, google.photos.types.MediaItem.filename=video-c523eb1bb7a18b3e31f97ac581bffabf-V.mp4}
all i do is append =dv to the end of baseUrl
cl...@gmail.com <cl...@gmail.com> #23
mean:
I cannot remove above comment...
ro...@catfood.net <ro...@catfood.net> #24
jl...@gmail.com <jl...@gmail.com> #25
me...@woet.me <me...@woet.me> #26
la...@gmail.com <la...@gmail.com> #27
ar...@gmail.com <ar...@gmail.com> #29
will this be fixed anytime soon?
dr...@gmail.com <dr...@gmail.com> #30
pu...@gmail.com <pu...@gmail.com> #31
dr...@gmail.com <dr...@gmail.com> #32
ji...@gmail.com <ji...@gmail.com> #33
dr...@gmail.com <dr...@gmail.com> #34
ke...@gmail.com <ke...@gmail.com> #35
gi...@gmail.com <gi...@gmail.com> #36
ro...@googlemail.com <ro...@googlemail.com> #37
go...@iamgo.net <go...@iamgo.net> #38
th...@gmail.com <th...@gmail.com> #39
ar...@gmail.com <ar...@gmail.com> #40
ca...@gmail.com <ca...@gmail.com> #41
sl...@gmail.com <sl...@gmail.com> #42
o....@gmail.com <o....@gmail.com> #43
yt...@bu.edu <yt...@bu.edu> #44
ma...@gmail.com <ma...@gmail.com> #45
du...@gmail.com <du...@gmail.com> #46
vi...@gmail.com <vi...@gmail.com> #47
ju...@googlemail.com <ju...@googlemail.com> #48
lo...@gmail.com <lo...@gmail.com> #49
ca...@gmail.com <ca...@gmail.com> #50
jb...@gmail.com <jb...@gmail.com> #51
an...@gmail.com <an...@gmail.com> #52
lu...@gmail.com <lu...@gmail.com> #53
lo...@gmail.com <lo...@gmail.com> #54
th...@gmail.com <th...@gmail.com> #55
ma...@gmail.com <ma...@gmail.com> #56
na...@gmail.com <na...@gmail.com> #57
al...@gmail.com <al...@gmail.com> #58
[Deleted User] <[Deleted User]> #59
i can easily download the original video with =dv but =m18, =m22 etc simple dont work after full video encode
it works for a few then is gone
mi...@stallinger.cx <mi...@stallinger.cx> #60
wa...@gmail.com <wa...@gmail.com> #61
[Deleted User] <[Deleted User]> #62
ke...@osmosit.eu <ke...@osmosit.eu> #63
Hello Google,
any news on that topic? The first issue has been introduced in 2018. Would you please come with a solution? ${baseUrl}=dv does not work and it has definitely something to do with the exposed endpoint.
Many thanks
With best regards
ju...@gmail.com <ju...@gmail.com> #64
are you still working on this? I don't want do download my videos squished down in quality with the api...
bp...@gmail.com <bp...@gmail.com> #65
ne...@gmail.com <ne...@gmail.com> #66
er...@gmail.com <er...@gmail.com> #67
y....@gmail.com <y....@gmail.com> #68
to...@gmail.com <to...@gmail.com> #69
Come on google, I'm PAYING you extra to store original quality video. you are holding my data ransom here... please fix this bug.
ju...@gmail.com <ju...@gmail.com> #70
to...@gmail.com <to...@gmail.com> #71
th...@gmail.com <th...@gmail.com> #72
ci...@gmail.com <ci...@gmail.com> #73
ja...@gmail.com <ja...@gmail.com> #74
cr...@gmail.com <cr...@gmail.com> #75
cr...@gmail.com <cr...@gmail.com> #76
Poor decision. OneDrive provides original quality via API.
se...@gmail.com <se...@gmail.com> #77
83...@gmail.com <83...@gmail.com> #78
gu...@gmail.com <gu...@gmail.com> #79
br...@gmail.com <br...@gmail.com> #80
What the fuck is going here Google ? Do you want users let your services down ? I always lov(ed?) Android, but those kind of WFT is making me really reconsider it for the future
or...@gmail.com <or...@gmail.com> #81
to...@gmail.com <to...@gmail.com> #82
gi...@gmail.com <gi...@gmail.com> #83
dp...@gmail.com <dp...@gmail.com> #84
My data is too valuable to entrust to Google if they are going to snub their customers by not fixing a bug like this after knowing about it for 3 years. I'll be exfiltrating my Google One data and canceling my subscription ASAP.
jg...@gmail.com <jg...@gmail.com> #85
ch...@gmail.com <ch...@gmail.com> #86
f....@gmail.com <f....@gmail.com> #87
ar...@gmail.com <ar...@gmail.com> #88
ms...@gmail.com <ms...@gmail.com> #89
ru...@gmail.com <ru...@gmail.com> #90
so...@gmail.com <so...@gmail.com> #91
du...@gmail.com <du...@gmail.com> #92
va...@gmail.com <va...@gmail.com> #93
ha...@hagafiles.com <ha...@hagafiles.com> #94
va...@gmail.com <va...@gmail.com> #95
jo...@gmail.com <jo...@gmail.com> #96
ah...@gmail.com <ah...@gmail.com> #97
st...@gmail.com <st...@gmail.com> #98
M
ol...@frolovs.me <ol...@frolovs.me> #99
I never heard of Google Photos product previously although I have been working in Google Cloud Partner ecosystem for over two years, so am quite familiar with Google's product portfolio both in and outside Google Cloud.
When I learned about Google Photos from one of the Machine Learning courses that I am taking I thought that it sounds like a pretty good product so I spent some time to check it out. I liked the interface and the features but I also learned that this product does not allow to export the photos and videos back at their original resolution/quality level. This is vendor lock-in and is a deal breaker.
I cannot recommend this product to my customers and friends. In fact, I feel that now that I know about the vendor lock-in situation, it is my duty to mention this to any client or friend who is using Google Photos or is considering it. I also feel it is my duty to mention this every time I mention Google Photos in my line of work as an example of successful application of ML models.
I believe that in our time, and I'm writing this in year 2023, not allowing customers to export and take away all their data is socially unacceptable for a SaaS. I'm looking forward to this being fixed so that I can try this product again and begin recommending it to my clients and friends.
kl...@mail.com <kl...@mail.com> #100
di...@gmail.com <di...@gmail.com> #101
xi...@gmail.com <xi...@gmail.com> #102
pr...@gmail.com <pr...@gmail.com> #103
Please provide a solution to this
ro...@gmail.com <ro...@gmail.com> #104
This is very frustrating; there shouldn't be a difference between downloading through API and through web browser
ju...@gmail.com <ju...@gmail.com> #105
th...@e-x-e.dk <th...@e-x-e.dk> #106
da...@gmail.com <da...@gmail.com> #107
ph...@gmail.com <ph...@gmail.com> #108
li...@google.com
Does this person(s) still work for Google?? Why would it take 6 yrs with no update??? I literally discovered this bug just AFTER signing up with 5tb plan. Well...just cancelled the account and moving to another provider.
sa...@gmail.com <sa...@gmail.com> #109
I've started the process of migrating my large library over to a self-hosted instance. (You can export your photos with Google Takeout, and there are scripts to add back the metadata.)
Once you self-host, getting the highest quality version isn't a problem.
ap...@gmail.com <ap...@gmail.com> #110
Is there at least a private API we can use for this? How is the web interface accessing the media?
xd...@gmail.com <xd...@gmail.com> #111
How on earth is the core function of downloading the original video missing from the API? Do you say this is intentional?
Has anyone tried any workarounds, private APIs or anything else? There must be a way
Description
The issue is simple though, I'm reading the Guide => Access media items => Video base URL.
It explains it's required to add `=dv` to the video's base URL but I get the video in a smaller resolution. If I open the same video from the Google Photos webapp I get it in it's original resolution. The documentation says exactly:
"To do this, concatenate the base URL in the following format with your required dimensions:"
But I don't understand where I'm supposed to define the required dimensions and I get a lower resolution video. It specifically says "that this parameter is not compatible with the height and width parameters."
I've tried the following combinations:
But I really don't know how can I download the video in it's original resolution.
This issue is also reported as a question in Stack Overflow