publisher integration problem in data fusion

[macslywood]

Hello everyone,

I have a problem when I embed publisher files into another publisher file in an image block via data merge. The integration works well, but if I export the generated files in jpeg, the integrated publisher file is in low definition (with the diagonal lines of blocks that appear...).

The export goes well if I do it in PDF or any other format.

I hope that's clear enough, I'm having trouble explaining the situation easily. Is the bug known, or is there a workaround?

 

Thank you for your attention.

 

Greg

[NathanC]

Hi @macslywood,

Your issue somewhat sounds like the issue raised in this thread, on M1 macs exporting to PDF with JPEG compression enabled can result in artefacts/white blocks appearing all over the images on the final PDF images and cause image quality issues. Is this potentially the issue you're encountering? I would first try disabling Hardware Acceleration (AKA Metal) under Preferences > Performance, restarting the app and then try your export again.

If the aforementioned issue is not what you're seeing and disabling Metal does not sort this, could you provide additional screenshots and a sample file where you're encountering this issue?

Many thanks.

[macslywood]

Unfortunately, this is not the same problem. I'll try to explain more clearly (but it won't be easy!).

I want to create images to integrate into the signatures of emails for people in my company.

There are 3 different entities. I therefore created publisher files with different colors to make the backgrounds of the signatures, and the fields corresponding to the surnames, first names, function... which are put in place on top with the data fusion module. the color backgrounds are also integrated with the data fusion module in an image block so that the entity corresponds with the person.

If I export the generated files to PDF, it works fine. But if I export in another format (jpeg, tiff...) the background image is generated in low definition with the lines in the blocks (see attached image).

I tried your settings in case it fixes my problem, but unfortunately it didn't work

 

 

PS : sorry if it's not clear. the problem is already not very easy to explain, but being French, and therefore very bad in a foreign language 😜 , I go through google translation which. don't make things better!

export pdf.pdf

[NathanC]

Thanks for clarifying, the quality of the JPEG file is determined by the pixel resolution (Along with the Quality slider) and will always appear in lower quality in comparison to your PDF export which is comprised of vector curves, however the picture frame lines on the JPEG are unusual. Could you provide me with the .afpub file that has been generated from your data merge (prior to you exporting to PDF/JPEG)? I can provide a private upload link if needed.

[macslywood]

yes, I am well aware that the quality of the jpeg export depends on the resolution, but the most surprising thing is the appearance of diagonal lines in all the blocks.

I attach the package of the file generated by the data fusion.

pour forum.zip

[NathanC]

Many thanks for the file,

This is very unusual, it appears that the embedded .afpub file that you used as a part of your original data merge document that uses picture frames with stroke/fills applied has the Wireframe cross being rendered when exporting your final merged document to any Raster based file format, such as JPEG or PNG which should not happen.

I've managed to replicate this on a brand new doc, I created a new .afpub file with two picture frames in it and then saved the file. I then placed the .afpub file in a different new document and then re-scaled the placed document so that it was a fair bit smaller and then exported to JPEG, the exported result had the wireframe cross on the picture frames. I'll get this logged with the developers.

In regard to your file, probably the most feasible workaround would be to re-create or edit your embedded publisher file(s) and use just standard curves/shapes instead of picture frames, that way you would avoid these being incorrectly drawn with a cross/wireframe when exporting to a raster format and then re-generate your data merge again.

[macslywood]

ok, I checked and indeed it works well when we modify the image blocks in simple paths! thank you very much for the solution, waiting for the developers to fix the bug.

Have a nice day and thank you again

[Affinity Info Bot]

The issue "Exporting to a Raster format can incorrectly draw the Picture frame Cross when it is an embedded/linked Publisher file" (REF: AFB-7547) has been fixed by the developers in internal build "2.1.0.1742".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[macslywood]

Thanks a lot !!! Another question, do you know if there are plans to introduce a function to automatically delete fields that would be empty in a data merge instead of leaving a space at present?

[NathanC]

1 hour ago, macslywood said:

Another question, do you know if there are plans to introduce a function to automatically delete fields that would be empty in a data merge instead of leaving a space at present?

Not that I'm aware of, if this is a function you would like to see implemented feel free to make a post over on the feedback & suggestions section 🙂

[macslywood]

thank you, i will do that!