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

Madpeaz

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by Madpeaz

  1. #RonP - If you hit ESC while it is loading, it then allows you to press the Cancel Button, which then takes you back into the Photo Persona. But the Tone Map processing is still going on in the background. I believe you should be able to abort a process, if it's not what you intended to do, and not have to wait for something to finish. They could disable the ESC key to prevent the Cancel button being pushed, but that's not good for workflow with an unnecessary pause. Window 10Pro, i7, Nvidia K5000 Quadro, 32GB Ram.
  2. Okay this problem I found, was more by mistake than intent. It’s to do with the Tone Mapping process not stopping, despite cancelling and exiting the Tone Map Persona. For example, develop a RAW file of about 23MB and rasterise, then go into the Tone Map persona. The image will start loading and the progress bar is displayed. But, If I wish to immediately cancel that process, you are unable to click Cancel, not until that process is complete. So, depending on image complexity, it can take a while. The only way to exit Tone Map Persona quickly, is to hit ESC, then click Cancel. So, we are now back in the Photo Persona, and you want to paint a red squiggly line across your image. But when you select your paint brush and start painting your squiggly line, nothing happens? The mouse is moving about, but no paint is visible? Then suddenly, you have a load of red splodge over your image! It seems to me, the memory is still being hogged by that previous Tone Map Process, meaning, until that previous process is complete, everything else does not appear to work? Well, it does, but invisibly and usually ends up in a mess. You can see from the Info panel, memory whirring way, until that stops whirring, you can’t really do anything. As I mentioned, it was by mistake I found this issue. It was when I loaded a 54MB PNG file and clicked Tone Mapping by mistake – Then couldn’t work out why, when using the crop tool, it would not rotate? I’m sure if these unwanted background processes were zapped when not used, everything would function a much quicker for a great user experience. I noticed this issue was also present in V1.10. Hope this is of some use. ToneMapProcess - NotStopping.mp4
  3. The White Balance problem, appears to only happen on non-RAW files bought into the Develop Persona, I.E. jpg, png. tif etc. But if you use the White Balance Picker while in the Develop Persona, it will work on non-RAW files - but not the slider.
  4. @CallumThanks for the update, yes the effect is by design in V1 - Though I cannot disable Metal in V1 to check, as I don't have hardware acceleration.
  5. I don't know if it was a bug in Affinity 1.10 that was fixed in 2.0? Or a bug in Affinity 2.0? But whatever the case, BoxBlur-Divide-Test.afphoto file created in AFP 1.10 do not display the same, when opened in AFP 2.0. The problem arises with the Box Blur (or any blur) using a Divide blend, on an inverted image layer with a blend mode, in my case of Add. In AFP 1, this combination creates a drawn outline effect, with a slight canvas texture. In AFP 2, It's a white box? I use this technique as a base for creating postcards with a line drawn watercolour effect. Alas, in AFP 2 I cannot create the same effect, or can find a workaround as yet. The closest thing is using a procedural texture filter, but I lose the colour. For the time being, I will continue to use AFP 1.10 until a suitable solution can be found. But It looks like in AFP 1, the live blur filters have a procedural texture when layer blend mode is Divide. Any ideas? BoxBlur-Divide-Test.afphoto
  6. Chris B thanks for your help, and for getting it logged. It will be a good one to resolve 👍
  7. Thanks, Alas, I tried that too, done exactly the same as you did. Some of the images I work with are of fairly low resolution, around 800px width, and so I want to see them at 100% actual size. If the images were around 5000px width, that's fine fitting to screen when tabbing between them, you don't really notice the jump. But on smaller images, you do!
  8. Thank you for the suggestions, I have tried those suggested, alas none made any difference. But in my opinion and my experience, this is a bit of a bug. Maybe just a Windows thing, I don't know? My computer is not slow by any means with an i7 CPU & Quadro grapics card, tabbing between two images shouldn't be too taxing, even on a low spec machine. As mentioned, it needlessly zooms to fit screen and back down to 100%. If that glitched could be removed, that would be great.
  9. My issue is when tabbing between two images or more, of which are all at 100%, each image will in turn ZOOM to fill the screen/workspace before it goes back to 100%. I find this quite annoying, especially if I'm trying to compare something like a 'Before & After'. I have set in Preferences, Limit initial Zoom to 100%, but that does really help my case, in fact it does exactly the same as tabbing between two images. The Zoom issues I believe have been raised in the past, in regard to cropping, but it would be a whole lot nicer experience if the epileptic flicker would disappear! Or at least give an option somewhere to turn it off. The issue was in 1.10, though it was a shade slower and didn't look like a really horrible screen glitch. I personally, do see this as 'bug', as I cannot find a useful purpose for an image to Zoom up to nearly 200% and back down 100% in 1/500 sec. In the attached example video, there is one point it didn't Zoom up! - Now that is a friendly bug we need a few more of them. Thanks for all the effort that goes into this software, I now use it 90%. Tech: Windows 10 - 24GB - SSD - Nvidia Quadro K5000M AF-Photo-ScreenFlicker.mp4
  10. Yes, wish this could be addressed at some point, it may seem like a small thing but as mentioned, it really kills workflow having to keep amending the brush size. Photoshop has global default option that keeps the chosen brush size the same, regardless of which brush is used. I know in Affinity Designer, you can keep the brush size the same, but even that is not very efficient, having to press 'Alt' everytime before you change the brush. Of course, if I have missed the option in Affinity Photo that fixes this problem, please let me know.
  11. I am having the same problem with New Pattern layer crashing Affinity. It doesn't take much to make it crash even with the default 32x32 grid. Just create new document, a small 800x600 document will do, go layer>New Pattern Layer - Select the brush tool, reduce brush size and place a dot in the centre of pattern. drop the brush tool, select the Move tool and zoom in & out a few times using the (ctrl) & mouse wheel, then click somewhere on the screen - Kerpoof! It appears to only crash when using (ctrl) & mouse wheel and while the Move tool is selected. Selecting the magnifier tool, the (ctrl) & mouse wheel combination seems to be fine. I've attached the crash report. System: Windows 10 Pro 21H1 i7 24GB Ram Nvidia Quadro K5000M d746897b-67c2-42da-8fd9-643f3888a1d0.dmp
  12. You can, while in 'Unconstrained' mode adjust the crop tool to a particular ratio you want - Then click the 'Custom Ratio' mode - This will un-grey 'Create Preset' in the hamburger menu, thus allowing you to save it as a preset.
  13. Thanks I'm glad the work around helped, hopefully the crash issue will be resolved soon.
  14. Yes I have the same problem, though I can get around it. In my case it appears to be an issue with a modified linked resource? And so until it's updated in the resource manager and saved, the file will crash Publisher. To open my file that keeps crashing Publisher, I just create a new blank document first. By doing this it appears to bypass crash issue so to allow the problematic file to open, to which pops open a dialogue box "Linked Resource Changed" Within the Resource Manager I click the 'Update' which sets the "modified" file to "OK" - I then save the file and all appears to be back to normal, though obviously there is an issue.
  15. I too have an issue with 'Live Filters'. Some of filters(Voronoi, blurs etc) are being completely ingnored as mentioned above, when printing/exporting pdf on all three - AFPhoto, AFPublisher & AFDesigner.
×
×
  • 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.