Jump to content
You must now use your email address to sign in [click for more info] ×

GregoryOR

Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nevermind. I downloaded the mockup a 2nd time and the embedded file is there and works as expected. I can't find any way to delete this topic I've created.
  2. Newbie question here. I have used mockups with PS in the past, and am now trying to use one with APh, and have no idea how to go about it. In PS, there was an smart object layer, that, when you double click on it, opens a new window, and you can delete their non-perspective image, replacing it with your own, but in APh, the embedded image is just a pixel layer, and I have no idea how to replace their cover with my own. Here is a screenshot of the layers. The top Cover layer is the non-perspective image, I guess, but I delete it, nothing changes in the perspective image. I'm happy to look at a tutorial, but the instructions for the mockup are for PS, and I can't translate them to AP. Any help would be appreciated
  3. This image has gone through a lot of conversions - starting as a jpg photo, then converted to png "sketch effect" using an online tool, then optimized using ImageOptim, but the final png before placing in AFPub is sRGB IEC61966-2.1 as you show in the resource manager screenshot. The paper background image is a jpg, with the same color space and color profile as the sketch before placing into AFPub. I just created a new AFPub document with the same color profile as the images, and placed them in the document. The I exported as digital-high quality PDF and again as X-1a:2003 PDF. When I open both in AFPub and look at the resource manager, the transparent image has been exported differently between the two. In the digital HQ pdf, the image is faded, and is a TIFF with RGB color space and no ICC profile. In the X-1a pdf, the image is perfect, and is a JPG with CMKY color space, also no ICC profile. What tool are you using to compare the downsampled and non-downsampled? Curious that it is showing RGB color profiles for the exported embedded images, but the resource manager in AFPub that I am using shows something very different. But it does suggest that the export process is where the sRGB2014 profile is introduced, rather than the placement of the image in the document. I find this fascinating, and am learning so much that I didn't know before!
  4. Wow, thanks for the thorough explanation on color space! I have so much to learn about this stuff! My PDF is meant to be viewed digitally, so the CMKY color mode choice was unintentional. I thought I used a web template to create this booklet, but maybe I accidentally chose a print template instead. I tried changing the export settings to RGB, with no change to the output, so then chose PDF/X-1a like you suggested, and it looks great! I usually ignore preflight, because it flags a bunch of intentional stuff as warnings, and for this document, it was spelling mistake warnings for a bunch of latin words, and bleed hazards, which aren't an issue with my document, and non-proportional scaling, which is on purpose. Thanks again, for not only a solution, but some learning as well!
  5. Thanks @Callum Here's a trimmed down version of the afpub file, screenshot of settings, and the comparative exports. I have never touched the PDF export settings from installation. It looks like only the embedded images are faded. Text and curves all look the same between PDF and JPG exports. SketchTest.afpub SketchTest.pdf
  6. Would you happen to know if there is a setting somewhere where I can confirm which channels are being exported and possibly change it? Thanks!
  7. I am exporting pages for a virtual book in both JPG and PDF formats. The JPG's come out perfect. The PDF images are so light they are unusable. Please see the attached screenshot, with the PDF export on the left and the JPG export on the right. Can anyone explain how I can get the PDF exported images to look right?
  8. So, I see that when I double click on a brush, it does show the name in the stroke properties panel. But that field doesn't exist when I display the stroke properties panel while an object is selected. WTF???
  9. I created a design earlier that used a brush for the stroke, and I want to use the same brush for some new work. Is there any way to know which brush I used on my previously-created shapes? When the shape is selected, and I browse through all the many brushes, I don't see any selected, and in the stroke properties panel, I don't see any name for the brush either. What I ended up doing is saving as with a new name, but that can't be the best way to do match the brush style between objects.
  10. That's slightly different. I always use a single artboard with mutliple layers. If a layer is selected and I select Export, it still defaults to the whole document option.
  11. Thanks for the suggestion. I tried deselecting "Enable Metal compute acceleration" in settings under Performance>Hardware acceleration, but there was no change in the behavior.
  12. In other apps, I am used to aligning all selected objects to the first one selected. I know I can do that using the align panel, but it's a bit of a PITA to use. I would much rather have all my alignment tools automatically align to the first selected object. Is there no way to change the default behavior so I can just use the buttons in the toolbar rather than the annoying panel? Thanks, Gregory
  13. +1 for me. Transform objects separately is a great feature that I just read about on this thread, but it resizes proportionately, and I would love to resize all to the dimension I type in the Transform text field.
  14. Interesting. I just tried the Merge Geometry function myself, without the point transform or overlapping the 2 end point, and it worked fine. Not sure conceptually what the difference is between merge and join, but merge works and join doesn't. Quite odd! This is the easiest fix so far! Thanks.
  15. Hmm, I just tested it myself, and yes, in v.1 it works fine. So it's the interaction of v.2 with OS 13 with M1.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.