Jump to content

sw-fuzzy

Members
  • Content Count

    11
  • Joined

  • Last visited

About sw-fuzzy

  • Rank
    Newbie

Recent Profile Visitors

355 profile views
  1. I have worked quite a lot with AP on the iPad pro during a trip and now exported psd-files for further fine tuning in Photoshop at my desktop computer. I have found out that there is an inconsistency in the AP parameter scaling of adjustment layers when opened in Photoshop. For instance a black&white conversion with the AP setting red=green=yellow=50%, blue=cyan=magenta=0 will open in PS as red=green=yellow=127, blue=cyan=magenta=0, which gives a totally overexposed picture. To get the correct tonal values in the picture as with AP I have to change the Photoshop setting to red=green=yellow=50. I attach the corresponding screen shots... The same happens for lightness/contrast: An AP setting of lightness=10% will result in a PS value of 25. It seems that all AP percentage values are stored in the psd file with reference to the value 255. This is quite annoying because it means that I have to rescale all parameters in Photoshop to get the same tonal values as with AP. A similar bug appears in the size change of a document. If I have a document size of 2100x2800 px with 300 dpi and I choose <centimeters> instead of <pixels> the program offers me the silly values of 2100x2800 cm instead of computing the actual document size which would be 2100/300*2,54=17,78cm width and 2800/300*2,54=23,71cm height. Likewise I can choose <inch> to end up with the total nonsense of 2100x2800 inch..... Greetings, Stephan
  2. I am fully on your side and claimed the same in a critical comment. Read this statement which shows that our desires will never be fulfilled: https://forum.affinity.serif.com/index.php?/topic/42040-affinity-ipad-version-is-not-worth-the-money/?p=210361
  3. Okay, thank you Andy for putting it in a nutshell. This makes clear that my desire will never be fulfilled by AP. It may have been my fault, but nowhere I found such a short and clear statement in the announcement of the software. I assume that this is a basic drawback which also is valid for the desktop version. My workflow is based on the smart filter technique of PS where I always can go back to the RAW data to tune them directly with ACR or update the master layer by an external standalone RAW editor like Hasselblad's Phocus. It is obvious that a complete picture processing is not possible on a mobile system like the iPad (without color calibration and other deficiencies). A serious processing will always need final tuning on a desktop computer. The more it is necessary to protect the original data information without losses if one starts working on an iPad. Lightroom mobile under this aspect is a quite valuable tool which offers a nondestructive RAW development which has of course restrictions but which can be modified and improved after coming home and synchronizing the data with the desktop computer so that it is not necessary to start again from scratch. My wish and hope was that AP on iPad would offer a tool to get ahead of some limitations of LR mobile but now I am aware that it is the other way round. :( Regards, Stephan.
  4. After my experience with Affinity on iPad you can develop a RAW image, but afterwards this development is gone and you cannot go back and edit your development parameters (like color temperature or b/w conversion or any other setting). For my work such a nondestructive RAW file development is of basic importance for further post processing. Is there any plan for such an improvement ?? As long as this feature is not available Affinity for me cannot rival Lightroom mobile... Regards, Stephan
  5. Okay, it was a bit harsh to use the word "crap"... But I don't see any help or sense in a tool which is able to open a RAW file but then cannot store the development parameters in nondestructive manner in order to modify them. This is even more astonishing by realizing that the nondestructive layer technique outside of the RAW development indeed works. I tried the software this afternoon several hours but could not get satisfied with the results and therefore I am tired to wait for any improvements. My general impression is that Affinity on iPad always will be problematic. For serious post processing for sure one has to use a powerful desktop computer. The advertising policy of Affinity therefore seems too euphoric. I took it by word and thought that this tool might offer things which I miss with Lightroom mobile (e.g. tilt corrections). But I realized that all the various (and to my opinion too many) post processing possibilities in Affinity cause basic problems in the software performance whereas on the other side the fundamental feature from my point of view (RAW development) is a weak spot. So I think that Lightroom mobile still is a more suitable tool for the iPad which even allows local corrections and runs smoothly even with 50MPx files ... Regards, Stephan
  6. It would have been nice to answer my comments on the RAW develoopment ...
  7. I bought the iPad version of Affinity in order to be able to work on RAW files on the road without a computer, but I am totally disappointed: - the software runs very slowly with RAWs of 20 MB which nowadays is a reasonable file size. Other data like Hasselblad 3fr files (50 MPx) are almost impossible to handle, the display likes to freeze very often.... - the most annoying thing is that the RAW development is destructive, i.e. if I push the develop button and afterwards realize that I better should modify the development all the settings and informations are lost. If I open the developer again the color temperature and tint are unknown and the settings are 0 / 0. All other changes also are lost and the control buttons are in 0 position. And if I use a black & white conversion in the development tool I cannot go back to the original color version once I pushed the "develop" button. This is total crap and I want my money back. Regards, Stephan Edit: I use the newest version 1.6.2 on an iPad Air 2 Fortunately the order cancellation in the Apple AppStore works much better than your software... I just got back my money. Good bye
  8. LR mobile works very well with RAW files (loaded to Photo by the SD-card connector or directly imported from iCloud). Equally well with pictures taken directly with 3rd party apps on the iPhone which allow RAW-file storage (dng).
  9. This is a more or less true statement. The iPad always can only be a very weak compromise to do some quick & dirty processing and under these circumstances one has to ask if the use of RAW files gives any basic advantage. But at least Lightroom mobile works quite well and also provides automatic synchronisation with the desktop app (even for 50 MPx medium format files !!).
  10. Sorry, but it seems quite senseless to me if you support the RAW file format of Hasselblad (3fr resp. fff) but do not support the lenses of this company. Under these conditions Affinity is no solution for me.
  11. I downloaded a test version for Windows and I realized that there is no possibility to apply a lens profile to the RAW file for development. In first place I am not interested in manual lens corrections but the most important thing is that the manufacturer's lens profile is used for automatic lens correction. I use a Hasselblad H5D-50c. I developed the Raw file in Photoshop RAW (where the lens is automatically identified and the profile applied) and compared it to the development in Affinity. Since there is no identification of the used lens in Affinity no lens correction is applied although the "lens correction" is switched on. The same drawback appears with pictures taken wit a NIKON D750 …. Under these conditions the software is useless for me... Or did I overlook something ??? Best, Stephan
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.