I noticed one thing when updating to InDesign CC 2017..............
The data merge speed is much, much faster than previous. (when exporting to pdf).
Anyone else notice this?
Haven't noticed anything faster CC 2017 but haven't done any data merge since upgrading.
seems normal speed to me, but everything I do is FAST
:rotf:
Is that what your wife would say?
actually, not fast enough.
:lmao:
I hear ya
doesnt actually seem any faster to me, but I dont think I have done any very large merges lately
What did you update from? The only time I noticed a speed increase was when going from Indesign CS6 to Indesign CC as Indesign became a native 64 bit app and could use all your RAM rather then the limited use it had in CS6.
From the CC before 2017 to CC2017. Just one jump.
I noticed it on a very large merge, over 10,000 pages. Seemed to take a half an hour in the previous version, this one only about 5 minutes.
I dunno, was very noticeable to me but if others don't notice it, maybe there's some other reason.
(moon phase, climate changing, who knows).
Ooops, it did it again.
375 page 2 sided merge, one side with a 3 inch 600 dpi logo, the rest text, exported in 30 seconds.
Now I KNOW it would have taked about 4 or 5 minutes before.
It's just lulling you into false sense of security, setting you up for your next acrobat crash.
Quote from: Farabomb on June 08, 2017, 06:15:29 AMIt's just lulling you into false sense of security, setting you up for your next acrobat crash.
Yes, sometimes I feel like Charlie Brown when Lucy pulls the football away when he's trying to do a place kick.
:vomit:
(http://i.imgur.com/YejL7u8.jpg)
I think your right about it being faster now, I had a 10,000 page merge, that took foooreeevvver to make the pdf previously
ooo now i am excited to do my next 10,000 page merge...
actually no I am not, it took over 13 hours to rip at the indigo!
and that was after res-ing it down a little
Oh man!
That reminds me of the Brisque :laugh:
leave a complex job to rip overnight!
yeap, we had one once that took most of a day to rip, as in something like 22 hours... it was crazy and we couldnt send any new work to the rip while it was doing that (could still print any jobs already there though).
and for some reason they cant cancel a job while it is in the queue... seems odd to me but that is what the operator (boss man) tells me.
So if i accidentally send a variable data job into the queue, then we are stuck till it rips