Linked Files Blured

[Vaclav Slovacek]

Hello,

this is an issue that has been in Affinity Publisher for a long time and has not been resolved so far. When using a linked document the resources they get blurry often. I have tried to find the exact root cause and it is hard to replicate as it happens seemengly randomly. I have tried to find what is the root cause and tried switching Linked/Embedded.

This specifically happens when a linked/embedded file contains another linked/referenced document. Publisher has obviously some lazy loading strategy when I zoom in it loads the high-quality non-pixelated version. However, very often it simply does not happen and the object stays blurry. And it stays blurry even when exporting/printing the content which makes the Publisher unusable.

It is also hard to tell what actually makes the content pixelated, some content from the linked document is sharp, but some is not. Sometimes when I resave the linked document different objects become blurred. In the screenshots, there is an example where a bench from a linked document is blurred but after moving it a bit and saving again would make it sharp. This is the same object as the other sharp benches.

From the past conversations I have removed them from the iCloud folder but it does not make a difference.

Is there a way to provide logs when this happens? Because this was not resolved for ages.

Too sad that a feature that promises to increase productivity leads to wasting time on trying to figure out what is wrong.

Is there a way how to force load the sharp linked content at least during print/export?

[NathanC]

Hi @Vaclav Slovacek

Based on your screenshot the render of the bench appears to be the low quality cached preview of the resource similar to what Publisher shows if a resource is missing, based on your description I would not believe this to be the case, but for 100% confirmation does the resource status (And the linked resource(s) inside the linked file) all show as OK and not missing? If the resource states are all OK and it still renders the poor quality preview could you confirm the below?

• What MacOS version are you using?
• Is Publisher up to date? (2.5.5)
• Where are the source file and linked resources kept? (E.G Local drive, Cloud Drive, NAS drive etc.)
• Could you provide a copy of a currently affected document so we can see if the issue can be observed/replicated? I’ve provided a private upload link below.https://www.dropbox.com/request/0wo45O4VCjvsRoa1vFIS

On 9/9/2024 at 11:13 AM, Vaclav Slovacek said:

Is there a way to provide logs when this happens? Because this was not resolved for ages.

Not for this type of issue i'm afraid.

On 9/9/2024 at 11:13 AM, Vaclav Slovacek said:

Is there a way how to force load the sharp linked content at least during print/export?

Resource Manager doesn't currently have a 'Refresh all' button, but you could try removing and re-placing the resource if the link/embed switch doesn't work.

[Vaclav Slovacek]

If the resource states are all OK and it still renders the poor quality preview could you confirm the below?
All resources show OK.

What MacOS version are you using?
14.6.1 (23G93)

Is Publisher up to date?
2.5.5

Where are the source file and linked resources kept? (E.G Local drive, Cloud Drive, NAS drive etc.)
Local drive, they were in iCloud Drive but I have moved them a while back to check whether that could be causing the issue

Could you provide a copy of a currently affected document so we can see if the issue can be observed/replicated? I’ve provided a private upload link below.
Is there a way to collect all the linked content to a document? So I do not have to hunt them all over the place (there are quite a few)

Resource Manager doesn't currently have a 'Refresh all' button, but you could try removing and re-placing the resource if the link/embed switch doesn't work.
I believe you understand but this is extremely time-consuming and error-prone. It efficiently defeats the purpose of using the feature.

[Vaclav Slovacek]

I have saved two documents as a package (Affinity - Designer, Atlas - Publisher). However, it does not seem I am able to replicate the exact behavior in the package. 

When I open the package many resources that have not been loading are now loading.

However, in the Atlas file/Publisher case, I have issues after loading. I have to scroll around to "force" the Publisher to load/show the high-resolution images and eventually the Publisher just becomes unresponsive. 

Let me know, if you need the source docs in a different shape. I really did not want to hunt for individual linked files and copy the file system structure. But if that is necessary, I might need to do it.

[BBG3]

Hi @NathanC I have this problem in AD. Sometimes, it takes a few seconds to 2 minutes to become unblurry; sometimes, it remains blurry.

[Vaclav Slovacek]

There seems to be some lazy loading that sometimes works, sometimes it does not. I would understand it as a performance optimization that Affinity loads the stuff you are looking at (first, or only that content). However, there are two issues with it:

1) Sometimes it is slow, like @BBG3 mentions

2) The much worse case it is loads never, even when you PRINT or EXPORT. Which makes it useless for an actual production.

I am using Affinity for protyping on a long term project with a good faith this gets resolved before an actual production is needed. But it is sticking for so long that might become a risk soon.

[MikeTO]

I think there may be a known bug related to this.

 

[walt.farrell]

1 hour ago, MikeTO said:

I think there may be a known bug related to this.

That topic seems related, but has no bug tag and seems not to have ever been examined by Serif.

[NathanC]

Hi @Vaclav Slovacek,

Thanks for sending those files over, I can confirm I'm able to reproduce your issue. After opening and re-saving the 'Dvur - Backyard.afpackage' file as a .afpub and then subsequently placing the .afpub in a new empty document I'm observing the resource loads the low quality 'Missing' preview of the objects, but if I zoom in far enough the resources eventually load most of the time. It's entirely random as to whether or not all the linked objects within the placed file load the expected quality preview.

If I double-click to edit the linked resource contents I can similarly see this low-quality preview again. Performing any further actions such as closing the linked resource and parent document or just panning around in the parent document the app will eventually result in a freeze or app crash, I've confirmed this is the same on both MacOS and Windows.

I was originally under the impression that this may relate to the symbols in the 'Dvur Backyard' file as we have a similar issue to this historically logged, but after detaching the symbol instances these same problems persist. I'll log your file with the developers for further investigation into what's causing this.

[BBG3]

Hi @NathanC

Is there any temporary solution to not seeing blurry external links? I had about 100 external links that Affinity Designer showed me at the beginning without any problems, but after closing and opening AD, all my links were blurry. I can't finish my job. It is critical to finish my job today and I got stressed.

Thanks

[Hangman]

Hi @BBG3,

What file format were the linked files?

I'm interested because I've seen something similar with linked EPS files...

[BBG3]

Hi @Hangman.

You are always ready to help members. I appreciate that.

The links are connected to an AD file, which has different artboards.

[BBG3]

@Hangman

My finding:

If I click and select a linked blurry image and then zoom out or zoom in, the image becomes unblurry. This action is needed for every single linked image.

[Hangman]

Hi @BBG3,

I've seen the exact same problem with Linked EPS files, as noted in this post with the same resolution...

Out of interest, if you change the status of the files from Linked to Embedded, close, and then reopen the file do the files display at their full resolution without the need to zoom out or zoom in?

[BBG3]

28 minutes ago, Hangman said:

change the status of the files from Linked to Embedded

Thanks for your help, @Hangman. Unfortunately, I can not do that. I have a master design file (many related designs), complex mockup files ( a combination of 100 artboards), and a test print file. These files can't be merged into one file.

Thanks anyway. 🙏

[Hangman]

Just now, BBG3 said:

Thanks for your help, @Hangman. Unfortunately, I can not do that. I have a master design file (many related designs), complex mockup files ( a combination of 100 artboards), and a test print file. These files can't be merged into one file.

I was thinking of trying this more as a test, so for example, if you have say one particular Artboard that appears blurry when linked, could you embed just that one to see if it resolves the problem... or even just link the artboard in a new empty document and if it also appears blurry there then embed it to see if it fixes the issue...

If that's not an option then I completely understand, I just wanted to clarify whether or not it's the fact that the files are linked that is the cause of the problem if that makes sense...

[Sensational Sebastian]

On 9/17/2024 at 4:24 PM, NathanC said:

Hi @Vaclav Slovacek,

Thanks for sending those files over, I can confirm I'm able to reproduce your issue. After opening and re-saving the 'Dvur - Backyard.afpackage' file as a .afpub and then subsequently placing the .afpub in a new empty document I'm observing the resource loads the low quality 'Missing' preview of the objects, but if I zoom in far enough the resources eventually load most of the time. It's entirely random as to whether or not all the linked objects within the placed file load the expected quality preview.

If I double-click to edit the linked resource contents I can similarly see this low-quality preview again. Performing any further actions such as closing the linked resource and parent document or just panning around in the parent document the app will eventually result in a freeze or app crash, I've confirmed this is the same on both MacOS and Windows.

I was originally under the impression that this may relate to the symbols in the 'Dvur Backyard' file as we have a similar issue to this historically logged, but after detaching the symbol instances these same problems persist. I'll log your file with the developers for further investigation into what's causing this.

 Just want to add that I am experiencing the same issue in Affinity Photo 2.5.5 on macOS 15.1 Beta（24B5070a）. See the attached example files.

Linked file resolution issue - example images.zip

[NathanC]

Hi @Sensational Sebastian,

Thanks, but i'm not sure it's the exact same issue as reported by the OP. I'm able to consistently export your 'File with link.afphoto' out to JPEG and the quality is identical to the 'Original file.aphoto' high quality JPEG export since the placed resource status is 'OK'. Whereas if I delete the 'Original file.afphoto' so it's missing in 'File with link.afphoto' and then export out to JPEG the lower quality matches the 'File with link exported.JPEG' file in your ZIP, which indicates that the resource may just simply be missing and needs re-linking, or perhaps that the JPEG export settings were different.

Check out the ZIP file attached for reference, i've named the three exports accordingly.

File res.zip

[Sensational Sebastian]

Hi @NathanC

Thanks for the reply and please let me know should I open another forum post for this issue. I have double checked, the linked file is definitely there (which can also be seen by the fact Affinity doesn't indicate a missing resource when opening the file). I've attached a screencast showing the steps to reproduce this issue including the resulting output files.

 

This is a very long shot, but since Affinity shows the “Affinity Photo 2” would like to access data from other apps." dialog at each restart of the app (even if access has been granted), could it be that Affinity – in a similar manner – doesn't properly restore its security scope bookmarks/access rights and thus fails to access the linked file?

Linked file resolution issue v2.zip

[NathanC]

Thanks for the screencast, from what I can tell it looks like the quality difference between the two .afphoto file is present even prior to exporting out to JPEG. What happens if you delete the document and file > place it again and export to refresh it? If that doesn't have an impact, if you place it as an 'Embedded' type resource and export is that any better?

I did also notice that all the documents in Finder throughout the process have a checkmark next to them, are they being backed up to a Cloud storage service or Backup software? What if you attempted this again but in a location that's not being actively synced to the Cloud or a Backup system in case that's somehow interfering?

[Swörl]

I'm having the same problem with Designer 2.5.5 on MacOS 14.5.

I'm stacking 12 32-bit EXR files, 8k dimensions (3D renders). They're all linked and Status is "OK" according to Resource manager.

The document ALWAYS opens blurry. I tried the zoom-in-zoom-out trick, that works (it refreshes to a sharp copy) if I select each linked file manually in layer manager one by one and then zoom.

I have 128Gb ram, of which 100 free. When it opens the file, I can clearly see that Designer is not using enough ram to cache all of the linked files: only 1.4Gb. It uses up 6Gb after all the zooming and getting sharp links.

 

 

[NathanC]

Hi @Swörl,

This is a separate, but known issue specifically with linked EXR files currently logged with the developers, i've bumped the issue with your report. 🙂

[Sensational Sebastian]

Thanks, @NathanC

 

I've performed another test in a folder not synced by the backup program. However, the issue persists. All linked files are shown (and consequently also exported) blurry. If I embed the previously linked file, the embedded file loads in full resolution again.