Jump to content
You must now use your email address to sign in [click for more info] ×

lefteye

Members
  • Posts

    6
  • Joined

  • Last visited

  1. I use Adobe Bridge CC (which is free) and FastRawViewer to rate and select files, and steer clear of applications such as LR that require importing of photos and cataloging. Bridge does all I need in that regard. ACR is a great raw developer - simple and to the point. I use Bridge and open raws into Affinity's raw developer (just as if ACR). All that Affinity lacks is the ability to save a sidecar along with the raw. Affinity certainly does not need to integrate a DAM (if it ever does and forces cataloging I'm out). It just needs to save the raw settings as a sidecar. I'm not sure why everyone doesn't want this? It's just saving the settings as a text file, no big deal to implement. I'm certainly not asking for it to become Capture One etc, just to save a sidecar - that's it, that's all, nothing else added.
  2. I'm not sure why you are trying to look away from the fact Affinity Photo is an image editor AND a RAW developer. Just like I don't use Lightroom, I use Photoshop and ACR. When Affinity develops a raw file the raw file is not destroyed - this is obvious, the raw developer is not destructive. The settings used to develop the raw could be saved within a sidecar file without any problems or length coding. The settings are not an 'image file' they don't need to be another image format, they are just a text file - this is obvious. I presume you know what an .xmp file is - it's not an image file. I can't believe I'm having to explain this. The raw develop settings, under the Basic, Lens, Curves and Tones tabs, can at present be individually saved as presets - these preset are not image files, they are just text files - this is obvious. If all the Basic, Lens, Curves and Tones tabs could be saved as one collective preset then associated with the raw file as a sidecar then the raw developer within Affinity would become incredibly useful - and just by saving presets collectively as a sidecar. Affinity already has all the raw power it needs, it can save presets, it just need the guys at Affinity to do an afternoon of coding to add the sidecar save/load ability. Alternatively we could all forget that Affinity can already develop raw files and save raw setting presets, and also pretend that it destroys raw files.
  3. In my OS Prefs, Highlight is set to the default of pale blue (I expect 99% of OSX users leave it as pale blue) - I don't see how this affect the text colour of the Apply button. It seems to be that the text colour retains the white of your dark theme option, and unlike all the other buttons in the Light mode, doesn't change the text to black, hence the white on white issue.
  4. I've read many requests for this, the reasons for it's importance (BTW it's pretty much essential!), the reasons from Affinity why it hasn't been implemented and the cumbersome totally impractical workarounds; I'm not going to reiterate all that here, but simply state the case... 1. if the .xmp sidecar format cannot be implemented due to incompatibilities with Adobe etc, use a proprietary sidecar format (to cover the all the Basic / Lens / Details / Tones adjustments). This is actually an easy job, I could write this code in less than a day - its just a write/read text file. 2. if local adjustments cannot be included yet, omit them, just give us the global adjustments in a sidecar now (and then work on inclusion of local adjustments). 3. add an option to use the 'Previous Conversion' settings (this is just a copy of the last 'sidecar' file in an application known fixed location - that's overwritten with each conversion). / 4. associated to raw though not to sidecar files... when in Develop, viewing gat 1:1 zoom, and adjusting the Detail / Sharpening, the pixel render of the screen result is persistently smoothed, when he file is Developed it is not smoothed. Why is the screen smoothed in Develop mode?? - this renders Sharpen adjustments erroneous and impossible to equate to the developed outcome, please remove this weird smoothing of pixels in raw Develop mode! Thank you.
  5. I'm a new user of Affinity Photo. Coming from Photoshop there's two features I'm really missing in Separated Mode - either I haven't found them or I recommend they are added. 1. As a pref option, allow the application window to extend down below the main top toolbar - that can be sized to fill the screen. I often have other applications open and my desktop is quite busy with files, so an application window hides all this. It's a big deal. When not in Separated Mode the application window does it's job and hides all my other applications and the desktop - but I need to work in Separated Mode - and hide what's behind. 2. with multiple files open (again in Separated Mode) an option to scroll/pan all windows at once. So eg if I zoom in to 100% on two or more files, holding 'Space-bar' down and dragging will drag all the windows together in sync.
  6. Mac OSX 10.10.5 Affinity Photo 1.8.6 When using, Prefs > User Interface > 'Light' UI style, all dialogs buttons are missing their APPLY label (Apply is white on white). On clicking the 'empty' button Apply does then appear - just as the dialog closes.
×
×
  • Create New...

Important Information

Terms of Use | 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.