Scott and Carl, Many thanks for your feedback. Much appreciated.
After checking into this image a bit more I would like to come back to the apparent issue in a bit more detail. As my snow image above has demonstrated at least to me, the E-M5 II is capable of high resolution, pretty much artifact free quality images, provided one uses sufficient care in shooting and post-processing an image. So if something doesn't look quite right, the question arises: WHY?
The snow scene I shot from within my house, wind not causing camera motion. The tree branches may have been minimally affected by wind, but certainly not the fence wires. Also the grey stripes, in the first version of the image derived from the raw file, could be traced back to post-processing inadequacies and eventually avoided.
The current image
was shot about 15 yards away from a road with heavy car traffic. There might also have been an occasional minimal puff of wind. This could have possibly had a slight impact on camera motion with negative consequences. So I would like to examine the central part of the image a little closer.
When shooting in high res mode the E-M5 Mark II, one has to use a tripod and one gets three files per shot if the camera settings are set to
SL F + RAW and
High Res Shot, namely an .ORF, .ORI, and a 7296x5472 .JPG image. Of course, PS CS6 can read the .JPG image. With the help of the
Olympus High Res Shot Raw File Photoshop Plug-in Software Software Download | Olympus High Res Shot Raw File Photoshop Plug-in | OLYMPUS IMAGING CS6 can also read in the .ORF file, resulting in a 9216x6912 image. However, so far I am not aware how to directly read in a .ORI file with CS6.
In contrast Iridient can read in all 3 files, the .ORF, .ORI, and the 7296x5472 .JPG image.
Iridient can also save the .ORF file as a 16 bit .tif image in these pixel sizes 4608x3456, 7296x5472, 9216x6912, and 12288x9216. Other pixel sizes seem possible, but I have not tried them.
Likewise Iridient handles .ORI files.
Whereas for the .ORF file the E-M5 Mark II has combined several shots into a single file, with advantages and apparent disadvantages, the .ORI file contains the data just from a single shot. So it's very convenient to retreat to a single shot image if the multiple shot composite doesn't give the desired outcome, for whatever reason.
In the following I have used CS6 (with Olympus Plugin) and Iridient to generate images and crop out the central part.
Processed with CS6 (with Olympus Plugin), default settings. Image shot at Date Time: Mar 11, 2015, 6:21:19 PM.
I clearly can see the diagonal stripes in many parts of this crop, going from the upper left to the lower right.
Iridient has the following panels:
Expo Color Mono Curves Detail Lens.
Processed with Iridient, default settings except all boxes checked in the Lens panel. Image shot at Date Time: Mar 11, 2015, 6:21:19 PM.
Here the diagonal stripes seem less pronounced and are barely visible to my eyes.
Clearly some sort of pattern is visible as an artifact in the image.
Can one make that pattern more visible or preferentially make it disappear?
Processed with Iridient, default settings except all boxes checked in the Lens panel. Image shot at Date Time: Mar 11, 2015, 6:21:19 PM.
Here I also set in the Detail panel, Edge Detail from 100 to 500 = max, Texture/Micro Detail from 5 to 25 = max.
Now the stripes have become more visible to me eyes.
So in conclusion I agree with Carl that some unintended camera motion must have affected this composite image.
The next question on mind is what does the image look like that can be derived from the one shot .ORI file?
Here is the crop from it, processed the same way as the last image and mapped to the same size.
Image shot at Date Time: Mar 11, 2015, 6:21:19 PM.
Of course no sign of camera motion. To my eyes this image also has coarser features.