MXI Files

I received a bunch of MXI Files and loaded them into Final Cut, now that FCP has created the quicktimes in my capture scratch, can I delete the MXI files to free up hard drive space, or does FCP need them as a reference?
Thanks!

Do you mean MXF files? I have never heard of MXI files.
If they are MXF files, from the HVX-200...don't toss them. While the newly created quicktime files do not reference them, they are you MASTER TAPES in essence. Back them up, put them on a shelf.
Do you throw your DV tapes in the trash after you capture them? I didn't think so.
Shane

Similar Messages

  • Can I retrieve the version information in the mxi file using the C   sdk?

    Hello
    I am trying to find a way to get the version information that is available in the zxp package from within the C++ code (I have a mixed C++ / html - JS) plugin
    In the mxi file there is e.g.
      <macromedia-extension id="..." name=".." version="0.1.4">
    Which the extension manager can read and display during plugin installation
    Now I would like to get hold of that 0.1.4 in C++ code by preference using an AI SDK C++ call.
    Anyone knows whether that is possible and how?
    All help warmly welcomed!
    Peter

    The only properties and methods for the Link object are listed in the Acrobat JS API Reference you linked to. JavaScript can set a link action, but once set it is not retrievable by JS.
    You should be able to write an plug-in with that could be added to a user's system to access this data.

  • Install files to desktop in MXI file

    What is the proper syntax to place files on the desktop (PC/MAC) in an MXI file?
    ex.
    <files>
          <file source="sourceFiles" destination="???????????"/>
    </files>

    Thanks Xiaoyi,
    Here is the proper syntax to install, in this case an entire folder, to the desktop:
    <files>
          <file source="sourceFiles" destination="$userhomefolder/desktop"/>
    </files>
    Should work for Win 7 and Mac
    SH

  • Photoshop 13.0.1 breaks mxi files API

    This worked in CS6 13.0.0, and is only showing up after updating to 13.0.1. 
    Our MXI file has the following files that are bundled with the plugin.
    <files>
        <file destination="" file-type="CSXS" products="" source="Dashboard.zxp"/>
        <file destination="$presetsfolder/Actions/Kubota set-up Actions 2.atn" products="Photoshop,Photoshop32,Photoshop64" source="bundled/Presets/Actions/Kubota set-up Actions 2.atn"/>
        <file destination="$presetsfolder/Scripts/Activate Kubota Dashboard.jsx" products="Photoshop,Photoshop32,Photoshop64" source="bundled/Presets/Scripts/Activate Kubota Dashboard.jsx"/>
    </files>
    When installing our plugin after updating to 13.0.1 we get the following error.
    Can't create folder 'Drive:Applications:Adobe Photoshop CS6:Presets:Actions:Kubota set-up Actions 2.atn'.  After hitting OK the installation rollsback and prevents the installation from occuring.

    It turns out this issue was specific to Apple OS X Mountain Lion.
    However, we figured out how to work around this.
    Instead of using $presetsfolder/Actions and $presetsfolder/Scripts, we use the $actions and $scripts tokens instead.  Not sure why this would break with a dot update, but there it is.

  • $ExtensionSpecificEMStore in MXI file

    Hello,
    I took a MXI file I found here as a starting point to make my own one.
    The following section deals with actually copying the files in the proper location:
    <files>
         <file source="content/" destination="$photoshopappfolder/Plug-ins/Panels/myPanel" file-type="ordinary" />
    </files>
    That's fine, it works, files are there.
    I'd rather move the files in the User/Library/Application Support/Adobe/CS5ServiceManager/extensions/ folder (with the java ucf.jar tool I've been able to package and sign the extension, but I prefer to follow the mxi way).
    So I've changed the destination to "$ExtensionSpecificEMStore/myPanel".
    The MXI compiles without any error, the ZXP that's generated seems to work (ExtensionManager CS5 opens it and install the extension) but neither the files are there (in the CS5ServiceManager subfolder), nor I can find the extension in the menu. And by the way, I'm not able to find the files anywhere.
    So, what does "$ExtensionSpecificEMStore" actually means here? The doc says "Attribute for version 5.0 that degrade gracefully. Specifies the folder that stores extension-specific file."
    Thanks in advance for your help,
    Davide

    I'm making progress.
    It seems the correct way isn't to pack everything into a ZXP file (created with ExtensionManager via MXI file) but
    1) Pick the extension files and use the Java ucf packing and signing tool to create a ZXP file.
    2) write a MXI file with extra instructions (for instance, I'm interested in the auto-update feature) which is then used to re-pack the ZXP into a new ZXP.
    So the lines will be:
    <files>
          <file source="myPanel.zxp" file-type="CSXS" />
    </files>
    This works, it installs the extension, that loads nicely in Photoshop.
    Strangely enough, I can't see any file neither in the
    Photoshop/Plug-ins/Panels folder,
    nor in the
    User/Library/Application Support/Adobe/CS5ServiceManager/extensions folder
    So... where are they?! I couldn't be able to find them anywhere, but the extension loads. Puzzling.
    TIA,
    Davide

  • Installing an .mxi file

    I've downloaded the Toolkit for CreateJS to install in my shiny new copy of Flash CS6.  The .zip contains an .mxi file.  When I opened the Extension Manager, all it was looking for was .mxp files.  Can anyone tell me how to get this Toolkit installed?  Many thanks.

    You nedd download the file Toolkit-for-CreateJS.zxp
    double click and go
    http://download.macromedia.com/pub/flashpro/ToolkitForCreateJS/1_0/Toolkit-for-CreateJS.zx pn1UJS39gdKhiOvjbq40lA&sig2=kAHFVdig_nHyqKvhm1qjIg

  • Question about defining [bit] attribute for products in MXI file ( bug ? )

    Hi,
    When I define the [bit] attribute for a product element in xmi file (set to 64) and create the package, Adobe extension manager CS6 denies to install it on a 64-bit system (by saying:) because it is a 64-bit extension!!
    I tried it in two different environments (Vista and 8 - 64 / CS6) with same result!
    Is it a bug (known?) or am I doing something wrong?!
    <product version="8" maxversion="8" primary="true" name="InDesign" platform="win" bit="64"/>
    Any idea would be appreciated, thx, mim

    The bit attribute means the Win32 or Win64 version of the product for which this extension can be installed. It has nothing to do with the Windows OS architecture. Since InDesign CS6 has noly 32 bit version, you don't have to specify bit as "64", even if you are using Windows 64 bit.
    Starting from CC, InDesign has both 32 bit and 64 bit version on Windows. But they have different product name, "InDesign" and "InDesign64" respectively. So if you only want to create the extension for 64 bit InDesign CC, you can specify:
    <product version="9" name="InDesign64" />
    The "primary" attribute is no longer used on CC. The product name of InDesign on Mac is still "InDesign", so "platofrm" and "bit" attributes are unnecessary to be specified in this case.

  • Can I have an Action file install when a ZXP is opened in Extension Manager for CC 2014?

    I have an extension that I'm packaging as a .zxp file.  I'm using Adobe Exchange Packager and setting to the proper install location for the files for the extension.
    However, my extension requires an action file (.atn) is installed in the user's Actions panel.  Of course, I can include the .atn file in my package and copy it to a folder on the user's computer.... BUT, is there any way I can include that .atn file in the .zxp package and when Extension Manager unpacks the files, it INSTALLS the included .atn file into the user's version of Photoshop?  So, this way the .atn file is already installed in the user's Actions panel after the extension installs through Extension Manager...so the user doesn't have to worry about installing the .atn file as well?
    (If there were a folder to place the .atn file into, I could do that, but I do not believe that there are any folders for CC 2014 that hold .atn files in which the panel will read, if at first not installed in the normal way.  I believe this is new for CC, and that the actions are held in a .psp file.)

    I am not sure about the .atn file location but it sounds like you want to create a 'hybrid' extension.
    You create a .ZXP containing your CS extension and then create an MXI file which includes the .ZXP and .atn file.
    You would then wrap this into another .ZXP which will be used as the installer.
    Further information can be found at http://www.adobeexchange.com/resources/7

  • How to configure the zxp so that it will place the related files for the panel in specific folder other than the usual 'C:\Program Files (x86)\Common Files \Adobe\CEPServiceManager4\extensions\' folder ?

    Hi,
    I am Working on a panel for Adobe Premiere pro CC, Now we got a panel set up which will install all the related folders and files which are part of the Extension content folder in the
    C:\Program Files (x86)\Common Files \Adobe\CEPServiceManager4\extensions \Panel\CONFIG folder. But we need to change this location to C:\Users\USER\APPDATA folder or any other user specified folder during installation itself.
    Is there any way to do this from extension builder?
    Thanks and Regards,
    Anoop NR

    Thanks guys,
    Got it !! Hybrid extensions.
    I am using Adobe Extension builder 3 in Eclipse to code and create the zxp for Premiere pro panel.
    Seeing the hybrid extension part in  HTML Panels Tips: #10 Packaging / ZXP Installers | Photoshop, etc. I have added a hybrid extension panel using the bundle manifest editor in the extension builder. it creates an mxi file automatically with all the properties, I have to change the maximum host version number in the mxi file in order to make the extension work in the Premiere pro CC 2014. Using the Hybrid option in the Bundle manifest editor we can choose a set of folder paths for placing the files during installation itself and later can be used using 'csInterface.getSystemPath(SystemPath.CODE)' from javascript functions to modify them.
    Thanks for your relpies,
    Anoop NR

  • XML validation error while parsing MXI Manifest

    Hi,
    I have created an hybrid extension for Photoshop. I want to upload my extension on Adobe Exchange. during the upload process I get an error,
    "XML validation error while parsing MXI Manifest: Declarations can only occur in the doctype declaration. Line: 19 Position: 791 Last 80 unconsumed characters".
    The error description specifies that description in MXI file is not valid. Below are the contents of my MXI file.
    <macromedia-extension
               name="yyy"
               id="com.yyy"
               version="1.0.0"
               type="object"
               requires-restart="true">
              <author name="abcd" />
              <products>
              <product familyname="Photoshop" maxversion="" primary="true" version="12.0"/>  
              </products>
    <description>
              <![CDATA[
    <p><font size="14" color="black"><b>abcd</b> qwertyuioipafgjhkjljljklkjl
    <br><br>
    Open Extension via: Photoshop top menu > Window > Extensions > abcd.
    <br><br>
    Online support at: <a href="http://www.abcd.com/help.php">http://www.abcd.com/help.php</a></font></p>
    <br>]]>
    </description>
    <ui-access>
              </ui-access>
    <license-agreement>
    </license-agreement>
    <files>
                <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.html" products="" source="zxp-support/Description/abcd.html"/>
                <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.png" products="" source="zxp-support/Description/abcd.png"/>
                <file destination="" file-type="CSXS" products="" source="abcd.zxp"/> 
                <file destination="$automate" file-type="plugin" platform="mac" products="Photoshop" source="mac/abcd.plugin"/>
                <file destination="$automate" file-type="plugin" platform="win" products="Photoshop32" source="win32/abcd.8li"/>
                <file destination="$automate" file-type="plugin" platform="win" products="Photoshop64" source="win64/abcd.8li"/>
    </files>
    </macromedia-extension>
    Can anyone please point out why am I getting the error?
    Thanks

    Hi CarlSun,
    Thanks for the reply. I have made the changes suggested by you.
    I have few queries:
    1.  Can we use attribute "source" in the description tag?
         I have created a local html page and specified it in source attribute. but the Extension Manager CS6 did not render the local html page and displayed      the following:
         No description avaliable. Click the following link for more details.
         "http://www.abcd.html". Is it possible to display a local html page in Extension Manager CS6?
    2. Can I display an image (png) in CDATA under description tag? If yes, then can you please guide me how can I do so?
    3. As suggested in tech notes MXI file must include UTF-8 encoding as header (<?xml version="1.0" encoding="UTF-8"?>). The MXI I am using does      not have this header. Do I need to include the header?
    Thanks

  • Does ucf.jar handle spaces in file names?

    As far as I can see, it does not:
    humber:zxpdir williamg$ find .
    ./foo
    ./foo/foo bar
    ./foo/foobar
    humber:zxpdir williamg$ java -Djsse.enableSNIExtension=false -jar ../../../adobesigningtoolkit/ucf.jar -package ../foo.zxp -C /Users/williamg/Projects/zxptesting/build/zxpdir/ .
    humber:zxpdir williamg$ unzip -l ../foo.zxp
    Archive:  ../foo.zxp
      Length     Date   Time    Name
           41  08-26-13 19:46   mimetype
            0  08-26-13 19:46   foo/foobar
           41                   2 files
    That appears to indicate that the file “foo/foobar” is being added to the zipfile, but that “foo/foo bar” is not.
    Is this a known bug, … and if so, is there an ETA for it to be fixed?
    As an aside: is there a way to determine the version number of the ucf.jar that I have? “-version” doesn't seem to be available on the command line.

    According to the documentation:
    “If you have created your product using earlier versions of these tools, or the free Creative Suite SDK, or if it is a script or  C++ plug-in, or some combination of these things, you can manually create a manifest MXI file and package your delivery files into a ZXP, using the command-line utility in the Packaging and Signing Toolkit. See the section Packaging Manually”
    (The link points to the section which indicates that the UCF command line tool should be used to create the package.)
    Is this documentation wrong?
    The Packager utility indicates that it supports the following types of content for Photoshop:
    Actions (ATN)
    Brushes (ABR)
    Gradients (GRD)
    Patterns (PAT)
    Scripts (JSX)
    Swatches (ACO, ASE)
    That does not include filter plug-ins (.8bf on Windows, .plugin on Mac), and so it does not apply to my use case.
    (Furthermore, it does not appear to be possible to run the packager tool from the command line, meaning that it is not useful to me since it would be very difficult to integrate it with our build system. Is it possible to run the Packager from the command line?)

  • ActionScript 3.0 MXI woes

    I'm having an issue creating an MXI that installs a handful
    of .as files into a location that Flash CS3 projects can see on
    their default classpath. Unfortunately, the default classpath for
    AS3 projects is $(AppConfig)/ActionScript 3.0/Classes but this is
    not accessible from any of the location tokens the Extension
    Manager knows about.
    For previous releases I've been able to specify the default
    classes directory via the $flash token in my MXI files but there's
    no longer a good way to do this without explicitly specifying in a
    ReadMe where a user should install the files...which kind of
    defeats the whole purpose of having the nice automatic extension
    manager.
    Has anybody else run into this and found any solutions?
    Thanks!

    Nope - the only workaround I can see, which isn't all that
    helpful, is to pop up a prompt asking the user where they'd like to
    install the classes. This, of course, pretty much defeats the point
    of having the installer at all...

  • Need help copying file into main configuration folder

    I'm trying to create an extension for Dreamweaver CS3 and I need to place a DLL in the
    C:\Program Files\Adobe\Adobe Dreamweaver CS3\configuration\SourceControl
    folder of the actual application directory rather than a user directory. To do this I have the .mxi file and a javascript startup file. All attempts to place the DLL in the correct folder have resulted in the file being placed in the user directory. Most things work from the user directory but the SourceControl folder is an exception.
    Is there a way I can force a file to be moved to the main SourceControl directory using the .mxi or in javascript? Or is there a way I can register my DLL some way or do something else to make it work? The API and e extension guide have not been useful.

    Open iTunes without your phone connected. Then, as you connect iPhone to your computer, press and hold Command-Option (on a Mac) or Shift-Control (on a PC) until you see iPhone appear in the sidebar. This will prevent automatic synching. Then use the iTunes File Menu -> Transfer purchases from XXX's iPhone.
    If you still gave problems, you can download your applications again. You have to click the "Buy" button and you will get the warning about your credit card being charged, but then you will be offered the chance to dowsnload again for free. Complete instructions are here: http://support.apple.com/kb/HT2519

  • CS6 JavaScript API .mxi path

    How can I call the .mxi using the JavaScript API?
    In previous versions of the plugin I could easily call upon the mxi file to grab a token definition value using the dw.getConfigurationPath().
    As in the following example: dw.getConfigurationPath() + ’/Extensions/myextension.mxi’;
    The reason for storing the path in the mxi is because it is the only place that I know will dynamically create the path such as: Macintosh HD:Users:<UserName>:Desktop:MyFolder: or C:\Users\<UserName>\Desktop\MyFolder respectively when I enter a token definition of $userhomefolder/Desktop/MyFolder.
    However now that the .mxi file has been moved to the extension manager folder in CS6 I can no longer use
    dw.getConfigurationPath(). My question is how do I now obtain the .mxi path now?
    Thanks.

    You need to post scripting questions in the Adobe Photoshop Scripting forum.
    -X

  • File info Panel doesn't show up in CS6 apps

    Hi all,
    I have compiled a File Info Panel with EB2. It opens fine in CS5.5 apps but it's not accessible with CS6.
    I can't see any settings in EB2 to have both versions supported. I also tweaked the manifest and get the ZXP recompiled but then althought the panel does appear, the content isn't built.
    Any hint on what's happening ?
    Best,
    Loic

    Hi Loic,
    Do you know what directory you are installing the panel to? Is it /Users/<username>/Library/Application Support/Adobe/XMP/Custom File Info Panels/3.0/panels/
    Can you try placing the panel inside of  /Users/<username>/Library/Application Support/Adobe/XMP/Custom File Info Panels/4.0/panels/ instead. If your panel does not display when you open the FileInfo dialog on your development machine then you may need to adjust the flash player trust file so it is pointing at the 4.0 directory; /Users/<username>/Library/Preferences/Macromedia/Flash Player/#Security/FlashPlayerTrust
    In the MXI file update the paths so it deploys to the 4.0 directory.
    I will forward this issue onto the Extension Builder team as it seems supporting FileInfo panels between suite versions is not currently available.
    Kind regards,
    Lea

Maybe you are looking for