Lee_T

Hi alicia828282, Would you please follow the instructions on the post below to get a crash report for us to examine? Lee

Hi Ezbaze, Thanks for the detailed information. I've added a bug report for this. Lee

The software freezing was likely a response to a fill action made with all the now blue layers selected, as I would imagine completing this action would take -quite- a bit of time, it would have felt like a freeze. Unfortunately without a backup I would say the best course of action is now to remove the blue layers, as combined pixel area of the document even trimmed is still 4+GP so you will likely find your document will still lag quite badly with GPU acceleration enabled. The overall size of the document isn't so much of an issue as long as each layer isn't unnecessarily large. Lee

Was there anything on the layers before they were blue? It's unfortunately impossible to say how they were created at the size they were, but as @Old Bruce suggests, use rasterise and trim to remove everything outside of the canvas. As for the document dimensions itself, what is the destination for your artwork, i.e. print size, device etc as the filename and layers suggests this is for an animation rig. so depending on the zooms you are expecting the canvas size may be necessary of course, but for a visual indicator the yellow box is the resolution of a 4k display. Lee

apologies, I meant the stroke studio panel.

Hi Blastkist, Your document is HUGE, and with GPU acceleration enabled, you are likely massively exceeding your video card's RAM. Unclipped, the canvas is 25605 x 39065 or approx. 1GP. A single layer of this would not be an issue but you have many, many layers using most of the canvas size, even though they do not fit fully on the canvas. Each one of these layers has to redraw when you make an operation. I would examine if this is realistically needed. you can get better performance by disabling GPU acceleration (and relying less on GPU RAM) but in all honesty I think you have overshot the size requirements. Lee

@loukash @retrograde I've been unable to recreate this issue. Which keyboards are you using? Apple keyboards, having a low profile leaves their switches somewhat open to interference from the smallest of debris. If you are using the original keyboards, it may be worth a quick blast with an air duster underneath your keys to prevent anything from interrupting your keypress. Lee

I've tested with a Huion Inspitoy Q11K, Right click works fine on this particular tablet. My driver options do not have the "use mouse events etc...." option, have you tried disabling this? Lee

Hi Blastkist, welcome to the forum, Sorry to hear this has happened with your file, the previous advice on backing up is of course a wise course of action, possibly alongside versioning if you want to be doubly sure you can't lose everything. If you would like to send us the file using the link below, we can take a look at it and see if we can recover anything, though I cannot guarantee success or a timeline for this. https://www.dropbox.com/request/iGtqYzevfepDNr9gDi8v Lee

Hi Cartoonjosh, 8px or 8pt? The brush studio shows pt value only, this means it may show differently to your context tool bar. Lee

Hi moretap, Not within Designer as far as i'm aware, but using a CSS to SVG converter seemed to work fine. https://www.kmhcreative.com/downloads/CSS2SVG.htm (note, the SVG it generates may import very small and will need to be expanded) Lee

Hi cgidesign, Could you show your settings for both your Kamvas and windows ink? This isn't a tablet I have access to unfortunately. Lee

I would recommend a batch process with no macro to a format such as a 16bit TIFF to maintain dynamic range. Then run the TIFF's through the batch processor with your macro. Lee.

Hi Maxi, There are certainly limits to what's possible with data merge, this sounds like it's outside of those limits. Lee

Hi rddpozi8, Batch processing uses a simpler version of the RAW develop engine, so you may see some differences when using this method additional processing. Lee

Hi urbancoop, Could you please use the following link to send yours: https://www.dropbox.com/request/tIZZkGs9TrRyL9iK4XWF Lee

Hi Piet, Could you please upload the document here as a package for us to take a look at: https://www.dropbox.com/request/iOMAKeNlWYQN5Kn8fxam Lee

Hi rcheetah, it appears that the PDF is not embedded. Lee

Thanks, i've forwarded those on. Lee

My example above is an exaggerated example, you don't need to go this far. As explained, the RAW file contains this information in the way it presents, and will need to be corrected post develop due to it's extreme nature. As we have non destructive RAW editing, and you can bring out your image with the full dynamic range, this should not be an issue. It's not a workaround, it's working around the deficiencies in an image. Lee

Hi ps. There is not the possibility to change this at the moment. Lee

Though a little tricky to remove using RAW adjustments alone, the blue light is possible to remove once developed. Strong blue light (especially LED) will always cause a camera issues, those issues are likely automatically countered in Sony's own software during initial processing as they know exactly how their camera will behave with it. I tested these images in lightroom and encountered the exact issue, though with lightroom only doing RAW processing, they've added some tools like their HSL/Colour adjustments which can be used to counter the blue LED affect, whereas in our software you have the benefit of processing the image much further once developed. As you can see from this quick edit with no local adjustments, the blue light is no longer an issue. Lee

Hi ASee, We can take a look at the file but unfortunately I cannot guarantee recovery or a timeline. https://www.dropbox.com/request/OUiXd5RKIQZJE150kTHR Lee

In Settings > Assistant > Develop Assistant > Change Tone curve to Take no action You should find that this gives you the results you were expecting Lee.

Hi craigenputtock, Does this persist after a full restart? Lee