Invalid plug-ins with Reader 9

I cannot open PDF files-- or Adobe Reader itself-- because I immediately receive a message "Invalid plug-ins Adobe Reader will close", which it does immediately. I unistalled Reader and reinstalled it but still there seems to be an invalid plug-in. I have the latest version of Reader.

Use the forum for Adobe Reader.

Similar Messages

Invalid Plug ins

I cannot open PDF files-- or Adobe Reader itself-- because I immediately receive a message "Invalid plug-ins Adobe Reader will close", which it does immediately. I unistalled Reader and reinstalled it but still there seems to be an invalid plug-in. I have the latest version of Reader.

Use the forum for Adobe Reader.

Build Plug-Ins with CS4 SDK under OS X 10.5 SDK with Xcode 3.1.2?

I have existing Photoshop Universal Binary Plug-ins built under OS X 10.4 and the OS X 10.4 SDK, with Xcode 2.1.x & Photoshop CS3 SDK. They are mature and stable.
I am attempting to build these Plug-Ins with the new CS4 SDK under OS X 10.5.6 & 10.5 SDK with Xcode 3.1.2.
They do not build as there is a conflict in PITypes.h with the attempted redefinition of uint32, already defined in the Apple header cssmconfig.h, amongst other problems.
Has anyone built with a similar configuration?
Thank you!

I've had good luck with Snow Leopard 10.6.1, XCode 3.2 and the Photoshop CS4 SDK by changing the build settings like this:
1. Open the Target Info window: Project->Edit Active Target
2. Change Architectures from native to 32-bit Universal (because my native is 64 bit)
3. Make sure Base SDK is 10.4 (you must have that installed of course). If you select 10.5 for some of the Photoshop examples, you get complaints of depreciated APIs.
4. Change C/C++ compiler version to GCC 4.0
In the case of using these steps, there is no need to edit any headers, comment anything out, etc.
Hope that helps!

My Photoshop Elements 6.0 suddenly can't download plug-ins to read input from my cf photo card, or s

My Photoshop Ele
ments 6.0 suddenly stopped loading ph
otos from my CF Card with the message that it could not download
plug-ins to read the device. It al
ways worked before. Would it help to re-install Elements, or should I look for a way to download the Plug-in. Don't even know what it is called. Thanks

When you browse to Computer is your CF card shown as a removable drive?
If not try shutting down the computer and re-starting and then inserting the CF card or plugging in the USB again.
Open Elements Organizer and press Ctrl+G to bring up the downloader and under Source click refresh to locate your CF card.

Nik PLug-ins with Aperture

Greetings, This is for anyone using Nik Software plug-ins with Aperture. Is there a way to back out of adjustments once you've saved your work in the Nik editor? When using with Photoshop, the Nik adjustment will create a "layer". Deselecting the layer will allow you to essentially remove the adjustment. I don't see any way of doing that in Aperture. Am I missing it, or are you basically down the road with the adjustment once you make it?
Thanks.

Once you save in NIK, the adjustments are "baked in." There's no way to go back and remove them. What NIK does is save the TIFF file that Aperture creates and hands over to it, with the NIK adjustments. This won't affect the original RAW file.
You could always go back and send that same TIFF file to NIK an indefinite number of times. It wouldn't really be "non-destructive" but you can re-do or tweak any adjustments you want to tweak.

Error Messages/Building Plug-ins with Eclipse SDK or VCExpress 2005

Hi,
I am an newbie in building InDesign-Plugins. I have installed the Adobe InDesign Plug-in Editor on my Windows XP PC (InDesign CS3 SDK, Eclipse, JRE 1.5, Visual Studio 2005 (VCExpress Edition for C++)).
I tried to build one of the example Plug-ins with Eclipse. After startting the build process of the "transparencyeffectui"-example or the "DollyXs"-example the following message appears:
Buildfile: F:\SDK\workspace\DollyTest\build.xml
win:
[echo] Now compiling FR file F:\adobe_indesign_cs3_products_sdk_503win\source\sdksamples\dollytest\Dolly.fr for win
[delete] Deleting: F:\SDK\workspace\DollyTest\ODFRC.res
[echo] FR Compilation Complete: Attempting to build C++ files...
BUILD FAILED
F:\SDK\workspace\DollyTest\build.xml:66: Execute failed: java.io.IOException: Cannot run program "D:\Programme\Microsoft Visual Studio 5\Common7\IDE\devenv.com": CreateProcess error=2, Das System kann die angegebene Datei nicht finden
Total time: 485 milliseconds
The compiler did't start because the file "devenv.com" is missing in the "Microsoft Visual Studio 2005/Common7/IDE"-directory.
The free "Visual Studio Express Edition" is delivered withot this file.
Where can i get this file? Or is it possible to change the exec line in the built-xml-file to get the Compiler started?
So I started the VCExpress-Programm an opened the transparencyeffetui-Project-File to start the build process. But again i got an error message:
1>------ Erstellen gestartet: Projekt: TransparencyEffectUI, Konfiguration: Debug Win32 ------
1>Performing Custom Build Step
1>Compiling...
1>VCPlugInHeaders.cpp
1>f:\adobe_indesign_cs3_products_sdk_503win\source\precomp\common\WShukHeaders.h(70) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
1>Build log was saved at "file://f:\adobe_indesign_cs3_products_sdk_503win\build\win\objD\TransparencyEffectUI\Bui ldLog.htm"
1>TransparencyEffectUI - 1 error(s), 0 warning(s)
========== Erstellen: 0 erfolgreich, Fehler bei 1, 0 aktuell, 0 übersprungen ==========
There is no "windows.h"-file in the SDK directory. I tried to include all available SDK-"inculde"-directories to the VC++ directories in the option menue in VCExpress but i got the same error message.
Any ideas how to get the plug-in build with Eclipse or Visual Studio Express 2005 (C++)?
zaphodbeeblebroxxx

OK, so first some background:
1) The basic process goes like this:
a) one release doc (edited by the developer, presumably) and the
template docs are copied to the build area
b) Each doc is unzipped (ODT's are just ZIP files) into a subdir
c) The doc contents are copied around; this is to allow Ant to
replace its special @VAR@ variables in the document content
d) The docs are zipped back up into ODTs
e) The ODTs are converted into PDFs using OOo's macro functionality
Here are the troubleshooting steps I would apply:
1) Make sure the external.odt file exists - check the build area
(//content/build/<pluginname>/tmp/) and can be opened using normal
OpenOffice
2) Check that the release.odt file exists (same location) and can be
opened using normal OpenOffice
3) See if you can manually convert the external.odt file into a PDF -
the command we use is simply:
soffice -invisible
macro:///Standard.Collectors.External2PDF(${pkgdir}/tmp/external.odt)
(replace ${pkgdir} with the build directory path).
If all that works, then the Ant build process should work.
Also - what does that OpenOffice error popup say?
DCorlette
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=416875

Can I use Topaz plug ins with PS from the cloud?

Can I use Topaz plug ins with PS from the cloud?
Can I use Topaz plug ins with PS from the cloud?

Your Creative Cloud account allows you to install software on two computers, regardless of operating system. Just log in to Creative Cloud from your second computer and install the app. See http://www.adobe.com/products/creativecloud/faq.html.
If you opt to do so, your files will be synched between the machines and Creative Cloud itself.
--- Ben

How to "not" share FCP Plug-ins with other users

I'm Installing FCP on a new Intelmac. Several users/editors will use the computer in the editsuite.
how can you install your FCP plugins so that they only load if your loggin with your useraccount.
in other words how to NOT share your plug-ins with other useraccounts.... ?
2.5 GHz dual Quad G5 + 933 QuickSilver G4 Mac OS X (10.4.9) 2x 23" Cinadisplay, Digidesign Digi 002R

Hello
Hopefully I'm not infringing the Terms Of Use by asking you to have a look at THIS PAGE of the Apple Discussions guide.
Regards,
J

VI Search Path not working in LV2011 for VI Server Plug-ins with exe

I have found what seems to be a problem with the search path when a LabVIEW 2011 built executable calls a Plug-in VI.
When the plug-in VI has subVI’s from vi.lib on its diagram the executable has to know where to find them. Not all VI’s in vi.lib are part of the run time engine or the dll’s that may get generated as part of the build. The things you have to do to make plug-ins work for an executable are explained in several Developer Zone articles. The article titled “How Can I Change or Set the VI Search Path for LabVIEW Executables” describes the ini file setting viSearchPath. When this is set to the vi.lib directory I have not encountered problems with previous versions up to and including LabVIEW 2010.
I have come across an example in LabVIEW 2011 where it doesn’t work. I have attached an example (I am using LV2011 SP1). It demonstrates the basic plug-in architecture. Everything works in the development environment. But it doesn’t work from a built exe. I haven’t included the actual built exe in the zip file in case that causes a problem downloading it. If you run the build spec from the src directory project file the exe should get generated in the bld directory. The problem appears to occur when certain VIs from the analysis library are in the Plug-in. In the example attached, the Plug-in VI is very simple but I have placed the troublesome SubVI on the diagram. The VI in this example where there is a problem finding it is the Butterworth Filter VI. I have placed it on the diagram in a conditional disable structure so it is easy to enable and disable. When enabled and you run the test Plug-in VI the error 1003 is raised, meaning a subVI cannot be found in the dynamically called VI (for example see this post). Note that a way round this may be to incorporate the Plug-in VI into the built exe but this shouldn't be necessary. It’s not a problem with this specific filter VI, as it occurs for other VIs I try on the diagram. However if you place an FFT VI on the diagram there is no problem. I suspect that one is built into the Run-Time Engine.
I also note I am running Win7 64 bit and 32 bit LabVIEW (note the relevant viSearchPath in the ini file – you may need to change if you are on different version of Windows). If the example is converted to LabVIEW 2010 everything works as expected for the built exe. I tried that on a colleague’s computer running XP and 2010 but I am pretty sure in still also works on Win 7.
Things I am suspicious of are that the analysis VI’s are part of a LabVIEW library (lvlib) and perhaps something has changed there? I understand there is a problem with OOP in LabVIEW 2011. Perhaps it is related to that as that seems to be an issue in 2011 (see this Discussion Forum post). Perhaps it is related to OS version?
I also tried generating a Source Distribution to extract out all the vi.lib VI’s and place them directly in the Plug-in directory. That didn’t help.
Interested in whether anyone else reproduces this behaviour. In any case something is different in 2011.
Attachments:
LV 2011 test Plug-in.zip ‏42 KB

I found some more out about this issue working with my local NI rep here in Australia. Apparently something has changed in the compiler between LabVIEW 2010 and 2011. Using the viSearchPath token in the ini file, as described in various Developer Zone articles, now guarantees that the Plug-in will not work. The only way to make it work appears to be to create a Source Distribution. I noted in my original post that I had already tried this and it would not work. It turns out that having the viSearchPath token in the ini file when using a Source Distribution causes the error 1003 to occur. When the token is taken out of the ini file the Plug-in (containing an analysis VI) with a Source Distribution works - in the simple example I posted.
Well I then found its a bit more complicated than this. It all worked for the simple example I posted. Recall we found the error when there was an analysis VI in the Plug-in VI. In our actual application (which is a large one) that calls Plug-ins - we still got the error 1003. By trial and error I found a workaround. There are certain Build Spec settings for the calling exe that I set and found worked. On the Additional Exclusions page I found that I had to make sure that I left unchecked "Modify Project Library File after removing unused members". I've always had trouble understanding the need for this setting. In the Build Spec Help on that page it notes that the build will take longer. In most builds you remove polymorphic VI instances, remove unused members of Project libraries and also Modify the project library file after removing the instances (this is a sub setting of the previous). This makes the exe smaller in size and a quicker build time. Obviously modifying the project library caused a problem. In the big application exe calling Plug-in, I probably have the same analysis VI on the diagram (I haven't actually checked and also whether it is the same polymorphic instance) and in the simple example I posted I definitely did not have VI in the calling exe example - so there may be some clue there. I should try putting the same analysis VI on the calling exe diagram in the simple example to see what happens but I'm running out of energy on this one :-(
So none of this gives me much confidence and I wish I could get a better explanation from NI regarding this behaviour to be sure I am not going to encounter a different problem for different calling exe and Plug-ins. I was advised that a CAR would be issued. Perhaps this is now expected behaviour for 2011 but it would helpful if some definitive explanation could be given about what has changed from LV2010. And an update of Developer Zone articles on the subject would be helpful.

Failure to authorize third party plug-ins with 7.1.1

I am running 10.4.2 on a new g5. I just upgraded to 7.1.1 from 7.0.1 and I get multiple crashes on the authorization of the plug-ins.
I got the message
"the application auval quit unexpectedly" numerous times.
I also got another message about missing a required software extension. Something about enginelibcarbon.
Any thoughts? Thanks for the help in advance.
Joe

Well, in order to upgrade to 7.1.1 you need to upgrade to 7.1 first. You cannot upgrade directly from 7.0.1.
Also, after you do the proper upgrade, you may want to repair your disk permissions with Disk Utility immediately following.

Can I use third paty plug-ins with Photos? If so, how?

Would really like to still use my NIK Software and topaz plug-ins...Am I still able to do this with photos? If so, how?

Thanks leonie...I would much rather pay the $$ for Aperture than use the free Photos program- it's a shame that Aperture development has ceased...not in love at all with Photos yet...maybe in time...

Need help using Waves 64bit, 3rd party plug-ins with Premiere CS5

I'm trying to install and use a bundle of 64bit 3rd party audio plug-ins from Waves in Premiere.
I am on a Mac running OS 10.9.3.
I can't figure out how to get Premiere CS5 to recognize my 3rd party Waves 9.3 bundle.
The plug-ins are listed and fly by one by one on the loading splash screen while Premiere launches. I can't find them anywhere in Premiere once it launches. Aparently both the VST and AU units work. But how? Where/how do I load the plug ins so I can access them in the audio effects folder?
thanks in advance!
Alex

i think the audio plugin manager was something new added, but i dont remember when. as im looking thru older threads at cs5, they make it sound as if premiere will just load and use what it can. when an effect doesn't show up, its usually cause premiere determined it couldn't use it. if you have the 64-bit version of premiere and 64-bit audio plugins, they should work, unless premiere has some issue with them. i think waves uses vst3 and AU (audio units)? while vst2 should work in cs5, im not sure if vst3 or au are supported until cs7. so im at a loss, unless someone else knows better. if you have access to audition, you can try to load them in there to use.
Premiere Pro CC (7.0) | Premiere Pro New Features
Premiere Pro Mac - VST & Audio Unit Support - Something is wrong....
VST Plugins work in CS4, not in CS5
VST plug-ins not loaded at all Snow Leopard 10.6
Virtual Studio Technology - Adobe Premiere Pro

Using 32-bit Plug-ins with jBridgeM and Metaplugin -- crash?

Hi all,
I just switched from MainStage 2 to 3.1.1 because 2 kept crashing.
Since I use a couple of 32-bit plug-ins (VB3 and Dune), I had to get jBridgeM and Metaplugin.
Now I can crash MainStage in no time at all.
Does anyone have (positive) experience with using 32-bit plug-ins (or VSTs) with "wrappers" in MainStage 3?
Are people complaining LOUDLY to Apple about removal of the support for 32-bit components (and VSTs in the first place) in their "professional" music apps.
stp

Hi again,
To add to the above note, the tools I found are:
     jBridgeM - wraps 32-bit VSTs for 64-bit hosts
     VSTAU Manager - wraps VSTs as AUs
     Metaplugin - lets you plug VSTs into an AU host
Unfortunately, the workflow doesn't produce working plug-ins, and there's no 32-to-64-bit wrapper for AUs.
Does anyone else have this issue?
Are the other wrappers (e.g., FXpansion's) any more reliable?
stp

Using Plug-Ins with GarageBand

Hi there
I am wondering if there are any plug-ins I can get that help me visualise equalisation bands within a song.
Cheers
Toby

I found a cool free spectrum analyzer called sndpeek at http://soundlab.cs.princeton.edu/software/sndpeek/
Only thing is that it is standalone.

Lost my 3rd party plug-ins with upgrade to CS4

The 3rd party (Boris) files are still in the program files, but they are no longer in my effects panel. How can I get them back? Do I have to reload original software and complete all the updates again? Thanks

Good Morning Jim,
For future reference, I am attaching the response from Boris tech
support that solved the problem. Thanks again for your help.
There are two things you can do - you can reinstall the RED plugs,
this time
into the CS4 directory, or you can move the plugs from the CS3
directory to
the corresponding CS4 directory. The second would be quicker, but
requires
CS3 to still be installed. If it is, you just need to move the files
called
"FL7-BorisRed4P3.prm", "FX6-BorisRed4P3.prm" and "IM-BorisRed4.prm"
from
this location -
C:\Program Files\Adobe\Common\Plug-ins\CS3\MediaCore
To this location -
C:\Program Files\Adobe\Common\Plug-ins\CS4\MediaCore
If you do not find the RED plugs in the CS3 MediaCore folder, try
looking
here instead -
C:\Program Files\Adobe\Adobe Premiere Pro CS3\Plug-ins\en_US
David J. Whiteford
A/V Production Specialist
Justice Department/Federal Bureau of Prisons
Management & Specialty Training Center
791 Chambers Rd.
Aurora, CO. 80011
303-340-7857
>>> Jim Simon <[email protected]> 10/15/2009 1:11 PM >>>
You're welcome.

Invalid plug-ins with Reader 9

Similar Messages

Maybe you are looking for