Jump to content


  • Content count

  • Joined

  • Last visited

About Tschens

  • Rank

Recent Profile Visitors

566 profile views
  1. You made my day, DM1 from Down Under :-). It works perfectly with files from the OMD E-M1. The files from OMD E-M1X cannot be imported, even not with the very recent iOS update 12.2. I hope there will be a minor update soon which solves this issue. Cheers, Jens
  2. Good point, thanks for that. I tried it with an ORF file from the brand new Olympus OMD E-M1X, which is not supported yet. Maybe that's the problem. I will try with another ORF file in the evening and let you know.
  3. Unfortunately, this doesnt work for me. I have the following RAVPower device: https://www.amazon.de/RAVPower-kabelloser-Kartenleser-Zusatzakku-Festplatten/dp/B00VUGUPH6/ And I did not find an easy way to import my Olympus RAW (*.ORF) files from either an inserted SD card or a connected USB harddrive. Although there is the option to open an ORF file via the provided RAVPower "FileHUB" app with affinity, affinity crashes without an error message (it simply closes). Urgently waiting for a solution. iCloud is not an option since I am often on travel where I dont have an internet connection. Any ideas? Jens
  4. Currently, this seems to be the only solution. I will try that.
  5. That's exactly the way I do it. However, when I open >10 files in order to insert my copyright logo via a macro, it is not relly convenient to click >10 times file, export, etc etc. The saving procedure takes much longer than the real work on the files. The exporting procedure is currently an absolute no-go for me. Is there really no solution for that issue?
  6. Exporting each single opened file is really cumbersome. I was searching for a solution for that, thinking that there must be one, and came accross this thread. Come on, developers/support/moderators. Is there really no option for exporting all opened files in a row with a few mouse klicks? What is the export persona good for? When I have several files opened and switch to the export persona in order to define the exact export parameters and switch then to the next file, I am I am bounced back into the another persona and have to repeat everything for the second file. Same is true for the next 23 files. "§$%&/()'#=(/*+&%$§%&/()=??
  7. Tschens

    Problem with macro

    Ok, here is the whole package (brushes, macros, example pics [pre & post]). The macros only work correctly if the layer is named "Hintergrund". The macro called "Jens Hartmann Photography 1.7" works for landscape format, the "Jens Tangerine V.1.7 hochformat" for vertical format. The third one produces only the frame, without text. However, since Version 1.7., all 3 produce only the frame without any text. Thx for your help. Btw: Any idea how I can get the macro to work independently from the layer name? Affinity Macro Bug.zip
  8. Since I upgraded my beta from 1.6.5 to 1.7.0.x, I have a problem with a macro which I use to create a frame+copyright text around my pictures. The final 2 steps of the macro is a self-made "picture brush" with my copyright text. This picture brush doesnt work any more, it simply doesnt appear in my pics. I re-created the final 2 steps of the macro and it worked again, but after re-starting affinity it again doesnt work. Is this a known isue? I could provide the macro + picture brush, if needed. Btw: Is there a way to erase single steps within a macro or to re-arrange the order of the single steps of a macro to fine-tune it? Couldnt find this option so far. If the answer is no, please put that on a wish-list. :-)
  9. Just an update on the installation procedure for Neat Image 8. The installer automatically detects Affinity Photo as well as Affinity Photo beta. However, the path where the plugin for the beta is installed is wrong: C:\Users\YOUR_USER_NAME\AppData\Roaming\Affinity\Photo\1.0 (Beta)\Plugins It should be: C:\ProgramData\Affinity\Photo\1.0 (Beta)\Plugins Just move the NeatImage8.8bf file into that folder and it will work. Hope this helps, Jens
  10. I think I have a similar problem. I have an RGB document with large areas of "black" (RGB 0,0,0). When I take the pipette in order to grab this black, and then switch from RGB to CMYK, it is shown as CMYK 72, 68, 67, 88. Even more strange, when I do the same in Adobe Photoshop, the CMYK color is 86,85,79,100. When a printshop printed this file recently, they had to add a black frame with Photoshop in order to add some space for the frame (print on canvas). And now guess: After printing, the additional black frame was much darker then the original black, and it looks terrible. Is it a bug or a feature?
  11. Tschens

    Field Blur Filter Bug

    When applying a field blur filter in the form of a live filter layer, the handle is not movable, it always drops when I try to move it. In contrast, the filter/blur/field blur option works perfectly fine. Regards, Jens
  12. Tschens

    Underwater Photography

    Hello, my name is Jens and I am an Austrian Underwater Photograph. Many of my pics are developed with Affinity Photo or Affinity Photo for iPad. Thanks to the Affinity team for the option to present my work on the Spotify Website, and special thanks to Charlotte for her support. Here we go: https://affinityspotlight.com/article/underwater-photographer-dr-jens-hartmann-blue-water-blue-sharks-no-ground-below-me/ Feel free to ask your questiona on underwater photography here. Dive safe, Jens
  13. Tschens

    Wrong/No lens correction?

    After searching around for 10 minutes, I finally found out what you mean. I have to disable the lens correction in the assistant. I was always playing around with the check box on the right hand side (see screenshot) which did not help at all. BTW: The checkbox in the assistent window "Hinweis, sobald der Assisstent eine Aktion durchführt" [something like: Message, as soon as the assistent performs an action] does exactly nothing. No message. Never. This would have been helpful to solve my issue. I think we have some potential for improvement in the GUI here :-) Thx for your help! Jens
  14. Tschens

    Wrong/No lens correction?

    Any news on that problem? Here is another example. Left: Irfan view. Richt: Affinity. The tree on the right side is totally blurred in Affinity Photo. I provide the original ORF file as well. Unfortunately, I found now way to bypass this problem. A correction of this bug would be very much appreciated since currently I cannot work on my 8 mm fisheye ORF files with Affinity Photo. PA140224.ORF