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

jorismak

Members
  • Posts

    132
  • Joined

  • Last visited

Everything posted by jorismak

  1. It's a beta. They want DWM since it's an improvement for a lot of things, while without DWM graphics drivers can cause issues. So they want to know everything works fine in pure DWM mode, because that way they know it's their code which is OK at the end. After that, if they enable non-DWM mode and things start crashing and glitching, it's clear it's the drivers fault and not the program in that case. Seems reasonable for a beta, although I never saw another program do it this way. Note that this doesn't exclude Windows 7 at all, it excludes Windows7 with the classic-windows-theme enabled. If you leave it to the default Windows 7 look it works OK. The only serious issue of this all is 10bit support on older Pro-gfx cards in Windows7, which disable DWM most of the times. No clue how this is in Windows 8 / 10.
  2. You pick the colorspace to _output_ / develop out of your raw file here (i believe):
  3. In the (my) other thread it was thought (by a developer I believe from Affinity) that the 16bit thing is a bug. Only some plugins work, but none seem to work in 16bit for now (even the whitelisted stuff like Color Effex). They're surely working on it. Note that you need to add your plugins folder to the preferences (edit -> preferences -> photoshop plugins) and then restart Affinity for Photoshop plugins to appear in the filter->plugins menu. No plugins folder was added during installation so none appeared out-of-the-box, needed to add the plugins folder by hand.
  4. Or explained a bit differently, that sRGB you see is what _you want it to be_ when you're done editing the RAW file and make it into a real photo with pixels. If you want it to be something else, pick something else :). As stated above, raw files don't have a color-space yet, it is 'undefined'. The job of a raw-converter is to take that data and map it to real color, and while doing so choose in what profile you want that color to be. Affinity just defaults to sRGB but you can pick Adobe RGB or ProPhoto or whatever you want. About the size: As you may know or not know, an image sensor (in your Nikon at least) is working in _groups_ of pixels. The Bayer filter. Now, at the sides of your image, you have pixels that are only half a group, or less. So what is a raw-converter to do with those edge-cases where it does't have a full group of pixels available to make up color? Most camera's and raw-converters crop those edge cases, but Affinity (and dcraw and some others) choose to 'make something up' at the edges to not throw away the few pixels at the side. As example, my Sony DSLR gives files of 6000x4000 with in camera jpg, and also when using raw-converters like DxO and CameraRaw. But the resolution is actually 6008x4024 or something like that. So most converters crop 24 pixels at the sides and 8 at the top + bottom to get 6000x4000. Others don't. Perfectly normal.
  5. I've opened an ORF from my OMD-EM10 mark1 and it seemed OK, but it was the first raw photo I opened and I don't know if it opened correctly as a raw file. Later when I tried an ARW from my Sony I went searching and saw the 32bit-HDR type selected (so it's using all the info available in the raw file) but I didn't test this with my OMD-EM10 Mark1. It seemed fine though. (Initial sharpness and colors made me think 'raw' and not 'preview jpg' but like I said, I didn't double-check). Will check it out later tonight / this weekend though. And I can supply samples if the file are needed of course.
  6. After adding my photoshop plugins folder and restarting, I see all my plugins in the list. (and I had the checkmark 'allow unknown plugins' checked, because _every_ plugin is listed as unknown) But they are all greyed out (including Nik Color Efex and Topaz Denoise 6 which are listed as fully working on the Mac version). Switching the workspace to 8bit they became all available, but I if they only work in 8bit I wouldn't really call it 'compatible' or working to be honest. And the first I actually tried using is CF Systems ColorPerfect, which immediately crashed upon loading (access violation message). Another question (which I can probably figure out be searching and reading but still), am I supposed to work this with raw files: Open the raw file, switch to the 'develop persona' if Affinity doesn't do it itself, make adjustments in the right and when I'm done press the 'develop' button in the top left? Also, the lens corrections I could find where all manual, are there any kind of automatic lens correction-profiles? In the case of raw files from micro 4/3 camera's which have 'embedded' distortion correction, do they apply?
×
×
  • 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.