"Font Capture.exe" won't unload when AA2 is closed

Nearly every time we work with AA2, when you close the program (or it crashes etc) I see
a little window advising something called "Font Capture.exe" is waiting to close, and then
it does not close and you have to force it to using "end now".

Offhand I'm not sure if this is related to viewing the PDF Help files for AA2 and/or plug
ins -- or not -- nor why it's even being run and/or how to stop it. 

Does anyone know? Is it perhaps related to something like Bridge that gets installed with
AA2, even though have never run that?  Any way to keep it from running - or is it
a necessary component of something Adobe has installed?

Thx in advance for any insight.

Some more investigating this seems to reveal that something called Adobe Gamma may be
the problem.  At least in my install of AA2, it installed that all by itself -- and put it in
the startup for Win XP too.  Disabling using msconfig seems to stop it from loading --
at least for now. I'll update if I learn anything more.

Per the task monitor, not having any part of Gamma running seems to def. reduce the
system load and overhead, so if you are experiencing overall clogging when running
AA2 (which we see a lot here), this might be something to look into. 

 

Some more investigating this seems to reveal that something called Adobe Gamma may be the problem.  At least in my install of AA2, it installed that all by itself -- and put it in the startup for Win XP too.  Disabling using msconfig seems to stop it from loading -- at least for now. I'll update if I learn anything more.

Per the task monitor, not having any part of Gamma running seems to def. reduce the
system load and overhead, so if you are experiencing overall clogging when running
AA2 (which we see a lot here), this might be something to look into. 

I'm pretty sure that Adobe gamma shouldn't be in the startup - AFAIK you only need to run it when you've screwed up your monitor settings. It certainly shouldn't be chugging away in the background. What might be happening is that it's having some sort of a fight with a similar app belonging to your video card. To be honest, I really don't know why it gets installed with Audition anyway - I really can't see the point with a non-video app.

FWIW, neither my DAW or my Daily Driver have a FONT CAPTURE.EXE file anywhere.

To be honest, I really don't know why it gets installed with Audition anyway - I really can't see the point with a non-video app.

I believe it's a part of the video suite whose function is for accurately assessing your on-screen colour gamut which is essential for proper video color matching and because Audition was bundled with the suite, that's why it gets installed, so to call Audition, which also imports video, a "non-video app" is somewhat misleading.

To be honest, I really don't know why it gets installed with Audition anyway - I really can't see the point with a non-video app.

I believe it's a part of the video suite whose function is for accurately assessing your on-screen colour gamut which is essential for proper video color matching and because Audition was bundled with the suite, that's why it gets installed, so to call Audition, which also imports video, a "non-video app" is somewhat misleading.

That would be all fine and dandy if it were true, but it isn't. It installed itself on my laptop, which has no other part of the suite on it, and never has had... it's on the Audition disc in the commonfilesinstaller folder installer, and it doesn't need to be there.

And Audition isn't a video app. It just happens to import video files as a reference point, not as a way of making critical colour judgements.

That would be all fine and dandy if it were true, but it isn't. It installed itself on my laptop, which has no other part of the suite on it, and never has had...

That's fine about installing Audition standalone but it still has to work with Premiere and the other products in the suite. Also, the most important program in the suite, even though you didn't install it, is Photoshop and the Gamma is part and parcel of this, so Audition HAS to have the Gamma installed because of work done in the other apps for perfect visual and video rendering. Basically, it's for monitor calibration between the suite apps

That's fine about installing Audition standalone but it still has to work with Premiere and the other products in the suite. Also, the most important program in the suite, even though you didn't install it, is Photoshop and the Gamma is part and parcel of this, so Audition HAS to have the Gamma installed because of work done in the other apps for perfect visual and video rendering. Basically, it's for monitor calibration between the suite apps

Your logic is completely back to front. On this system, Audition doesn't have to work with anything. If another program needs gamma correction, then it should install it, not Audition. I didn't install Photoshop because I couldn't install it even if I wanted to - it's not even on the Audition disk. Ergo, it has no relevance at all. If an install disk with Photoshop 'needs' gamma correction, then it should install it. Audition does not 'have to have the gamma installed' - it's completely unnecessary. And also you are wrong about the calibration between applications - that's not what it's for. It is simply for calibrating your monitor. It has nothing directly to do with the individual apps at all, because they all behave the same way anyway - no inter-application calibration is required.

On the system that has Premiere installed, gamma is there quite legitimately, just as the Bridge is. The Bridge is yet another common app that has very little relevance to Audition, and that's installed automatically with Audition too. I wonder how many Audition-only users use the Bridge at all? Very few, I bet...

If I tell you that Adobe haven't got this correctly sorted out, you'd better believe it. The arguments about the Bridge inclusion started  before you ever saw AA2.0, I can tell you.  Hopefully now it's out of the suite, all this additional rubbish can come off the install disks.

Thx for all the replies, guys. For my 2 cents, I agree with Steve entirely. If some other suite
component needs it, THAT should install it- at least to my logic! (and should tell the user
so, too...)

It was slowing things down and hogging even more resources-- and I didn't even know it was
installed at all until I tried to start hunting down possible causes for why the machine ran so sloppily
with AA2 yet far better with 1.5.

The Audition installer really should offer a user the option to install or NOT install such things. Fine that
for a Premiere or suite installation Gamma is impt to have. But no such thing on this system, AA2 was
simply installed from the upgrade version bought directly from Adobe. Many users (like us) are not
running it for sound to picture work-- so at least they ought to offer more of the standalone option--
with the ability to later add any non-installed features, as many other programs allow you to do.

On the disc set I got from Adobe, there were no (identifiable at least!) files for Photoshop on
there, unless it's encrypted or buried in the CAB files or something. Just the Audition disc (which
does have Bridge files), the Loopology disc, and the 2 Total Training DVDs.  No Photoshop
seems to have been installed either.

Since others reported no Gamma in their install, there obviously must be different builds of
the product - and perhaps the upgrade build does things the others don't.

AA2 still taxes the resources of this P4 2.5 gig system greatly more than 1.5 does, even with
no plugs running and only a few tracks in MV but then others have written a lot about that.

Add a few Waves plugs -- or Ozone for that matter-- and it really maxes things out.
Add a Behringer BCF2000 running USB2/MCSo mode, even more. I tried a UA card
too figuring that maybe those plugs would be easier on the resources (since they run on
their own board) - but no. By the way, I posted elsewhere here that the UA card and
plugs DO seem to run OK with AA1.5-- even though UA does not support that (they
do support 2.0 though). I've only done limited testing of the UA with 1.5 though, so
I can't advise whether the whole lot of them run OK with 1.5, we have the Ultra bundle
of their stuff.

Yes, Bridge is installed too -- and no, have never had any reason to use it at all. But can't seem
to find any additional overhead THAT's adding - if anyone else has successfully uninstalled that
and AA2 still runs fine for them, please post here -- thx. 

I posted the initial note on Adobe's forums as well, maybe some factory folks will see it there- hope so.

Rich LePage

Yes, Adobe Gamma does install automatically when AA2 is installed.  (At least it has on my 2 installs).  Personally, I find it quite useful, since I use my computer for photoediting (though not with PhotoShop) as well as audio.

However, it does set itself to start automatically with Windows, which can be very annoying if you don't want it at all, and there appears to be no way to uninstall it.

On my computer I have a small utility called StartUp.cpl which allows me to select and deslect programs which should start with Windows.  I know it is possible to edit the msconfig file, but this is rather easier to deal with (I have an icon permanently on the desktop and can very quickly access the control panel applet to change any settings).

On my computer I have a small utility called StartUp.cpl which allows me to select and deslect programs which should start with Windows.  I know it is possible to edit the msconfig file, but this is rather easier to deal with (I have an icon permanently on the desktop and can very quickly access the control panel applet to change any settings).

It's not exactly difficult to put an msconfig icon on the desktop... you don't have to edit the file at all; there's a control panel for that!

However, it does set itself to start automatically with Windows, which can be very annoying if you don't want it at all, and there appears to be no way to uninstall it.

I don't know if you need to really. There isn't much of it, and if it's not running, it's not exactly a lot of a problem having it there. Since there's no uninstaller for it, I don't think that it will be particularly heavily integrated into the registry, although I haven't checked this aspect of it yet.

Since there's no uninstaller for it, I don't think that it will be particularly heavily integrated into the registry, although I haven't checked this aspect of it yet.

As far as I can tell, the only significant registry entries for it relate to starting it when XP starts - in other words, the fact that it shows up in msconfig at all. I disabled it at startup, and have had no problems at all with this.

if anyone else has successfully uninstalled that and AA2 still runs fine for them, please post here -- thx. 

I uninstalled Bridge from the Control Panel (all 200MB of it!), and both AA2 and PS CS2 still run fine.

Paul

Thx Steve and Paul. Steve's running it the way I am, apparently - disabled via MSCONFIG.

But glad to know Paul removed Bridge and AA2 still runs OK-- I'm def. going to try that too.
(with a restore point put in first..and maybe a Ghost boot drive backup first too..)

Anything that reduces the load when AA2 is running has to be a help.

I'm def. a "less is more" fan-- both in Windows-land and (whenever possible) with audio
processing too.

Has anyone had to restore boot drive from an image like using Ghost -- does that affect the
activation at all?  I've done that with XP a couple times on systems running AA1.5 and
CEP 2.0 but not AA2.

Rich

if anyone else has successfully uninstalled that and AA2 still runs fine for them, please post here -- thx. 

I uninstalled Bridge from the Control Panel (all 200MB of it!), and both AA2 and PS CS2 still run fine.

Did not see a way to do this in Control Panel for my AA2-only install.
Does this maybe have to be done using the "repair" option for the existing AA2 install?

Thx-- Rich