Jump to content

fritzunruh

Members
  • Posts

    36
  • Joined

  • Last visited

Reputation

10 Good
  1. Did you sort this out? I'm having the same issue with an A1 and would really like to turn it into the correct direction as well.
  2. I looked into it a bit - I'm afraid you're right and its shutter capping... Does someone have a source on how to address the tension of the shutter springs and maybe even get to the parts that might need lubrication on a Canon A1?
  3. I really hope you’re wrong :(( Most of the pictures of that roll were shot a the fastest shutter the camera offers (1000th), the ones that show the problem were definitely shot at that way though!
  4. Hey guys, I encountered a problem and was hoping somebody might have seen it before and can tell me if my suspicions are correct and my lens is somehow broken. I got hold of a Canon 35-70mm f4 FD Lens for my A1, which looks good and does work without issues on multiple shots but when stepped down quite a bit (probably above f8) theres a huge area that is heavily underexposed. It is definitely nothing in front of the lens or inside the body that is blocking the light either, most of the shots of the roll are fine. This is what the aputure blades look like... I feel they should be more evenly round then they are, or am I wrong? Testing on a digital camera with adapter works without issues on all aputures, although they do not close when I take a picture. Did someone see this problem before? Is the lens one for the trashcan? Thanks a lot!
  5. Thank you! AE-1P, Canon 50mm 1.4, Tri-X 400
  6. Bangkog in january, taking the time of to digitalize my negs, too.
  7. I see, unfortunately I don’t have access to the scanner easily to try again in 16bit. I do eventually want to use ACR or LR for edits, I just left out the editing part for testing what might cause the artifacts. My problem and question is why it looks the compressed way it does after leaving LR or ACR as a lossless tif or png export. The problem doesn’t exist before, shouldn’t a lossless export no matter what bitsize look just like that - lossless? Or at least not create heavy compression artifacts I’d expect from a low quality jpeg? Because thats what’s happening and I have no idea what could cause the issue or if it just happens on my system for some reason.
  8. Thanks, I know that there’s a little issue with this banding in the original file, my main problem is the way it looks after leaving LR or ACR as a lossless tif or png, because it looks way different from the source data.
  9. It makes a lot of sense to test where the issue is and eliminate the edit as the root of the problem. So your theory is that there is no problem at all and it’s just because it’s 8-bit? That would mean that if you were to open the tif in ps through ACR (like I asked before and you asked why on earth you would do that) then exporting a lossless png you could replicate my compression artifacts exactly, right? That’s a way of tackling a problem and finding out if it’s just you, the software, the hardware or no real issue.
  10. I‘d like to be able to edit the picture without introducing artifacts. The reason I‘d like to do so is to apply creative edits such as crop, contrast and color. Is that impossible in your professional opinion? None, the artifacts appear without any further edits whatsoever. I exported them in any way I could imagine, see above. Exporting is not necessary to get the artifacts either, they appear as soon as the image is processed by ACR and opened within photoshop. I’m still not sure in what way exporting a quality level 3 jpeg is practically comparable to opening the image through ACR. Theoretically I understand that I might be inducing a step of processing the image, that has an effect on it, but I can’t believe it has such a massive destructive impact and that’s just the way it’s supposed to be.
  11. Because that is where the problem is! Lightroom and ACR seem to run a similar engine that both cause this problem, I‘m aware that the file itself isn’t the issue but the processing through LR/ACR, that’s why it would be interesting to see how it goes on other systems. How is exporting a compressed jpeg and opening a TIF with LR or ACR the same?
  12. Tried the custom settings already, unfortunately no change. Thanks for trying to help, it really is an odd problem, just glad that I‘m not just too stupid. I just got in touch with Adobe, something I should have done earlier, they offered they check the file and try to replicate the problem on several systems - I‘ll let you know how my odyssey ends.
  13. But did you send it through ACR when opening it in PS? When I turn off the automatic ACR for tiffs I don’t get the banding as well.
  14. For the sake of completeness: I tried to work with the flawlessly exported png-files, to see if it might be an issue of the original tif itself - it isnt. Even the pngs created by PS show the issue as soon as LR or ACR touches them.
  15. Thanks for staying with me in these hard times, John. You're right, disabling ACR helped photoshop being able to save as a png without issues. 1) Turning on GPU works, too. 2) Web-legacy export to png works (although with reduced contrast) 3) PS export works with and without sRGB (the latter with reduced contrast) 4,5) Works with GPU as well 6-9) When just the GPU for ACR is deactivated, the issue appears within ACR preview as well as in PS as well as in all exports. When GPU for ACR preview is activated but processing GPU is deactivated the issue doesnt appear in ACR preview but in PS as well as in all exports. When GPU for ACR is completely activated the issue doesnt appear in ACR preview but in PS as well as in all exports. In conclusion, it seems that a GPU acceleration is needed for the whole process but fails when the data is handed over from ACR to PS - exporting directly from ACR produces the error as well.
×
×
  • Create New...