-
Posts
912 -
Joined
-
Last visited
Reputation Activity
-
Jens Krebs got a reaction from Ideagonal in Copy and Paste of pinning settings
When copying and pasting a pinned object, the pinning settings are not copied and pasted, but Publisher applies the last pinning settings that were used. Would be nice is objects were copied and pasted "as is".
Sample:
- insert pinned object (1) into text, set it to "align LEFT"
- insert second pinned object (2), set it to "align RIGHT"
- now copy and paste object (1)
- result: the pasted object (1) is aligned RIGHT even though the copied object was aligned LEFT
- when pasting from the clipboard, Publisher uses the current settings from the ,pinning' panel instead of copying the objects settings.
-
Jens Krebs got a reaction from Petr Bajer in Turn off spellchecker?
It's in the TEXT menu, there's a submenu called "Spelling". Turn off "Check spelling while typing" — made me slightly mad as well.
-
Jens Krebs reacted to thomaso in Global Symbols? A.K.A. Symbols shared between documents?
Why embedded, not linked? I guess if you embed the file then it doesn't update if its original file changes, because embedded = not linked.
And what did you actually understand / misunderstand when you replied to @Jens Krebs's initial hint of linked documents?
-
Jens Krebs reacted to R C-R in Global Symbols? A.K.A. Symbols shared between documents?
To me, this sounds just like linked files, except possibly for the "stored globally" part. If by that you mean somewhere on a cloud server, I think that would be problematic for several reasons, including accessibility issues & privacy/security concerns.
-
Jens Krebs reacted to thomaso in Global Symbols? A.K.A. Symbols shared between documents?
What do you mean with "additional steps"? – To make a symbol globally available you would need to give it a unic name and choose a file path. To avoid choosing a file path they either would be stored all at one predefined place (e.g. Affinity user library folder) or you create a link in your file system which is available on 1-click.
In what aspect do linked document's differ, especially since it seems to make you avoiding this way of both globally available and auto-updated Affinity design work?
If I create a symbol in AD, save it as .afdesign, place that in APub, I can edit the symbol via a double-click (its .afdesign opens in APub), change and save it. Apub informs me in the .afpub which is using this symbol about my symbol's original being auto-updated:
-
Jens Krebs reacted to AdamW in Affinity Publisher Customer Beta - 1.10.0.1085
Status: Beta
Purpose: Fixes / Improvements
Requirements: Purchased Affinity Publisher
Mac App Store: Not Submitted
Download: Download
Auto-update: Not Available
---
We are pleased to announce that Affinity Publisher Customer Beta 1.10.0.1085 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
Due to current and anticipated changes to help with performance issues this version is now 1.10.0 and replaces the previous 1.9.4 beta. All previous changes from 1.9.4 have been rolled into this beta.
As such, we strongly recommend that you do not use this beta for real work as data could be lost and the files you save are not guaranteed to open in previous / future versions of Affinity Designer.
---
Fixes and Updates
Text
- Added Emoji support
Import / Export
- IDML Import - fixes for specific documents
- IDML Import - improved text style grouping and added import of keyboard shortcuts
- SVG Import - Parser improvements for whitespace handling
- SVG Export - Fix for export of stretched text when transforms are flattened
- RTF Import - Fixed specific crash if line breaks occurred in the vicinity of ligatures
- RTF Export - improved support for Unicode characters above 64k
- RTF Export - wasn't closing small caps correctly
Resources
- Improved performance of Resource Manager for documents containing of placed documents
- Placing an embedded document was incorrectly favouring any currently placed instance over the source file
- EPS files can now be 'Made Linked' in Resource Manager if the original source file is present
---
To be notified about all future Mac beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread
-
Jens Krebs reacted to garrettm30 in Affinity Publisher Customer Beta - 1.10.0.1085
Now we finally know: 1.10 before (and possible others) before 2.0
But since you have not released 1.9.4, you have put us in a bit of a bind here. Remember that your recommendation for the 1.9.4 betas was this:
I have followed that advice, particularly as 1.9.4.1076 "Fixed issue with Paragraph Minimum letter spacing." That fix is fairly major in that it causes reflow. Therefore, I have been using 1.9.4 betas to use that fix so my documents will not reflow once 1.9.4 would be released. But now there is no 1.9.4, and the current recommendation is
That leaves us stuck, with no recommended version for fixing the text reflow. In order to open my existing "real work" documents that were made using the 1.9.4 betas "in preference to the store version," as advised, I only have these options: 1) open in 1.9.3 release where layout will reflow due to the unfixed bug, 2) use this new beta for real work despite your strong recommendation not to, or 3) use the last 1.9.4 beta exclusively and sit out the 1.10 beta process entirely until release. Option 3 seems the only reasonable choice to me.
I beg you to consider locking down 1.9.4 and releasing before moving on.
-
Jens Krebs reacted to Andy Somerfield in Affinity Photo Customer Beta (1.10.0.244)
Status: Beta
Purpose: Features, improvements and fixes.
Requirements: Purchased Affinity Photo
Mac App Store: Not submitted
Download ZIP: Download
Auto-update: Available
Hello,
We are pleased to announce the immediate availability of the first build of Affinity Photo 1.10.0 for macOS.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
The changes in the 1.9.4 betas have been rolled into 1.10.
Affinity Photo Team
Changes Since Previous Beta
- Added support for emoji 😃👌😻.
- Added the ability to load ACM lens profiles.
- Assorted improvements to astro stacking, including the ability to edit the names of stacked images and the ability to stack images for different filters simultaneously.
- Fixed issues opening some DNG files.
- Assorted other small fixes.
- Localisation improvements.
- Help improvements.
Changes Since 1.9.3
- Serif Labs RAW engine improvements.
- Assorted astro stacking improvements and fixes.
- Fixed Nikon D780 Raw loading when using Serif Labs engine.
- Attempted fix for occasional flickering of rendered document.
- Fixed crash when deleting a procedural texture constant while the cursor is still in the description text field.
- Fixed erratic behaviour with placed images.
- Fixed missing controls when procedural texture dialog is in non-English.
- Fixed crash when macro recording selected layer change in Japanese UI.
- Fixed lockups when loading certain PSD documents with smart objects enabled.
- Added the ability to open FITS files directly, with control over demosaicing.
- Performance and memory usage improvements when using placed images.
- Performance and memory usage improvements when using embedded documents.
- PDF import and export improvements.
- Significant performance improvements in low memory situations.
- Fixed small visual issues when switching back to templates from presets in the new document panel.
- Fixed gradient map adjustment rendering issues.
- Fixed expression input issues with decimal separators other than ".".
- Fixed issue whereby ISO speed was incorrectly reported for some images.
- Help improvements.
- Added support for Xtrans sensor images in astro stacking.
- Added GPU acceleration for blending ranges (in Advanced Blending).
- Further, significant, performance improvements for documents with many layers.
- Significant performance improvements when converting documents between ICC profiles / pixel formats.
- Fixed performance issues with previous build with certain GPUs.
- Fixed spare channel / mask editing.
- Assorted metadata panel tweaks.
- Further panorama stitching performance tweaks.
- Added a new "median" mode to the frequency separation filter.
- The gradient map adjustment now has a GPU implementation.
- Restored the GPU rendering improvements which were dropped towards the end of the 1.9.2 beta. The benchmark version is once again set to 1920.
- Improve performance when manipulating the selected layer immediately after loading a document.
- Significant performance improvements in low-memory situations, reducing use of the swap file.
- Panorama stitching performance improvements.
- Significant performance improvements for documents which contain flattened, opaque layers (usually the result of merge visible).
- Render EXIF exposure time as decimal if above 1.
- Fixed F-number always showing as "f/0" for Leica M-series cameras (and others).
- Fixed issue whereby LUTs would incorrectly report "Identity" as the description.
- Fixed potential crash when quitting with layers still on the clipboard.
- Fixed performance issues with CMYK documents when GPU acceleration is enabled.
- Assorted small fixes.
- Localisation improvements.
-
Jens Krebs reacted to GarryP in Could the image used for the data merge function of Publisher on the website be a little more ‘appropriate’?
I wasn’t sure where to put this thread so please move it to a more appropriate place if necessary.
I have two very minor issues with the image used for the data merge functionality:
1. The changes between the samples are very difficult to spot – one digit difference in number under vertical barcode, one digit difference in number to the left of the horizontal barcode, and one digit difference in the vertical barcode number (red ‘circles’ in my attached image).
2. It includes barcodes, which might lead some people to think that Publisher can create barcodes, which it can’t (by itself).
Would it be better to use an image which shows easy-to-spot differences, maybe conference name/photo badges or something like that?
Not a major problem but something which I think could be improved.
-
Jens Krebs got a reaction from garrettm30 in 1 bit TIFF/Bitmap support please
Firstly, even though this workflow works, it is incredibly tedious and requires another software — working professionally I don‘t have the time and my customers don‘t want to spend the money wasting my time like this when I could just use InDesign, import the original file and recolour it with a single mouse click.
Also, you need to consider that the sample above is an artwork and since vectorising is never 100% accurate by doing so you change the artists vision in many subtle ways that may change the aura / impact / energy / personality of the image — an absolute no-go!
There are workflows that require 1 Bit images for one reason or another and fact is, that all three Affinity products are currently not suitable when you need to work with this kind of images.
I think it is important to raise and push the issue with 1 Bit images once in a while and talk bout it, hoping the developers implement it at some point, but ‚alternative workflows‘ are just not feasible in many cases and currently the situation simply is that you have to use another software if you need to work with 1 bit images — and for me that is absolutely fine; I like the Affinity apps very much, but in cases where my favourite tool doesn‘t work, I use a different one.
-
Jens Krebs reacted to AdamW in Affinity Publisher Customer Beta - 1.9.4.1082
Status: Beta
Purpose: Fixes / Improvements
Requirements: Purchased Affinity Publisher
Mac App Store: Not Submitted
Download: Download
Auto-update: Available
---
We are pleased to announce that Affinity Publisher Customer Beta 1.9.4.1082 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update from the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
---
This beta has a performance focus. We have addressed a number of issues particularly with the handling of placed images and documents. If you notice performance improvements (or regressions!) over 1.9.3, or if you notice bugs which appear to have been introduced in 1.9.4, please let us know.
Fixes and Updates
Resource Manager Improvements New 'Relink' option for missing resources New 'File Type' column in Resource Manager Improved efficiency when updating Resources for some documents Show progress for long operations Improved memory management for placed PDFs set to Passthrough Improved output of placed PDFs set to Passthrough to targets not supporting Passthrough Artboard Labels could disappear Fixed some issues with Picture Frame content scaling ---
To be notified about all future Mac beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread
-
Jens Krebs got a reaction from GryphonArt in Smaller PDF Files, please!
Answer found, but not a solution
I played around with the two files I uploaded above and discovered that Publisher ALWAYS (independent of the PDF settings) creates curved text when using some particular fonts ... when I switch the entire publication to Arial, the file size (including embedded fonts!) shrinks down to 0,3 MB.
So, the answer is, that Publisher apparently cannot embed all fonts (InDesign, Quark and all other DTP applications I have used throughout my career do) which, unfortunately makes it unusable for me -- it is an absolute dealbreaker not being able to provide my customers with files that come at a reasonable size for downloads / web publishing.
What I don't understand is, that the early beta versions DID embed fonts (see old file 1-2019 above), so the feature must have been removed or deactivated somewhere between the first betas and release.
Can someone from Serif explain, what happened, please?
-
Jens Krebs got a reaction from PaoloT in Smaller PDF Files, please!
OK, not sure if someone is still reading this, but I made a little experiment:
I created a publication in InDesign and exported it with my ,usual' print settings (crop marks, 300dpi, CMYK colour profile ...). The file size of this export is 75MB.
Next I opened this PDF file in Affinity Publisher and exported it wit the same settings – resulting in a PDF of 408(!) MB.
Considering that there was only 75MB of source material and all fonts are installed on my computer, this is quite strange.
Happy to supply both files (original InDesign PDF and the new one) to Serif, if they are willing to investigate.
-
Jens Krebs got a reaction from PaoloT in Smaller PDF Files, please!
Thanks Ash, thanks Alan,
I have played around with the settings (reduced the JPG quality down to 70, set the downsample boundary to everything above 72dpi and tried to export with and without layers), but this particular file I am experimenting with is always at least 13 MB (the print file is 140, but that doesn't matter).
When i did exactly the same publication (we are talking about the same amount of text, same fonts, same amount of images, same page count, same layout) in InDesign (and a test in Quark XPress before I decided to wait for Publisher) during the last couple of years the print files were about 15 MB and the web files somewhere around 1 MB with similar export settings as in Publisher.
I'm going to try some of the PDF reducing apps, but my point stays that Publishers PDF files are significantly larger than Adobes and the ones form Quark XPress and with the images being of the same size and quality (the 15MB and 140MB print files have exactly the same resolution and print settins), the issue has to lie somewhere else.
-
Jens Krebs got a reaction from GryphonArt in Smaller PDF Files, please!
I really like the PDF export and am fine with the speed and everything, but the file sizes are SO MUCH BIGGER than from the competition, that it starts hindering my workflow.
I don't mind the size of a high-res print file, but there should definitely be a setting equal to other applications "smallest file size" -- many of my customers want to have their publications online for download on their website and large files are just really inconvenient. I have tried setting the image resolution and JPG quality down, subsetted fonts and restricted the Acrobat version to 8 (my normal tricks to save a couple bytes), but the files are still monstrous compared to ,other software'.
What exactly is blowing up the file size? Maybe I'm just missing a setting?
-
Jens Krebs reacted to MattP in Affinity Designer Customer Beta (1.9.4.2)
Status: Beta
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not Submitted
Download: Download
Auto-update: Not available
Hello,
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
Thanks again for your continued support!
Many thanks!
Matt
Changes This Time
- Fix for non-UK locales... sorry...
- Fix for Trotec Job Control incompatibility
Changes Since 1.9.3
- Potentially huge performance improvements for large documents. We've spent a long time looking at this and have improved performance many-fold for large documents and improved scalability. If you have particular documents that still appear 'too slow' then feel free to share them with me and I'll do my best to look into them
- Memory handling improvements
- Fixed PDF Export group opacity potentially being applied twice
- Fixed potential crash when quitting with layers still on the clipboard
- Localisation improvements
-
Jens Krebs reacted to MattP in Affinity Designer Customer Beta (1.9.4.1)
Status: Beta
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not Submitted
Download: Download
Auto-update: Not available
Hello,
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.9.3 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
Thanks again for your continued support!
Many thanks!
Matt
Changes This Time
- Potentially huge performance improvements for large documents. We've spent a long time looking at this and have improved performance many-fold for large documents and improved scalability. If you have particular documents that still appear 'too slow' then feel free to share them with me and I'll do my best to look into them
- Memory handling improvements
- Fixed PDF Export group opacity potentially being applied twice
- Fixed potential crash when quitting with layers still on the clipboard
- Localisation improvements
-
Jens Krebs got a reaction from GryphonArt in Smaller PDF Files, please!
Fonts unfortunately still ARE the issue, and especially converting them to curves increases the file size significantly for me (my projects tend to have a lot of text). The problem I am reporting here is that even if I specifically select to embed fonts, the text is converted to curves anyway.
I have resolved to printing and then saving as PDF for this project but cannot use AP for anything until this is fixed. I need high-res print files with crop marks and low res web files without, embedded fonts and reasonable file sizes for both and don't have time or patience (nor have my customers) to fiddle around with workarounds, experiments or helper tools.
-
Jens Krebs got a reaction from g333 in Smaller PDF Files, please!
OK, not sure if someone is still reading this, but I made a little experiment:
I created a publication in InDesign and exported it with my ,usual' print settings (crop marks, 300dpi, CMYK colour profile ...). The file size of this export is 75MB.
Next I opened this PDF file in Affinity Publisher and exported it wit the same settings – resulting in a PDF of 408(!) MB.
Considering that there was only 75MB of source material and all fonts are installed on my computer, this is quite strange.
Happy to supply both files (original InDesign PDF and the new one) to Serif, if they are willing to investigate.
-
Jens Krebs got a reaction from Petar Petrenko in Why no Bitmap mode?
Even though many user asked for it and explained in detail the many uses of 1-bit images, the developers made it very clear that there are no plans whatsoever to implement it (search the forums, there's many topics on this).
They might or might not change their minds in the future, but currently the answer has to be: No, there isn't -- If your work or workflow requires 1-bit images, Affinity is not for you!
Take a peek at "PhotoLine" -- great software, super fair price!!!
-
Jens Krebs reacted to MEB in 3 page spread
Hi Lukas_Klenk,
Welcome to Affinity Forums
Currently Affinity doesn't support spreads with more than two pages nor is it planned for the first version. Please check this post (and thread) for more information.
-
Jens Krebs reacted to Peter Werner in 3 page spread
I can think of the following two workarounds:
Create separate artboards in Designer and then place those as linked or embedded files on a single all-encompassing page (Publisher) or dartboard (Designer). That way you can export the whole thing, but you also have the ability to export every artboard as a separate PDF. The disadvantage is that you have two separate files to deal with (though you can at least open both in either application) Have 3 individual artboards next to each other and one overlapping artboard that encompasses the other 3. -
Jens Krebs got a reaction from frindley in 3 page spread
You can create a slice that spans your three (or more) artboards in Export Persona of Designer and export as one PDF.
-
Jens Krebs got a reaction from Jenna Appleseed in Publisher Persona?
I guess that Designer and Photo are being so tightly integrated, that they don't actually START the other applications but simply switch to the tools and allow you to work on objects in you Publisher file as if you were using Designer and Photo (literally being in there as personas) ... so, you would use the Publisher persona button to switch back to the Publisher persona after editing your image or vector graphic.
-
Jens Krebs reacted to MattP in Affinity Designer Customer Beta (1.9.2.4)
Status: Release Candidate
Purpose: Features, Improvements, Fixes
Requirements: Purchased Affinity Designer
Mac App Store: Submitted
Download: Download
Auto-update: Not available
Hello,
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.9.1 version recently released to all customers (although it still installs parallel to the released version, as described above). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
Thanks again for your continued support!
Many thanks!
Matt
Changes This Time
- A few fixes for opening documents which contain embedded documents.
- Fix for dragging an asset which contains an artboard into the document.
- Fix for exporting large images occasionally failing.
- OpenAsset fixes.
Changes Since 1.9.1
- Fix for insta-crash encountered in the Vector Brush tool on 'Undo' action.
- Fix for inability to create a new Object Style if the only difference was a property of the stroke.
- Added support for OpenType reverse chaining contextual single substitutions.
- Significant performance improvements for assets (import, export, organisation, etc.).
- Unsplash stock panel functional again.
- Typography panel performance improvements.
- Help improvements.
- Localisation improvements.
- Fix for Assets and Symbols transforming greatly when dragged onto resized artboards.
- Small fixes for occasional misbehaviour of placed PDFs.
- Fix for OpenAsset issues.
- Misc fixes for My Account feature and content downloads.
- Hopefully fixed an occasional problem with the New Document dialog not showing content after tabbing away to another app and back again.
- Renamed the export area options to something more friendly (on the Export dialog).
- Misc visual fixes for menu items that were not the correct (app) colour scheme.
