Jump to content

Subclavius

Members
  • Content Count

    49
  • Joined

  • Last visited

Everything posted by Subclavius

  1. Hello PaulEC, Thank you, that explains why I can't find it on the menu. The shortcut ought still, in my view, to be visible on the User>Preferences>Keyboard Shortcuts so it can be changed.
  2. Digging a little further I found the following topic: https://forum.affinity.serif.com/index.php?/topic/60033-re-apply-a-filter/ from June 2018 which shows a picture of the Repeat last filter option. This appears to have been removed or left out of later versions
  3. Affinity Photo 1.7.3.481/Windows 10 I was assigning the keyboard shortcut <ctrl>+<alt>+<f> (to New fill Layer) only to discover that it is duplicated. It apparently clashes with <Repeat Last Filter> but I cannot find that command in the User>Preferences>Keyboard Shortcuts menu to remove. The newly assinged shortcut works successfully as it overrides the <Repeat Last Filter> but it would be nice to be able to remove the pre-defined assingment (or assign that to another key combination). Nigel
  4. (1) the combination Ctrl+Shift+] and Ctrl+Shift+[ is assigned by default to Arrange>Move to Front/Back. I was unaware of this and assigned the combination to Document>Rotate 90 Clockwise/Anticlockwise. I have been using the combination quite happily until I discovered the the clash. The issue is that AP does not warn that this is a duplicate combination (2) I have been unable to assign any keyboard shortcuts using the arrow keys (up/down/left/right). The default keyboard shortcuts such as Ctrl+Alt+Shift+Left (Flip Horizontal) work ok in practice Any comments anyone?
  5. I always run AP full screen so can't really answer your question but I would suspect that there's not much in it. However, I have noticed that the first time that AP loads a LUT it takes significantly longer than subsequent times. I guess that AP has to load up additional libraries from disk into memory
  6. It does work though, albeit slowly! I imagine that the processing time is heavily dependent on the computing power available to you. Here are the statistics from my machine (windows 10 64 bit, AMD FX6350 (6 core), 16 GB RAM and AMD Radeon R7 200 series graphics card). I created a LUT from AP at maximum export detail level of 126x126x126 which gives a file of 51.5MB. It takes 12 seconds to load and process the file. AP will also use the graphics processor and any (and sometimes all!) available memory. If your machine is taking minutes to load it, then probably you're running into memory/processor (or just possibly graphics processor) limits. If your machine is 32 bits then you should consider upgrading. Good luck!
  7. Hello mircokopf, I've tested LUTs both created within APhoto and externally, including one I created from scratch. As far as I can tell they work just fine and the filename doesn't seem to matter. You say that no files are showing up in the file explorer dialogue. What file extension are you using? According to the help, the following file types are allowed: I always use .cube. Can you provide any more details?
  8. Dear Affinity Team, Thank you for the latest update, particularly the bug fix with masks in groups. Had previously to revert to 1.7.1 to continue. I agree with mapline in that all fixes, major or minor, are appreciated, please keep them coming! Nigel
  9. Hello carl123, Thank you. That has fixed the problem. I'm glad someone understands this stuff! I'd like to leave this post open for the moment: perhaps a knowledgeable person from Serif would like to comment, on whether this is likely to be addressed or added to the stack of feature requests, or simply closed. Nigel
  10. I want a macro to add 2 pixel layers at the top of a AF layer stack, fiddle with them and then group them together. When attempting to record the macro I can get everything done except that last bit (grouping) because APhoto does not permit selection of more than one layer at a time when recording a macro. I have seen work around methods but they don't work for me because the layer stack contains an arbitrary number of layers and I only want to group the top 2. Am raising this as a bug rather than a feature request as I find it annoying. At the moment I have to use the work around of an almost complete macro and do the grouping (and naming) by hand. Any help would be welcome. Nigel
  11. Hello martinch and Old Bruce, If it's of interest, I posted this method in the tutorials section of the forum: It was tested on a 1.7.0 beta but it appears to work in current production 1.7.2. Any comments would be appreciated. Nigel
  12. I very much second the idea of an import facility for legacy PagePlus files. I can understand the pressure to get AP out there but I can't help feeling that Serif has let down its legacy users of PagePlus here in not supplying it. I have seen it suggested that export -> import can be achieved by means of a pdf but I find that wholly inadequate. The elements of the page (e.g. a table) are lost as functional elements and only the 'picture' content appears. Short of a turnaround from Serif it means starting again from scratch. Nigel
  13. Hello Walt, Thank you but I feel this misses the point. Yes, groups restrict the operation of layers to within that group so that only that group is affected. My point is that the b+w conversion layer fails to operate at all because it cannot 'see' the underlying background pixel layer without the presence of an unnecessary local pixel layer within the group. Nigel
  14. AP 1.7.0.367/Windows 10 64 bit I think this is a bug but am not 100% sure - feel free to close if it's by design. It seems that a black and white conversion within in a group only has a local effect on pixel layers within that group. Have included 3 pics: a b+w conversion outside the group (works ok), b+w conversion within the group (no effect), and b+w combined with a local pixel layer (non-transparent) within the group (works ok). This may look like an odd thing to do but it arose as I was trying out 2 different b+w conversion options on the same pic. It seemed to make sense to use 2 groups rather make multiple copies of the original image. Any comments? By the way, thank you for all your hard work on releasing version 1.7. Nigel
  15. I have posted an article on how to set up curves manually in the Tutorials forum: It uses a LUT and requires some manual editing to set up but it isn't rocket science. Nigel
  16. Hello All, I'm posting this in response to the following thread: I was also searching for a method of inputting (x,y) number pairs into Affinity Photo to make a compensating curve for digitial negatives for alternative processes. It looks to be possible by using a 1D LUT (Look Up Table). The enormous advantage of a LUT is that the file (typically with .cube extension) is manually readable and editable. I've put some details and screenshots below as 'proof of concept' (it means I haven't tested it in practice!). Pic 1 shows the original image (test 2 bw [original]) - it is a greyscale image Pic 2 shows a typical alternative process curve made up with a curves adjustment but not yet applied (test 2 bw [typical alt process curve]) Pic 3 shows the above curve applied to the image (test 2 bw [alt process curve applied]) Pic 4 shows a 1D LUT created from the curve in pic 2 applied to the image (test 2 bw [alt process curve via LUT]). To generate the LUT data I printed the adjustment curve on paper and measured it! Notes on method: Note that this method ONLY works with the current beta version (1.7.0.293). I have tried it in the current production version but the LUT implementation is flawed and it does not work! There are minor differences in the histogram between pics 3 and 4, probably due to the sampled nature of the LUT with its linear segments (and also measurement accuracy!). The method utilises a 1D LUT - pretty much what they were designed for (although the idea was for video implementation). However 3D LUTs also exist and if you export an LUT from AP then it will generate one of these. Notes on LUTs: An LUT relies on having equally spaced points along the x-axis. This is a MUST. If you have made non-equally spaced density samples, it will not work or you will have to interpolate. An LUT can have arbitrarily many data points. In this example there are 78 so that the important information in the rapidly changing areas of the curve is captured although it means that the curve is over-specified in the linear segment. The format is self explanatory (see example). Comment lines begin with a # character. Here is the link to the Adobe LUT specification for those who want to delve further. There is no specification for the x-axis data points. They are assumed to be equally spaced. The numbers supplied are for the y-axis data points and there are 3 of them (in the given range 0.0 to 1.0) one each for RGB. It is important that the RGB numbers are identical otherwise you will get a coloured output. I have used 5 decimal places here but it's arbitrary. I've attached below the sample LUT that I made up - the numbers were created in an Excel spreadsheet. Feel free to adapt it. I would be interested in any comments. Nigel LUT test 2 bw.cube
  17. Just one item for me: In the curves adjustment box add the ability to specify the points being added (x%, y%) to the curve just like blend options. This would be immensely helpful for creating digital negatives for alternative processe (e.g. platinum printing) Nigel
  18. Hi BillCrum, You should check out the latest beta release (currently 1.7.0.258) to see if you can reproduce your problem - I know that you've said it's a different problem but the beta release contains the latest updates. I can now load large files of 16bits greyscale correctly and the loading is a lot faster now. Nigel
  19. Hello Gabe, Thank you for the reply. I had already looked at the video tutorial but didn't find it really helpful in the context of this query. Your reply did however enable me to work out how to get a black and white image though. It seems that the 'meaning' of the axes changes from RGB to LAB. In RGB mode the vertical axis is dark to light whereas in LAB mode the vertical axis is blue to yellow or green to magenta. Thus in LAB mode the neutral point of the axis is not at the bottom (as in RGB mode) but half way up. If both the AOpponent and BOpponent curves are set to horizontal lines half way up (removing all colour information) the result is indeed a black and white image representing only Luminance. Clearly when both curves are set to horizontal lines at the bottom of the graph the resultant colour is thus blue+green -> cyan I would find it very helpful if the vertical axis could be coloured with a graded line from blue to yellow or green to magenta. Similarly on the RGB a graded line from dark to light would help. It's only a small wish in a great sea though! Thank you, Nigel
  20. Affinity Photo 1.6.5.123/Windows 10 64 bit This looks on the face of it like a bug but am not sure. A photo (pixel base layer) and a single curves adjustment in LAB mode working in 16 bit - if the AOpponent and BOpponent curves are set down to nothing i.e. desaturating the image, AF should according to me, produce a black and white image representing only the luminance. However I get a monotone image in some shade of blue. It doesn't matter whether the document format is RGB or LAB, I get the same result. Incidentally the behaviour is exactly the same in beta release 1.7.0.243. Is this a bug? Any advice about what is going on would be appreciated. Nigel
  21. I was thinking earlier of just the absolute basics but of course a fully featured SmartCurves would be fantastic. This is partially referenced in thread 76455: where the ability to save and load presets is requested. That would be so handy for alternative processes ...
  22. Hello, I would also like to see this feature implemented for precisely the reasons that mrenters described in the initial post. In the Blend Options panel of a layer it's possible to put in a large number of points and specify the input/output values for each one. It doesn't seem, on the face of it, to be be very difficult to implement this idea for the curves adjustment as well. Please, someone in the know at Serif, would you consider implementing this or putting on the roadmap? Nigel
×
×
  • 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.