toyotadesigner

A TIFF per se is not layered. Unless you have an option to select during export you can't save a TIFF with layers. But what is the problem to save a TIFF with layers with a different name?

Ahh, ok, thanks for the information. Didn't read all that stuff. As long as my workaround does the trick, I don't mind.

Well done Fred Flintstone ;) Long time ago when I was an active user of many forums I had promoted other software from 'small' companies as well. Sometimes it's worth the effort, sometimes not. I'd say that the Serif team deserves any possible promotion, so keep going. I've already promoted AP in 2 forums, but never got any response. Maybe the majority of human image editors is kind of arrogant or Adobe-centered? At least I always preferred exotic programs and supported small companies. Used PL, invested into the Ado... CS 5.5 for a client, just to uninstall that lousy stuff short time later. PL bugged me because of the endless vector features nobody really needed. They wanted to be Jack in all trades... So now - after a decade - it is time to push the reset button again and switch to AP. I'm getting very nice and clean results from this marvel. Thumbs and head up!

Hi Andy, Excellent statement and philosophy! As I said - as long as the result will improve, I will wait a tad longer. Today I used AP for more than 2 hours, loading different huge and medium size images and working with them. Over the time the loading accelerated, and I ended up with 30 seconds for a 650 MB file. Working with some TIFF files from a 24 MP digital camera was a breeze. Downscaling was fast, adding filters as well. I am not a coder, but I know that Mac OS X always had a problem to generate icons if the dimensions of an image exceeded a certain size. In finder the thumbnails from 24 MP files are generated relatively fast. The thumbnails for my huge files take ages... As I mentioned in another thread here, Graphic Converter doesn't even display thumbnails from my huge images. Nada. Or LightZone (ex LightCrafts, now free) doesn't display thumbnails from my huge files either. It appears to me that there might be a size barrier <sigh>: if an image is larger than x/y, Mac OS X needs a long breath to handle the files. Never mind, this problem seems to be only at my end, all other thousands or millions of users don't face this problem. So don't waste too much time for an extra button to dump history or investigating the problem at this very moment. Time will tell where the 'pointer is bent' ;)

From time to time I design 'mood cards' with images. Size: 6x4 inches or 5x7 inches (because the paper features this size and not - as usual - centimeter). 6x4 prints perfectly, but not 5x7: The printer tells me that the paper size is too small and I have to cancel the print job. However, when I print to Preview (Open in Preview), I can print 5x7 without any problems. So I think this is a bug in AD. What do you think?

Incredible! Thanks two tons for this trick - I've also been looking for this feature.

It would be great if AP would remember the last tool settings, i.e. the brush hardness or size, or the unsharp settings, the settings for downscaling (size and quality like Lanczos unseparable), etc. In most cases I reuse the same settings, but with each start I have to repeat the tedious procedure to adjust the settings again. Another point: If I use i.e. an effect 'curve', but decide to not use it, reset and close the dialog, it remains in the undo list. Why not - in the case of the reset - delete it from the undo history completely? BTW, how do the unsharp settings correspond to let's say PS settings? I can't find it in the help (any search doesn't show any result - the wheel just keeps turning in Mavericks).

Hi Andy, thanks for the fast reply. I don't have any other comparison than my 'old app'. Submitting a sample file is almost impossible with my limited bandwidth line. Downsampling: Yup, I just made a comparison - the Lanczos non-separable algorithm definitely is superior compared to others, so I will accept the longer processing time. The trick with the 'Undo' makes sense, so I will downsample the images, save/export them, close the original and open the down sampled image for further processing. My RAM slider is set to 6.144 (on my 6 GB RAM iMac). Undo limit to 1.024, View Quality Bilinear (Best Quality), Use precise clipping enabled. The internal HD has 400 GB free - should be sufficient for any image editor. I know that my iMac is not the fastest, but as long as I can process my images in a reasonable time I will keep it.

You might try http://www.xnview.com/en/xnviewmp/ for Mac OS X. It generates the thumbnails relatively quickly and uses an own database to store the data. Graphic Converter can not generate thumbnails from image which exceed a specific size. However, I don't know the exact size of the image which can't be processed.

I'm working with relatively large files: starting at ~ 120 MegaPixel, TIFF format, 16/48 bit color depth, scans from large format film, scanned @ 4.000 ppi, file size starting at ~ 650 MB. Files are stored on external FireWire 800 hard drives (WD Studio). Some file sizes even exceed 1.4 GB... Currently I'm still using PhotoLine, at 16/48 bit image editor. Opening an image with this editor takes around 10 seconds to display the image. Opening the same image (no other image editor running) takes almost a minute. That's a lot of time to read in the same image. What might cause this slow down? Are the image files pre-processed before AP can display them? Scaling down these images i.e. from 12.900 x 8.600 pixels to 1.500 x 1.000 pixels takes ages compared to my 'old app'. After scaling down i.e. to 6.000 x 4.000 pixels and then trying to apply a white balance or any other effect again takes ages. AP will not gain speed after scaling down an image... seems it keeps the original in RAM until I will close AP. OK, I have to admit that I'm running a 24" iMac 8.1 (late 2008) with 6 GB RAM, but with my 'old app' the workflow is considerably faster. I can not tell you anything about the behavior of PhotoShop, because I don't use it anymore (I did not like the cloud model). Simple tasks like i.e. retouching, adding a selection, etc. behave normal, that means without any speed lag. Will this be optimized in the final release? I guess that AP uses the same 'IOFireWireSerialBusProtocolTransport.kext' to access images from the external drives, so where is the bottleneck? What can I do to speed AP up (except investing into a new iMac)? Any suggestions? Any ideas or insights are highly welcome ;-)

Geez, the snapping of the crop tool to guides and image margins is fantastic! Thanks two tons for this feature! Now just shrink the code (file size) and I'll kick my other app (not PS, but PL).

Limit the forum language to English please! Reason: http://www.weltsprachen.net Rank #1: English Rank # 10: German ¡Antes de abrir un foro alemán, esperaría un foro Español!

You can use Preview to open the PDF, 'save as' and save it with the web settings in den options at the bottom. This will reduce the file size considerably. Or you can set up your own PDF parameters: Utilities -> ColorSync Utility. Duplicate one PDF setting, modify it, save it, close ColorSync, then repeat the procedure with the PDF file as mentioned above. Preview on the Mac is a very powerful tool ;)

As soon as snapping features for the crop tool will be implemented, I will use AP 100% for real work. But I guess this will be the final release. Until now I'm using it for scaling, some retouching and 'playing' (= getting used to it). Currently AP seems to be a bit slow, because loading an image file (from an external FireWire HD) needs 4 times as long as with my current image editor (no, not PS, just another 16 bit editor). I guess the final release will be optimized and load images faster. But I know that the wait is worth it.

I can confirm that the character window doesn't work as described, only the drop down box.

I've just noticed that the input fields (size, rotation, etc) don't accept scrolling up and down to change values with the mouse anymore. This was such a great feature - like in Cinema 4D. Though the numbers changed way too fast, I liked that approach a lot. Why don't you just implement this feature for all elements, i.e. line thickness, font size, transform, baseline, opacity incl. all variations, etc.? The sliders are always an extra step, and in many cases I miss the down arrow, so I have to click outside the field and then try again to hit the arrow. Make things simple :) OK, I know that many things sound simple, but are hard to code, but I think each mouse click is a waste of time :unsure:

geez, yes: add layer, hit q, paint with white and soft edge, hit q again, add modification i.e. exposure, done. Thanks two tons!

This one is driving me mad. The selection brush doesn't help me, so I want to add a layer, paint an area with a very soft paint brush and apply a filter to exactly that area with soft edges. No matter what I tried so far - I don't get it. Any ideas for a desperate AP user? BTW, I need the paint brush because I need a large, soft edge. The selection brush doesn't offer this kind of soft edge at all.

Just discovered this trick by asking aunt google - thanks a lot for the shortcut! Now it is a lot easier to retouch areas of different sizes.

Hi MEB, incredible! Not necessarily logical, but it works! Thanks a lot for these insider tricks! What a relief for my work...

I have some 2.400 fonts installed and active, can't repeat the bug. Only the first time when I open the drop down it takes a little while, but then I can either scroll with the mouse or with the arrows. iMac 8.1 (27", late 2008, with 6 GB RAM). Maybe a re-install will help? Did you check and verify your fonts lately with font book?

I'm still on Mavericks in case this is important. When working with several elements and i.e. selecting a few of them, then click outside of the elements, the purple snap indicator lines are still visible: It is kind of disturbing... Is it a bug in Mavericks or in my graphic card? iMac 8.1 Another question: Selecting several single lines with a black stroke doesn't allow me to apply a white stroke. Even if I group them, I can't apply a white stroke, though the menu gives me the option. So how can I assign a new color for fill or stroke to multiple selected elements? Any trick for this task which I have missed until today? Any help will be appreciated, because it is a very tedious task to select the single elements, modify the color or stroke, deselect and select the next element.

MEB: Incredible - Thank you very much! Now my Easter weekend will be a lot better :)

I prefer to set up a document in metric units (mm, cm). However, when selecting the metric system, the font sizes are also in mm - this is no-go! How can I manage to set up the document in metric units, but the font sizes in points (pt)? Any help will be appreciated.

I am using scanned large format images in the architecture biz. Sometimes I need to correct building anomalies. So when I open an image file and display a grid, it comes in light grey, which is rather useless in many cases because of white buildings or bright skies. Is there any chance that you implement a feature or an option to set a different color for the grid? In addition: The snapping is really bad, not to say it doesn't work at all. No snap to guide lines, no snap to grid, nada, even though I have enabled the snapping. I've set the radius to 0, 8, 15 and 22 pixel - no difference. When I use a mesh to straighten building corners, I need a snapping to the guide lines or at least to the grid (btw, same problem in Affinity Designer). I know the speed is kind of slow on my 8.1 iMac with a 3.06 Core Duo with 6 GB RAM, particularly with the very large images (13.092 x 8.728 pixels, ~650 MB per file), but somehow the speed appears a bit slow compared to my other 16 bit image editor (PhotoLine, not PhotoShop!) Also loading a file takes a long time - some 16 seconds compared to 4 seconds to my old app - from my external FireWire 800 HD (WD). Even if AP will be slower than my old app, I like to have a precise tool, and this includes a precise snapping. Any help will be appreciated!