Jump to content
You must now use your email address to sign in [click for more info] ×

Leigh

Staff
  • Posts

    3,203
  • Joined

Posts posted by Leigh

  1. 16 hours ago, Paul Mudditt said:

    In my tests of iPadOS 16 public beta on my M1 iPad Pro, the problem appears to have been fixed in both Photo and Designer, so maybe an obscure OS bug affecting some devices rather than a Serif bug.

    Thanks for letting me know. We've tested this in Tech also and you're correct - will pass the information to our QA team to double check. Thanks again.

  2. On 8/19/2022 at 5:24 PM, RobinMcL said:

    Yes and no! The ultimate, most important, critical issue is that I am trying to make a book that is bound in signatures (just like an ordinary book). Hence, I absolutely MUST have imposition. This, in turn, implies that the spreads MUST be split into separate pages and then imposed into signatures (each signature is, essentially, a "booklet") So YES if I export spreads than I get the correct number of crop marks but, NO, exporting as spreads is of no use to me.

    It would be great to have this bug fixed, and also to have a page range printed as a booklet. In the meantime, I am using a bizarrely complicated workaround. I export pages from Publisher as pdfs with bleed but no crop marks.....

    Thanks for clarification. Unfortunately, the issue logged regarding printing a page range with a book was closed by designed by our developers. Your other issue regarding the crop marks and exporting to pages is most probably also to be expected but I will check with our developers to be sure. If they confirm that it's a bug, I will let you know.

  3. On 8/17/2022 at 3:52 PM, RobinMcL said:

    Dear EmT,

    There might be a question of terminology. I posted comments on further investigations (I made in the middle of the night) yesterday. (I simply could not sleep for worrying about this.)

    What I discovered was that IF I did NOT ask for crop marks, then there was NO extra bleed added. The "terminology" question arises in the following way. My Publisher document uses facing pages to produce a spread. Hence bleed goes round the outside and there is NO bleed in the gutter. Furthermore, and most importantly, there are only FOUR crop marks, one at each corner of the spread. The problem now is, how do I create a book from this? When I came to this stage, originally in PagePlus, I simply could not believe that the software would NOT let me give a range of pages and have it do the imposition to create the appropriate signature. (It's called desktop publishing so why does it stop me doing the actual publishing?!)

    Since my pdf software can do the imposition, it seems reasonable to export the PAGES to a pdf and print from my pdf software, using the crop marks to guide my trimming of the text block. Ahha! What should happen is that, since Publisher knows that my pages are part of a spread (facing pages) it should put TWO crop marks on the Left-Hand side of the LEFT page and TWO crop marks on the Right-Hand side of the right page. But that is NOT what it does. It puts four crops marks on EACH page. WRONG!! Now when these pages are put back together via imposition, there is a big gap between them. Whether one calls this extra bleed or just a big gap is of no concern. The issue is, that gap should not be there.

    If I do not ask for crop marks then this does not happen. So I may have used the wrong word. I was always wanting the bleed AND the crop marks. I have discovered that, if I don't ask for crop marks, I can still get the bleed. This lets me move ahead. I simply have to use some other method for deciding where to trim. This is not a big problem. But why can't I simply give a page range and have that printed as a booklet from Publisher?! I asked that question years ago and was told that Serif had no intention of providing that capability but no explanation of why was given. It is infuriating that I can print the entire document as a booklet but not part of it. I hope this is a clear enough explanation and that you can reproduce it. If not I can easily create a file for you.

    With thanks,

    Robin

    If you export your document to Spreads, does that give what you're looking for? The crops will then appear as you wanted on facing pages, two on the left side of the left page and two on the right of the right page. 

  4. 15 hours ago, Henric said:

    Hello!

    I'v just made some test.

     

    It seems to be document specific. 

    On M1
    x.afphoto works only without metal.
    y.afphoto works with both metal and without metal.

     

    On intel (i7 iMac)
    The same files as above works with and without metal.

     

    Many thanks
    Henric

    Thanks for the additional information. Is it possible to send me the document that crashes the M1 Mac with Metal enabled? If you would like me to provide a Dropbox link, just let me know.

  5. Thanks very much, will pass to QA.

    On 8/9/2022 at 1:46 PM, thomaso said:

    I don't need any .afpub to get fixed but I am interested …
    … what is causing these occasional issues in my two daily .afpubs with only locally save data?
    … how can I prevent the issues?

    Of course  - whatever QA find, we will let you know.

    On 8/9/2022 at 1:46 PM, thomaso said:

    … is there possibly any system report saved on disk which may help to detect the culprit?

    There's nothing in the app we can enable to create a log file but you could enable streaming in Console and use <Any> affinity in the search box to filter messages to anything related to Affinity. Not sure if you'll find any useful but it's worth checking. The other option would be to use a third party app called Sloth to see what Affinity as open in the background: https://sveinbjorn.org/sloth

  6. On 7/19/2022 at 8:02 AM, joe_l said:

    1) Rasterise the image (delete the adjustment before). Does rasterising an image convert it automatically to the document colour space?

    Yes. 

    Just wanted to let you know that we're still investigating. I'm also seeing the same issue when printing to a Canon Inkjet in the office. Changing the Colour Management settlings within the Print dialog made no difference.

  7. 7 minutes ago, Henric said:

    My Affinity Photo also crashes... But not at start up.

    Im able to work for a couple of sec. Then it craches. Last file I was working on was around 2gb. 

    MacBook Pro M1 Max, MacOS 12.5, 64 GB RAM, 1 TB, 32 GC.

    Same .afphoto file works well on my iMac from 2017.

     

    If you could upload a crash report here, that would be helpful.

  8. On 8/1/2022 at 2:23 PM, thomaso said:

    @Leigh, which one do you want? Aside the healthy current file version of "twitter.afpub" I still have two broken versions of it (one of the two .afpubs mentioned in the screenshots above which refused to open):

    879711514_apubcorruptedfilessamples.jpg.b2cd204d2d84e6073f894d19744fd125.jpg

    Since I usually add content only the two broken and larger .afpubs seem to contain data garbage which probably was removed in the current version by a Save As.

    Since the two broken files don't open any more I could not create a package of them but can send them as they are (as .ZIP?).
    Instead or additionally I could send the current, healthy version which contains the same images. (Before packing I'd need to fix some missing image links that I either just moved or, unfortunately, occasionally have renamed after their use in .afpub was done.) – So which of that 3 do you want?

    However, for an upload I'd prefer your dropbox.
    According to the summary I guess the packed size of "twitter.afpub" would be a few hundred MB.

    389734945_apubpackagesamplesummary.jpg.5d312c6dbc1d5a8d87bc6009f2c49f8e.jpg

    Also, I think I could find the other mentioned ("v1105 .afpub") in a backup. Let me know if it would be useful, too.
    (I remember I had tried one then and it didn't open either, so I assume it was a backup of the same .afpub version which didn't open some days later.)

    If you could package up the file that works and its resources, that would be great. Feel free to also upload the corrupted files - might be useful to our QA team.

    https://www.dropbox.com/request/2PCfg2wbwXnOSX178KWu

    Thanks again.

  9. On 7/26/2022 at 10:06 PM, casterle said:

    No, just a regular print to my printer, which is on my LAN if that helps.

    Unfortunately, the crash report doesn't provide much information about from confirming that it's crashing when printing. Does the app crash when going to File > Print or when pressing the Print button within the print window? Do you have any other printers installed? Do you have the latest drivers installed for the printer?

  10. On 7/7/2022 at 5:34 PM, thomaso said:

    This seems to be a rough recipe to replicate the error "Access lost ... while loading … Must close now":
    At least I was able to reproduce it ~ 5x with my test .afpub which grows daily (currently 165 pages).

    With a "large" document (= which creates quite a few temporary data / large .autosave) do some complex changes and save the document. Then closing the document and immediately reopen it (via open recent) appears to cause this issue for me and requires to get reopened one or two more times to avoid the error. Once it opened without this error I can't use this way to trigger it again, unless I worked in it again for some (unspecific) time and tasks.

    Since this .afpub (165 pgs) can be opened and does not cause issues while working in it I assume the error is triggered by a conflict of temporary data which
    a.) need to get deleted (<– closing the .afpub) and
    b.) get created (<– reopening the same file),
    as if this two tasks cross each other in the background. – In every case I see the document / layout as opened + get the missing font warning + get the missing resources dialog before the error occurs, which implies in my view there is no issue with this document at all but rather with get handled "in time" by APub.

    732732754_Apuberrorfailedtoload220706.thumb.jpg.e08df2a07abebdf5b845bca1625e7d5e.jpg

    I've been trying to replicate this on both my macOS and Windows machines but still not getting the issue. I've also tried a few other macOS machines and it's still working as expected. Are you saving locally or a to remote/network drive?

  11. On 7/15/2022 at 11:23 AM, joe_l said:

    Add me to those experiencing the same or similar "problem". CMYK document + RGB image with Selective Colour adjustment = Screen colours ok, Print colours too light. Changing document to RGB = Screen colours too light.

    @joe_l Seems like you have a different issue - please start your own thread and provide as much information as possible and we'll take a further look.

  12. Both Technical Support/QA have been looking into this and we "think" it's likely expected behaviour. I quickly tried to compare the same process in similar apps to see if they gave different results but was unable due to the apps requiring the same colour mode for both the adjustments and document. Have you been able to compare the results to other apps at all?

    The process you're using is very specific and is not something most users will run into. I completely understand your comments about wanting to get a detailed definition on how our functions are implemented and work at a low level but this information is only something our developers can comment on. As you're aware, our developers time is finite and as stated above, this is a specific workflow that most users won't come across, so it may take some time getting the information you require, if possible.

  13. 17 hours ago, vjsouza said:

    I've always found the Affinity Publisher 1.10 splash screen to be a bit gloomy, cluttered with information. And in the center, an image that resembles a DEAD WOMAN in a coffin. More sinister than that, only on a horror movie poster. Please Affinity team CHANGE THIS PICTURE FOR GOD'S SAKE! This appear to be a "Affinity Publisher Addams Family Special Edition"

    Affinity Publisher DEAD WOMAN splash screen.jpg

    Thanks for the feedback and I will be sure to pass it on. It's definitely not a dead person but you've all made your point :)

×
×
  • Create New...

Important Information

Terms of Use | 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.