Status Update
Comments
de...@gmail.com <de...@gmail.com> #2
de...@gmail.com <de...@gmail.com> #3
de...@gmail.com <de...@gmail.com> #4
Also now even thou the video says state='READY' if I download too soon the res comes back lower than 1080p.
I will file the state issue as a separate bug if I can get some traction on the original issue because as it stands now I am not sure what quality i should expect the doc us not clear.
jf...@google.com <jf...@google.com> #5
(This is related to
Please file a new issue about the video state, can you elaborate on what exactly you are seeing and what API calls lead to that issue?
jf...@google.com <jf...@google.com> #6
Can you confirm if the quality and frame rate is better 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?
el...@gmail.com <el...@gmail.com> #7
gi...@gmail.com <gi...@gmail.com> #8
ni...@gmail.com <ni...@gmail.com> #9
Unless rclone can download the original video then it is going to be pretty useless as a backup which is very disappointing.
Please provide a download option which does allow fetching the original unmodified video in the same way that downloading manually from
br...@gmail.com <br...@gmail.com> #10
jg...@gmail.com <jg...@gmail.com> #11
va...@gmail.com <va...@gmail.com> #12
With the Google Drive to Google Photos syncing feature removed I no longer want to use Google Photos are a primary storage place if I'm unable to recover uploaded files in full later. (I have the store full-quality option enabled and am paying Google for storage)
ic...@gmail.com <ic...@gmail.com> #13
af...@afxnet.net <af...@afxnet.net> #14
ad...@glassons.id.au <ad...@glassons.id.au> #15
cj...@gmail.com <cj...@gmail.com> #16
How is it so hard to fix glaring bugs in a public API? If you all had not pulled the Photos <> Drive sync with little notice we wouldn't be here. I'm going to start getting vocal in public ways about this blatant lack of respect and support in the coming few weeks if we can't get any attention on the multiple issues that have been raised with the raging dumpster fire that is the Google Photos API. This has moved from being annoying and inconvenient to a big issue, and then has transitioned further into straight up asinine levels of disrespect from the big G.
So, Google people... what say ye? Probably nothing I imagine, as that's par for the course at this point. You guys are the worst
gi...@gmail.com <gi...@gmail.com> #17
pa...@gmail.com <pa...@gmail.com> #18
st...@gmail.com <st...@gmail.com> #19
Just did it :) I believe if more people do that they MIGHT wake up and at least TRY to fix this!
gr...@poudrel.net <gr...@poudrel.net> #20
can you take a moment to fix this bug please ?
I tested today, the issue is still here...
om...@gmail.com <om...@gmail.com> #21
this is not much to ask , after all this is our data and if i put some of my data in your service it is you obligation to give it back to me in same way that i put it there reduce quality is not suppose to be your choice, this is the customer to choose,
make your fix please . we are all waiting.
after all we all use your services because we love them but give your crowed some attention.
ga...@gmail.com <ga...@gmail.com> #22
And whoever tried using Google Takeout knows how awful it is - it's just an excuse for google to say you're not locked with them forever. "Your account, your data." Right.
So disconnecting backup&sync from gPhotos was a bugfix? The bug was "our clients are moving to Dropbox" then.
Let's make some links to this bug in forums, as it is the major one preventing RClone from making a complete job.
on...@gmail.com <on...@gmail.com> #23
br...@gmail.com <br...@gmail.com> #24
st...@gmail.com <st...@gmail.com> #25
jl...@gmail.com <jl...@gmail.com> #26
ri...@gtempaccount.com <ri...@gtempaccount.com> #27
je...@korabelnikov.com <je...@korabelnikov.com> #28
pu...@gmail.com <pu...@gmail.com> #29
ad...@bullserve.co.uk <ad...@bullserve.co.uk> #30
be...@gmail.com <be...@gmail.com> #31
lu...@gmail.com <lu...@gmail.com> #32
me...@woet.me <me...@woet.me> #33
Just star it, and refrain from commenting unless you are adding something of substance.
fr...@gmail.com <fr...@gmail.com> #34
st...@gmail.com <st...@gmail.com> #35
se...@gmail.com <se...@gmail.com> #36
ri...@gmail.com <ri...@gmail.com> #37
jo...@gmail.com <jo...@gmail.com> #38
du...@gmail.com <du...@gmail.com> #39
They probably aren't, unless multcloud does something very improbable like using a non-documented API.
But it should not be difficult to check: open a few random photos (I recommend at least a 10% sample) in Google Photos, click on the "(i)" icon on the top right corner to see its information, then note the size in bytes. Compare that size to the one being shown for the local file corresponding to that same photos. If they are the same in all cases, then your local copies have almost certainly as much quality as the "original" ones on Google Photos.
Good luck, and please report back and let us know how it goes, it could be a good idea to start using Multicloud.com if they indeed manage to copy the original pictures.
jo...@gmail.com <jo...@gmail.com> #40
Well, bad news. Made one experiment with my mobile phone:
0) acquired 1 photo and 1 video
1) uploaded to GPhotos
2) transferred with MultCloud from GPhotos to GDrive
3) downloaded from GDrive to HDD using "Backup and Sync"
4) took out the SD card to get the original data
5) made direct download, using the web interface, from GPhotos to the local HDD
The results with the photo:
1617275 bytes in SD card (step 4)
636520 bytes in GDrive and local HDD (steps 2 & 3)
The results with the video:
13127681 bytes in SD card (step 4)
1692875 bytes in GDrive and local HDD (steps 2 & 3)
The not so bad news, step 5 got me back the original data (compared with "fc /B"), with one small mismatch: the video filename had original extension ".3gp" and the direct download returned ".mp4" (strangely enough, GDrive and MultCloud were both able to keep the file extension ".3gp").
Thanks for your this tracked issue which raises the warning, and the prompt comment to my question. Now I know for sure that I lose information by using the workaround I was trying to get photos and videos from GPhotos.
st...@bmd.at <st...@bmd.at> #41
ke...@osmosit.eu <ke...@osmosit.eu> #42
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
wa...@gmail.com <wa...@gmail.com> #43
Another customer looking for access to my original data via API.
I'm appending "=dv"
to the item's baseUrl
as per
I'm returned an HTML doc claiming a 400 Bad Request error with no details (see bottom).
Fetching images using baseUrl += "=d"
works perfectly. The only difference between the requests used to fetch images and videos is the appended 'v' to the URL for videos.
We would really appreciate a fix or to this issue. It would be a pain to have to migrate to another service but this one is starting to rival it.
Response to a GET to baseUrl += "=dv"
:
<!DOCTYPE html>
<html lang=en>
<meta charset=utf-8>
<meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
<title>Error 400 (Bad Request)!!1</title>
<style>
*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
</style>
<a href=//www.google.com/><span id=logo aria-label=Google></span></a>
<p><b>400.</b> <ins>That’s an error.</ins>
<p>Your client has issued a malformed or illegal request. <ins>That’s all we know.</ins>
jf...@google.com <jf...@google.com> #44
We understand that this is an important issue for many of you. While we don't have any updates to share, please do continue use the +1
functionality on the issue tracker to highlight this issue. Please do not reply unless you have any new information to share.
If you are seeing severely compressed (or low quality) videos, check that the mediaMetadata.status
field is READY
before accessing its base URL with the =dv
parameter. You may receive an error or a low quality version of the video before it has finished processing. This issue covers the case where the video has finished processing, but the returned video has a lower frame rate/quality than expected.
Re
ch...@gmail.com <ch...@gmail.com> #45
bp...@gmail.com <bp...@gmail.com> #46
ki...@heldig.org <ki...@heldig.org> #47
ne...@gmail.com <ne...@gmail.com> #48
be...@gmail.com <be...@gmail.com> #49
ta...@gmail.com <ta...@gmail.com> #50
ma...@gmail.com <ma...@gmail.com> #51
pa...@fletch.cx <pa...@fletch.cx> #52
jo...@felixideas.ch <jo...@felixideas.ch> #53
jo...@gmail.com <jo...@gmail.com> #54
ni...@gmail.com <ni...@gmail.com> #55
el...@gmail.com <el...@gmail.com> #56
ku...@gmail.com <ku...@gmail.com> #57
fi...@gmail.com <fi...@gmail.com> #58
th...@gmail.com <th...@gmail.com> #59
lu...@m1cr0man.com <lu...@m1cr0man.com> #60
nd...@gmail.com <nd...@gmail.com> #61
se...@gmail.com <se...@gmail.com> #62
ni...@gmail.com <ni...@gmail.com> #63
83...@gmail.com <83...@gmail.com> #64
ap...@gmail.com <ap...@gmail.com> #65
ar...@gmail.com <ar...@gmail.com> #66
ga...@gmail.com <ga...@gmail.com> #67
I want to be able to download full resolution videos from Google Photos for video editing and vlogs, and if the API doesn't allow for I'll have to switch to another cloud provider.
we...@gmail.com <we...@gmail.com> #68
af...@afxnet.net <af...@afxnet.net> #69
been downloading the videos manually from Google Photos since 2019.
ca...@gmail.com <ca...@gmail.com> #70
wi...@gmail.com <wi...@gmail.com> #71
This seems like baseline functionality, can we get an ETA on when this will be addressed?
al...@proton.me <al...@proton.me> #72
ke...@gmail.com <ke...@gmail.com> #73
si...@gmail.com <si...@gmail.com> #74
ar...@gmail.com <ar...@gmail.com> #75
wi...@gmail.com <wi...@gmail.com> #76
th...@gmail.com <th...@gmail.com> #77
ke...@knnth.co <ke...@knnth.co> #78
zl...@gmail.com <zl...@gmail.com> #79
ol...@gmail.com <ol...@gmail.com> #80
ps...@gmail.com <ps...@gmail.com> #81
ro...@gmail.com <ro...@gmail.com> #82
je...@gmail.com <je...@gmail.com> #83
ma...@merlinstoll.nl <ma...@merlinstoll.nl> #84
al...@gmail.com <al...@gmail.com> #85
ps...@gmail.com <ps...@gmail.com> #86
er...@gmail.com <er...@gmail.com> #87
source -
gi...@gmail.com <gi...@gmail.com> #88
This is a long standing bug. ALL videos downloaded by this API are ALWAYS transcoded to lower quality. There is no trouble reproducing this issue at all. If you want a demonstration, go get my google photos backup project and use it to download a few videos, compare them with the same downloaded via google photos web app.
al...@gmail.com <al...@gmail.com> #89
gi...@gmail.com <gi...@gmail.com> #90
0t...@gmail.com <0t...@gmail.com> #91
For tracking changed files/photos, this would require a normal full account access login and the API to look for changes which aren't implemented in the project.
hu...@gmail.com <hu...@gmail.com> #92
jj...@sigi.icu <jj...@sigi.icu> #93
iv...@gmail.com <iv...@gmail.com> #94
ts...@gmail.com <ts...@gmail.com> #95
al...@gmail.com <al...@gmail.com> #96
th...@e-x-e.dk <th...@e-x-e.dk> #97
da...@gmail.com <da...@gmail.com> #98
ph...@gmail.com <ph...@gmail.com> #99
li...@google.com
Clearly this isn't a priority...but SIX years and nothing??? I l discovered this bug literally right AFTER signing up with the 5tb plan under my developer account. Didn't even think about checking beforehand since it's such a basic feature. Well...just cancelled that account, my wife and son are also cancelling their separate accounts, and moving to another provider.
su...@gmail.com <su...@gmail.com> #100
ke...@gmail.com <ke...@gmail.com> #101
ed...@gmail.com <ed...@gmail.com> #102
cr...@gmail.com <cr...@gmail.com> #103
Could you please provide an update here?
ad...@datacenter-heller.de <ad...@datacenter-heller.de> #104
This would make it a lot simpler to export phots. The Takeout is a joke, with all the JSON scattered across. Either Google should address this or offer a takeout option that simply downloads photos and videos with their original EXIF and date created data, so that users can simply move their library to another service!
Description
For example a 200mb video comes back as 4mb.
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).