Posts Tagged ‘photography’

I’m Back! I think.

26 January 2017

Well, this is odd. It’s been a bit over a year, I think (too lazy to look and see for sure) since my last posting here. On top of that, this particular post isn’t necessarily my standard fare. It’s probably a mix of rant and quick updates. All ranting is my personal opinion, of course. No pretty pix, those will come later.

So, which first, the rant or the updates? Ah, you figure it out, they’re all mixed together.

Photography wise, it’s been a bust, between building the Vardo (done!), Idaho weather, my dad, and other stuff, I’ve not actually gone out “to do photography”. I’m working on that, though, and you can expect some more pictures this year. Time lapse. Video. Landscapes. Macro. Whatever grabs my attention at the moment. And yes, I did indeed say video, that wasn’t an error.

I’ve written a small script, more a proof of concept idea than anything else, that I plan to video. If it turns out good enough, I might even look into YouTube. My granddaughters want me to start putting my videos up there and I’m tempted. If this project works, I probably will start putting a couple of older videos up and create more. I never expected to get into or enjoy making video but I find I do.

Don’t expect much in the way of audio on my videos. I’ll try and include music based on the input of other people, but I have a beef with the lousy captioning on YouTube and am going to extract my revenge by including captions and no voicing. So there. I swear, I never know whether to laugh or cry when I see the automatically generated captions on most of the YouTube videos. It sucks. The only ones any good seem to be those that go out of their way to include captioning themselves.

This next video project is showing me a bunch of stuff already, and I can’t get out to the Owyhees to film it. Film it…video it…whatever. I have a DJI Phantom 4 and that’s what gave me the idea for this video. Next up, I needed a video recorder that could become your eyes, so I wound up asking around and borrowing a GoPro Hero 4 Black. The video specs for that match well with the video specs for the drone, BUT the Hero 4 is a fixed fisheye. More on that later.

The Hero 4 has no playback capability and the only way you can get any kind of immediate feedback or live feed, is to use their Capture app. Or a third party one. And guess what? Those idiots at GoPro seem to think you absolutely need to log into their servers before you can get any use out of the app. Yeah, right. Waaaay out in the middle of the Owyhees, where I set up for my video on the GoPro and test it, where there’s NO cell service? How in Hades am I supposed to log into their servers from there? Stupid and pointless. However, I did manage to find an older Capture version and that one lets me have live feed and control over the camera to change settings WITHOUT having to log into their freaking servers first. Those of you out there wanting this…look for the newest version prior to 3.x. It also has the older logo. Just be sure and don’t allow your apps to automatically update or it’ll get replaced with the new one. You’d think losing their market share would warn them and that it’s logical that if you want to keep your fan base, you shouldn’t push out an upgrade that makes it impossible to use the app where there’s no service. Especially for a camera intended for extreme stuff out in the middle of nowhere. I guess common sense isn’t part of the job requirement there.

Now about the GoPro fisheye situation. For my wants, the fisheye gives me a great wide field of view, but it does have those pesky fisheye effects. You know, the curved  vertical and horizontal lines that should be straight.

To remove the fisheye effects, there are plenty of tutorials and apps out there. The first I tried was the GoPro PC app. Posts, reviews. blogs all say it has a built-in fisheye fix that’s good. Guess what? Yup, you got it. It, too, requires a server login. Forget it, I’m not gonna look for an older version of that, too. That made it easy to uninstall and discard with only a second or two’s thought.

I moved on to four programs that I already have. I’ve restructured my home systems so I have a laptop that’s just for photography work. On that machine, I have Linux as my OS: Ubuntu Studio. There are some things I don’t like about the OS layout, so I may just migrate to a clean, minimal Ubuntu 16.04 and have only the video and graphics programs that I find work for me. And yes, there is a point to mentioning this.

The four programs I was looking at for the fisheye removal are: Adobe After Effects (Win), daVinci Resolve Free (Win), OpenShot (Win/Linux), and Kdenlive (Linux).

OpenShot was the first I looked into, and while it’s a nice basic editor, it was taking me too long to find out how to deal with the fisheye effect so I dropped that approach. I then went and played with After Effects and it did a reasonable job, but the file size went from 357 MB to 12 GB. HUH? OK, I figured that was user error and I could set the parameters better later or transpose to a different format. At the same time I was playing with After Effects, I was messing about in Kdenlive. That one was not only easy to deal with the fisheye, but it had a couple different ways to do so. After I got done trying After Effects, I then looked into daVinci Resolve. This was just as easy to use as Kdenlive but the free version is apparently time bombed or has a file size or video length restriction. Unlike last time I used it, this time it slapped a watermark on the entire video. I’m going to look into that, but if that’s the case (time bombed or file size) then I’m going to toss it.

So, looking at the various outputs, I was rather surprised to find out that the best resulting corrected video came from my Linux machine: Kdenlive’s Defish filter. Not by a little, but by an easily noticeable difference. File size, quality of resulting video, quality of corrections…Kdenlive was the best. daVinci Resolve was the next, but it had a huge file size as well. That I expected, though, as Resolve doesn’t output the final video, only the feed into the conversion. That I could live with. To be honest, though, when I started looking at these I really didn’t expect the Linux program to come out ahead like that. That was a very welcome bit of support for my Linux love.

I’m going to take a look at PiTiVi (also Linux) later and see how it compares to Kdenlive, but going forward right now it looks like for my project I’ll be using Kdenlive as my editor.

On the writing front, I’ve been assembling an ebook with the various tales of the Pa’adhe. It has a cover for each story plus the ebook itself. I need to create three more covers, so I’m waiting for the weather here to get better so I can go get the pictures I need. We’ve busted the local records across the board for snow this winter. We got more than the winter of 1985, and that was on the ground only about two weeks. This winter’s snow has been on the ground for over a month now, and it’s been piled high. Buildings have collapsed as a result of the amount and type of snow.

I’ve sure enjoyed my first year retired, but funny enough, I sort of seem to be way more busy than when I was working. And I’ve still not gotten back into my radio stuff. Maybe this year!

A Return Update

5 March 2015

It has been a weird beginning to the year for me.

I fully meant to return to this blog well before now, but somehow writing for my blog just wasn’t a priority. From time to time, I’d think of something to write about, but I just never sat down and actually did so.

From an amateur radio standpoint, I’ve been working to develop something I refer to as The Thumper. It’s based on something I read about in a blog post where the ham described his fondness for CW (Continuous Wave, aka Morse Code) and an on-the-air experience meeting a group of deaf learning ham radio and cw. The original Thumper was mentioned only in passing, and described as “a device that attaches to their forearm and taps them to indicate the Mose Code being received.” I have various issues with LED displays and my current tactile transducer setup leaves much to be desired. For The Thumper, I’d started by utilizing an Arduino driving a RC servo and while that does work to an extent, it has an inherent speed limitation that I don’t like. Almost anything over 10 wpm keeps the servo at the end of travel, making it impossible to detect the characters. I’m now looking at using a vibrator similar to those in cell phones, compliments of a good friend and fellow ham. Although not what I originally envisaged the vibrator does show better promise and a nice theoretical response to faster CW speeds. Coupled with a LED, it may turn out to be the best solution for me to listen to the radio. I know, but the combination might turn out to be better than the parts. Right now, I’ve only got the Arduino driving the vibrator. Still to be done is receiving and converting over-the-air CW signals provided via the audio jack of my radios.

Plans are under way for more Owyhee explorations, and while doing that I fully intend to try HF radio work from way out in the middle of nowhere. I’m building an end-fed, multi-band wire antenna that should be tuned to each band: 10m, 20m, 40m, and 60m. It’s only mobile in that you can easily carry it coiled up in the vehicle, to use it you have to park and deploy it. We’ll see how that works in practice, but I’ve got good expectations. I’ll be focusing, of course, on CW and PSK but when solo. If I have a friend along, I’ll be trying some phone work as well. More than likely, I’ll be band scanning and if I hear anything, I’ll pause on that and see if I can contact the other person.

Photography-wise, I’m currently teaching a beginning photo class, but with a twist. In all my previous classes I noticed that there was never a deaf or hard-of-hearing person attending. This time, I told the community education group that I would teach a beginning class in sign language. When I shared this idea with the few deaf community members I knew, the enthusiasm was outstanding. In the end, due to various reasons, there were only three in my class. We’re having a blast and there would have been at least two more were it not for an age limitation posted on the community education web page. That limitation didn’t apply to my class, but that exemption information was not passed on to the people that wanted to sign up. Word’s starting to get out there about this class, though, and I’ve mentioned I’ll offer it again, the same way. One of the reasons for doing this is that I just felt like turning the tables on the regular offerings…they’re oriented towards hearing people, the deaf have to get an interpreter. This time, though, it’s the hearing that have to get an interpreter if they try to attend.

I have also been investigating the use of the Shutterbug Remote with my Pentax K3 DSLR. Testing with an iOS device showed that the remote works well with the K3, but I’m getting crashes using the Android version of the app on my Samsung Galaxy Note 4. Testing with a Samsung Galaxy S5 shows it works reasonably well with that phone, so now I’m trying to determine whether or not it’s a setting, a FW, or a HW issue with my Note 4. An email to the developers has not provided any response, so I’m very unimpressed with the customer service aspect of their website. Enough that I’m not providing a link to it. It would be really nice to get this remote working with my phone as it’s a great little device which when used as an intervalometer provides better timing control capabilities than the built-in intervalometer mode of the K3. If I can’t get it working, I’ll definitely have to create an Arduino intervalometer or something.

I’ve built a new woodworking bench (above) in my garage along with a DIY woodworking bench vise (below). These will come in handy when I start building the Vardo.

On the Vardo front, I’ve started gathering materials to modify the trailer for the Vardo. It took me a while to figure out the best way to use my flatbed trailer for the Vardo, and still be able to easily use it as a flatbed trailer. One of the things I had to deal with was me being “greedy.” The flatbed trailer is 12’ by 6’ and I had been doing my designing based on that entire area.

Image of a 6 foot by 12 foot utility trailer with one pair of wheels. Sides are an open framework of angled metal. Tail gate is about 4 feet tall when up and contains a metal mesh. Parked next to a blue-green 1992 Chevy Blazer in front of the garage in the driveway.

This is the new utility trailer that will become the base for the Vardo. I’m especially happy to get the all metal bed.

I was going to have a big Vardo that had luxurious room inside. Kind of a contradiction to my original plans for a simple, cozy Vardo, actually. As a result, one of the things I had to figure out a way around was the six tie-downs on the trailer bed near the sides. I finally realized that they provided a perfect way to fastend the Vardo to the trailer, a la pickup campers: straps built onto the framework of the Vardo that connect to the trailer tie-downs via turnbuckles. To do that meant I had to narrow the width of the Vardo box to fit inside the tie-downs enough that I could hook them into place and tighten. It’s only a 6” loss in width, give or take, but it also freed up the solution to another issue: I wanted to put the same kind of mesh that I had on the tailgate along the sides of the trailer. That way, things put in the trailer wouldn’t roll out under the existing side rails. And I could use that now open area to store poles for awnings, and other such gear.

I’ve been doing quite a bit of fishing lately, for rainbow trout. Normally I would catch and release trout, but my wife and I have found that we like the fish. I’ve learned to fillet them so that we don’t really need to worry overmuch about bones while eating. Only about 15 minutes from my house is a great little pond where, so far, I’ve always managed to catch my limit every day. I didn’t use to fish that much, or to enjoy it, but I’m finding I do. I’ll probably go fishing rather regularly while retired, using that to supplement our diet with fresh fish on a regular basis. It’ll be interesting to see how the fishing goes as the weather warms up.

K3 First Light – M42

17 December 2014

To paraphrase the narrator in a YA fantasy trilogy, “Say what you will about the Pentax K3. Say that the K3 is fast.”

All images here are shown without any post processing other than to convert from RAW to JPEG. I did resize them smaller to save space but you can still see the noise and M42 for comparison.

Sunday I got up about 0300 to get a drink of water and looked out the window at the night sky. It was so clear, the stars were so bright, I could see Orion, and it was 30° F.

I went back to bed. I lay there, thinking how great the night sky was. I thought about my new camera and how it would be a great chance to check ISO vs shutter speed. I thought about how I would set up that test. I thought how Orion was right there. I thought how I really should go out and take some astrophotos.

After the third time through all that, I thought, “Geez! Quit thinking about it! If I’m going to think about it this much, I should just get up and do it!”

So I did.

M42, the Orion Nebula, aka the Great Nebula in Orion, taken with my new Pentax K3, 400mm, 5 sec., f/5.6, ISO 1600.

M42, the Orion Nebula, aka the Great Nebula in Orion, taken with my new Pentax K3, 400mm, 5 sec., f/5.6, ISO 1600.

I mounted my Tokina 400mm on the K3, set up the tripod, connected the cable release, and went to work. My plan was simple: to run a series of shots to explore the results of different shutter speeds applied to each available ISO suitable for astrophotography.

First of all, this was from my driveway, which is not exactly a dark sky site. The light pollution isn’t all that bad, fortunately, but it’s there: you can’t see the Milky Way, but you can make out M42, the Great Nebula in Orion, as a fuzzy patch.

Given the 400mm’s small field of view, I decided to make M42, the Orion Nebula, my target because it was right there in plain sight, at a comfortable angle, and easy enough to line up on. Since this was just a test to see what I would get, I set up everything and did the shooting without checking each image immediately afterward. After all, I just wanted to see what each combination of ISO and shutter speed would give me. Plus it was 30° F and getting colder.

From experience using my K10D, and to some extent my *ist DL, I knew that I needed to expose for 10 or more seconds to get anything. I wanted to see how much noise there was at the higher ISOs. I decided that I would test with the following string of shots:

ISO: 51200, 25600, 12800, 6400, 3200, and 1600

Shutter speed: 30, 25, 20, 15, 10 seconds

The remaining variables were constant: aperture was wide open at f/5.6 and the focus was manually set. Since this 400mm doesn’t have an autofocus or auto-aperture, the K3 required me to manually enter the focal length. There was no setting on the K3 for 400mm but there was 600mm so I used that. Afterwards, for just the photos posted here, I used an EXIF editor to correct the reported focal length (changed from 600mm to 400mm) and effective focal length (changed from 900mm to 600mm).

The first new thing I played with was the focus. The Pentax K3 has Live View, and I was eager to try that. My 400mm is fully manual, so I set the camera to manual focus mode. Then I made sure the aperture ring was turned to 5.6, wide open. Next I focused through the eyepiece as best I could, triggered Live View and zoomed in on one of the stars visible. Watching the Live View, I adjusted the focus ring on the 400mm until I had the sharpest possible view of the star. I don’t think it was perfect, but it was definitely at the best possible focus.

The next step was to compose my shot. I was using a cable release to avoid any shaking from pressing the shutter release. For the timing, I wanted it to be consistent, so rather than using Bulb mode I used Manual mode and set the shutter speed to each of the desired values as the shoot went on.

I started with ISO 51200 and 30 seconds. Then I went to 25 seconds, 20 seconds, 15 seconds, and finally 10 seconds. At that point, I dropped the ISO to 25600 and worked my way back up the exposure times. Next, ISO to 12800 and downward on the speeds…you get the idea. I shot all the times against each ISO before changing ISO settings.

At the top of this post I mentioned that the K3 was fast. I’m used to every 30 second exposure needing 30 seconds to store the image to the SD card. Even with my old, non-high speed SD cards, storage to the card even with noise reduction on was still well under 30 seconds. It even seemed to speed up as the shoot went on, perhaps due to the cold?

While changing the ISO, I accidentally went to 5 seconds exposure when I moved the wrong wheel. I was about to change it back to 10 seconds when I decided, “Why not?” So for the end of the downward run at 3200 and the upward start to 1600 ISO, I had two 5 second exposures.

It wasn’t until the next later that morning that I actually looked at the pictures to see what I got. The results, as they say, were nothing short of astounding. For one thing, I flat out did not expect to get the purple/pink of the nebula in the images. I simply had never tried imaging M42 with the 400mm before. Hades, I hadn’t even expected that simply with the 400mm I could achieve a “classic” image of M42! I thought you needed a big telescope for those.

At only 5 seconds of exposure at 1600 ISO, I fully expected the whole image to be black, with maybe a couple of stars showing up. That was NOT the case and I was floored with the result.

The unprocessed (other than to convert from RAW to PNG) 1600 ISO 5 second image is at the top of this post. Even the 3200 image below is awesomeness.

M42 Orion Nebula Pentax K3, 400mm, f/5.6, 5 sec., ISO 3200

M42 Orion Nebula
Pentax K3, 400mm, f/5.6, 5 sec., ISO 3200

There is more noise with the 3200 than the 1600 ISO, as would be expected, but more of the nebula is visible in the 3200 ISO shot, again as expected.

At first I didn’t expect to see star trails, but then I realized that the field of view through the 400mm is so small that it would take less exposure time for the stars to move across the image than for, say, a 135mm lens. Or a 50mm.

At the higher ISOs, the image is actually washed out from being overexposed! I absolutely did not expect that. Things really only start getting visible in the 10 second 51200 ISO exposure.

M42, the Great Nebula in Orion, buried in the overexposure. This is the first image (see text) where M42 is truly visible in a test image. Pentax K3, 400mm, f/5.6, 10 sec., ISO 51200.

M42, the Great Nebula in Orion, buried in the overexposure. This is the first image (see text) where M42 is truly visible in a test image.
Pentax K3, 400mm, f/5.6, 10 sec., ISO 51200.

Working through the images afterwards, it was very noticeable that there is a line in the sand related to noise and it’s at the 12800 ISO vs 6400 ISO point. This is clearly evident in the two images below.

Showing the dividing line between ISO 12800 (left) and ISO 6400 (right). This is the point where the noise level really drops between ISOs. To either side of this line the noise level is gradual, here it's somewhat abrupt.

Showing the dividing line between ISO 12800 (left) and ISO 6400 (right). This is the point where the noise level really drops between ISOs. To either side of this line the noise level is gradual, here it’s somewhat abrupt.

All in all, I am very pleased with my new Pentax K3 camera. I certainly didn’t expect to get such a “classic” image of M42 with just the K3 and my old manual 400mm Tokina. And with the pink/purplish glow of that nebula, to boot! This camera has several tools such as internal stacking that are ideal for astrophotography and I’m really excited to play with them.

Hmmm. I wonder what’s possible with my Classic Celestron C8 mounted on the camera? Or even just with the K3 plus 400mm piggybacked for tracking. ISO 1600 for 3 seconds each, stacked? ISO 3200?

I can’t wait to get out and try again now that I know what this Pentax K3 is capable of.

The best of the season to you all!

See you next year.