6 ms·

Author here: Note that I did select Original and it still seemed to compress the RAW file in Google Drive view. Single downloads do yield the original.

by rubenv 11y ago

jervisfm 11y ago
Have you tried Google Takeout [1]? I understand that will let you download all your data. [1] - https://www.google.com/settings/takeout https://www.google.com/settings/takeout
- patcon 11y ago
  Wow. That's a polished interface. Glad it exists
  - zo1 11y ago
    Unfortunately, it's a bit iffy for individuals that have unreliable internet. The download link expires after a while (last time I tried to do a large export).
    - bwillard 11y ago
      Sorry about that. Did you try the move to drive option? One of the reasons we added the ability to move the finished archive to Drive was to allow users with unreliable internet connections to use the Drive Sync tool to sync the finished download down to their computer. I know it is a little inconvenient but it should make it possible to download a large archive over an unreliable connection. (I work on the Takeout team)
      - zo1 11y ago
        I didn't know about that option; I must have missed it at the time, or it wasn't available back then. I'll give it a go, thanks!
      - oh_sigh 11y ago
        Does your takeout archive include the drive takeout archive?
        bwillard 11y ago
        It does, there was a lot of debate on whether it should or not. If you have strong opinions one way or the other I would love to hear them as we are open to changing that behavior. If you don't want that behavior, or just want to export part of your drive (or photos) collection you can expand that product in the Takeout UI and just select certain folders.
- smtddr 11y ago
  Whoa, nice. Had no idea Google could provide me the _original_ files I uploaded to youtube.
saidajigumi 11y ago
What does "compressing" a RAW file even mean? Is the actual content in the smaller downloaded version in some other format (e.g. JPEG)? Or is it simply truncated, either due to a bug or else stripping the actual RAW data, leaving only an embedded JPEG image? It seems implausible that anyone would consider it a good idea to reencode a RAW file as a matter of course. Transcode it to process and/or compress it? Sure. But what comes out the other end isn't usually a native RAW file. (native RAW -> DNG workflows don't count.) This assumes that such a thing is even possible: e.g. that all RAW formats they'll see permit an alternate compressed encoding. If they did, someone needs a good stern talking-to. Pretty much the last thing that anyone who uses RAW files would expect is a workflow that tampers with the files while still allegedly remaining in the native RAW format.
mvgoogler 11y ago
Thanks for the article. I work on the photos team. I will file bugs for the drive-sync issue and the issue with the large downloads failing and try to get some answers.
- rubenv 11y ago
  Nothing but love otherwise! In case it wasn't clear: Photos looks fantastic. Add an API and it's perfect.
  - saurik 11y ago
    Given that it doesn't have an API, I don't understand why it was announced at Google I/O. What is supposed to be a conference for developers has somehow turned into a place for Google to demo a ton of random new end-user product features.
    - sangnoir 11y ago
      In your opinion, only those products with API's available today should be announced? That sounds overly restrictive. By the same logic - Projects Jacquard and Vault shouldn't have been announced either. I think it's fair to announce products so devs can be ready when the API becomes available.
      - biafra 11y ago
        Only if they really plan to add an API. What about Hangouts for example? Did they announce an API for Photos?
      - saurik 11y ago
        First of all, "there were a couple things tacked on to the presentation that maybe could one day be used by a developer" is a pretty desperate argument, given that the keynote was three hours long and focussed on a ton of things that don't have any API at all, like Photos, and did not mention a single implication for a developer even for the things which had APIs, such as Now on Tap (which means that developers had no reason to bother going to the sessions on that feature, as it was clearly something designed for end users only; apparently it actually has a couple APIs). However, sure: I'll bite. No: announcing random stuff that we can't play with and that they won't talk to us about is totally useless for developer. This entire event was just about causing people to go "wow, they are smart". I am a developer quite interested in 3D video, and so despite seeing Project Jump and going "ugh, another end-user product announcement", I figure I might as well talk to the engineers about it: only, they aren't willing to say anything about what might be available or how it works or essentially anything about their plans... so good luck "getting ready". Regardless, the next thing you really need to defend, as this is what we are talking about: what are you, as a developer, doing to get ready for Photos? Google I/O has become less and less developer-focussed ever since it started (I have gone every year), and has turned into more and more of just a showcase of their end-user products. This year as the epitome, and all of the developers that I know who attended were quite disappointed; even the ones who still liked last year's somehow were now also saying "this event seems to have lost its purpose and is no longer useful".
mvgoogler 11y ago
Quick follow-up. I can reproduce this on my own account. I uploaded a raw (NEF) using desktop uploader using the "Original" setting. Downloading through the photos app returns the original NEF file. Downloading via Drive returns a file with the original name ("Foo.NEF") that is actually a jpeg. So this is clearly broken. Bug filed. I will follow up when there is some kind of resolution.

Author here: Note that I did select Original and it still seemed to compress the RAW file in Google Drive view. Single downloads do yield the original.

by rubenv 11y ago

Author here: Note that I did select Original and it still seemed to compress the RAW file in Google Drive view. Single downloads do yield the original.

jervisfm 11y ago

Have you tried Google Takeout [1]? I understand that will let you download all your data. [1] - https://www.google.com/settings/takeout https://www.google.com/settings/takeout

patcon 11y ago
Wow. That's a polished interface. Glad it exists
- zo1 11y ago
  Unfortunately, it's a bit iffy for individuals that have unreliable internet. The download link expires after a while (last time I tried to do a large export).
  - bwillard 11y ago
    Sorry about that. Did you try the move to drive option? One of the reasons we added the ability to move the finished archive to Drive was to allow users with unreliable internet connections to use the Drive Sync tool to sync the finished download down to their computer. I know it is a little inconvenient but it should make it possible to download a large archive over an unreliable connection. (I work on the Takeout team)
    - zo1 11y ago
      I didn't know about that option; I must have missed it at the time, or it wasn't available back then. I'll give it a go, thanks!
    - oh_sigh 11y ago
      Does your takeout archive include the drive takeout archive?
      - bwillard 11y ago
        It does, there was a lot of debate on whether it should or not. If you have strong opinions one way or the other I would love to hear them as we are open to changing that behavior. If you don't want that behavior, or just want to export part of your drive (or photos) collection you can expand that product in the Takeout UI and just select certain folders.
smtddr 11y ago
Whoa, nice. Had no idea Google could provide me the _original_ files I uploaded to youtube.

saidajigumi 11y ago

What does "compressing" a RAW file even mean? Is the actual content in the smaller downloaded version in some other format (e.g. JPEG)? Or is it simply truncated, either due to a bug or else stripping the actual RAW data, leaving only an embedded JPEG image? It seems implausible that anyone would consider it a good idea to reencode a RAW file as a matter of course. Transcode it to process and/or compress it? Sure. But what comes out the other end isn't usually a native RAW file. (native RAW -> DNG workflows don't count.) This assumes that such a thing is even possible: e.g. that all RAW formats they'll see permit an alternate compressed encoding. If they did, someone needs a good stern talking-to. Pretty much the last thing that anyone who uses RAW files would expect is a workflow that tampers with the files while still allegedly remaining in the native RAW format.

mvgoogler 11y ago

Thanks for the article. I work on the photos team. I will file bugs for the drive-sync issue and the issue with the large downloads failing and try to get some answers.

rubenv 11y ago
Nothing but love otherwise! In case it wasn't clear: Photos looks fantastic. Add an API and it's perfect.
- saurik 11y ago
  Given that it doesn't have an API, I don't understand why it was announced at Google I/O. What is supposed to be a conference for developers has somehow turned into a place for Google to demo a ton of random new end-user product features.
  - sangnoir 11y ago
    In your opinion, only those products with API's available today should be announced? That sounds overly restrictive. By the same logic - Projects Jacquard and Vault shouldn't have been announced either. I think it's fair to announce products so devs can be ready when the API becomes available.
    - biafra 11y ago
      Only if they really plan to add an API. What about Hangouts for example? Did they announce an API for Photos?
    - saurik 11y ago
      First of all, "there were a couple things tacked on to the presentation that maybe could one day be used by a developer" is a pretty desperate argument, given that the keynote was three hours long and focussed on a ton of things that don't have any API at all, like Photos, and did not mention a single implication for a developer even for the things which had APIs, such as Now on Tap (which means that developers had no reason to bother going to the sessions on that feature, as it was clearly something designed for end users only; apparently it actually has a couple APIs). However, sure: I'll bite. No: announcing random stuff that we can't play with and that they won't talk to us about is totally useless for developer. This entire event was just about causing people to go "wow, they are smart". I am a developer quite interested in 3D video, and so despite seeing Project Jump and going "ugh, another end-user product announcement", I figure I might as well talk to the engineers about it: only, they aren't willing to say anything about what might be available or how it works or essentially anything about their plans... so good luck "getting ready". Regardless, the next thing you really need to defend, as this is what we are talking about: what are you, as a developer, doing to get ready for Photos? Google I/O has become less and less developer-focussed ever since it started (I have gone every year), and has turned into more and more of just a showcase of their end-user products. This year as the epitome, and all of the developers that I know who attended were quite disappointed; even the ones who still liked last year's somehow were now also saying "this event seems to have lost its purpose and is no longer useful".

mvgoogler 11y ago

Quick follow-up. I can reproduce this on my own account. I uploaded a raw (NEF) using desktop uploader using the "Original" setting. Downloading through the photos app returns the original NEF file. Downloading via Drive returns a file with the original name ("Foo.NEF") that is actually a jpeg. So this is clearly broken. Bug filed. I will follow up when there is some kind of resolution.