Here's a bash script I've used that copies all CC activated fonts to a folder on your desktop:

#!/bin/bash
cp -R ~/Library/Application\ Support/Adobe/CoreSync/plugins/livetype/.r/ ~/Desktop/cc_fonts
cd ~/Desktop/cc_fonts/
for x in .*.otf; do mv $x `echo $x | fc-scan $x --format "%{postscriptname}\n" `.otf; done

You'd need to install fontconfig to get the nice file names. 

Let me know how your experience goes with SmartStream. I demoed it a while back and ran into constant lockups trying to do custom javascript.

Still on FusionPro since it does literally everything, even if I have to reformat stuff since not all styling comes across from InDesign. We're still on an old version too, and might have to switch to their subscription service soon.

Quote
Oh really, can you elaborate? Particularly on the 70#T as we run a fair amount in that range, uncoated & coated.

Any waviness in the paper will stop the JPress, in order to save any crashes on the heads. And 70# ends up getting just a bit too wavy to feed through unless you put them in the conditioner/jogger machine for a while. We've had no issues with 80#, and sometimes will just eat the cost of going to 80#. Also in the winter months we can usually get the 70# to run after just letting it sit for a couple hours and hand throwing the paper.

For the dutch cuts, I've been throwing them through Agfa Apogee with the old Preps 5 integration module. Although even that has a limit of 10,000 pages. It's really only an issue for variable documents.

Digging up old threads because I been away for a while.

The JPress is impressive. We've been running the 720 for a couple years now. There's some issues with backing up < 70# text, and > 13.5 mic'd cover stock. And dutch cut cut/stack impositions aren't possible unless you impose before submitting to XMF. But, honestly those are the only negatives I've seen. Consistency, quality, and uptime have been great (much better than iGens and Iridesse). There's some maintenance to do every day you run, but really not much more than offset.

If you have any specific questions let me know.

Also having beach balls on a mac mini running Mojave. It's something network related for sure. 2 other machines on Mojave and they are fine. Besides the standard Adobe / Pitstop stuff, the similar stuff I have to AaronH is I'm also running XMF and have a NAS unit. Can't really not use the NAS, but have you noticed if the beach balls occur when running XMF? I never trust java apps. I'm going to run without it for the week and just use one of the other workstations when needed. Might be a driver issue and XMF/java network access on newer Apple machines.

We were looking at the CRON machines for a bit. They looked really well made. Almost like all the parts were made on the same line as other machines (a china specialty). Pricing was about 40% cheaper than even the steal we got on a new Agfa unit.

Only reason we didn't go with them was service. At the time there was only one place near Chicago that would service it (where we were buying it from). They only had 2 techs on staff, and they were already spread thin with being a 3rd party service provider for Agfa/Kodak/Heidelberg, everything, and also being a reseller. The times previous we used them to service a platesetter they weren't the quickest, but they were competent. We went with Agfa with a service contract because being down for 2-3 days would kill us.

QuoteOh I bet they will. It's an interesting move for Apple. Windows still supports 32bit software in Windows 10. I imagine it's to simplify development though, if you only have to do half of the coding work behind the scenes...

I think it's a large part them prepping a move to ARM processors, which, for Apple are only 64 bit.

Used Mac prices are going to be going up. We had to order a new workstation early just so we wouldn't get stuck with Catalina.

From the demo versions I was able to use, SmartStream seemed the most powerful. XMPie didn't seem to have any actual scripting language support besides their own limited version. With SmartStream I believe you could use javascript, even though it crashed on me quite often.

XMPie you're looking in the mid to high 5 figure range for a desktop and server license. SmartStream I think was a good bit cheaper.

But, both were really limiting, and with SmartStream crashing too often, we passed on both.

While FusionPro has quirks, and requires a little more work upfront on simple jobs. It was hilariously cheaper. $1,000 per workstation. And it doesn't tie up your InDesign while it's running. Plus the scripting is way more flexible.

If SS is working, like DCurry said, just keep using it. It'll output PDFs just fine.

Running Apogee 9 here. Both files render and trap without any warnings. And both render the same way. Page 2 is k only on both files.

XMF also gave no issues at all.

Forgot to mention I believe InDesign scripts can't be called at merge time. So you'll need to merge to a new InDesign document and then run any scripts from there, then export your PDF.

Here's how to do it using grep styles:

https://colecandoo.com/2012/02/18/square-pegs-now-fit-into-round-holes/

Depending on the amount of text you have though, it's going to be a pain. But, that's really the only way I know of without moving to an actual variable data plugin or program.

MacOS 10.15 will likely drop support for 32 bit apps entirely. I know for us that means we won't be able to upgrade any further since our version of Apogee Client is 32 bit. Which also means no more mac workstation upgrades either.

What's going to hold you back?

Edit: Also looks like Curve 3, Fiery, FusionPro, and Preps 7 are gonna hold us back.

If converting from LAB spot to CMYK double check your output profile. As that will cause different cmyk results depending on which one you choose.

Conversion of 286 C:
US Web - C100 M83 Y12 K4
Gracol 06 - C100 M80 Y13 K1
Gracol 13 - C100 M79 Y0 K13

Unless I know I need to match a spot color in process, I always like to honor the application values if a spot has a CMYK definition. Cuz you know, lazy designers will modify values of a color but not rename it.

Not sure if the 2015 is that much different than the late 2013 21.5, but I was able to replace the drive in about 20 minutes. The hardest part was removing the left over adhesive strips before putting the new ones down. I used the OWC kit, and the drive had no special cables needed (my mid 2011 did need a special thermal sensor, but I think they dropped that nonsense when they went slim). It's stupid that Apple went with the adhesive instead of the magnets like on the older models. But it's actually pretty easy to get into.

Really considering going hackintosh for the eventual upgrades around here though. But, Intel's been dragging their heels and the newest processors actually aren't that much faster than what we currently have.