• thatsnothowyoudoit@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    How so? Genuinely curious what’s missing as someone who tried it on a job, and loved it.

    I just sent a job to print yesterday and the printer didn’t bat an eye.

    Are we talking specific types of printing? Like booklets or runs with specific imposition needs or something else?

    I think ultimately it will depend on what one needs printed. It would easily meet most common printing requirements as far as I can tell.

    • MrSebSin@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      You guessed it with booklets or anything long format really.

      As a 20+ year Adobe user, I tried switching about a year ago. Seems like the only way to give it proper go, was to dive in head first and force myself to exclusively use Affinity. Of course there’s a bit of a (frustrating) learning curve but overall it went pretty smooth. I genuinely thought I was going to make it work.

      That was until I had to setup a 40 page catalog. Ran into various minor issues, but not insurmountable. IIRC the main issue that ultimately made me go back to InDesign was the handling of support assets and glitches as the catalog got more “heavy” with stuff.

      I think I would have stuck with Affinity if I could go back and forth between Publisher/InDesign, but I couldn’t take what I started with and finish in the other app.

      • thatsnothowyoudoit@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 months ago

        Thanks for the reply. Makes sense. I haven’t had any jobs recently that would push us there.

        CC is also priced low enough we can sign back up for a month if we need it.

        One feature set of CC I’ll miss is the libraries functionality working across all the apps. Someone on the team needs a client asset in any app ? (AE/ID/PS/AI) There it is.