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

carl123

Members
  • Posts

    8,485
  • Joined

Posts posted by carl123

  1. 5 hours ago, Amy Choue said:

    What do I need to do to fix it? When I click on "fix" on the right side of "Missing font," a dialogue box opens (Font Manager), and it seems I can choose a font to replace the missing font there. Do I simply choose a font there and click on "Close"? Does this take care of the missing font error? 

    No, Font Manager just lets you assign a "temporary" font to replace the missing one, so you can print or export your document. You will still get the preflight error warning you that the original font is unavailable on your system.

    5 hours ago, Amy Choue said:

    It seems I didn't use that "BaskervilleURW-Reg" font anywhere in the file. If it was used, it has to be in the Headings, and none was in that font. Are there ways to go to the places in the file where "missing font" was used?

    Yes, you use the Find & Replace dialog

     Use the Cog menu and under Fonts change the ALL dropdown to Missing

    Then in the Font Family dropdown you can select the missing font

    Click OK in that dialog to close it and then click Find in the Find & Replace panel

    You will then get a list of all the occurrences that missing font is located in your Document. Clicking any of those occurrences will take you to the page where that font is used

    You can then change it manually or if you prefer you can use the same Find & Replace panel to assign a new font to replace the missing one for all occurrences where that missing font is found

    Either way, this change is permanent and preflight will no longer give an error for that missing font

  2. On 2/2/2024 at 6:38 PM, johan belmans said:

    The Raw layer Embedded option in Develop Persona is great. The macro solution for copying the Develop Persona settings is good, but it would be great if once developed , a simple right click on the layer (in Photo Persona) would copy the settings and then paste the same settings on a different layer in the same .aphoto file.

    This is useful in case you have to update a layer with a new version of a specific image, but still need the same Develop Persona settings. If I need to save each time a macro for each individual .aphoto file I will end up with too many macros. As far as I am aware, the macro is not saved within the .aphoto file.
     

    With the Move Tool active, select the developed Raw layer and you will get an option to Replace Image in the context toolbar. When you use that option to replace the original image with a new version of that image, the previously applied Raw edits will be applied to that image also

  3. 16 hours ago, Sylvain Hamel said:

    I tried many afphoto files and I realized that it seems to take a while to load the linked RAW file (40 to 80 seconds maybe).

    I'm surprised because it takes less time to load the RAW file in the Develop Persona.

    Loading a RAW file in the Develop Persona only performs the basic operations needed to load the file but if you then do other things like exposure, curves, noise, shadows etc then all that additional processing has to be redone when you open the APhoto document before the preview (pixelated) image is updated.

    Which would explain the increase in time when opening an APhoto document compared to just opening the RAW file

     

    If I load the sample file you uploaded in your first post it takes me 22 seconds until it is unpixellated

    For some reason you appear to have duplicated the RAW layer in the APhoto file. If you did this so you have a backup then this is not necessary as the original RAW file is not touched. But far more importantly duplicating this (not needed RAW layer) increases the time for "depixelation" to occur significantly. By deleting that additional RAW layer or simply hiding it, and resaving the APhoto file, then the time it takes until the image is unpixellated drops to 11 seconds (half the original 22 seconds).

    It looks like each RAW layer has to be processed separately. So don't duplicate the RAW layer if you don't have to

    As an additional experiment after deleting your (not needed) RAW layer I then went back into the develop persona and reset all the adjustments (lots) you did to the RAW file back to their defaults. This then enables the file to be fully opened (unpixellated) in just 4 seconds so it's clear that whatever adjustments you do to the RAW layer increases the time to process the document when you reopen it. But there is not much you can do about this, it's just an observation.

     

    On 1/28/2024 at 10:00 PM, Sylvain Hamel said:

    With these files, the image most of the is displayed properly after 1 to 2 minutes

    Not sure why it takes your PC 1 to 2 minutes to "display properly" but it may just be that my PC is faster than yours. You may want to post your PC's specs memory, cpu, drive, (SSD?) for analysis, also a screenshot of Edit > Settings > Performance may be useful 

     

  4. 22 minutes ago, prentice1024 said:

    but the Windows file manager continues to show the date and time on dictionary.propcol as 1/8/2024, the date of installation

    Sounds like you are not copying the right dictionary.propcol file

    Are both Publisher versions exactly the same?

    Were both Publisher installations from the same source (Affinity website or Microsoft store)?

    and were they the same as regards you installed either the ".exe" version or the "MSIX" version?

     

  5. 1 hour ago, gotanidea said:

    we can hold the Alt key in Affinity Publisher

    All the ALT key does is disable snapping

     

    15 minutes ago, bbrother said:

    Placed images (images layers) are treated differently. By default their aspect ratio is maintained when resizing and you need to use SHIFT-drag from corner handle to make the opposite (resize without maintaining aspect ratio).

    But if you drag from a middle handle then SHIFT-drag works in reverse for placed images

    There may be a good reason for this (that I don't understand) but it does get a bit confusing at times when working with placed images

×
×
  • 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.