![]() ![]() Well, the structure of the files is a bit different indeed. You may ask about the difference between original raw file and output DNG file. Or you can save result as JPEG or TIFF and you will get the same image you see in the program. You can save it to DNG file if you want to postprocess result in your favorite RAW engine like Adobe Camera RAW or UFRAW etc. So after stacking of source images, after fixing artefacts with retouching tools, even after adding text and scale you still have raw image as an output/result. The image update is a bit slower, but the initial underlying raw image stays always absolutely intact! Even when you use retouching brushes in Helicon Focus, the program copies raw data back and forth and then applies postprocessing operations to show you the result on the screen. Each time you pan or zoom the image, the program takes raw data and applies all the raw operations. With this new mode Helicon Focus does most of the raw development ‘on the fly’ just in order to display the images on the screen for you. ![]() Let’s compare the processing algorithm structures to make the difference more apparent: With a new feature of Helicon Focus the file processing chart looks differently. Once all the stages of raw development are done you will not be able to go back to, let's say, white balancing any more or undo highlights clipping. On each stage some part of image data might be lost. During raw image development, on the way from raw file to the one in the chosen format data goes through a range of processing stages. Raw image files contain data from the sensor that underwent minimum changes. To understand all the benefits of this new processing mode let’s have a simplified overview of raw development process algorithm. Even more – you can even retouch stacking result without actually developing it! How is it all possible you ask? Let’s start from the top. It means that color balance and highlights clipping – which are the most destructive operations of all the postprocessing/raw development – can now be done after focus stacking is completed. ![]() My experience is that they will hold their breath for a period of time (assuming they are calm) and then occasionally take a big breath of air.Helicon Focus Pro now has got another truly valuable feature – it can process raw files in their native color space. The vast majority of my photography is of pit vipers. Assuming the light did not change drastically and the frog did not change position from one sequence to the next, would this be a recommended strategy?Ģ. Suppose I swapped out all the exhale shots from the sequence for an inhale shot from one of the other sequences, in an attempt to have a stack of all inhale shots. For each focus point, there’s a reasonable chance that I’ll have at least one photo where the the frog is inhaling. ![]() Suppose I run a sequence of focus shifts on the frog, then I do it again, one or more times. You get straight to the point, include all the necessary information, and somehow manage to answer nearly all the questions I had coming into each video.ġ. Great workshop, Steve! You have a gift for teaching. So, are these pre-adjustments even necessary then? To me it seems like you are doing the same steps twice at the additional costs of being able to edit a stacked Helicon raw file (which presumably is more powerful than editing an already processed TIFF) !! ? You say they are minimal, but in the field you are also shooting manual to make sure lightning doesn’t drastically change. I guess I am confused quite a bit by the necessity for the pre-processing adjustments. Or is it even necessary to first make these adjustments? If Helicon uses raws and also preserves the output file as raw, would it not be more powerful to do these adjustments on the final stacked raw file (and potentially save an editing step)? But would it make sense to export as DNGs instead of TIFFs and then use Helicon, which can deal with raw files? I guess, if you always are adjusting the files in lightroom first, using the raw files is kind of obsolete, because these are necessarily just that “raw”. I am tempted to go with Helicon, because of that. I know that Zerene Stacker does not accept raw files, but Helicon does. Is there a reason, why you are always exporting as TIFFs ? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |