I’m not sure if the butterfly house is part of the Discovery Gardens or merely adjacent to them, but several companies have written indexes and algorithms to search this fancy Internet thing, and seeing as I’m a professional researcher, I guess I can go find out… Continue reading “Texas Discovery Gardens – the whole story”
Texas Discovery Gardens – Bokehmatic!
Thanks to a Groupon, Hana and I found ourselves at the Texas Discovery Gardens over in Fair Park a couple of weeks ago. The weather was beautiful. I shot a roll of film that I’ll share at some point, and otherwise rocked Hipstamatic—my old standby—on the iPhone 5.
I’m going to stretch the posts out a bit on this, as I’ve done for awhile now. But to be honest, I’m feeling the need to do more contemporaneous shooting and posting, rather than shooting in spurts and then setting posts up to run weeks or months in advance.* Continue reading “Texas Discovery Gardens – Bokehmatic!”
Hipstamatic D-Series: best of the best
And this is the best of the best, I think. So spooky. So very, very spooky.
Of course, I only got 289 shots with it, and most of those were just shooting whatever to fill up test rolls.
Snapseed vs…
So is the Workaround worth it? For some things, maybe… but it’s really just another image toy.
So here’s the Original.
And here’s the Snapseed edit.
Compare that to a similar edit from Enlight. 
Pretty similar…
Except for the Glow filter in Snapseed (which I quite like), and all the borders and artistic filters and whatnot in Enlight (which I don’t much use), the apps have similar capabilities.
To tell the truth, Enlight is far more powerful, but it’s also $4. Snapseed is free. The Workaround might be worth it.
Snapseed file-save workaround
So here’s the workaround to get a good new image. Continue reading “Snapseed file-save workaround”
Maybe it’s not Snapseed’s problem…
Last night while I slept, Jorge sent me an email with a workaround to the Snapseed image saving problem: “The best way I ahve found is to import your photos using AirDrop. Your edits will all be intact and it works a lot faster than uploading to DropBox…”
Thanks, Jorge!
After reading Jorges email, curious about why this might be, I did a bit of searching around and read up a bit on Snapseed’s new ‘Stacks’ feature, which Google uses to add a ‘non-destructive workflow’ enhancement to Snapseed.
With Stacks, edits are stored in a metadata file, and you can go back and modify adjustments or remove them entirely at any time.
When you save a file, all you really save is this metadata file. And when you save a copy, Snapseed copies the original image, adds a new file name, and associates a new metadata file with that image.
As I surmised, it’s a feature and not a bug, and it comes via Apple: this is the exact same behavior you find with the Edit options in the Camera Roll.
Still sounds buggy, but at least it’s on purpose, and not entirely Google’s fault (though they could easily add a ‘Save as…” option that baked in the edits and make this easy on us).
In researching and finding the source of the problem, I came across another workaround and a description of how the whole process works.
It would be nice if Google modified the Save as Copy to save the image with edits baked in, or if they implemented another save option that saved the image with edits in place, but until then, we have two workarounds.
Sad thing is, Enlight is as good and needs no workaround; VSCO is as good and needs no workaround; there are likely other apps that provide similar options and don’t require a workaround. Don’t believe me? I’ll post some compare/contrast later tonight, InshaAllah.
Here in a bit, I’ll post screenshots of the workaround. I was going to post them here, but this post has gotten long enough already.
Did 2.0.1 fix the problem with Snapseed?
So I noticed that Snapseed had a bug-fix update after work today, and eagerly installed it.
Did 2.0.1 squash the bug?
Before I get to that, I thought of something I forgot to check earlier… the newfangled Photos app I won’t be using…
Sadly, it doesn’t see the edits either. (This was likely a silly test, as it seems probable that it uses Image Capture to import, but was worth a check anyway.)
Maybe this too was fixed in the update? I hate it when other people do this, but… you’ll have to read on to find out. Continue reading “Did 2.0.1 fix the problem with Snapseed?”
