Image Resizing on XML Import

HI there,
I have a Captivate 5.5 project and when I simply export an XML and immediately import again my buttons resize automatically for some reason.
Has anyone come across this before?
IMAGE BEFORE BELOW
IMAGE AFTER IMPORT
Any help appreciated.
Thanks
Keith

Hello again
I'm a bit confused. I'm sure that the client is always right, but what is gained by exporting as XML, doing nothing, then importing the XML right back in? Sounds like a flaky workflow to me. And maybe that's what is confusing Captivate. If no changes have been made to anything, perhaps it's getting confused.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

Similar Messages

  • How to delete empty tags after xml-import

    Hello collegues,
    I'm totally new in this forum so excuse me if I make a mistake, but I've a little question.
    I've imported text and images with a xml-import but sometimes empty tags (the colored invisible blocks) are in my text, with the result that I can't Find/Change on double-returns.
    Does anybody know an awnser to this matter? I would love to write an apple-script that will find/change this so i don't have to look after all my pages.
    Thank you very much in advance.

    ThePictureCreator wrote:
    ...I can't Find/Change on double-returns.
    What's your search query? I think you should be able to, with either a grep find of "\r+" or a normal text find of "^p^p". InDesign pretends like the tag-holding characters aren't there for the purpose of search. But you will lose the empty elements along with the extra returns. Maybe that is the problem?
    Jeff

  • [JS CS5] Resizing graphics after importing XML, but before placing on page

    I've been looking for an answer for this for a long time, and judging by the other posts here, many others are also.
    Given an XML file consisting of:
    <root>
         <products>
              <product>
                   <image href="file:///filepathhere"/>
                   <description>
              <product>
                   <image href="file:///filepathhere"/>
                   <description>
    I can import this into a layout, and drag the products element to a text frame. All the images appear inline, and then I run a script that uses XML Rules to locate the images, resize the image frames, and apply an object style. The trouble is, that once in a while the images references by the XML are so enormous that they simply exceed the bounds of the pasteboard, and things blow up.
    So what I want to do instead, is to somehow resize the images to a manageable size BEFORE I drag the products element into a text frame.
    Ole posted a possible solution here: http://forums.adobe.com/message/1108974#1108974
    In that post, he says that "If you're using CS4, can use the resize method to resize graphics that have not yet been placed in a layout." I've been trying to implement his "rough" script, and I can't work it out.
    This is what I have:
    var myRuleSet = new Array (new processImage);
    with (myDoc) {
         var elements = xmlElements;
         __processRuleSet(elements.item(0), myRuleSet);
    function ProcessImage(){
         this.name = "ProcessImage";
         this.xpath = "/root/products/product/image";
         this.apply = function(myElement, myRuleProcessor){
              var myImage = myElement.graphics.item();
              myImage.resize(CoordinateSpaces.innerCoordinates, AnchorPoint.centerAnchor, ResizeMethods.multiplyingCurrentDimensionsBy,[.1,.1]);
              myImage.parent.fit(FitOptions.frameToContent);
              return true;
    "myImage" isn't valid in the script above. Does anyone know if this is possible, and if so, what I'm doing wrong? Thanks for any light anyone can shed on this!

    After spending some more time with this today, I've realized that what Ole was talking about here: http://forums.adobe.com/message/1108974#1108974. He said that "If you're using CS4, you can use the resize method to resize graphics that have not yet been placed in a layout."
    What he was referring to was graphics that are in overset text, not graphics in XML that have been imported but not placed.
    So, there is no way that I know of to process images and image frames in imported XML that hasn't been placed in the layout yet.
    But, a good workaround to my problem that I developed was to first place the imported XML into a very tiny temporary text frame, so that all images are immediately overset. Then I process the images to a manageable size using the resize method, per Ole's suggestion. Then, and only then, do I move the content onto my layout. This avoids problems with graphics being pointed to in the XML that may be too large for the pasteboard.
    I hope this obscure technique is useful for someone!

  • InDesign CS3 Scripting XML Import Multiple Images into same Text Frame

    I am having trouble importing multiple images into the same Text Frame using XML import. I imported 5 images into the text frame. However, all 5 images are laying on top of one another. Does anyone know if there is a way to have all images laying out like how Microsoft Word handles inline images, i.e., laying out next image to the right of previsous image in the same line and if there is not enough space left in the line, then wrap to next line. Thanks in advance. I understand I could use JavaScript to do post import processing, e.g, calculate the image size and place each images accordingly. But I am trying to see whether there is a way to do this without scripts.

    You can apply an object style to all anchored images by script. A text frame containing main flow should be selected.
    var doc = app.activeDocument;
    var textFrame =  app.selection[0];
    var rectangles = textFrame.texts[0].rectangles;
    if (rectangles.length > 0) {
         for (var i=0; i < rectangles.length; i++) {
              rectangles[i].appliedObjectStyle = doc.objectStyles.item("Cover");
    However, there is a better approach:
    Step 1
    Create place holders for a single "Book" element and format it as needed -- apply an object style to the cover.
    Step 2
    Import the xml file -- the placeholders are replaced with data from the 1st xml element
    Step 3
    Drag & drop the element containing all "Books" elements into the main flow -- all elements are placed and formatted the same way as in step 1.
    Finally, add a new page, click the overset text icon and autoflow text to add pages so that to fit all the text.
    Hope this helps.
    Kasyan

  • Importing causes pixelation and image resize doesn't work - Elements 13 Macbook Pro

    As I import any photos, from any place, when I open them, they appear pixelated. I watched some tutorials and used image resize, which doesn't do anything but change the size, even if the resolution is turned up. I also saw something about preferences, which didn't do anything, all versions are up to date. What is the problem? Why will it never change?

    Hello Smis,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I understand you are having issues with your HP Monitor on your MAC. I am providing you with an HP Support document: Updating a Monitor Driver, where it states under the sub-heading Using HP monitors on a Mac "HP monitors are not supported in a Mac environment. However, newer Macs use graphics with VESA modes and can display to most HP LCD monitors. To do this, connect the monitor to the Mac while the Mac is off, and then turn on the MAC. The monitor should operate at 60Hz. The INF and software for the HP monitor are for Microsoft Windows and cannot be run in a standard MAC OS environment."
    This being said all I can advise is that you check to see that the monitor is set to operat at 60Hz and contact Apple for assistance if that does not get your monitor displaying correctly.
    I hope I have answered your question to your satisfaction. Thank you for posting on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

  • Ways to implement image resizing using plug-ins?

    Hi Photoshop developers,
    I'm a developer with a few Photoshop filter and selection plug-ins under my belt, and I have a good understanding of the SDK and tools and suites it provides. My next project is an algorithm for enlarging/resampling images to different pixel dimensions. I'm wondering if anyone has any suggestions for or experience with the best combination of plug-in types to implement this.
    Clearly, I can't just write it as a filter plug-in, since there is no way to change the image dimensions from within a filter.
    I'd like the resized image to remain within Photoshop (as a new window or in the original one), so an export plug-in on its own is not sufficient.
    Import plug-ins seem promising, since they allow the creation of a new document of the required size. However, as best I can tell from the Photoshop 6.0 SDK documentation, import plug-ins cannot access the image data from other open documents (or even the clipboard), nor do they provide any support for channel ports and the Channel Port suite.
    My best idea at this stage is to create an export plug-in to provide the user interface and calculate the resized image, and then an import plug-in to import the resized image back into a new window. (I'm supposing a further automation plug-in would then be written to perform this export/import sequence.) The difficulty I see with this approach is how to communicate the resized image data between the two plug-ins. Since the resized image will potentially be very large, the ideal solution would be to store it in channels managed by the Channel Ports suite. However, I cannot see how the channel ports created in the export plug-in could be communicated to and used by an import plug-in. The alternative would be for the export plug-in to save the resized image to a temporary file on disk, however this seems unnecessary.
    So, my questions, specifically, are:
    a) Is it possible to create new channels using the Channel Ports suite (sPSChannelPorts->New()) in one plug-in, and have those channels persist to be used in another plug-in?
    b) If so, how would the channel ports be communicated between the plug-ins?
    c) Alternately, are there any alternative architectures available for implementing an image-resizing algorithm using the plug-in types that are available for Photoshop developers.
    Any responses would be greatly appreciated; I know this is a low-traffic forum...
    Thanks,
    Matthew.

    I would make an automation plug-in and a filter plug-in.<br /><br />1) Run the automation which runs your filter to gather current image <br />information<br />2) Create a temp file of the new document<br />3) Make a new document<br />4) Call the filter again to reload the temp data on disk<br /><br /><[email protected]> wrote in message <br />news:[email protected]...<br />> Hi Photoshop developers,<br />><br />> I'm a developer with a few Photoshop filter and selection plug-ins under <br />> my belt, and I have a good understanding of the SDK and tools and suites <br />> it provides. My next project is an algorithm for enlarging/resampling <br />> images to different pixel dimensions. I'm wondering if anyone has any <br />> suggestions for or experience with the best combination of plug-in types <br />> to implement this.<br />><br />> Clearly, I can't just write it as a filter plug-in, since there is no way <br />> to change the image dimensions from within a filter.<br />><br />> I'd like the resized image to remain within Photoshop (as a new window or <br />> in the original one), so an export plug-in on its own is not sufficient.<br />><br />> Import plug-ins seem promising, since they allow the creation of a new <br />> document of the required size. However, as best I can tell from the <br />> Photoshop 6.0 SDK documentation, import plug-ins cannot access the image <br />> data from other open documents (or even the clipboard), nor do they <br />> provide any support for channel ports and the Channel Port suite.<br />><br />> My best idea at this stage is to create an export plug-in to provide the <br />> user interface and calculate the resized image, and then an import plug-in <br />> to import the resized image back into a new window. (I'm supposing a <br />> further automation plug-in would then be written to perform this <br />> export/import sequence.) The difficulty I see with this approach is how to <br />> communicate the resized image data between the two plug-ins. Since the <br />> resized image will potentially be very large, the ideal solution would be <br />> to store it in channels managed by the Channel Ports suite. However, I <br />> cannot see how the channel ports created in the export plug-in could be <br />> communicated to and used by an import plug-in. The alternative would be <br />> for the export plug-in to save the resized image to a temporary file on <br />> disk, however this seems unnecessary.<br />><br />> So, my questions, specifically, are:<br />><br />> a) Is it possible to create new channels using the Channel Ports suite <br />> (sPSChannelPorts->New()) in one plug-in, and have those channels persist <br />> to be used in another plug-in?<br />><br />> b) If so, how would the channel ports be communicated between the <br />> plug-ins?<br />><br />> c) Alternately, are there any alternative architectures available for <br />> implementing an image-resizing algorithm using the plug-in types that are <br />> available for Photoshop developers.<br />><br />> Any responses would be greatly appreciated; I know this is a low-traffic <br />> forum...<br />><br />> Thanks,<br />> Matthew.

  • Layout Problem in XML Import

    Dear All,
    I am new in InDesign. I have some problem. I am using InDesign CS3. I want when XML file will be import layout should be come according to our specification with image. Is it possible any script or XSLT. If yes please give me some guiduence.
    I have done XML to Tagged Text using XSLT. But i want to go through XML Import options.
    Anyone please help me...
    Thanks and Regards,
    Byomokesh

    If possible, purchase a copy of A Designer's Guide to Adobe InDesign and XML: Harness the Power of XML to Automate your Print and Web Workflows.
    This book will answer most questions you might have about using XML with InDesign.
    For a short answer, you need to first create styles, then map them to the tags, then import the XML. I will send you an example via email (the author emailed me directly).
    Best regards,
    Tad

  • In iPhoto how do I stop files from auto resizing as they import? I don't want my files reduced to 72. The option to choose size on the export menu not suitable for up sizing, as you can't restore the quality removed?

    in iPhoto how do I stop files from auto resizing as they import? I don't want my files reduced to 72. The option to choose size on the export menu not suitable for up sizing, as you can't restore the quality removed.

    Short answer: They are not resizing, there is no quality lost. The dpi is only set when you decide what size you're printing at
    Longer answer:  Dpi means nothing in the digital world of your computer. There are no "inches" to have "dots per..." Size is measured in pixels. That's the same on your camera. It doesn't take 10 x 8 or 6 x 4 shots. It takes shots measured in megapixels. For instance 4,000 x 3,000 is a 12 megapixel camera.
    Using that example, that shot from that camera has 12 million pixels. So that's how many "Dots" there are. To decide the ratio of dots per inch, you now need to decide the "inches" part. And that's printing. Print at 10 x 8 and the dpi will be 4,000/10 or about 400 dpi. At 6 x 4 then it's 4,000/6 or 660 dpi. Work the other way: Print at 300 dpi and the resulting image will be about 13 inches on the longer side.
    So, your photo as a fixed number of pixels. Changing the dimensions of the print will vary the dpi, changing the dpi will vary the dimensions of the print.
    For more see http://www.rideau-info.com/photos/mythdpi.html
    Regards
    TD

  • Image resizing & conerting to byte[]

    I'm working on a servlet. I have an image stored in a database
    (jpg or gif), and i need to resize it before sending to browser.
    I know how to create an Image from a byte array, and resize it,
    but how can i create again a gif/jpg file from the Image object
    and transform it again to a byte array to send to client?
    Thanks!!

    Hm...that was only half the answer...
    For jpg encoders, there is one in rt.jar that works, but it requires some manual labor...and starting up the awt event thread which is sort of costly.
    Here's an example of how to encode a file to jpg.
    (You must include rt.jar in the classpath for it to compile and run)
    import com.sun.image.codec.jpeg.*;
    import java.io.*;
    import java.awt.*;
    import javax.swing.*;
    import java.awt.image.*;
    public class Test extends JFrame
         public Test()
              super("JPG encoder");
              getContentPane().setLayout(new GridLayout(2,1));
              ImageIcon theIcon = new ImageIcon("image.gif");
              int w = theIcon.getIconWidth();
              int h = theIcon.getIconHeight();
              getContentPane().add(new JLabel(theIcon));
              setVisible(true);
              BufferedImage theImage = (BufferedImage)createImage(w, h);
              theImage.createGraphics().drawImage(theIcon.getImage(), 0, 0, Color.black,null);
              setLocation(300,300);
              try
                   FileOutputStream theStream = new FileOutputStream("image.jpg");
                   JPEGImageEncoder theEncoder = JPEGCodec.createJPEGEncoder(theStream);
                   theEncoder.encode(theImage);
                   ImageIcon theNewIcon = new ImageIcon("image.jpg");
                   getContentPane().add(new JLabel(theNewIcon));
                   pack();
              catch (Exception e)
              {e.printStackTrace();}
         public static void main(String[] args)
              new Test();
    }You can easily change that FileOutputStream to a ByteArrayOutputStream and then just extract the bytes...

  • Discussion about image resizing

    Hi,
    I'd like to get some point of views regarding image resizing ....
    Handling images is always a lot of work, having to resize, give names, then alt tags then titles  etc ..... Depending on the design, on one page one image has to be 200px wide , on another 150 and in the gallery 600px ..... Hw do you handl this, do you really resize all images so they fit where they need to be , and do thumbs everytime or do you use automatic resizing .... Server side, css ?
    In an ideal world I would like to have just one folder with one version of all images and be able to use those ones without having to resize them manually .... What do you reckon ?
    Obviously, I'm not talking about high resolution images or full screen images but images that would rnge between 400 to 600px wide for instance. Do we still have to think about server load and download speed today in 2012 ? Do you think or know it really affects ranking on search engines .... well ... debate is open , I'm really interested in getting all point of views as they surely be very different from one user to another !!

    In the old days, when connection speeds were modem-sized, it was important to be conservative with regard to page weight.  In this era of high-speed internet, it's not so much.  My pages that use lots of full-size and thumbnail images will often just use the larger image resized for the thumbnail.  Resizing down is fast and cosmetically acceptable. 
    Also, I'm certain that image size has no impact on search engine ranking.

  • Copy, Move, or XML import drops non 1080p clips with no warning

    What are the limitations on moving, copying, or exporting/importing XML?
    It seems that FCPX dropped all my clips that are not 1080p. And to make matters worse, FCPX went through the motions like it was moving/importing, but ignored the clips that were not 1080p and gave me no warning.  So I worked on the project for 2 days only to discover that part of the clips were missing.
    Has anyone else found this problem or do I have a configuration problem.
    I have some Gopro video and timelapse that are large frame sizes, 2.7k and whatever the medium timelapse stills were set to.  These are the problems.
    This seems to work with XML on the same computer, but when moving to a second computer is were the problem comes in.  The move/copy either events or clips dropped all my odd sized video clips, even on the same computer.  Again no warning.
    You can import the original clips but not copy, move, or export/import XML to another computer.  I thought XML export was the recommended way of working in a distributed enviornment with FCPX 10.1?
    Configuration:
    2 computers
    both OSX 10.9.2
    both FCPX 10.1.1
    all media is external to the libraray, so it needs to be re-linked when moved.
    It does appear that if I copy the library to the other computer that everything is OK, but not with XML.
    Should export/import XML work with non-standard frame sizes?  It would seem that if you can import the original clip, that you should be able to copy, move, export/import XML.
    Rick

    Thank Louis for the reply.
    My problem is not the media, but clip instances.  I have the media on both computers.  For some reason the unlinked images are not loading accept for the 1080p.  When the clips show up, I can re-link them without problems.
    I re-ran the XML import/export between computers, doing a complete round trip.  This time it worked!  I apparently am having a repeatability probelm, so I have some more work to do.
    However when I did a Copy event to Library command, only the 1080p clips appeared.
    Any suggestions on how to make this more repeatable?  Like emptying a cache or something.
    BTW  the clips that were dropped are 2704x1524 - would that make any difference?
    Rick

  • Insane XML Import, Huge Project, Duplicate file names work around...

    I planned on kicking off my journey attempting to edit a massive multi year documentary on FCPX with a nice introduction of the blog I'm going to keep about the experience, but I've run into a bit of a roadblock, or maybe major speed bump at least before even getting to that point. I wanted to share what is working as a work around for me and you guys can tell me how I'm doing it wrong.
    Ok, I will try to explain this as succinctly as possible. I'll write in somewhat stream of consciousness just to try and get through it quicker... Basically, after discovering the work around below, I am now utterly confused on how FCPX handles the relationship between its own database of where media is stored, and the actual media itself. I have plenty experience on FCPX now, probably done 30-40 pro commercial jobs on it over the last year since XML became doable as I'm also a Resolve Colorist and all the FCPX projects where hardcore coloring product spots. For commercial work, I never needed to worry about splitting up footage up over multiple Events. Everything, all in one, FCPX handled it no problem. (well the occasional beach ball, but that seems to be a thing with FCPX in general)
    This will be my 10th feature documentary as an Editor. Every one before it was either on Avid's many flavors over the last 12 years or FCP Studio. When this new film came along, I made the decision a few months ago to use FCPX for a few reasons, but mostly because I'm insane and I like to try to mix it up for myself in a career that can get stale quick if you aren't willing to be that way. The film was shot over 2+ years, every shoot was multi cam 5D (yes i know, looks great, but please kill me), I haven't done the math on length, but there is over 10,000 clips of video (this is actually medium in size compared to what I've dealt with before). Its 5D, so theres external audio for everything. FCPX's syncing is great, but I've learned that theres an unsaid window of heads and tales clips must fall within to sync properly with the nearby clips, if they are too far apart FCPX gives up. One shoot day could have 3 cams, 50 clips each, and 2 audio files to sync to, FCPX simply cannot handle this, so off to Plural eyes they went, no problems.
    Ok, all this is relevant eventually I swear! Again, in the past, all in one event, no problem. I tried for fun to bring all media into one Event on this film. It worked, but there is a 10+ second spinning beach ball for every single move you make, so thats no good. Ok, I'll separate the Events out to, lets say, each shoot month. Well that's dumb, in verite documentary, any shot could be the first, any shot could be the last, you need a command over all searchable footage at all times. Shift selecting all events to search *****, and it actually takes longer for FCP to reload each event each time than it does to just have the one massive one. So no go there. Next hair brained idea... What if make a new Event that is just Compound Clips of all the other Event's contents and do more with Markers and Favorites in logging that I was planning to parse it all out. That way I'm working with and FCPX is dealing with 50-60 clips instead of 10,000+ Quick test, Cmd-A, Opt-G, boom, boom, boom, move all to dedicated to Event, hide huge Event, BEHOLD, that works! FCPX chokes a little bit on the insane length of some of the clips, but searching, and general performance is back on par!
    So your saying to yourself "Ok *********, sounds like you figured it out, what's the problem." Well to you I say, "Not so fast!" Remember, that was just a quick test using the media I had imported into the massive 10,000+ clip Event. To do this project proper, I am having to import Multicam sync'd XMLs from Plural Eyes. And this is where it all starts to fall apart. A little foreshadowing for your eager eyes. 10,000+ files all shot with multiple 5D's over the course of years. What does that mean? many, many duplicate file names!
    FCPX as well all know irritatingly imports XML's as new Events, not into existing ones. This obviously takes a lot of burden off media management because with a new Event comes a new database referencing its own version of the raw media. All well and good, and I'm betting its starting to click for some if you advanced users where I'm finally going with this. So I have 50 or so XMLs to bring in, all done no problem. Now I want to replicate that singular Event like I did with the Compound Clip test and have it all in one place to be my master as extensive logging begins for easy searching once editing begins. Highlight the Events, click Merge Events. NOPE. I get a new "Kill Yourself Now" error (a term I coined for Out of Memory and General Error messages in FCP Legacy meaning there ain't much you can do about it): "Two or more files have the same name. Change the names and try again, because I don't know what the **** to do with them." Ok I made up that last part but that's basically what it's saying. Just take the variable out of the equation, this happens with every which way you could try to get the clips together. Merge Events, dragging events on top of each other, dragging just the Multicam clip alone, nothing gets passed that message. What's worse is that while Batch Renaming seems like a solution, the renames do not populate inside the created clips and there is no way to Batch Rename those. Renaming everything at the finder level isn't so great because then I'd have to resync and theres an offline/online thing going here where the film has to be reconformed eventually.
    Basically, I've found that FCPX handles media management in completely different ways depending on whether you are importing into one Event yourself or doing essentially what is a new import with FCPX moving or merging Events. If you bring in all the media to one Event, on a macro level FCPX goes through file by file making aliases referencing the master file. If it hits a duplicate, it makes a parenthesis counter, and keeps going. And with the genius of FCPX metadata, that file name doesn't even matter, you can change it at the Finder level and FCPX will keep the link intact. BUT for some reason if you try to do this outside the realm of a single Event and combine files after the fact a different process takes over in creating this database system and can't handle the duplicates. I can't totally figure the reason other than it probably is scared to change the originally referenced alias to something else (which it shouldn't be scared of since Merge Events deletes the original anyway).
    This is where it gets INSANE and where I lose all understanding of what is going on, and believe me it was a delicate understanding to begin with. It comes in to play with the work around I figured out. I make the master Event with the 10,000+ clips. Then I import all the XMLs as dedicated Events. Now, I then drag the Multicam clips into the master Event, it WORKS! just takes it, no "Kill Yourself Now" error. Stranger still, now with the switched referenced Event, it even takes into account which aliased duplicate file name it's referencing in the Original Media folder. Somehow, it's taking into account the original file path and saying "Ok, I see 5 instances of MVI_5834.mov. Based on the original file path or maybe creation date or god knows what, it must be MVI_5834 (fcp3).mov." It connects perfectly. I can even remove the old XML imported Event with no problem. Crazier yet, I can now move those again to the dedicated Event I wanted originally that only contains those Multicam or Compound Clips.
    So instead of going straight from A to C, going from A to B to C works even though that actually seems way more complicated. Why can't FCPX handle Merge Events and dragging clips the same way it handles media imported into a single Event. And weirder still, why can't FCPX handle the (fcp1,2,3...) appending in the same scenario. But if the appended links are already there, No Problem. And for the love of god, it'd be nice to important XML's into existing Events and make the correct referencing happen right from the get go, which is really the source of all the above headache. I'd have no problem helping FCPX with a little manual pointing in the right direction just like any other NLE needs.
    Ok, having said all of that crap above, my question is, have I missed something completely simple I should have done instead? Now that I have everything in place how I originally envisioned, I think I will still play around a little bit more to make sure FCPX is really going to be able to handle this project. I'm at a stage right now where going another direction is still an option, although the dare devil in me wants to make this work. Media management aside, once you start editing on a FCPX timeline, its hard to go back to anything else. Apple is going to have to figure out some way not to access to everything at all times to work fluidly or big projects like this are never going to be practical in FCPX.
    Sorry for the long confusing post....

    I'm having the exact same problem, but I know nothing of ruby scripts. I've exhausted my resources with tech support, and after literally hours of work with them it seems I now am faced with either re-rating each individual song, or pointing iTunes to each song that it can't locate. Is yours a solution that could help me? How can I find out more about Ruby Scripts? Thanks for your help, hellolylo (or anyone else who might also be able to help...)
    Kenn

  • Error messages during XML import of Project Pro 2010 files

    Hi folks,
    I'm trying to diagnose a couple of sick Project Pro 2010 files loaded from Project Server by saving them locally as XML files and then reimporting (not connected to the server during import).  The anomalous behavior exhibited by both files
    is that one takes 15 minutes to load from the server, while another takes over 20 minutes. These are not typical load times for this server.  In both cases, Project consumes about 25% of the CPU during the load process. There's little network I/O
    while this goes on, and when externally linked schedules are loaded to the cache, they load very quickly.  Other than the long load times, the schedules appear to be behave normally, except for some very odd print preview behaviors in one of the schedules
    that I asked about in a different thread (among other things, the default print preview start date is 17 years after the default finish date, and the finish date is about 11 years before the schedule actually starts).
    The questions I'm asking here are about errors I see when I try to import the files exported as XML, and whether they might provide any clues as to what's causing the load time issues.
    When attempting to import one of the files saved as XML, a pop-up appears that says, "The actual finish date is before some of the previously entered timephased actual work values. If  you continue with this operation, Project will truncate
    some of the previously entered timephased actual work values. To continue, click OK..."
    When attempting to import the other file saved as XML, I get a series of pop-ups identifying a series of tasks that say, "The timephased edit will cause 'Develop Requirements Review Meeting Mi...' to start before 'Conduct Requirements Review"
    finishes.  As a result the task link cannot be honored.  You can: () Continue. Keep the timephased edit and ignore the link.  () Cancel. Ignore the timephased edit.  (OK/Cancel/Help)".
    Interestingly, both files contain external Project Server predecessor / successor links.  In the case of the first file, the XML import just appears to strip those out.  In the case of the second file, I get a long series of pop-ups (with
    some buggy text inserts) in pairs.  The first message in the pair is typically "An import error occurred.  The element <PredecessorLink> in the <Task> element with <UID>=611 has invalid data.  Verify that the file
    name and path are correct, and then try again. (OK)", where the indicated UID varies. The second pop-up in the pair appears to have a buggy text constructor and looks like this, with "[stet]" indicating the apparent buggy text inserts,
    "An import error occurred.  The element [stet] Verify that the file name and path are correct, and then try again. [stet] in the 309 element with <UID>=7 has invalid data. [stet] ^4 (OK)"
    In the second pop-up of the pair, the "xyz element" varies, but the "<UID>=7" reference and "^4"  are consistent. In the XML, UID 7 appears to refer to a calendar, a task which includes a number
    of entries similar to:
    <TimephasedData>
    <Type>24</Type>
    <UID>7</UID>
    <Start>2014-10-03T08:00:00</Start>
    <Finish>2014-10-04T08:00:00</Finish>
    <Unit>2</Unit>
    <Value>PT8H0M0S</Value>
    </TimephasedData>
    ... and to an assignment:
    <Assignment>
    <UID>7</UID>
    <TaskUID>10</TaskUID>
    <ResourceUID>-65535</ResourceUID>
    <PercentWorkComplete>100</PercentWorkComplete>
    which includes blocks like:
    <TimephasedData>
    <Type>2</Type>
    <UID>7</UID>
    <Start>2014-10-17T08:00:00</Start>
    <Finish>2014-10-17T17:00:00</Finish>
    <Unit>2</Unit>
    <Value>PT8H0M0S</Value>
    </TimephasedData>
    Eventually, the second file also does load with no external file links indicated.
    Again, I'm just looking for anything that might be a clue to the long Project Server load times.
    Thanks in advance,
    LP

    Slow performance can come from a number of different things. Without knowing more detailed information about your setup or workflow, it's difficult to accurately troubleshoot.
    -What kind of Mac are you using?
    -What is your source format?
    -Where is your source footage located?

  • XML import only creates one record at a time

    Hi All,
    I have an XML import map that automatically imports data into main product table. It's working fine when the XML file has only one main record. When it has more than one record, the import manager and import server can only import the last record in the file and skip the rest.
    I already checked the record matching tab. It correctly shows that all records will be created and 0 will be skipped. Even the log file indicates all records are created after I execute the map. Yet, when I try to look for them in the data manager, I can only find the last one. If I execute the map with the exact same file again, it will create one more record again and skip the rest.
    Someone else posted the same question a while back: Import map issue one record at a time. But it was never answered. Does anyone else have this issue? Is this a MDM bug?
    Thanks,
    Kenny

    Hi Kenny,
    Please refer to the note below:
    Note 1575981
    Regards,
    Neethu Joy

  • How to place the images in Indesign xml file by Javascript?

    How to place the images in Indesign xml file by Javascript?
    We got the Indesign xml file, how to give the image placement link by Indesign javascript? Please help me its urgent.

    Hi,
    You can pass the image url as a href attribute=> file:///Users/me/Documents/my_pic.jpg directly within your xml. It just needs that you pass a local, static and valid url.
    If you want to add image later once the xml is flowed and so target specific nodes and inject images, it's a bit more complex. If the node is not part of the layout, you may try to reach the XMLElement objet and such an attribute, then layout the element.
    var x = some XMLElement
    x.xmlAttributes.add("href","file:///Users/m/Documents/my_pic.jpg" );
    If already placed, then you have to get the associated pageItem, then place your file into it.
    pagItm.place ( File ( "/Users/m/Documents/my_pic.jpg" ) );
    Hope that helps,
    Loic
    http://www.loicaigon.com

Maybe you are looking for