onamac

Does it take care of the trapping?

I have indesign files, but also old Quark files. Is there going to be that capability in the future for Quark (even older versions)? Thanks.

I too can't get them to work. First, their status shows up (in preferences) as Unknown. But when trying to use them, I always get the message: Cannot Proceed. IPC Memory in use or Image size is too big for the system. I no longer have my Photoshop CS3 installed, but I have Photoshop Elements 15 and they do work on the same image in there.

There are a few things that do not behave as what I've become accustomed to (from being a long-time Photoshop user) and had to launch PS just to get it done quickly. I really have big hopes for Photo though.

Well, I don't need page layout in AP since that will be what Publisher is for. But I still want a text tool in AD and AP. Many times I do a logo and need a text tool for that, so I wouldn't want it removed completely!

I agree with these comments. I too feel that as much as iOS apps have a great market, it is still difficult to manage photos in a professional capacity (you first have to import the photo into the iPad for starters, which is not the same as a connected drive). iOS is great for people uploading camera shots to Pinterest or Facebook, but I can't imagine sending a client job to a print house from my iPad, let alone trusting it for color accuracy or even zipping the file. So I still see the need to offload it to desktop to complete it. That said though, it's not a criticism of Serif or their reasonings. I respect that, and I can imagine so much to do that they would want to target both but have to choose priority. iOS is a big market. I feel Publisher is the app that will let us truly move from Adobe as long as we can rely on its output (and that it covers the needs of a professional designer...trapping, color, etc). I think what Serif has accomplished is amazing at the very least, and I applaud their successful efforts. I know I am anxious for Publisher, and I think I probably share that with everyone else, hence this topic.

I'd like to bump this post to clarify what is the best way to handle resizing, per my previous post questions. Thank you!

Oh, and thank you Ben in advance. Am looking forward to an answer on this as I want to know the best way to resize in AP for best results.

Thank you. 1) When you say "best advice is to use standard DPI, you mean 72? and if so, then why would the 2x and 3x be finer res when the original was only 72? I'm trying to understand how AP is handling this scenario. 2) Let's say you want to create a new image and your target is a 600x200 standard image, and a 1200x400 enlargement of that image. When you launch AP, what do you enter as the settings to begin the image (and at what size)? 3) If you already have an image done at 600x200, and then want to engage the 2x retina, what do you do in AP to get the best quality? 4) RE: your comment "the document DPI will be used to determine..." Does that mean that the images are "fluid" and not committed to pixel size until final export, meaning the pixels won't suffer the enlarge (pixels stretched) /reduce (pixels discarded) damage?

+1. I'd say there are two schools of thought on the library/catalog subject. Some people like having their assets imported and stored in the app. Some people would prefer the app simply read your folder structure, with no import, like Bridge (or Lyn) does, so storage is not proprietary. I have become a person who prefers to take advantage of the OS's Finder and folder structure than use a proprietary storage. Here's why: over the years I have had many, many apps that held my content in its own proprietary format. That's fine, but only if the content is still mirrored on your hard drive. Unfortunately some didn't maintain the assets outside of the app itself. Some of these apps have since gone out of business / apps no longer work with OS. Some were difficult to sync both ways with what was already imported in them versus what was in your actual folders, so you may have new stuff in the app but not in your folders, or forget to sync, etc. Some import-type apps are just convoluted and you have to be very careful NOT to accidentally delete your original photo/asset because it will also delete it from your hard drive. Plus, some were only valid back then because at the time, they provided a feature that the OS didn't have, which is likely redundant now. So to me, they were just short-term solutions, and were risky and problematic in the long run. I used to use a photo asset app which was great for display, but unfortunately it stored the data plus has now become extinct. I lost all that data and had to painfully re-assemble what I could salvage, and some of it is just gone. But what I did salvage is now in folders. I'm finding these days that I can replace those apps via Apple's OS, which includes doing my organization in Finder using folder structure (which I did before anyway), and not via an app...because Finder's way will always work and be compatible in future OS upgrades. So an asets app based on that principle is a good thing by working in conjunction with Finder, not trying to replace it. For a little example, I used to use a proprietary app to organize my document types, which were then dependent upon that app. Now, I am taking advantage of Tags, so I tag the documents accordingly, and put the tag labels in my sidebar. I also had an app that was good for organizing my apps, for those little apps I'd forget I had that did such and such. I've now tagged them too. Now if I want to look at x, y or z, or a category, or whatever, I just press the tag in the sidebar and up comes all the stuff that used to depend on an app to do. It's really a breeze and it's future-proof. And by tagging my apps by category, it makes a quick launcher too. Not to veer from the DAM subject but this is just an example of using the power of the OS in conjunction with an app, which is what I'd prefer the new DAM to be.

Thanks MEB. I figured this was just a well-edited promo video. In your promo videos (for both AP and AD) there are segments of intriguing things that I would love to see as their own videos, this being one of them, because they rush by so quickly in the promo. There really isn't another tutorial available which covers this exact thing.

When you mentioned Image layer versus pixel layer: Is an Image layer like a smart object layer? In other words, other than raster, what is the significance / benefit of an image layer? For resizing? Thanks.

I didn't see anything in the preferences to choose which disk to use, or if you can actually assign a different hard drive for that duty? Thanks.

OK, now I'm getting somewhere, thank you very much! I now see using Source gets the mesh around the object instead of the whole document, hence my thinking it was the pen tool. That solves that question. Now the only thing is in the video it looks as though they are affecting the whole glass at the same time rather than point by point to warp the shape because it doesn't look like any points are selected when they are doing the warp.

Thank you. But how do you draw the mesh around the object (i.e. drinking glass) to begin with? When I use the mesh warp tool, it draws a white outline around the area I drag to, but when I release the mouse, there is no selection. Do you draw something first with another tool? In the video, it looks as though the outline was started with the pen tool and then built upon. When I use the pen tool to draw the selection which looks like what is in the video, it vanishes as soon as I switch to the Warp mesh tool.The tool looks like the node tool (white arrowhead), but I can't come even close to whatever it is they are doing. When I use the warp mesh tool, the history says "warp mesh" but there is nothing happening on my document. There must be something I am missing here.