Jump to content

Lagarto

Members
  • Content Count

    1,012
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This might perhaps explain the problem: You have many lnked CMYK files the file size of which is huge, e.g. here 4400p x 3400px original from which you only used a small-size version in the layout. The default for PDF (for Export) setting is that it does NOT downsample oversized images. This might have worked in previous versions so that if files are linked, they have been resampled despite of this setting, but now they are embedded with full size in the export file, if not downsampled. Please try if forcing downsampling in your export, as in the screenshot below (you can access the settings by clicking the More button in the Export dialog box), resolves the problem: I know that there were changes in 1.8.0 in the way embedded and linked files are handled, but do not know the details, yet. But this could be one of the changes. UPDATE: Yes, this seems to be the reason for the problem. I just created mini-sized version of the 4-photo CMYK file that in full size took 20MB, now the produced PDF was a huge 63MB file. But when I downsampled with the above default setting (and produced at 300 dpi resolution), the file size dropped to 1.5MB. I'll check how this worked in previous version, but I bet that differently! It is a complete mystery how stamp size versions of photos result in over 40MB bigger export file than when used in full A4 page size. This must be a bug... UPDATE2: Tested now the same file where large CMYK photos are in stamp size (to produce very higt effective PPI; or "Placed DPI" as the term is in Affinity Resource Manager) and exported it with the default "(for Export)" PDF settings using previous release version 1.7.3, and the resulting file size was slightly above 10MB, so over six times smaller than the file produced by version 1.8.0. I can see the point of including linked files in settings that are meant "for export", but there must be something wrong with the algorithm that causes increase of the file size by over 600% just because the placed size is minimal! Anyway, what seems to have happened is that the original CMYK TIFFs have been included unpacked, as their sizes were 26MB and 30MB. Why this does not happen when the same images are in full A4 placed sizes, does not make sense. At A4 size the placed PPI of these images is about 300 which does not trigger "downsampling", but in miniature size the effective ppi is about 2500, which naturally triggers downsampling. Now if downsampling is "OFF", full size original TIFFs seem to be packed in (>60MB size); if the setting is "ON", they will be downsampled at 300ppi at their placed sized (1.5MB at stamp size). If the effective PPI is less than 375ppi (default), it seems JPG compressed resampled images ae produced at placed sizes (>20MB at A4 sizes).
  2. Do you need to to supply the graphics as vector art, or could it be a highres monochrome bitmap (either with hard edges or a gray scale)? If the latter you could perhaps convert your vector art to bitmap and then remove the solid black part (to be "painted" by the fabric) and provide just the color part? But it is of course quite a cumbersome workaround...
  3. I use regex in InDesign with a script that marks hyphenations (hyphens at line endings) between vocals, as this is considered bad hyphenation in Finnish language. But the rule cannot be applied mechanically, as it is perfectly fine to add a hyphen between compound words the first part of which ends in a vocal and the second part (divided onto the next line) starts with one. Also, sometimes hyphenation just cannot be avoided, or the problem needs to be resolved in another way (manually rehyphenating the entire paragraph etc.) so these kinds of things simply need to be gone through manually to do the job properly. But the point is that regular expression that at least could highlight the problematic parts or spotting them one by one, would be highly useful. EDIT: Just checked the script and it is a complex combination of regular expressions and InDesign object model code where the latter is crucial as that is the only way to iterate through the lines of each story of the publication and examine first and last characters of a line -- the text itself probably does not contain anything (a control code etc.) that indicates wrapping and that could be searched. I am not sure if that kind of feature could be implemented, though, as an app-specific extension?
  4. I ran a second test with the default PDF export settings but using 144dpi resolution instead of the default ("Document DPI", in this case 300dpi), and the difference between the 1,7.3 and 1.8.0 is similar as with the 300dpi version (revised): 4.478MB vs.6.157MB so the difference is not that big. So false alarm, this cannot explain the huge increase in the file size you have experienced. After having a second look on the missing CMYK files in your document, they are mainly just small files, so they should not dramatically increase the file size even if they were embedded. Having full size CMYK photos, however, would make a difference since already 4 photos (of which only 2 were different) produced a 20Mb file size.
  5. I just tested this again with large CMYK photos (they are those that are missing from the file) and can confirm that there is a dramatic change. With version 1.7.3 release the file size of the PDF produced with the default PDF Export settings was 3.6MB, but with version 1.8.0 it is 20.6MB. It seems that CMYK TIFFs are not compressed at all??? UPDATE: I ran the test again, and the settings were not identical. The old version produced 14.1MB file of the same content that version 1.8.0 produced the 20.6.MB so the difference is not that dramatic, after all. There was recently a thread where Affinity apps' default for using JPG compressing files at quality setting 85 for print files and export was questioned, as e.g. Adobe apps use "Maximum quality Automatic JPG" compression setting by default in similar circumstances, minimising loss of quality but yet achieving remarkable compression rate. I just tested this with the document mentioned above (that produced 20.6MB file size with version 1.8.0) with InDesign, and the CMYK version at "Maximum JPG" compression with 300dpi output downsampling to 300ppi for images above 450ppi produced a 9MB file in CMYK mode so roughly the half of the size that 1.8.0. does. Affinity does not use by default downsampling for large files, but for this particular document the setting does not have any effect as the files are not that big so using the downsampling setting with Affinity export did not have any effect on the file size.
  6. I compared the PDF (Export) settings with version 1.7.3 but did not notice changes. This PDF preset uses by default document DPI but it can be overridden. I ran this with default settings (at 300dpi) but using image downsampling for images with more than 300dpi (there are many), and the resulting file had the size of 45MB. Low-quality screen PDF - digital (small size) uses 85 JPG compression at 72dpi and the resulting file had the size of 3 659KB, so based on this I'd say this file compresses pretty much as expected. These files were produced on Windows version but @Fixx produced similar sized files on macOS so there should be no difference. Perhaps something just went wrong with the export, or perhaps there are recent 16-bit RGB images amongst the missing files, as they are known to increase dramatically file sizes of exported PDFs.
  7. Can you provide original art (just the leaves), or at least the PDF, and information on the way it was produced (which PDF export settings were used). It would be interesting to know what causes this behavior. You seem to have applied the gradient using an FX but which blend mod?. I tried with a couple of different settings but could not reproduce the problem.
  8. Borderless printing is not available for A6 paper size when using this printer: Borderless Paper Sizes • 4 × 6 inches (102 × 152 mm) • 5 × 7 inches (127 × 178 mm) • 8 × 10 inches (203 × 254 mm) • Letter (8.5 × 11 inches [216 × 279 mm]) • A4 (8.3 × 11.7 inches [210 × 297 mm]) https://files.support.epson.com/docid/cpd5/cpd54003.pdf (That is, the driver does not support this, and therefore not the apps, either.) As it seems you need to print multiple copies (with different names), you could try using Affinity Designer's N-Up printing feature and print four A6 size pages borderless on an A4 sheet paper and then cut them in half twice: Note how the red frame marking printable page border is not inset because the borderless printing for A4 sheet size is checked in the printer driver (accessed by clicking Properties button). This method would also allow you to print double-sided invitation cards as long as the artboards are correctly arranged.
  9. Please also check that the initial cause for K100 definitions becoming rich black is not in document color mode being RGB or Grayscale rather than CMYK. In the former case the Black well shown above by @thomaso (similarly as "Black" of the Grays palette) will be RGB 0,0,0 and in the latter G0, which will both be converted to rich black when you export to print PDF with any of the standard print profiles. What is more confusing is that if the document color mode is anything other than CMYK/8, even explicit K100 definitions will be converted to rich black when using most of the PDF export methods intended for creation of a PDF for commercial press (there are certain exceptions where CMYK definitions will be retained in an RGB color mode document when exporting to CMYK PDF, e.g. when using PDF/X-1a, but most profiles cause rich black generation unless using modified settings. The correct method to produce a document for press is using CMYK/8 document color mode and the recommended color profile right from the start of the project, and then use CMYK (and PANTONE) color definitions. If a grayscale mode is used, the document must be exported with custom settings that do not force CMYK conversion. A document color mode can be changed but this often results in need to reassign colors or make manual adjustments. Document color profile can also be changed, either by assignment or conversion, the latter of which causes all color definitions to be changed and swatch assignments becoming broken. There might also be point in reimporting image file after such change to avoid inadvertent export time conversions.
  10. Here is a Publisher document showing cross fading of superimposed photos using the Transparency Tool which is applied on "Image" objects (= bitmaps with a vector wrapper) so that gradient transparencies become an editable property of image objects. Transparency Tool is available also in Designer but if this document is opened in Photo, the technique seems to be hidden so the gradients cannot be accessed there. crossfading.afpub
  11. The rendering option could perhaps be grayed out unless pixel dimension is changed from the original -- that would make it clear that the image is just saved as it is (no pixels modified).
  12. Thanks, looks good, and it is great that Affinity can directly by pasting SVG code render it as graphic! The problem with equations in curve mode is that color of each element (outlines and fills) needs to be redefined to K100 (if the publication is to be produced for press) and sometimes the objects cannot be easily selected. Consistency in size may also be hard to control. I do not personally produce scientific texts but rather create pubications containing them so my primary interest is in print production of already finished text (with equations as inline objects embedded in the original text) so therefore my focus was in equation editors of apps like Word and LibreOffice Writer and the methods of getting the equations reliably in different page layout apps. Many writers who produce scientific texts are fluent with LaTeX so the original text might be plain text requiring rendering with apps like TeXmaker + TeXstudio, but for print production this is bit heavy workflow (and LaTeX typically not directly importable in page layout apps), so Word and LibreOffice, both supporting LaTeX expressions -- the latter with a plugin), is often used, instead. Online equation editors, however, would be very useful when producing scientific presentation directly with a publication app like Affinity Publisher.
  13. If you change your color profile from within FIle > Document Setup (even if you keep the same color mode), all your color values will change, incuding K100. This happens both in 1.7.3 and 1.8.0 release version (Publisher / Designer). I think you also lose all swatch assignments (the links get broken). EDIT: (Assuming that your change mode is "Convert" and not "Assign"; if you just "Assign", there are no changes in color values) The K100 values will probably convert to one and same four-color black. You should be able to find replace and return K100 values for the text this way. But as for graphic objects, I guess it is a manual job.
  14. I have continued a bit my explorations with equations, and here is a kind of a summary of what I have found. My interest is in font or vector format inclusion of equations, ability to have the equations defined in K100, and ability to use them effectively inline. Microsoft Word equation editor (Office Math) is powerful equation editor and can produce equations in many different ways, including writing them as LaTeX expressions. Ways to get Word equations in publications as inline elements (as a contrast to more cumbersome and non-editable, limited quality image embedding solutions): 1) Export from Word as PDF a) Embed (passthrough), e.g. InDesign, QXP [Problem: how to convert RGB black to K100; needs to be cropped) b) Convert to curves, e.g. Acrobat Pro, Ghostscript, CorelDRAW, save as EPS or PDF and then import to Affinity apps c) Open embedded font, e.g. Xara Designer Pro Affinity apps: PDF with fonts embedded not directly available (fonts messed up if opened), so need other apps so that can be opened as curves; also works on macOS NOTE: None of the apps I have tested can open PDF for editing while mapping the fonts used by the document to installed highly complex Cambria Math font (I tested Illustrator, CorelDRaW, and QuarkXPress). Xara however can use the embedded font (but with restrictions). 2) Copy paste from Word (as Enhanced Windows Metafile): a) Affinity (fully editable as Cambria Math font) (Windows only) Easy to convert to K100, and adjustments like bad tracking can easily be fixed. 3) Use MathType and convert Word equations to EPS or WMF a) InDesign, QXP (EPS, already K100); the most effective and professional method of including equations in publicsyiond b) Affinity (WMF -- Windows only; fonts Times New Roman and Symbol editable; needs K conversion; EPS versions do not work) NOTE: MathType is not compatible with macOS Catalina (but works fine with previous versions) A free alternative to Word is LibreOffice, which also has a very powerful equation editor, and here are methods of getting LibreOffice equations in Affinity apps (Publisher used as an example): 1) Export from LibreOffice Writer as PDF: a) Embed (passthrough), e.g. InDesign, QXP [Problem: how to convert RGB black to K100; needs to be cropped) b) Place and extract (Affinity; works if LibreOffice installed), fonts editable, easy to convert to K100 c) Convert to curves, e.g. Acrobat Pro, Ghostscript, CorelDRAW, save as EPS or PDF and then import to Affinity apps d) Open with embedded font, e.g. Xara Designer Pro This workflow works also on macOS 2) Copy paste from Word (as Enhanced Windows Metafile): a) Affinity (fully editable as Liberation Serif and OpenSymbol fonts) (Windows only; on macOS equations get pasted as images) Editable and easy to convert to K100. Here is an Affinity Publisher file using most of these options, which should be useful if you are going to use Publisher with scientific publications (if you are using Designer, the pages can be changed by using the spread navigation control on the bottom left corner of the app): Equations_Demo.afpub Here is a print PDF version of the same document: Equations_Demo.pdf
  15. Yes, it seems so. I also experienced strange things like when using a bit different size (I deleted some knobs more or less randomly, e.g.) then different knobs (e.g. 1st and 3rd) would have the exceptional shadows. Transparent background however does not seem to have any effect on this anomaly, so it is not specfically related to just export of PNG and TIFF with a transparent background (as I have verified the error also when the document bacgkround is not transparent).
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.