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

Petr Lobaz

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, the info panel shows RGB color values regardless the bit depth, i.e., white is always 255/255/255 in both 8bit and 16bit images. Is it possible to swich between value formats, such as 8-bit value, 16-bit value, percent, etc.? Petr
  2. I agree that "extenting possibilities beyond Photoshop" has zero priority, generally. But sometimes, the extension is for free. For example, we agree that numbers in curves editor would be great. Allowing them to be non-integer is for free in the programmer's view, as the curve is calculated in floating point anyway. It is just a useless restriction of the input box that does not allow decimal point. Another example: you can define opacity for a layer, from 0 to 100 %. Then there is a simple formula that calculates final color. But, this formula does not require opacity to be from 0 to 100 -- the formula works for any number, e.g., 200 % or -50 %. There is no reason to restrict the user from inputting such numbers -- the only thing the programmer must do is to handle the opacity slider somehow.
  3. Yes, numbers in the curves dialog would be more than welcome. Anyway, curves could be extended way beyond what Photoshop offers, for example being able to zoom to a specific part of the curve, enter non-integer values, or choose numbers range (sometimes it is better to work with 0-255, or with 0-100, 0-65535, etc.) This is espcially useful whan handling LAB corrections or scientific images. And ability to select more than one point on the curve would be great, too! In Photoshop, I can adjust contrast of the specific tonal range using two points, e.g. (50, 25) and (100, 50). Then I can select these two points and move them upwards or downwards, which lightens or darkens that tonal range, but the cotrast is left untouched.
  4. Sort of. A lot of professionals I know (including me) are very unhappy with Adobe business model and keep using CS6 or older for good reasons. Serif seems to provide a very good alternative. 1-bit support is then more than welcome. For Affinity Photo, at least export of proper 1-bit format is more than welcome. There is one more use case for 1-bit images: preparation of embossing dies. These must be also strictly black-and-white, either vector or 1-bit image.
  5. Hi, it seems it is not possible to set non-integer dpi value in Affinity Photo for desktop (Windows 10). The value set in Document / Resize document is always rounded to the nearest integer value. This is unacceptbale in, for example, lenticular printing, where dpi must be set with precision 0.01 dpi or better. Also, resolution of some printing devices such as flatbed Oce Arizona is not integer (for example, 601.183 dpi), and rounding to integer mostly destroys the lenticular print. When I open an image with non-integer dpi, weird things happen. If the dpi was set in Photoshop, Affinity Photo seems to round it. If the dpi is set in GIMP, Affinity Photo reads it as a completely different value (580.574 dpi in GIMP is interpreted as 290 dpi in Affinity Photo). Or, maybe I do something wrong... Petr
×
×
  • 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.