DarkClown

I agree, an active selection will delay the histogram significantly!

OK ... this was my biggest fear ... May I say "a liittle prayer: Workflow - Workflow - Workflow .... Affinitys (denied) blind spot. Thanks firstdefence for your answer and suggestions. Seems a "slightly complicated, but do-able" way to overcome this disability. Can a moderator please shift this thread into the "Future features and suggestions" area?

I need help from the experts. I do have a pixel layer that need fine tuned straightening. To get there I choose the crop tool, zoom into the top left corner (on pixel level - high zoom level to be precise!) select "straighten" in the context toolbar ... click on the exact top left pixel and move the mouse to the most right side of my screen (button pressed). Regrettfully the screen now does not move (pan/scroll). The cursor keys don't move the window either ... Not even with Shift or CTRL. How do I get to the very right side of my pixel layer to select the second point for straightening? Or is straightening only possible when start and endpoint can be seen on the screen (and reached without scrolling)??? Maybe there is a magic key that enables such basic functionality as scrolling? Curious, Timo

I fully agree with i5963c ! More or less identical situation here .... I use CaptureOne as Raw developer and do the refinement with AP ... So I hardly ever get in touch with the development persona. But waiting for a histogram or thumbnail for 10 minutes is just inacceptable ... And you may be able to work without the thumbnails in the history but adjusting the levels-layer is simply impossible without the histogram. And i seriously wonder, why histograms in the pixel persone are supposed to be less important than in the develop persona. Wouldn't it even be easier to handle them the same way? Cheers, Timo

Hmm, we are talking Photo Persona here. Not CPU driven means GPU driven? What is the conclusion?

Yes ... but previously had no problems with Opel CL ...

For the second time AP crashed (app crashing to desktop or app not responding any more - had to shut it down this time with the task manager) when working with curves. In all cases without a crash report nor a recovery file (at least AP did not mention one and I couldn't find one). The only life-sign at the point of crash was a settings.dat file in the crash reports folder If I'm loosing my work anyhow - I can as well work with the beta version

I wonder if there is a way to explicitely re-genrate Thubnails and Histograms in AP. As you can see in the picture sometimes these don't get generated at all ... sometimes it takes between 10sec and a minute for them to show up. Edit: I have to correct myself ... in this case it only took 25minutes for the thumbs and histogram to appear. I did not expect they would show up at all ... but eventually they did .. Cheers, Timo

Sometimes it seems to be valid to remind Affinity that moving a million objects in Lightspeed (what is absolutely great!) is the problem of fewer people than beeing able to use the programs in an effective way. I'd like to bring up the handling of windows to program managers attention. Just to clarify the issues in a visual way I'd like to demonstrate how it could be done effectively in comparison to Affinity products - using PS 6 as an example. Just a simple "undocking" of a window - PS doesn't change the zoom factor, builds the new window neatly around the resulting window and places it within the working area: PS vs AP 1.mp4 Next example - Zooming in and out PS leaves the content in the center of the window - regardles wht the zoom factor is so you can instantly go on working on the document - unlike AP. The document is moved out of the center and after movin in it can't be found any more ... plenty of additional steps necessary to go on working. PS vs AP Center 3.mp4 3rd example - Resizing of windows as long as there's space (this is an feature in the PS preferences - would be nice and save a lot of additional keystrokes in Affinity): PS vs AP Windows Resize .mp4 As well you can see that the toolbar in PS is roughly 60% of the toolbar in AP ... would be nice to get a smaller toolbar as well and increase workspace... If one of the abouve mentioned features should be available in Affinity I could not find it - and I'd be happy if someone could point it out to me 🙂 Cheers, Timo

Same Problem here ... Regardless of the hardware accel. (doesn't matter if OpenCL is on or of). Dreadful with undocked pictures ... I can get me a coffee and Affinity is still slowly doing its resize work when I'm back ... Isn't it ironic ... beeing proud of the program speed with nearly a million of vecor object but not able to resize a single simple window ...

Hi Sean, sorry for the delay. I tried to record a crash - but unfortunately crashes seem to "know" they are beeing recorded and tend to avoid recording. The Corsair SW is kind of essential since it drives all my keyboard macros and settings 😞 I deinstalled the Sage Thumbs SW and it seems to reduce the amount of crashes. I'll keep you posted in case I figure out more details or I manage to get a crash recorded. Cheers, Timo

Of course Currently HW accel. is on ... I'll try to turn it of and check again. 290a38ed-9c34-40bd-aec7-6170df6e5832.dmp 26a57cd5-836b-4646-be46-fb4a0f4f50ee.dmp 0b11e829-11b2-43fc-88ec-76adb80044a8.dmp

Latest Beta (1.10.0.1115 ) constantly crashes (without error massage - simply vanishes) in various situations (e.g. dragging a point)

The file format (bitstream) was frozen on December 25, 2020, meaning that the format is now guaranteed to be decodable by future releases. https://en.wikipedia.org/wiki/JPEG_XL

Ah, I get it now. I wasn't aware that the pure RGB colours (and combination of them) indeed behave differently than all other colours (sorry for misspelling in the previous posts - had to much contact with US Americans lately ;-) )... Thank you for the good and detailed explanation - very much appreciated! I guess this behaviour really needs a bit of explanation since common filters e.g. curves obviously (sometimes!) do not work as expected ... Cheer, Timo

Hi Sean, thank you for your reply. Frankly spoken I don't understand your explanation. Maybe I did not describe my issues clearly enough or misleading. I 'll try to be a little more precise on 2 major topics: 1) If you set the stroke color of a vector brush to "transparent" the bitmap part is displayed in black with various bitmap based opacity shades. My expectation would be that the bitmap also completely turns "transparent" - instead of "shades of black" 2) In the video you can see that the setting for the vector brush at the beginning (color of filling and shape) is exactly the same as in the end but the curve adjustment behaves differently (At the beginning filling is transparent/shape is solid color - and adjusting the curve does not affect the bitmap color. At the end the fillings are identical but the curve adjustments DO affect the bitmap color). So the process of changing color in between must have changed something so the curve adjustment behaves differently later. This hardly can be an effect "by design". Same setting should result in the same behavior. If you still think these effect are caused by a color I used can you please explain that in a little more detail? Cheers, Timo

In the attached video you can see a behaviour I can't explain. I used a single vector-brush curve and put a curve adjustment filter over it. Chaging the curve obviously does not affect the bitmap part of the vector brush. Changed the stroke to transparent (the brush element does not get transparent but black - strange - maybe by design). Still the color does not change when adjusting the curve. Now changed the fill of the curve. the fill somehow (unknown blendmode) gets merged with the bitmap. And the curve filter is able to change the color of the fill. But interestingly the bitmap of the brush also changes! Now changing the stroke back from transparency to a solid color the curve can as well change the appearance of the vectorbrush bitmap. And even when turning of the fill (or back to transparent) the curve NOW is able to change the bitmap color - despite the setup is the same as in the beginning of the video .... (see video) Judged by my simple mind this behaviour does not make sense ... maybe I wasn't able to grasp the dimension of complexity behind the color bahaviour. I'd be thankful if someone could explain this to me ... vb color.mp4 ----- 2nd topic: In the help file it says: To modify vector brush strokes: Select the Vector Brush tool, unless already selected. CTRL-click on the brush stroke. But this action will only delete the curve.... Cheers, Timo

If there's anything you can't complain about it's the value for money! Outstanding!

I'm sure there a some topics that might cause discussions since some people don't care/don't use them or simply get along with what's there (maybe even due to lack of knowing better). On the other hand there are workflows that undoubtly need a serious rework (e.g. parameter resets, lacking ability to remember useful defaults, missing commands that would ease workflow etc.). Considering that I've been trying for 5 years to adapt to the "Affinity way" to handle things I feel able to judge what changes are an improvement (sure there are some things!) and where significant additional steps are required to get things done. Some procedures are just illogiocal and ridiculous ... until today ... just try to change parameters for export: edit first parameter "dimensions" and change the area - all entered data gets resetted ... completely ridiculous ... programming wise a tiny change. Still not done after 5 years ... of course you can define it as "by design" ... does it improve the workflow? I guess no 🙂

Hi Xiphien, first of all welcome to the forum. It's propably a bit unfortunate to start your first post with such a rant. Despite the fact one can extract understandable issues from your post the majority of readers will react defensive or agressive like Mia. You are picking on a long term critisized topic where the affinity guys tend to have "little sense" for: the workflow. I'm with AP now for roughly 5 years (getting away from any Adobe product) and been trying to support, critisize and bring in ideas. Many things did not make their way into the product - dome did. And by the time I got an undestanding what is helpful to report and what not. - When you struggle with any kind of behaviour you will always find someone here (even from the Affinity support) that will be helpful and explain things (even if the answer can easily be found in Google) - When you found a bug you will always get feedback (or people showing you what to do better to overcome the bug or to tell you that it's not a bug but a feature "by design") - In many cases expect them to seriously work on a bugfix for the next or upcoming version if the bug can be tracked (meaning: asap). - When you have suggestions for new features or how you would like to see things change put it in the "suggestion" section in the forum. Don't expect any Affinity answer - they don't comment on suggestion or future development (maybe people agreeing with you or pointing out a workaround) - Don't bother to mention workflow improvements since it propably is the only thing that will have no effect on development at all. From my experience even crucial topics in workflow haven been ignored for 5 years. There seems to be quite a strong force behind affinity to keep some things as initially invented and not willing to learn or change. Mayby internal changes would be to significant to change things without a major release. So my recommendation would be to kindly ask for support when you struggle with something. Put each question in a single topic post and put things in the right forum. As Alfred already mentioned trhis is the beta forum and your rant propably more belongs to the general forum And always keep in mind: it's not as bad as it seems and you'll get used to some new things - old habbits can be a struggle sometime Cheers, Timo

True, it doesn't always happen ... sometimes they are instantly there, mostly it's between 5-30 seconds, but occasionally it can last up to 10 minutes for the thumbnails to come up ...

Happened twice with the same document, generated from a focus stack. Not really reproducable ... I'll let you know, when it happens again.

Just FYI ... AP Beta crashed twice without any error message, when closing a vector curve - including complete data loss (no recovery file). Cheers, Timo

Is anyone else experiencing problems with thumbnails in the layer palette? Sometimes they are not build at all (see picture) - sometimes it takes a long time for them to appear. This can be really upsetting when you need the content (e.g. histogram in curves). Unlike in the example picture (it's a "merge visible" layer) the histogramm mostly comes up when you wait long enough. additional thumbnails from layers that are based on a layer where the thumbnail does not appear, have no own thumbnail either ... In this example I copied 2 additional marked areas for the eyes. The display itself shows the correct pixels. But as you can see I masked certain areas of the copied areas and also the mask do not show. Cheers, Timo

you can't (or better "should not") activate windows Ink in the tablet options ... it completely screws the tablet functionality!