Plug-Ins -- Static vs Dynamic Guidelines

Are the general pros and cons of static vs dynamic plug-ins currently documented? e.g. in any of the specifications? Or the current OSMF documentation?
If not, what are cases where it is recommended to use one over the other?
Thanks,
g

As a 3rd party vendor, I'm inclined to offer only dynamic plugins due to the fact that we're often rolling in new functionality and/or fixing issues and do not want to deal with each publisher having diff't versions or having to distribute new static plugins to each publisher as we make one of these sort of changes.
While I can appreciate the benefits of the elimination of run-time loading that comes with dynamic plugins, the benefits of dynamic plugins from 3rd party vendors outweigh the "cons"
In response to the mention about the publisher not wanting to "risk" breaking the player, I suppose that is a concern if the plugin being used is absolutely necessary for the overall functionality of the publisher's player, but I'd hope that the OSMF plugin framework is handling any fatal errors from a plugin such that they do not kill the player
-jason
VP Product & Technical Operations
ScanScout, Inc

Similar Messages

  • Is there any plug-ins for static code analysis in Jdeveloper

    Hi,
    Is there any PMD, check style and static code analysis plug-ins available for JDeveloper? Those are available for Eclipse. How to achieve that in the JDeveloper?
    Regards,
    Raghu.

    This should help-
    PMD plugin for JDeveloper 11.1.2.0
    http://develishdevelopment.wordpress.com/2012/03/12/have-released-pmd-jdeveloper-extension-4-3/
    Always mention you Jdev version. Here I just assumed yours :P

  • Photoshop CC 2014 - error: javascript plug-ins was missing

    hi, i have this problem: when i try to open different things, like photomerge or libraries, i see always this message: "photoshop don't open ... because was missing javascript plug-in".
    Please tell me a solution, i reinstalled but nothing.
    Here are the info system:
    Adobe Photoshop versione: 2014.2.1 20141014.r.257 2014/10/14:23:59:59 CL 987299  x64
    Sistema operativo: Windows 7 64 bit
    Versione: 6.1 Service Pack 1
    Architettura di sistema: Famiglia CPU Intel:6, Modello:7, Stepping:7 con MMX, Intero SSE, SSE FP, SSE2, SSE3, SSE4.1
    Conteggio processore fisico: 4
    Velocità processore: 2833 MHz
    Memoria incorporata: 4095 MB
    Memoria disponibile: 1828 MB
    Memoria disponibile per Photoshop: 3402 MB
    Memoria usata da Photoshop: 70 %
    Stampa 3D a più tonalità: disattivato.
    Interfaccia Windows 2x: disattivato.
    Highbeam: ^ 0 ®Dimensioni porzioni immagine: 1024 K
    Livelli cache immagine: 4
    Anteprima font: Media
    Composizione testo: Latino
    Monitor: 1
    Visualizza limiti: alto= 0, sinistra= 0, basso= 1080, destra= 1920
    Disegno OpenGL: attivato.
    OpenGL - Consenti GPU precedenti: Non rilevato.
    OpenGL - Modalità disegno: Avanzata
    OpenGL - Consenti modalità normale: True.
    OpenGL - Consenti modalità avanzata: True.
    AIFCoreInitialized=1
    AIFOGLInitialized=1
    OGLContextCreated=1
    NumGLGPUs=1
    NumCLGPUs=1
    glgpu[0].GLVersion="3.0"
    glgpu[0].GLMemoryMB=896
    glgpu[0].GLName="GeForce GTX 260/PCIe/SSE2"
    glgpu[0].GLVendor="NVIDIA Corporation"
    glgpu[0].GLVendorID=4318
    glgpu[0].GLDriverVersion="9.18.13.4052"
    glgpu[0].GLRectTextureSize=8192
    glgpu[0].GLRenderer="GeForce GTX 260/PCIe/SSE2"
    glgpu[0].GLRendererID=1506
    glgpu[0].HasGLNPOTSupport=1
    glgpu[0].GLDriver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
    glgpu[0].GLDriverDate="20140702000000.000000-000"
    glgpu[0].CanCompileProgramGLSL=1
    glgpu[0].GLFrameBufferOK=1
    glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="3.30 NVIDIA via Cg compiler"
    glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[1638 4]
    glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
    glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[96]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
    glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
    glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
    glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
    glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[60]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
    glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
    clgpu[0].CLPlatformVersion="1.1"
    clgpu[0].CLDeviceVersion="1.0 CUDA"
    clgpu[0].CLMemoryMB=896
    clgpu[0].CLName="GeForce GTX 260"
    clgpu[0].CLVendor="NVIDIA Corporation"
    clgpu[0].CLVendorID=4318
    clgpu[0].CLDriverVersion="340.52"
    clgpu[0].CUDASupported=1
    clgpu[0].CUDAVersion="6.5.12"
    clgpu[0].CLBandwidth=9.30992e+010
    clgpu[0].CLCompute=366.914
    Tipo di licenza: Versione di prova
    Numero di serie: Versione di prova
    Cartella applicazione: C:\Program Files\Adobe\Adobe Photoshop CC 2014\
    Percorso file temporanei: C:\Users\Stefano\AppData\Local\Temp\
    La memoria virtuale di Photoshop dispone di I/O asincrono attivato
    Volumi di memoria virtuale:
      Avvio, 232.9 GB, 165.8 GB disponibili
    Cartella plug-in richiesti: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Required\Plug-Ins\
    Cartella plug-in principali: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Plug-ins\
    Componenti installati:
       A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112  
       ACE.dll   ACE 2014/08/12-23:42:09   79.557478   79.557478
       adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
       AdbePM.dll   PatchMatch 2014/09/07-21:07:38   79.558079   79.558079
       AdobeLinguistic.dll   Adobe Linguisitc Library   8.0.0  
       AdobeOwl.dll   Adobe Owl   5.2.4  
       AdobePDFL.dll   PDFL 2014/08/18-15:13:12   79.512424   79.512424
       AdobePIP.dll   Adobe Product Improvement Program   7.2.1.3399  
       AdobeXMP.dll   Adobe XMP Core 2014/08/20-09:53:02   79.156797   79.156797
       AdobeXMPFiles.dll   Adobe XMP Files 2014/08/20-09:53:02   79.156797   79.156797
       AdobeXMPScript.dll   Adobe XMP Script 2014/08/20-09:53:02   79.156797   79.156797
       adobe_caps.dll   Adobe CAPS   8,0,0,13  
       AGM.dll   AGM 2014/08/12-23:42:09   79.557478   79.557478
       ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31  
       amtlib.dll   AMTLib (64 Bit)   7.0.0.169 BuildVersion: 7.0; BuildDate: Mon Apr 8 2013 2:31:50)   1.000000
       ARE.dll   ARE 2014/08/12-23:42:09   79.557478   79.557478
       AXE8SharedExpat.dll   AXE8SharedExpat 2013/12/20-21:40:29   79.551013   79.551013
       AXEDOMCore.dll   AXEDOMCore 2013/12/20-21:40:29   79.551013   79.551013
       Bib.dll   BIB 2014/08/12-23:42:09   79.557478   79.557478
       BIBUtils.dll   BIBUtils 2014/08/12-23:42:09   79.557478   79.557478
       boost_date_time.dll   photoshopdva   8.0.0  
       boost_signals.dll   photoshopdva   8.0.0  
       boost_system.dll   photoshopdva   8.0.0  
       boost_threads.dll   photoshopdva   8.0.0  
       cg.dll   NVIDIA Cg Runtime   3.0.00007  
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007  
       CIT.dll   Adobe CIT   2.2.6.32411   2.2.6.32411
       CITThreading.dll   Adobe CITThreading   2.2.6.32411   2.2.6.32411
       CoolType.dll   CoolType 2014/08/12-23:42:09   79.557478   79.557478
       dvaaudiodevice.dll   photoshopdva   8.0.0  
       dvacore.dll   photoshopdva   8.0.0  
       dvamarshal.dll   photoshopdva   8.0.0  
       dvamediatypes.dll   photoshopdva   8.0.0  
       dvametadata.dll   photoshopdva   8.0.0  
       dvametadataapi.dll   photoshopdva   8.0.0  
       dvametadataui.dll   photoshopdva   8.0.0  
       dvaplayer.dll   photoshopdva   8.0.0  
       dvatransport.dll   photoshopdva   8.0.0  
       dvaui.dll   photoshopdva   8.0.0  
       dvaunittesting.dll   photoshopdva   8.0.0  
       dynamiclink.dll   photoshopdva   8.0.0  
       ExtendScript.dll   ExtendScript 2014/01/21-23:58:55   79.551519   79.551519
       icucnv40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090  
       icudt40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090  
       igestep30.dll   IGES Reader   9.3.0.113  
       imslib.dll   IMSLib DLL   7.0.0.154  
       JP2KLib.dll   JP2KLib 2014/06/28-00:28:27   79.254012   79.254012
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libiomp5md.dll   Intel(R) OpenMP* Runtime Library   5.0  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       LogSession.dll   LogSession   7.2.1.3399  
       mediacoreif.dll   photoshopdva   8.0.0  
       MPS.dll   MPS 2014/08/18-23:43:19   79.557676   79.557676
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CC 2014   15.2.1  
       Plugin.dll   Adobe Photoshop CC 2014   15.2.1  
       PlugPlugExternalObject.dll   Adobe(R) CEP PlugPlugExternalObject Standard Dll (64 bit)   5.0.0  
       PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   5.2.0.52  
       PSArt.dll   Adobe Photoshop CC 2014   15.2.1  
       PSViews.dll   Adobe Photoshop CC 2014   15.2.1  
       SCCore.dll   ScCore 2014/01/21-23:58:55   79.551519   79.551519
       ScriptUIFlex.dll   ScriptUIFlex 2014/01/20-22:42:05   79.550992   79.550992
       svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114  
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114  
       TfFontMgr.dll   FontMgr   9.3.0.113  
       TfKernel.dll   Kernel   9.3.0.113  
       TFKGEOM.dll   Kernel Geom   9.3.0.113  
       TFUGEOM.dll   Adobe, UGeom©   9.3.0.113  
       updaternotifications.dll   Adobe Updater Notifications Library   8.0.0.14 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   8.0.0.14
       VulcanControl.dll   Vulcan Application Control Library   5.0.0.82  
       VulcanMessage5.dll   Vulcan Message Library   5.0.0.82  
       WRServices.dll   WRServices Fri Mar 07 2014 15:33:10   Build 0.20204   0.20204
       wu3d.dll   U3D Writer   9.3.0.113  
    Plug-in richiesti:
       3D Studio 15.2.1 (2014.2.1 x001 x003)
       Affresco 15.2.1
       Applica texture 15.2.1
       Asimmetria 15.2.1 (2014.2.1 x001 x003)
       Bagliore diffuso 15.2.1
       Bassorilievo 15.2.1
       Bordi brillanti 15.2.1
       Camera Raw 8.6
       Carta da lettere 15.2.1
       Cineon 15.2.1 (2014.2.1 x001 x003)
       Collada 15.2.1 (2014.2.1 x001 x003)
       Colore mezzetinte 15.2.1
       Colori NTSC  15.2.1 (2014.2.1 x001 x003)
       CompuServe GIF 15.2.1
       Conté Crayon 15.2.1
       Contorni accentuati 15.2.1
       Contorni con inchiostro 15.2.1
       Contorni poster 15.2.1
       Contorni strappati 15.2.1
       Coordinate polari 15.2.1
       Core misurazione 15.2.1 (2014.2.1 x001 x003)
       Correzione obiettivo 15.2.1
       Cristallizza 15.2.1
       Curtosi 15.2.1 (2014.2.1 x001 x003)
       Deforma 15.2.1
       Deviazione standard 15.2.1 (2014.2.1 x001 x003)
       Dicom 15.2.1
       Distorsione curvilinea 15.2.1
       Eazel Acquire 15.2.1 (2014.2.1 x001 x003)
       Effetto acquerello 15.2.1
       Effetto carboncino 15.2.1
       Effetto carta bagnata 15.2.1
       Effetto cromatura 15.2.1
       Effetto fotocopia 15.2.1
       Effetto increspatura 15.2.1
       Effetto incrinatura 15.2.1
       Effetto intonaco 15.2.1
       Effetto onda 15.2.1
       Effetto pennellate 15.2.1
       Effetto punti 15.2.1
       Effetto retinatura 15.2.1
       Effetto ritaglio 15.2.1
       Effetto sfera 15.2.1
       Effetto sfumino 15.2.1
       Effetto spatola 15.2.1
       Effetto spirale 15.2.1
       Effetto spugna 15.2.1
       Effetto vento 15.2.1
       Entropia 15.2.1 (2014.2.1 x001 x003)
       Esporta tavole di consultazione colore NO VERSION
       Estrusione 15.2.1
       Fibre 15.2.1
       Filtro Camera Raw 8.6
       Filtro Pacchetto immagini 15.2.1 (2014.2.1 x001 x003)
       Filtro ritaglia e raddrizza foto 15.2.1
       Flash 3D 15.2.1 (2014.2.1 x001 x003)
       Fluidifica 15.2.1
       Formato file bitmap 15.2.1
       Formato IFF 15.2.1
       Formato PNG 15.2.1
       Formato Targa 15.2.1
       Fuoco prospettico 15.2.1
       Galleria filtri 15.2.1
       Gessetto e carboncino 15.2.1
       Google Earth 4 15.2.1 (2014.2.1 x001 x003)
       Grana pellicola 15.2.1
       Grandangolo adattato 15.2.1
       Granulosità 15.2.1
       HDRMergeUI 15.2.1
       HSB/HSL 15.2.1
       IGES 15.2.1 (2014.2.1 x001 x003)
       Includi filigrana 4.0
       Increspatura oceano 15.2.1
       Intermedio 15.2.1 (2014.2.1 x001 x003)
       Intervallo 15.2.1 (2014.2.1 x001 x003)
       Involucro di plastica 15.2.1
       JPEG 2000 15.2.1
       Leggi Filigrana 4.0
       Luce al neon 15.2.1
       Massimo 15.2.1 (2014.2.1 x001 x003)
       Matita colorata 15.2.1
       Matlab Operation 15.2.1 (2014.2.1 x001 x003)
       Media 15.2.1 (2014.2.1 x001 x003)
       Media 15.2.1 (2014.2.1 x001 x003)
       Mezzatinta 15.2.1
       Minimo 15.2.1 (2014.2.1 x001 x003)
       Modulo Photoshop 3D 15.2.1 (2014.2.1 x001 x003)
       Muovi 15.2.1
       Nuvole 15.2.1 (2014.2.1 x001 x003)
       Nuvole in differenza 15.2.1 (2014.2.1 x001 x003)
       Ombra tratteggiata 15.2.1
       OpenEXR 15.2.1
       Pastelli su superficie ruvida 15.2.1
       Patchwork 15.2.1
       Pattern mezzetinte 15.2.1
       PCX 15.2.1 (2014.2.1 x001 x003)
       Penna grafica 15.2.1
       Pennello a secco 15.2.1
       Photoshop Touch 14.0
       Pixar 15.2.1 (2014.2.1 x001 x003)
       PLY 15.2.1 (2014.2.1 x001 x003)
       Portable Bit Map 15.2.1 (2014.2.1 x001 x003)
       Porzioni 15.2.1
       Porzioni mosaico 15.2.1
       PRC 15.2.1 (2014.2.1 x001 x003)
       Radiance 15.2.1 (2014.2.1 x001 x003)
       Rendering griglia di consultazione colore NO VERSION
       Riduzione effetto mosso 15.2.1
       Riflesso obiettivo 15.2.1
       Ritaglia e raddrizza foto 15.2.1 (2014.2.1 x001 x003)
       Routine FastCore 15.2.1 (2014.2.1 x001 x003)
       Routine MMXCore 15.2.1 (2014.2.1 x001 x003)
       Salva per Web 15.2.1
       Sfocatura con obiettivo 15.2.1
       Sfocatura migliore 15.2.1
       Sfocatura radiale 15.2.1
       Solarizza 15.2.1 (2014.2.1 x001 x003)
       Sommatoria 15.2.1 (2014.2.1 x001 x003)
       Spruzzo 15.2.1
       STL 15.2.1 (2014.2.1 x001 x003)
       Sumi-e 15.2.1
       Supporto multiprocessore 15.2.1 (2014.2.1 x001 x003)
       Supporto WIA 15.2.1 (2014.2.1 x001 x003)
       Timbro 15.2.1
       Togli interlacciato 15.2.1
       Tracciati per Illustrator 15.2.1
       Tratti a spruzzo 15.2.1
       Tratti ad angolo 15.2.1
       Tratti scuri 15.2.1
       U3D 15.2.1 (2014.2.1 x001 x003)
       Varianza 15.2.1 (2014.2.1 x001 x003)
       Vernice di fondo 15.2.1
       Vetro 15.2.1
       Vetro colorato 15.2.1
       Virtual Reality Modeling Language | VRML 15.2.1 (2014.2.1 x001 x003)
       Wavefront|OBJ 15.2.1 (2014.2.1 x001 x003)
       Wireless Bitmap 15.2.1 (2014.2.1 x001 x003)
       Zig zag 15.2.1
    Plug-in opzionali e di terze parti: NESSUNO
    Impossibile caricare i seguenti plug-in: NESSUNO
    Flash:
       Librerie
       Temi Adobe Color
    Periferiche TWAIN installate: NESSUNA

    You need to install the latest Java SE6 runtime, go to this link and download it and it should take care of your CS5 if you have Yosemite in order for it to run hope this works
    Java for OS X 2014-001

  • Unable to open Livecycle forms even with latest plug-ins

    Hi guys,
    I have a created a few dynamic forms designed using livecycle designer ES..In order for my users to open these forms, they need to have atleast Adobe acrobat / reader version 8.1 or higher to view these dynamic files. However, quite a few of my users are saying that they are still unable to open these forms directly from their browser although they have downloaded the latest Acrobat X version and the browser plug-ins in their computer. It happens to both windows and mac computers. But they are able to download these files and open it directly from their adobe reader though. It happens with all browsers for them...some of them have even called up mac support as well as adobe support and they were advised that it could be a problem with my forms that I find hard to believe since it opens in my computer and opens for a lot of other users. Its only a few users still having difficulties and I can't understand why!
    Also, I recently uploaded a dynamic file in acrobat file sharing. Why am I getting the below message when I have the latest adobe installed? I am able to open other dynamic forms in my browsers..why does this happen? I wonder if other user's problem is similar to this...not sure...
    To view the full contents of this document, you need a later version of the PDF viewer. You can upgrade to the latest version of Adobe Reader from etc...etc...etc..
    What can be the problem when the adobe version is already updated and also the plug-ins are updated too?? I have read a lot of links in adobe site itself which suggest various methods to test out the forms, browsers, plug-ins, etc..but this problem still happens to some users even after trying out these troubleshoots. Can someone explain if there are other limitations or solution for these users?

    I don't have an answer. However, since your question is not about Acrobat forms, but Designer forms, you need to ask in the LiveCycle forum that deals with Desginer forms.

  • Acrobat 10 and plug-ins for Acrobat 9 incompatibility?

    Hi,
    Today I've installed trial version of Acrobat 10 to check if my plug-in for Acrobat 9 could run for it as well. But after Acrobat 10 launch I've got a window:
    Acrobat.exe - Unable to Locate Component
    This application has failed to start because MSVCP80.dll was not found.
    Quick check over plug-ins shipped now inside Acrobat 10 showed me that they are using now MSVCP90.DLLL library instread of MSVCP80.dll used for Acrobat 9.
    Does it mean that we need to recompile our source code with higher version of MS Visual Studio? If so - what version should we use?
    Does it also mean that our plug-ins prepared for Acrobat 9 are incompatible with Acrobat 10 or there is some way they could still run without recompilation?
    Any comments on this would be highly appreciated.

    I always prefer to use shared libraries, i.e. DLLs, in their supposed shared way and not statically embedded into my executable if I know that some environment is pretty stable and customer is aware of various possible DLLs dependencies. If Acrobat could do some job for me - then I'm happy with that without allocation of additional memory/resources needed in case of static linking.
    So, you don't answer my question. What C++ compiler's version should be used to put MSVCP90.DLL reference now instead of previously used MSVCP80.DLL?

  • 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.

  • Adobe Acrobat Pro X - plug-ins not loaded

    I recently purchased Adobe Acrobat Pro for our company with multiple user licences.  Once installed I noticed a lot of features which were in previous versions are not available.  When I select the “Help” “About Adobe Plug-ins...” tab, almost all of the plug-ins are not loaded. Is this right and if not, how do I fix it. After reading numerous blogs I still do not have an answer – most refer to 3rd party plug-ins but not to this problem. NB: I am not an IT expert, but can help myself fairly well on software. Using Windows 7. Uninstalled Google Chrome as someone suggested it affects the plug-ins (which also did not solve the problem!)

    It's working correctly.
    The Help > About Adobe Plug-ins dialog shows the status of dynamic extensions which ship with Acrobat - not third-party plugins you may have installed yourself. These core extensions are loaded on demand, so if you don't have a document open, very few of them will be loaded. It's why the dialog bothers to tell you their status in the first place.
    Third-party plugins need to be reinstalled if you upgrade to Acrobat X, as the installation folder is different. Some that were written for previous versions won't work with Acrobat X, especially if they're not designed to cope with the Tools Pane or Protected View in 10.1, but they will not appear on that dialog - they appear on the next menu item down, "About Third-Party Plug-ins".
    The UI in Acrobat X is radically different from previous versions, but very few features are actually missing - what are you looking for that you can't find?

  • Can you import software instruments and plug-ins  from Logic Pro to GB

    Hello,
    I purchased Logic 7 Pro and I find it to be way too much for me. Is there a way to take the software instruments from Logic to GB? I am not even sure Logic comes with more software instruments than GB. Do they both rely on the Jam Packs for additional instruments.
    Is there anything else GB can borrow from Logic. I know I can move the sound effects aif files and use them. Just wondering about other plug-ins and the like.
    Thanks!!
      Mac OS X (10.4.6)  

    Here's how you get past the static interruption.
    Make your software track and ignore the static interruption. Its not being recorded into the midi information.
    Then export the track out and reimport it to a new track. Do this twice. Your export/import WILL have static in it but since it was random your two tracks will not have the static in identical places.
    Edit out the static in track one by replacing it with a static-less portion from track two. You'll now have a complete loop with no static interruption.
    xs4sis. The cool thing about the demos is you don't have to program anything just use the presets. Who CAN program those **** synths anyway?
    There are some demos that have a hundred presets to them. I love that!

  • Four FxPack plug-ins for Apple Motion

    Hi,
    just to let you know that I posted four plug-ins I made (Fake 3D, Numbers, Drop Shadow and Grow Bounds) with FxFactory Pro for Apple Motion.
    http://avseikkailuja.blogspot.com/2008/11/tapios-fxpack-10.html
    These plug-ins are totally free but registered version of FxFactory Pro 2.0.5 (or trial time) is required. Hope you find these useful.

    There's a new very advanced Motion 5 / FCPX lens flare plugin called mFlare. It is jus as great as Optical Flares fo AE and it's much cheaper. It includes over 110 presets, dynamic animation engine, 3D lights tracking, 13 lens flare objects and all important stuff. Check it out at http://www.motionvfx.com/mplugs-1.html

  • GB and Plug Ins

    I have two 3rd Party plug-ins (Slate Digital Trigger and IK Media Ampeg Bass Amps).  Both will no longer work in the new GB 10.0.  On top of that, my entire drum tracks are missing that were connected to Trigger plugin.  GB stated that theese two will not work and suggested that I reload both.  This DID NOT solve the problem for using the plugins and my drum tracks are still missing.

    Here's how you get past the static interruption.
    Make your software track and ignore the static interruption. Its not being recorded into the midi information.
    Then export the track out and reimport it to a new track. Do this twice. Your export/import WILL have static in it but since it was random your two tracks will not have the static in identical places.
    Edit out the static in track one by replacing it with a static-less portion from track two. You'll now have a complete loop with no static interruption.
    xs4sis. The cool thing about the demos is you don't have to program anything just use the presets. Who CAN program those **** synths anyway?
    There are some demos that have a hundred presets to them. I love that!

  • Ann: New InDesign Automation Plug-ins

    The Fuga plug-ins allow you to automate almost any InDesign workflow, without any programming. With Fuga you can create everything from variable data printing documents to advanced grids to complex documents like calendars and catalogs.
    Fuga is perfect for data merge type projects that you need more control over, and is a much simpler, faster, and more flexible alternative to scripting.
    Currently we're offering a test user program and live demos/QA sessions, if you're interested in either one post here or e-mail me at [email protected]. Test users will receive three months of Fuga free and additional training and support in exchange for letting us know how they're using Fuga.
    More about the plug-ins:
    Fuga is Free to download and test out for long as you'd like, no commitments, no hassle, and you get $50 in pages free when you create an account.
    Fuga is pay as you print, each normal page is $3.00, each VDP project costs between $3.00 (for up to 1000 pages) to $16.50 (for unlimited pages). See our FAQ to learn if your project is considered VDP or not.
    Work with our pre-created workflows, which you can customize and use in your own projects.
    Lean to use Fuga through our video tutorials and online resources, more of which are in the works.
    Templates can be reused, and the look and feel of documents can be changed easily.
    Workflows (AKA Fuga Flows) can include:
    Conditionals - choose from a large variety options like "if object is overset," "if any object selected," "if text contains" and many more.
    Text manipulation - format text and tables from within a Flow.
    Dynamic InDesign styles - apply different InDesign styles if certain conditions are met.
    Layout Management - advanced control over position, size, margins, layering, and pages.
    And much, much more.
    Works with InDesign CS4, CS5, and CS5.5.
    Fuga also introduces a new Versioning system to InDesign, and a new way of managing grouped objects.
    To download the plug-ins and more, go to http://www.fuga-tech.com.

    Run the Creative Suite Cleaner Tool, install again.
    Mylenium

  • Plug-ins for RealServer 8 and Oracle 9i

    We are in the process of figuring out what we need to stream video stored in 9i with InterMedia using RealServer 8 on Solaris. Oracle says that there is no plug-in for Oracle 9i yet. All the plug-ins I found on OTN, even the 8i ones refer to RealServer G2 or RealServer 7.
    Has anybody been working on getting this plug-in or this configuration working ? We'd like to use the new version of the db, 9i and also the newest version of RealServer. Thanks in advance.

    The plugin can be made to work with RealServer 8 and 9i with a workaround.
    Without doing a workaround, An invalid library message
    occurs when the RealServer loads the Oracle plugin and tries to locate/resolve all the libraries that the plugin needs.
    If a library can't be located then a invalid message is emitted.
    The workaround only works on Solaris.
    The workaround is to, simply go to ${ORACLE_HOME}\lib and
    create a new symbolic link to point to the version 9 library: `ln -s libclntsh.so.9.0 libclntsh.so.8.0`
    To check if things are now OK On Solaris, go to the realServer plugins directory and type `ldd liborclfs.so`.
    This will list the dynamic dependencis for the plugin. If any of the dependecies can not be found/resolved,
    it will list a not found message.
    Larry
    Also see:
    Re: Date format : minutes are showing as one digit when the minute value is 1-9

  • Using CFX Plug-ins: Requires Rosetta to be turned on?

    Hello
    I very much enjoy using the CFX free plug-ins that allow one to black out the edges of imported VHS video, where the static or not well aligned heads on older video, often occurs.
    Since the plugins are not Intel ready yet, the CFX states that you must force your iMovie app to be able to use Rosetta.
    One thing they do not address and I need help on, does this make everything I do in iMovie now become slower because of using Rosetta all the time? Or does it slip into Rosetta only to implement the plug in?
    TIA
    d
    Here is what the workaround is:
    This is a small tutorial on how to enable the option of "Open Using Rosetta" for iLife '06 applications. Here's how you do it. For this example, we will be using iMovie:
    1. Right-click on the iMovie application.
    2. Click "Show Package Contents"
    3. A Finder window should show up entitled "iMovie HD", and there should be a folder called Contents.
    4. Open Contents, and double click "Info.plist"
    5. Scroll down a ways to the bottom, and look for:
    <key>LSRequiresNativeExecution</key>
    <true/>
    6. Change <true/> to <false/>, or just delete it.
    7. Save the file.
    8. Then, open "Disk Utility" and repair disk permissions.
    9. After permissions are repaired, go to /System/Library/ and delete Extensions.kextcache and Extensions.mkext.
    10. Simply reboot, and...
    ...Voila! The "Open Using Rosetta" option should now be under there in "Get Info". This works for all of the other iLife '06 applications.
    EDIT: If deleting Extensions.kextcache and Extensions.mkext doesn't do anything, try moving the application from one directory to another. Also, what will definitely do it, is duplicating the file, however that may take a while depeneding on the speed of your computer and the side of the file.
    Mac Pro 2.66 Mac OS X (10.4.8) 2 Pioneer 110D Superdrives-750gig-1.2gig ram

    It is disappointing indeed, and perhaps a bit more explanation is required:
    "Rosetta Mode" means that your Intel-based Mac is executing PowerPC-code instead of native Intel code. This requires that the processor has to look up every single instruction, translate it, and only then can execute it. This leads to significant performance loss. The mere fact that Apple has managed to get even somewhat (perhaps borderline) acceptable performance out of Rosetta is a testament to the ability of their engineers.
    Our (cf/x) plug-ins currently are PPC-based only. Because of the nature of plug-ins (they are code that is literally plugged into the running code of the hosting application), a plug-in must always be written for the same processor as the host. iMovie can't simply cick into Rosetta and pop out of it randomly. Therefore you must run iMovie in Rosetta to run PPC-based plug-ins, or run it natively, but with non-native plug-ins disabled.
    Which leaves the question why we don't have native plug-ins. The answer is that we dont have them yet as there were significant compiler issues. 'Were', as in 'past tense'. A few weeks ago we had a breakthrough, and are now busily upgrading and porting the PPC code to Universal. Progress is slow, as we need not only to bring the code to Universal, but also have to integrate and test lots of new technology. On two architectures simultaneously. But we are quite sure we'll get there eventually. As always, though, I recommend you do not base any decisions on what I or other people assert, but simply wait and see what gets delivered.
    Cheers,
    -ch
    Please Note:
    I work for cf/x, may profit from posting here, and took the liberty of shamelessly tooting our horn here.

  • All plug-ins already assigned - SE Liveview

    Hi everyone. Some day ago I bought SE Liveview to use with my HTC Sensation. It works fine, no more disconnects every minute and so on.. The only problem is with plugins. I am able to download them from market and to load them in Liveview manager but when i try to add them to Liveview Application it says: "All plug-ins already assigned", not allowing me to add them. I tried to solve this problem searching for solutions down the web and i found a forum where some users say that the possible cause is ICS, and i have it on my Sensation.
    Does anyone of you all have a solution to this problem?
    Maybe is all due to an incompatibility between android 4.0 and live view, so please SONY ERICSSON update your app so we can use this device with our cell phones!!
    Thanks!

    I have not heard of this particular problem before so it might be as you say, a compability problem between the LiveView app and ICS.
    I will pass on your feedback about this and hopefully we'll see a update of the LiveView app soon.
    What are your thoughts about this forum?
    Let us know by doing this short survey: http://surveys.opinion-8.com/SE/SF/en
     - Community Manager Sony Xperia Support Forum
    If you're new to our forums make sure that you have read our Discussion guidelines.
    If you want to get in touch with the local support team for your country please visit our contact page.

  • Preferred package naming conventions for plug-ins?

    Every combination seems to be in use already...
    VIM plug-ins are vim-plugin_name
    XFCE plug-ins are xfce4-plugin_name-plugin
    GIMP plug-ins are (mostly) gimp-plugin-plugin_name
    I plan on making some plug-in packages for a application what dose not currently have any available. So as the topic says what's preferred package naming convention? I personally like the GIMP format best but just figured I'd ask first (should really be in the guidelines IMO).

    Ok well I guess I'll use the third option for now them.
    While we're talking about naming conventions I was just searching for the python cairo library noticed binding library's could do with some guidance to...
    cairo-perl
    pycairo
    ruby-rcairo
    IMO language-library_name would be a nice guideline.

Maybe you are looking for