nwhit

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.

I can see that problem happening. Of course, the issue in this thread isn't the same since the font menu corruption occurs on each and every new, blank document in all 3 apps. No carryover. For some reason, Affinity cannot use the Font Book collections without subsequently corrupting the All Fonts menu. And as per the various posts and pics, it's not just with a single font. The duplicate font styles happen to numerous fonts. As said before, the All Fonts menu is correct initially (in a blank, new document in any of the 3 apps), but if you then select one of the custom collections you've created in Font Book, there are then numerous duplicate styles showing for many fonts in the various collections. Following that, the main All Fonts menu now shows an increased number of duplicate styles for many fonts. That makes it pretty tough to pick a font and style, not knowing if it's "real" or not! Note: This issue is new as of v1.9.x since I used to use these same Font Book collections constantly in previous versions without any issues. Never had a problem previously.

FWIW, while I'm on a different machine (Intel, etc.), I just tried opening several large PS files in v1.10.0 and had no issues. You might need to upload a sample file or two for people to check to see if it's file related.

I just got through with an hour session in macOS 11.5.1 using the new 1.10.0 doing picture frames, sizing, moving, etc. and it all works fine. I did find with my APhoto that I needed to delete my v1.9.3 app, then download the new one to fix a problem I had with that upgrade. While I have the Affinity Store versions, you can also do that with the App store version. Sometimes that fixes some issues.

Sadly, no, a font manager does not solve the problem in newer versions of macOS such as Big Sur. Catalina and especially Big Sur and Monterey automatically add a few hundred fonts, all of which cannot be turned off (unless you use TypeFace font manager to turn off a few). Thus the font menu has many, many fonts showing that are hardly ever used. TypeFace font manager is one of the only ones that can actually disable the "Supplemental" set of fonts Big Sur installs, which is helpful, but it does not turn off the many, many others that show up in the Affinity All Fonts menu. The only real solution (prior to Affinity v1.9) had been using Apple's Font Book's customized collections so that in all apps you could go to/view a smaller subset of displayed fonts. Worked great until recently, so hopefully Affinity can sort it out and get it working again.

Yes, hard to figure this out. All other apps read the Font Book collections just fine, and like you, I use those collections for virtually all my text work. Hopefully the riddle can be solved in the next update!

HOORAY!!! I ended up renaming my 1.9.3, then downloaded a fresh version from the Affinity Store instead of updating. That seems to have fixed the issue. Working now!!! Not sure why the update messed things up, but at least it's now working!

Interesting note: I have OS12 installed on a Parallels VM along with my regular apps. I upgraded that copy of APhoto from 1.9.3 to 1.10.0 and Eye Candy works on that version. (Note: Affinity apps work (mostly) in the new Parallels v 16.5.1.) Very strange. On my normal OS11 installation, EC worked fine in 1.9.3 and all previous versions (from the Affinity Store), and worked fine on all the 1.9.4 and 1.10 betas. Still does. And restoring APh 1.9.3 from a backup, EC still works fine. Not sure what the issue might be. Was looking forward to the improvements in APub and APh in 1.10, so a bit discouraged right now.

Just tried the 1.10.0 final and EC has stopped working. Not only is the preview totally unusable, but the final end-product doesn't work. Oddly, it worked fine in 1.9.3 and all the betas including (as per the pics) the final RC2 1.10 beta. Screen shots of 1.9.3, 1.10 RC2 beta and 1.10.0 final. All Affinity Store versions. Metal on OS11.5.1. Had to downgrade back to 1.9.3 since I use EC for client work.

...and on 11.4

Still have the Font Menu corruption problem with this RC, same as with the other 2 apps.

The font menu corruption problem is still in this RC.

This is still an issue in the latest beta/RC 1.10.0.1115. This was not an issue prior to my upgrade to v1.9.x and/or Big Sur. Previously I used Font Book collections routinely without an issue.

In all 3 of the Affinity betas, if you select any Font Book collection, it shows numerous duplicate styles for many of the fonts. If you then select one of those collections, when subsequently then go back to the All Fonts listing, it will now show even more duplicate font styles, thus making it a bit impossible to select a font and style, not knowing if you've selected a real one or some corruption of the list. This first began with either v1.9.x and/or my switch to Big Sur. Can't be sure which caused it since both happened at about the same time for me. Prior to this, I used Font Book collections routinely in all Affinity apps without any issues. This problem was also confirmed by Old Bruce. Full details of the troubleshooting and narrowing down of the problem was reported in this 1.9 bug thread. However, the problem is still in the newest 1.10.xRC beta as well. Font Book collections are useless and will cause the main All Fonts menu to corrupt.

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.

INTERESTING!!! So you have the same issue with Affinity's listing of Font Book user font collections?!? As I've said in previous posts, I'm not seeing the duplication of fonts in any other app other than Affinity apps, and all Affinity apps are showing the same duplicates within the font collections, which if viewed, then corrupts the All Fonts list as well! Yeah, in the old days, I used to use Suitcase (years ago, and even before OSX), etc. to only have my main fonts showing in my main apps. But with Big Sur/OS11 especially, it is no longer possible to do that. OS11 puts 355 mandatory fonts into the System/Library/Fonts and Supplemental folders that can't be deactivated. Makes for a very congested fonts menu! I have for a few years used Font Book's user-designated Collections, and with no problems. I was using them routinely in Affinity apps as well and was not aware of the problem I'm now seeing. For me it started with what appears to be OS11 and/or Affinity 1.9.x. But interesting that you see the same thing! I haven't used a font management app in years, so am not aware if using one can overcome this issue. Might be worth the very hefty price they now ask for one of those previously inexpensive utilities if it could fix this problem. Maybe someone who uses a font management utility could answer that. The way it is right now with OS11, scrolling through several hundred mostly useless fonts to try to set type in client docs/images is really not pleasant at all. Thanks for the input, Bruce! At least I now know that I'm not alone in seeing this issue (and totally cursed!!). And it does raise the question, where is Affinity getting its Font Collection listing from? Or why is it "corrupting" Apple's Font Book's user Collections?

@Jon P Just to clarify, it does not appear that the issue involves the Futura fonts that were originally creating an issue in some docs due to being very old (now replaced). All fonts within any of my font Collections show up as duplicated when viewed under the Affinity Font Collection view, then subsequently corrupt the All Fonts list view as well after having viewed the collections list (see attached pic of one of the collections with every font containing duplicate styles). I have also tried deleting the macOS font caches using Terminal. I also downloaded a trial of Suitcase and used their utility to delete font caches. The problem persists. This suggests that Affinity apps appear to be referencing their own font cache, or at least a Font Collections cache. The Affinity apps are the only ones having this problem of a "corrupt" font list, especially font collections. Hopefully you guys can suggest a fix. Thanks.

Just to be sure, I just deleted my copy of Publisher (Affinity Store) and downloaded a fresh copy, deleted/moved all the prefs (App Support and Prefs), and restarted with Control, resetting everything. I still get the same issue. Under All Fonts, I get the correct number of styles within the problematic fonts. But when I look at a font collection, those same fonts then show more than double the number of actual styles, and then subsequently corrupt the All Fonts listing. I also tried clicking the Reset Fonts in the app/prefs. Didn't fix anything. This suggests that Affinity is storing the font info somewhere for all Affinity apps since they all are showing this problem?? If not, where are the apps getting the info for fonts and collections? While I have little expertise in this area, the actual font collections are correctly shown in all apps that use Apple's Font viewer/listing window, such as in Mail, Pages, Numbers, BBEdit, etc. That leads me to believe that the macOS file/cache of the fonts and collections is correct, but somehow the Affinity apps are retaining or showing a corrupt version. As said many times, I really need to find a fix for this so that I can get back to client work. Trying to scroll through the large number of Big Sur fonts just to get to our clients' set of fonts is a real PITA! And if uninstalling the app doesn't fix it, there must be a way to fix Affinity apps' font collections cache.

Chris, yes, this was a one-off. My concern is what did that Terminal session do? The nature of the commands are beyond my knowledge in Terminal, so was hoping you guys might understand what it was doing and if anything "bad" happened as a result. Just seems strange/suspicious that a crash in Photo would initiate a Terminal session of any kind! Thanks.