If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.
Special Thanks To:
Aaron Holmes
Aaron Wheeler
Adam Horden
Alan Scrimgeour
Andre
Andrew Haynes
Anonymous000
asabase
Austin Weil
barney
Barry
Bert Hickman
Bill Kukowski
Blitzorn
Brandon Paradelas
Bruce Bowling
BubeeMike
Byong Park
Cesiumsponge
Chris F.
Chris Hooper
Corey Worthington
Derek Woodroffe
Dalus
Dan Strother
Daniel Davis
Daniel Uhrenholt
datasheetarchive
Dave Billington
Dave Marshall
David F.
Dennis Rogers
drelectrix
Dr. John Gudenas
Dr. Spark
E.TexasTesla
eastvoltresearch
Eirik Taylor
Erik Dyakov
Erlend^SE
Finn Hammer
Firebug24k
GalliumMan
Gary Peterson
George Slade
GhostNull
Gordon Mcknight
Graham Armitage
Grant
GreySoul
Henry H
IamSmooth
In memory of Leo Powning
Jacob Cash
James Howells
James Pawson
Jeff Greenfield
Jeff Thomas
Jesse Frost
Jim Mitchell
jlr134
Joe Mastroianni
John Forcina
John Oberg
John Willcutt
Jon Newcomb
klugesmith
Leslie Wright
Lutz Hoffman
Mads Barnkob
Martin King
Mats Karlsson
Matt Gibson
Matthew Guidry
mbd
Michael D'Angelo
Mikkel
mileswaldron
mister_rf
Neil Foster
Nick de Smith
Nick Soroka
nicklenorp
Nik
Norman Stanley
Patrick Coleman
Paul Brodie
Paul Jordan
Paul Montgomery
Ped
Peter Krogen
Peter Terren
PhilGood
Richard Feldman
Robert Bush
Royce Bailey
Scott Fusare
Scott Newman
smiffy
Stella
Steven Busic
Steve Conner
Steve Jones
Steve Ward
Sulaiman
Thomas Coyle
Thomas A. Wallace
Thomas W
Timo
Torch
Ulf Jonsson
vasil
Vaxian
vladi mazzilli
wastehl
Weston
William Kim
William N.
William Stehl
Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Registered Member #15
Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
TDU,
Cool. See, your camera is just fine. For star trails, the easiest way is just the same as with sparks. Limit your exposure to about five minutes, assuming you don't overexpose the sky, and repeat this for about an hour or two. Limit time between exposures to about 5-10 seconds.
Now take all the exposures, and combine them in photoshop using the LIGHTEN blend method. This keeps the background the same intensity as a single exposure, yet stacks the star trails on top of each other.
Here is about an 1.5 hours of exposure from my place in Ocean City, MD. The sky is pretty bright here, so its not too spectacular.
Also, the best shots for star trails are centered around one of the poles (south in your case), so you get nice concentric rings.
Registered Member #15
Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
The streak is a boat. This was a quickie, so i didn't correct it. To correct it, i would simply make another layer (blend NORMAL) and erase that light using the eraser tool.
Registered Member #10
Joined: Thu Feb 02 2006, 09:45AM
Location: Bunbury, Australia
Posts: 1424
EastVoltResea wrote ...
... Limit your exposure to about five minutes, assuming you don't overexpose the sky, and repeat this for about an hour or two. Limit time between exposures to about 5-10 seconds.
Now take all the exposures, and combine them in photoshop using the LIGHTEN blend method. This keeps the background the same intensity as a single exposure, yet stacks the star trails on top of each other...
My camera takes at least 5 minutes to compute the noise reduction after a 5 min shot. Should I not be using the noise reduction?
As to Photoshop, I have resisted getting it so far. My distorted logic is that I can't "cheat" with my photos if I don't have it. I guess I will have to get over that.
Registered Member #15
Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
wrote ...
My camera takes at least 5 minutes to compute the noise reduction after a 5 min shot. Should I not be using the noise reduction?
I never use the in-camera noise reduction. You probably don't need it. Its basically only for getting rid of non-random noise such as hot pixels etc...
wrote ...
As to Photoshop, I have resisted getting it so far. My distorted logic is that I can't "cheat" with my photos if I don't have it. I guess I will have to get over that.
Yes, your logic is definitely distorted. Using photoshop to post-process images is NOT cheating and the techniques you would be using would really be no different than if you were in an actual darkroom manipulating negatives and film. Of course, if you cut an image from the Hubble Space Telescope and plopped it into your image, that would be cheating, but standard processing techniques such as sharpening, noise reduction, levels, curves, etc... are basically the equivalent of similar techniques used on real film in the darkroom.
Dan
BTW, here is another Milkyway image I took this past week.
Registered Member #27
Joined: Fri Feb 03 2006, 02:20AM
Location: Hyperborea
Posts: 2058
My camera takes at least 5 minutes to compute the noise reduction after a 5 min shot. Should I not be using the noise reduction?
The camera takes another 5 minute exposure with the shutter closed and subtracts in from the first image. If you don't do that in camera you have to do it manually because there are some issues with noise and CCD heating. If you do it manually you can just keep a few dark frames on your PC as long as the temperature and exposure length are about the same.
As to Photoshop, I have resisted getting it so far. My distorted logic is that I can't "cheat" with my photos if I don't have it. I guess I will have to get over that.
Since you are thinking that you are not likely to be tempted to cheat. The camera uses processing that is based on an algorithm created in a dark basement in Tokyo, since it is just a computer program it does not understand the image and will sometimes do it completely wrong. Correcting those mistakes are never cheating.
I always have my camera set to take JPEG+RAW, that way I can use the JPEG files for normal use and when the white balance turn out wrong or the JPEG file does not have the dynamic range required I load the RAW file and adjust that. The RAW file contains a lot more information both in colours and in details.
Registered Member #30
Joined: Fri Feb 03 2006, 10:52AM
Location: Glasgow, Scotland
Posts: 6706
Photoshop rules, TDU! The way I think of it is this: If you shoot JPGs with your digital camera, it's like shooting slide film with an old-fashioned film camera. The dynamic range is quite limited, and the camera does its best to fit the scene into that range, like Bjørn explained.
If you shoot RAW, it's like negative film: it captures more detail than can be shown on a print. (often 12 bits per colour, whereas JPEG files can only store 8.) You can then use Photoshop to "print" your "negative" to a JPEG file (or to a printer) using all the same fancy tricks, like dodging and burning, that people used to do in "real" darkrooms.
99% of the time I just shoot JPEGs, but at least I know what I'm missing
Registered Member #15
Joined: Thu Feb 02 2006, 01:11PM
Location:
Posts: 3068
Sort of. Regardless of the ISO, RAW or JPG mode, the camera always captures the exact same information at the sensor. Changes in ISO does not affect the sensitivity of the camera and does not change the amount of information recorded by the camera. Also, whether you are in RAW or JPG mode, the camera still captures the same information. However, in JPG mode, the camera's processor will automatically stretch the information as captured by the sensor to match that of the sensitivity of film. So in actuality, shooting JPG is more closer to that of negative film than RAW mode. In RAW mode, you basically get out exactly what the sensor records.
For most photos, JPG is absolutely fine as most of the information is distributed across the histogram, centered about the middle. However, when the processor stretches this data, data recorded at the extremes (highlights, and shadows) is usually tossed away. Again, with normal daytime photos, this information really isn't revelevant anyways.
However, with astronomical images, or even spark images, there is a lot of information which is recorded at the left end of the histogram (black) which is important to the photographer where JPG mode will simply throw this info away (due to the auto stretching by the processor). With RAW mode, this information is saved, and by manually stretching the histogram using photoshop for example, you can redistribute this important data over a large portion of the histogram which can then be readily seen by the eye.
For regular photography, this is most important for shadow recovery or highlight recovery. For astrophotography, this means tweaking out every bit of detail from very dim nebula for example.
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.