Created September 11, 2014 at 08:52AM Uploaded September 17, 2014 at 03:52AM Short http://flic.kr/p/pfXEaw Original
expression of freedom
2014-09-17
Glacier Bay, Alaska, 9-11 (C) 2014 RichHall.com
Created September 11, 2014 at 08:52AM Uploaded September 17, 2014 at 03:52AM Short http://flic.kr/p/pfZDdF Original
2014-09-06
2014-09-05
One Way to Split RAW+JPEG on iOS
 |
| Image via Wikimedia Commons |
Worry not. If you have a travel router like the US$36 HooToo TripMate at hand, you can split the RAW and JPEG pairs without much trouble, so that you can store the RAW files for later, and share the JPEG versions now.
1. If you don't already have it, buy the FileBrowser app from the App Store. It may well be the best $6.99 a travel NAS owner can spend, if only for its Chromecast button.
2. Connect your camera's memory card to the router via a USB card reader.
3. Configure FileBrowser to recognize TripMate by adding a server at 10.10.10.254 using your TripMate admin credentials (other routers have different specifics). Only configure once; after that, the NAS will show up automatically.
4. Use FileBrowser to copy JPEGs to the "Photo Library > Camera Roll" and RAWs to "My Files" (scratch space).
5. In a Web browser, log in to the travel router to tell it you want to remove the USB storage.
6. After disconnecting the memory card reader, you can then connect a portable HD to backup your RAWs, then remove the RAWs from the iPad to save space, while keeping the JPEGs in iOS for fun.
7. Send a howler to Apple to fix iOS. Kidding, but do politely let Apple know you need access to JPEG half of RAW+JPEG files in iOS apps (not just iPhoto) without this much trouble. "Squeak them wheels."
From the iOS Camera Roll, IFTTT can now see the new photos and upload them to Flickr. You can edit them in any iPad photo app and share them.
Of course, there are other ways around the problem. You could use a laptop, or manually shoot separate photos of RAW and JPEG, or edit RAW+JPEG files in iPhoto. EyeFi cards and apps help, but they're often too limited for extended travel. What I'm looking for are ways to shoot RAW+JPEG and get them into an iPad or iPhone using nothing but a Camera Connection Kit and iOS apps in a way that lets most photo apps access them.
Of course, there are other ways around the problem. You could use a laptop, or manually shoot separate photos of RAW and JPEG, or edit RAW+JPEG files in iPhoto. EyeFi cards and apps help, but they're often too limited for extended travel. What I'm looking for are ways to shoot RAW+JPEG and get them into an iPad or iPhone using nothing but a Camera Connection Kit and iOS apps in a way that lets most photo apps access them.
If you know a less obscure way to split RAW+JPEG for iOS, please leave a comment on the blog below, and I'll update the blog with your solution assuming I can verify it works.
Jim Heid suggests US$4.99 PhotosInfoPro, but I haven't tried it yet.
Have a perplexing tech conundrum to figure out? Circle me at Google+ and just ask; I'll do my best to think it through with you.
Jim Heid suggests US$4.99 PhotosInfoPro, but I haven't tried it yet.
Have a perplexing tech conundrum to figure out? Circle me at Google+ and just ask; I'll do my best to think it through with you.
Until next time...
2014-09-02
If Blogger, then Tumblr
After years of setting up social networks for clients and using them daily under code names or a job title, last weekend I decided to explore some possibilities using my personal site as an experiment. Instead of taking my usual Webhead approach, I wanted to find out what it would take to integrate a broad social media presence under three unreasonable constraints:
1. Don't rely on Facebook integration -- that would be far too easy
2. Avoid custom code or Yahoo! Pipes -- easy for geeks, but what might a Muggle do?
3. Pay as little as possible -- even if those who don't pay for a product are the product
Of course, the point of avoiding the usual shortcuts was to harvest new shortcuts, and I came away with more than a few. You may have a better strategy mine, but without any real code, IFTTT helped me blend a few dozen social media apps into two hubs on blog platforms. Each social site or app has its own strengths and weaknesses, so I use whichever seems best or easiest for a task, then let IFTTT automatically post my original content to Blogger and any other interesting links (likes, favorites, bookmarks, pins, etc.) to Tumblr. Sure, I could have done just one blog and let labels/tags sort them out, but a dual-blog setup also works fine and has some advantages.
To serve messages, I like Twitter for announcements and discovery, but Google+ as a forum for more in-depth discussions. So I let G+ handle Blogger's comments while Twitter tweets the Tumblr feed. For now, Blogger posts currently get two tweets: one for the Tumblr community, and the other for Google+ discussions. A small concession, but maybe I'll find a way to avoid double-tweeting Blogger posts.
Generally, it seems least obnoxious for automated messages to target blog and microblog platforms rather than community sites. In the background, content may be coming through Flickr, Instagram, Pinterest, YouTube, Google Sites, About.me, Feedburner, and on and on. Many of these have active communities of their own for whom automated messages could inspire ill will.
Web development experience probably wasn't necessary, but did aid the DNS tweaking required for adding Google Apps, Blogger, and Tumblr to your own domain name and burning RSS feeds through Feedburner to make them palatable for IFTTT. I did configure some `.htaccess` redirects by hand for fun, but that wasn't really necessary. I stuck with the built-in templates and only tweaked them through the included Web interfaces. [Correction: I added !important to one line of CSS which Google Sites munged, but the template would have looked fine without it]. I'll definitely start tweaking Web code in a few weeks, but it wasn't really required.
The approach should with Facebook and Instagram, but doesn't rely on them (to be sure, I haven't even connected Facebook yet). IFTTT replaced what I might usually do in PHP or Pipes. I paid nothing extra, beyond the usual domain name registration fees. I have a pro Web host available for later, but am not using it right now except for its DNS control panel, which the registrar also provides.
At this early stage, it remains to be seen how much amateur social networking I'll ever do; time will tell. Documenting a photography hobby and offering coding tips might be a place to start.
As a parting shot, please remember I'm not saying this approach is up to my professional standards. I just wanted to how well an uninitiated hobbyist might do over a weekend. Maybe I'm subconsciously lowering the bar to match my leap, but so far, I'm impressed with the current state of free Web tech for non-programmers.
If anyone is interested in specifics, I can cook up a step-by-step guide as I get spare time, and maybe work up some reusable IFTTT recipes to share. The guide Mike Elgan wrote about relaying Google+ to Twitter and Facebook covers several of the few remaining gaps in IFTTT's features, so remember it if you find something IFTTT has trouble doing.
1. Don't rely on Facebook integration -- that would be far too easy
2. Avoid custom code or Yahoo! Pipes -- easy for geeks, but what might a Muggle do?
3. Pay as little as possible -- even if those who don't pay for a product are the product
Of course, the point of avoiding the usual shortcuts was to harvest new shortcuts, and I came away with more than a few. You may have a better strategy mine, but without any real code, IFTTT helped me blend a few dozen social media apps into two hubs on blog platforms. Each social site or app has its own strengths and weaknesses, so I use whichever seems best or easiest for a task, then let IFTTT automatically post my original content to Blogger and any other interesting links (likes, favorites, bookmarks, pins, etc.) to Tumblr. Sure, I could have done just one blog and let labels/tags sort them out, but a dual-blog setup also works fine and has some advantages.
To serve messages, I like Twitter for announcements and discovery, but Google+ as a forum for more in-depth discussions. So I let G+ handle Blogger's comments while Twitter tweets the Tumblr feed. For now, Blogger posts currently get two tweets: one for the Tumblr community, and the other for Google+ discussions. A small concession, but maybe I'll find a way to avoid double-tweeting Blogger posts.
Generally, it seems least obnoxious for automated messages to target blog and microblog platforms rather than community sites. In the background, content may be coming through Flickr, Instagram, Pinterest, YouTube, Google Sites, About.me, Feedburner, and on and on. Many of these have active communities of their own for whom automated messages could inspire ill will.
Web development experience probably wasn't necessary, but did aid the DNS tweaking required for adding Google Apps, Blogger, and Tumblr to your own domain name and burning RSS feeds through Feedburner to make them palatable for IFTTT. I did configure some `.htaccess` redirects by hand for fun, but that wasn't really necessary. I stuck with the built-in templates and only tweaked them through the included Web interfaces. [Correction: I added !important to one line of CSS which Google Sites munged, but the template would have looked fine without it]. I'll definitely start tweaking Web code in a few weeks, but it wasn't really required.
The approach should with Facebook and Instagram, but doesn't rely on them (to be sure, I haven't even connected Facebook yet). IFTTT replaced what I might usually do in PHP or Pipes. I paid nothing extra, beyond the usual domain name registration fees. I have a pro Web host available for later, but am not using it right now except for its DNS control panel, which the registrar also provides.
At this early stage, it remains to be seen how much amateur social networking I'll ever do; time will tell. Documenting a photography hobby and offering coding tips might be a place to start.
As a parting shot, please remember I'm not saying this approach is up to my professional standards. I just wanted to how well an uninitiated hobbyist might do over a weekend. Maybe I'm subconsciously lowering the bar to match my leap, but so far, I'm impressed with the current state of free Web tech for non-programmers.
If anyone is interested in specifics, I can cook up a step-by-step guide as I get spare time, and maybe work up some reusable IFTTT recipes to share. The guide Mike Elgan wrote about relaying Google+ to Twitter and Facebook covers several of the few remaining gaps in IFTTT's features, so remember it if you find something IFTTT has trouble doing.
Storm at Stonehenge (Stormhenge) taken 2011-10-04 by Rich Hall http://richhall.com
Taken September 02, 2014 at 08:08AM Uploaded September 02, 2014 at 01:08PM Short http://flic.kr/p/oKBmoG Original http://ift.tt/1pm0aL8
Subscribe to:
Posts (Atom)