nwhit

The APub file has a linked APhoto file as a layer. That resource is in a picture frame and has 3 adjustments layers added using the Photo Persona within APub. However, on export, the PDF preview has that image darkened in any PDF export setting. It exports okay, but the preview is wrong. Other export formats show the image just fine (JPG, PNG, TIFF, etc.) with the exception of EPS, of course.

Doesn't crash for me.

Those are in v2. Try the free 30 day demo. The preview is in the export window and reflects your export settings. Metadata removal has always been in the More section of the export dialogue.

As an update, I just updated my M1 MBP to Ventura 13.1 beta and I no longer get the crash. Not definitive but may be a Ventura issue that will be resolved with the new version soon. Update: Spoke too soon! After trying it about 10 times, I let it sit for awhile. When I tried it once more, crash.

On the Serif website, there is a massive amount of information regarding the changes and improvements, including short videos that depict those new features/changes. MUCH easier than someone trying to type out that much info.

I’ve been doing very, very complex APub multi page docs in v2 with no issues like that. Runs quickly with little hesitation doing massive copy/pastes. Guessing it’s something unique to your computer or configuration.

If you are currently running CS6, just be sure you check the OS minimum requirement for Affinity V2 apps to be sure you don't purchase if you're on an OS that's too old to support it. FWIW.

A 10-minute free download would answer your question quite quickly. But OTOH, I found over the many, many months when Affinity was developing the IDML import in numerous betas, that any time my company came across an IDML import problem, it was very easy to upload it to their tech staff for evaluation and troubleshooting, which always resolved the problem, sometimes albeit after an upgrade. There are, of course, many things that can be done in ID that don't export well, much less import properly, but Affinity staff has been relentless in working on those issues to get them resolved, assuming they can be resolved. Sometimes it is the fault of ID, not Affinity that causes the import problem. May not be the answer you're looking for but it is a viable path.

In Publisher, you can select the Picture Frame, then check the Contextual Menu area for the Properties button. Change the Properties to None as far as scaling. Then using any of the corner points, you can resize only the frame. Also in this mode, when selecting the Picture Frame, the bottom right will now have a scaling dot that you can use to scale both the pic and frame.

The "solutions" have already been, very fairly, explained. If you just recently bought V1, Affinity has provided an email address to submit for possible resolution. If you bought so-so recently, and aren't ready to pay for the new version, don't upgrade. No one has to upgrade. Use v1 for a few more months or a year or so to amortize the cost over a longer period. V1 runs, produces massive amounts of pro-level media for our company's clients, and will keep running for the foreseeable future. Then later when you feel you've gotten enough "use" out of V1, then buy the new V2 version. That said, as been the history with Affinity, they are truly giving this fantastic software away at a very, very, very competitive price, whether at full retail or right now at the introductory price. Just seems strange that people are somehow construing that Serif are somehow forcing people to upgrade just because they launched a new version. If you don't want to pay the price, don't upgrade. Keep using V1 apps. They're great.

Best not to try then. Change is difficult for many people. And free is a pretty tough deal to accept. Personally, my media production company has imported hundreds of legacy ID files, most all without significant issues. And V2 of Publisher is dramatically better than V1 in my brief testing.

His answer seemed to indicate that he "meant" to say switching WITHIN Publisher (thus, the Photo Persona. When he said "Starting APhoto separately lets the menu entry appear again." seems to be in agreement with your instruction, Walt. Think he just isn't clear on the difference in the terms "Persona" versus full App.

Be pretty easy (and free) to simply download the 30-day free trial and give it a go. Easy way to test it.

As a media production firm, we've been running CS6 in a Parallels VM (Sierra for max compatibility for a bunch of software) for the last couple years with no real issues. Runs fast, works, shares files with the main OS, etc. Allowed us to upgrade the main host OS for newer software like Affinity.

Ah, yes. Driven past there many times! Amazing that a company this size can turn out such fantastic software with such great and personable support. Thanks to all involved! Good people!

Yes, I'm aware of that, but thanks for the reminder of that feature. It does, of course, assume that a person ALWAYS starts with a rectangular picture frame, which is often not the case. And I am unaware of a way to convert an oval/circle picture frame to square. Additionally, changing an existing rectangular frame to a circle using the corner option still requires a bit of tweaking in order to actually get it back to a circle or decent oval, and time = money for clients. Thus the Feature Request to have a simple toggle to go back and forth. Just be very, very handy for layout work. I would literally use it multiple times a day since several of our clients incorporate both round and square graphic items in numerous pubs.

I run into this all the time in Publisher. When revising previous publications or doing rough layouts, I have a need to change existing picture frames from square to round and vice versa. And, yes, I also routinely create shapes, then convert to picture frame. But when working on layouts, like to try an image contained in a rectangle, but also would like to easily be able to see it in a circle without having to start from scratch. And I don't want to go to the complexity of converting the frame into curves, then dealing with that. Just a simple toggle between square and round. Hopefully this would be a simple thing to implement. Thanks. And here we are in 2022 and hard to believe how long it's been since I've worked in ID!!! Actually since the first version of APub! Started with v1 of PageMaker, so been a long path to get to 2022!

Thanks @Dan C. I normally participate fairly deeply in the betas as these new features are added, but when PDF Passthrough happened, I was too busy to get more than superficially involved. Thus I missed the discussion on the ramifications for Preflight. Also seems odd that something so critical (the Preflight errors show virtually all the time due to the default being for an X-PDF) wasn't covered in the new video tutorial for the new PDF Passthrough/Placement. It would seem that most all users would get a preflight error after placing a PDF for passthrough since using PDF-x output isn't all that common except for users working with prepress requirements. I'm guessing most users simply ignore the errors (or don't use Preflight) because trying to find out the actual meaning of the preflight error is very difficult to ascertain. Perhaps it should be added to a Publisher FAQ section until it is better described in the Help. I watched the progress of PDF passthrough with great interest during the beta process since I used to have a background in print shops, newspapers, publications, etc. where it is a critical feature for modern publishing. I realize that it is still a work in progress with some rough edges still, so can understand how this might have been overlooked. Hoping at least the presence of this thread will help others who, like me, are initially baffled by the preflight error messages and can't find much of any info on the errors. Pretty simple to fix, assuming you know where to look!! 😉 Overall, Affinity apps just keep getting better and better. A few bumps along the way, but so refreshing as compared to the old standard apps. I was an Aldus PageMaker v1 user and trainer, so it's been a long journey to get to this point. While Publisher still has some glaring missing things, it is today highly competitive with far greater customer support. Thanks again.

Okay, after a whole bunch of searches and reading, finally found an answer in a beta thread. 1. In Preflight panel, need to click the Edit Profile in the little Actions menu (top right of pane). 2. Go down to PDF Passthrough, then select the minimum type of PDF you're wanting to Place. 3. Will need to Create a Preset for that setting since the Default seems to be a minimum of X-1a:2003. Otherwise you will always see the error message if you are Placing regular v1.7 PDFs. Overall, doesn't seem like a very intuitive or smooth way to do this preflighting. Would think there would be a better way, but who knows. Maybe in upcoming versions. Just wish that this would be explained on the need and how to do this in the online Help for the app! The Help says there is a Preflight for PDF Passthrough, but doesn't explain how it works and the need to set it to what you want in the Edit mode.

Just watched the Affinity video on placing content including PDFs, but like the online Help, it does not explain what kind of PDFs will actually passthrough instead of rasterizing. Rasterizing a placed PDF is not acceptable under most situations, so one would think that if there is a limitation on the kind of PDFs that will work, that info should be readily available in the Help. It's just hard to imagine that PDFs created in Designer won't work. I thought that might be a bug, but apparently it isn't. Sure could use some help on this since I have a publication that needs to be finalised.

Not sure how this got moved from Bugs to Questions. I've looked in the online Help for Publisher regarding the recent feature to Place PDFs as Passthrough, but I cannot see anything in the entire online Help that says what kind/type of PDF will actually passthrough without rasterizing on export (thus, not really passthrough). As per my original post, a PDF created in v1.10 of Designer apparently cannot be used for Passthrough in Publisher v1.10? That doesn't seem to make any sense, thus the question if this is a bug. Placing a Designer PDF shouldn't end up getting rasterized when exporting a PDF of the Publisher document, at least I wouldn't think so since that would be of little use. Right now, I cannot seem to locate any information of what is allowed to be Placed as a Passthrough PDF if I want to avoid the Preflight error message that it will be rasterized. If Passthrough doesn't work with Designer-created PDFs, then how do I create a PDF that can be Placed for Passthrough in Pub?

Working on a doc in 1.10.0 and have a couple PDF's exported from ADesigner. Have them marked as PDF Passthrough. Yet Preflight is warning "Placed PDF version (PDF-1.7) is not compatible with the PDF export version. The PDF will be rasterized on export." I haven't tried exporting yet, but the warning concerns me. I've tried exporting from Designer in both For Print and For Export, but get the same warning. If I place the Designer doc instead of the exported PDF, I don't get a warning. Obviously, I don't want the placed PDFs to rasterize. Is this a bug or is this newer feature just a bit more complicated than simply placing a PDF and having marked as Passthrough? Haven't tried exporting from Designer in PDF-x formats, but would think a "normal" PDF for Print or Export would be "compatible" in Publisher. But obviously I'm doing something wrong.

Aha! Think I may have found the workaround! According to this article by a prepress guy, apparently one of the font managers (TypeFace) can actually shut off/deactivate the OS11 System/Library/Fonts/Supplemental fonts, which are 283 fonts, many of which are seldom used by some people. Assuming this is true (I hope!!!), I can thus use TypeFace to create actual sets that would only include the fonts I want, plus it has to include the 73+ system fonts that cannot be deactivated. That would really help clear up the All Fonts dropdown!! http://www.jklstudios.com/misc/osxfonts.html UPDATE: Just tried to deactivate one of the Supplemental fonts and it worked! And it no longer showed up in APub All Fonts!!! Looks like I may have found the magic solution! Plus TypeFace is only $35, so a lot more affordable than some of the other options, which according to the article, none of the others can deactivate these 283 Supplemental fonts. Thank goodness!!

So in other words, the font sets/groups you create in a font manager become the only active fonts showing in apps??? But not clear on how can they not show (deactivate) the 355 "permanent" fonts in OS11 that can't be deactivated? Is a font manager app actually moving fonts out of fonts folders, or trying to deactivate fonts not in a group?? But that, of course, can't be done in OS11 with the 355 fonts in System/Library/Fonts. I guess I'm still not seeing how what is created as sets within the font manager apps affects what I see as font lists within apps. Old age, I'm thinking!! 😂

Old thread, but have a question. I've downloaded a few free trials of these mentioned font manager apps, but for the life of me I cannot see how to use them within Affinity apps! None of their documentation explains how to use the managers within an app, only how to organize fonts. Can anyone explain how to use TypeFace, FontBase, RightFont, etc. Like I said, adding and organizing looks easy. But how are these used within the Affinity apps themselves to select and set type? Thanks.