carl123

If you placed the image on the document, they will be image layers and you will see a "Replace image" option in the context toolbar, once you select that layer Alternatively, make a note of the x/y coordinates of the original pixel layer in the Transform panel, add your new pixel image and change the x/y coordinates to those noted previously, then delete the original pixel layer Alternatively, give us a full screen screenshot (or document) showing the Layers panel with one of the pixel layers you want to replace selected

The images posted are very small, without the Designer document it's going to be difficult seeing what is happening Can you upload it to the forum?

There is no scripting and macros can't do it either but you can create an export preset(s) in the Export Persona which may do most of what you want

Pretty sure that's not possible at the moment

Approximately how many CR2 files are you batch processing? Does it work in small batches or when trying a single CR2 file? In Edit > Preferences > Performance how much RAM is allocated to APhoto? Also check your C drive is not running out of space during the batch process

If by "bulk" you mean "batch" you can try switching off "Parallel Processing" in the New Batch Job screen In addition, in Edit > Preferences > Performance try switching off (untick) Hardware Acceleration (if enabled)

Recovered files are attached and they look OK to me but it's impossible to know for sure In file "_fenix-uniform-recovered.afdesign" the group near the bottom of the layers stack looks a bit dodgy when you try to move it. I have disabled (hidden) it in the recovered file as it does not appear to be part of any of the Artboards. You may want to consider deleting it if it is not needed (If you had no backups for these files NOW is the time to start doing regular backups on all files you work on) Can you tell us where these files where stored, such as a local storage device or non-local storage device? And, if local is that drive/folder synced to a cloud service like Dropbox or Google Drive? Note: Most corrupt files are not recoverable, you were lucky, do not rely on this forum to be able to recover all corrupt files in the future, do backups! _fatima-iv-recovered.afdesign _fenix-uniform-recovered.afdesign

Not entirely sure what you are doing but if you are using an Artboard, you can add a second Artboard and then rotate the view 180 degrees Then File > Place your reference Designer document onto the second artboard and it will appear the right way up Now there is no need to switch document tabs as both your working document and the reference document are on the same screen

@Danold I'm pretty sure there is a way to exclude Invisible layers but I've only used it on relatively simple designs. Do you have a sample map document you can upload to the forum, so I can see the document structure/layout you work with to see if it will work for you?

After you place the rectangle, select the small colour well just to the right of the colour picker in the colour panel. (Shown as blue in your first screenshot in this thread) This will then set the fill of the rectangle to that blue colour

Put a Rectangle shape on top of the whole image then set it to your picker colour Now run through the blend modes in the Layers panel for the rectangle and see if any give the results you want (or come close)

There can be a few reasons but first check that Protect Alpha in the context toolbar for the brush is not on If not that, please upload a full screen screenshot showing the layers panel, colour panel and the brush selected

Not sure why you are having a problem using the Selection Brush Tool? It seems to do a very good job on the first pass without any fine-tuning

@JamesP21 If you are using an old version of the software and can't upgrade for any reason Let Dan know what version you are using as maybe he has access to that version and can recover the document again using a version you can access

When you copied the original file to a new file the original message.... "This file is already open in another application" ...would not be relevant to the new file Hence the 2nd (different) error message