Jump to content
AdamW

Affinity Publisher Public Beta - 1.7.0.330 (Withdrawn)

Recommended Posts

Due to an issue discovered with the management of placed documents e.g here, here and the fact that document corruption can occur, we have chosen to remove the download links to Build 330. We will post another update to rectify this issue as soon as possible.

If you have already downloaded 330 you may wish to consider reverting to Build 312, but be aware that due to new functionality in the later build, documents saved in 330 may not load in 312.

Thank you for helping us find this issue.

---

Please note Build 330 fixes the following issues in Build 326. Build 326 has been withdrawn and we encourage you to update if you are using it.

- Converting an Embedded resource to Linked could delete the original resource
- Replacing Image on a placed PDF could leave Resource Manager in an inconsistent state
- Crash copying and pasting embedded document resources

Thank you for reporting these.

Status: Public Beta
Purpose: Stability and General Testing
Requirements: Mac OS 10.9 or above

Hi,

We are pleased to announce that Affinity Publisher build 326 is now available as a manual download from the link above. To be notified when there is a new beta please press follow on this announcement thread.

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 

We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. 

Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum

Many thanks for your continued feedback.

---

Fixes and Improvements 

A Note about Linked Images

Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size. Please note that unfortunately this will not apply for linked images in existing documents, they will have to be replaced in order to see an effect. When a document with linked images is opened you may now momentarily see a low-res preview before the full image is loaded and 'pops in'. This is expected behaviour.

Other Fixes

Menus / Studio
(Win) Docking Pinning Panel to the left/right causes crash on next run up
Deleting global colours could cause crash
(Mac) OS accented colour set to Graphite now works correctly for font controls etc
Fixes for Expression Parser

Tools
Fixed selection of Picture Frames from Masters
Vector cropped object in Picture Frame now scales correctly

Text / Tables
Fixed noticeable text lag under some circumstances with Character Panel visible
Fixed auto-correct crash e.g. typing (a)
(MacOS) Ctrl+Alt+Tab in a table inserts a tab and switches document
Prevented deletion of entire cell range with non contiguous selection
On converting a shape to a text frame the context toolbar now shows the correct text tools
Fix for Find / Replace All when found ranges were adjacent

Resources
Improved locating missing resources on file load
Fix for Resource Manager incorrectly reporting resources as modified under some circumstances
DocX improvements - fixes for lists, colours and paragraph run properties
---

Earlier Release Notes Beta 312

Share this post


Link to post
Share on other sites
4 hours ago, AdamW said:

Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size.

This is a huge improvement! I tried it on an A3 file that had one hi-res image. It was 15,3 mb in the previous version. In the update and after newly linking the image, the file size was only 1,1 mb! This is a big deal, as it makes for much less hard-drive clutter without loss of performance. Will this method of linking also be available for Designer?

Share this post


Link to post
Share on other sites
15 hours ago, AdamW said:

Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size

So great! Thank you.

Share this post


Link to post
Share on other sites

@Matthias , @postmadesign, @mac_heibu ,

@mkaneshiro, @SillyWalk , @fde101, @Jens Krebs, @>|<

Build 326 initially released in this thread has been withdrawn

Please download the replacement build 330 from the link above


Patrick Connor

Serif (Europe) Ltd.

Share this post


Link to post
Share on other sites

Some file sizes shrunk from 500 MB to almost nothing. Already reclaimed a few gigabytes with just a few Publisher files containing now linked, formerly embedded hi res TIFFs

Share this post


Link to post
Share on other sites
On 5/15/2019 at 1:46 PM, postmadesign said:

This is a huge improvement! I tried it on an A3 file that had one hi-res image. It was 15,3 mb in the previous version. In the update and after newly linking the image, the file size was only 1,1 mb! This is a big deal, as it makes for much less hard-drive clutter without loss of performance. Will this method of linking also be available for Designer?

This is great to hear! One less "deal-breaker" on my list!

Share this post


Link to post
Share on other sites
On 5/15/2019 at 10:46 PM, postmadesign said:

Will this method of linking also be available for Designer?

Looks like low hanging fruit to me. When installed, Designer and Photo will appear as Publisher “personas“ (”personae“?), ready to edit Publisher documents and feed them back to publisher again. These apps then will have to understand the new linking method. If Affinity decides to leave linking out we should have at least the (annoying) workaround of opening Designer documents in Publisher, changing the status of ressources from embedded to linked and continue with Designer.

Share this post


Link to post
Share on other sites

It seems a reasonable guess that it will also work in Designer when that product also gets through beta. Usually shared features between the Affinity apps work in the same ways. It's good for user consistency, but also I think it has something to do with shared code bases.

Share this post


Link to post
Share on other sites
51 minutes ago, garrettm30 said:

It seems a reasonable guess that it will also work in Designer when that product also gets through beta. Usually shared features between the Affinity apps work in the same ways. It's good for user consistency, but also I think it has something to do with shared code bases.

Designer 1.7 will clearly need to be able to open .afpub (or .afphoto, .afdesign) files saved by Publisher that contain Linked documents.

What we don't know, yet, is whether Designer will offer:

  • The option to prefer linked/embedded when creating a new file.
  • The ability to change linked files to embedded, or vice versa, or (in general) whether it will have the Resource Manager.

However, it is possible that both of those might be available using a combination of Publisher and Designer (for users who own both) when the additional Personas are enabled in Publisher.


-- Walt

Windows 10 Home, version 1903 (18362.145), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.1.404 and 1.7.1.404 Beta   / Affinity Designer 1.7.1.404 and 1.7.1.404 Beta  / Affinity Publisher 1.7.1.404

Share this post


Link to post
Share on other sites

Just for clarification, Adam: as long as I keep my images embedded rather than linking it, I would be on the safe side, even with .330? :/

Share this post


Link to post
Share on other sites
On 5/18/2019 at 7:31 AM, A_B_C said:

Just for clarification, Adam: as long as I keep my images embedded rather than linking it, I would be on the safe side, even with .330? :/

Hi A_B_C.,

Sorry I missed your post - yes, it is specifically the action of converting an 'embedded document' (pdf, psd, svg, affinity documents) from embedded to linked that creates a document that cannot be re-opened. As it happens, conversion between embedded and linked is fine for placed raster data (jpeg, png etc). Hopefully we should have a fix soon. In the meantime, as always, but especially if using 330, please keep regular backups.

Share this post


Link to post
Share on other sites

Thank you very much, Adam! That was very helpful, and I am feeling relieved now. :)

Keep up the good work! Publisher, together with the two other apps, is going to be a fantastic application. Of course, I have to add my ceterum censeo;) … but I can’t wait for the release version … everyone here is excited. :)

Alex

Share this post


Link to post
Share on other sites

Out of interest, will be be able to open files I created in 330 in the next beta - by this I mean 'working' files, not corrupt ones?

Obviously 312 can't open them but if you could clarify the situation for anything created (or saved in) in 330 would be great!

Share this post


Link to post
Share on other sites
2 hours ago, ConnectCreative said:

Out of interest, will be be able to open files I created in 330 in the next beta - by this I mean 'working' files, not corrupt ones?

I'm not in the Affinity Team but I can most certainly say that you will.

Share this post


Link to post
Share on other sites
4 hours ago, Seneca said:

I'm not in the Affinity Team but I can most certainly say that you will.

While the Affinity team has made strong efforts to keep old files compatible with new beta versions, they have reiterated multiple times that this is not guaranteed, and that file compatibility could potentially break between betas.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×