- #Suitcase fusion 4 fonts immediately deactivate update#
- #Suitcase fusion 4 fonts immediately deactivate pro#
#Suitcase fusion 4 fonts immediately deactivate update#
Our issue is further compounded by the fact that we elected to update all of the Adobe Applications on each machine based on issues with InCopy and InDesign that adobe have repaired in the Updates. We'd like to have control over our workflow, or at least be able to cutomise it to ensure our business can stay profitable, and that our workflow does not get messed up. But not instead of our other applications, which are already in place. We had assumed that the plugin's installed in FontExplorer dealt with this communication process?
#Suitcase fusion 4 fonts immediately deactivate pro#
We have all of the items " off" inside our CC desktop App preferences, but this does not seem to turn Typekit OFF! The third (possibly not final) issue here is that this now causes a conflict with FontExplorer X Pro on out client machines, where it does not seem to recieve the request to activate before Typekit kicks in, so our fonts do not seem to autoactive smoothly anymore.
The second issue for us it that we then get Typekit (or Creative Cloud Dektop App on behalf od Typekit - not sure of the correct term here) popping up on our screen asking us what we want to do with activating the fonts. The first issue here is, we have our default font manager set as FontExplorer, so we're unsure why Typekit even gets involved in this at all. With the recent updates to CC apps (inc the CC desktop app itself) we're now having Adobe typekit intruding on our auto activation of fonts when requests come in from InDesign and/or InCopy (this is also beginning to occur with other Adobe apps also, but we've not been monitoring that as much yet). We're a reasonable tech competent creative agency, so are cautious with our 'updates' of all products etc. We have an Adobe teams account, and manage our CC users from there, and also use the CC packager to keep all applications in sync from our server. We have invested significantly in font licenses/libraries and are therefore staying with this process for the forseeable future. The product works smoothly, efficiently and effectively, allowing for comprehensive font managment for our projects (across, print, film, and web). We use FontExplorer X Server to manage our fonts across the studio, and Font Explorer X Pro on all client machines (all Apple machines). We have a studio of 10 machines (+ server).
(Aplogies up front for this post being reasonably long, but I'm feeling like I should give as much info as possible). If it was a feature that we could 'use or not use' at will, that'd be great, but at this stage we do not seem to be able to 'not use' it at all. I deal with most of the workflow in the studio, and am finding this increadibly frustrating!!! Not wanting to add fuel to any fire here, however we're having this issue (or very similar) and it is creating for some very painful workflow problems in our studio.
0 kommentar(er)
