Peter Pokorny Posted August 15, 2019 Share Posted August 15, 2019 My first Test of the new RC of AP was very pleasing. Workflow is running very smoothly even within Groups an with a huge amount of layers. Very nice job! Well done! Link to comment Share on other sites More sharing options...
Peter Pokorny Posted August 15, 2019 Author Share Posted August 15, 2019 AP crashed again during creating tiff 16 bit Export with LZW compression Trying to export a huge file with a lot of layers to tiff with layers also still crashes with zip compression. Please correct this before releasing it. Link to comment Share on other sites More sharing options...
Staff Gabe Posted August 16, 2019 Staff Share Posted August 16, 2019 Hi @Peter Pokorny, Can you provide the document and/or steps to reproduce this? Thanks, Gabe. Link to comment Share on other sites More sharing options...
Peter Pokorny Posted August 16, 2019 Author Share Posted August 16, 2019 Hi Gabriel! I did the complete beauty retouching like listed in the AP Workbook. 1. komplete RAW Development 2. Frequency Separation with Layer Grouping and rep. brush 3. new pixel-layer skin tone with color brush and gausch blur 4. new pixel layer for lights recovering with color brush 5. dodge/burn layer with 50% gray filling and dodge/burn with dodge/burn brushes 6. duplicated details layer set to 25% 7. new pixel layer filled with 50% gray and with 25% noise within new group 8. new pixel layer for new lipp color and Gaus blur 9. new pixel layer for eye makeup and also with gaus blur 10. new pixel layer for eye brows with gaus blur 11. new pixel layer for eye optimization with gaus blur than taking visible together to one combine layer for sharpening (masking) one new layer for lights correction, midtown correction and shadows correction when finished resize picture to 40x60 cm and than documents --> export --> tiff 16 Bit (16 bit RGB) with LZW or ZIP compression. The issue should already be mapped with the dev team with an sample picture with layers in an other post to this topic. I have reported this already for the previous Release candidate but it didn't got done yet it seems. Here the link to the other post: where you replied to have it logged to the Devteam Gabriel. Sorrily it seems that they haven't corrected this issue yet. Link to comment Share on other sites More sharing options...
Staff Gabe Posted August 16, 2019 Staff Share Posted August 16, 2019 Thank you. In the future can you please try not to create duplicate threads of the same issue? It is sufficient to mention it also affects other versions/apps/etc in the original post, rather than creating a separate, identical issue with no information or link to the original one. stokerg 1 Link to comment Share on other sites More sharing options...
Peter Pokorny Posted August 16, 2019 Author Share Posted August 16, 2019 ok. will remember on it. I hope this issue will get solved before final release. Link to comment Share on other sites More sharing options...
Recommended Posts