PPT to Captivate 3: image import issue

Hi,
I'm creating a Captivate project by importing a PowerPoint
2003 project. After I import them (but not in PowerPoint), some of
the slides have weird images or words that show up. Sometimes
there's a grey or black blob in the upper left corner, sometimes
there's words like "class," "operations," and "situation," on
various parts of the slide, and sometimes there's lines. I think
they are something messed up in the code, but I'm not a programmer
so I don't know how to access that or fix it.
Has anyone ever encountered something like this? I've tried
re-importing the slides, but that doesn't work. And, sometimes the
images change, so I can't even just blot them out and call it good.
Any help would be greatly appreciated.
-Gretchen

Well, I figured out that the PowerPoint file had a very
subtle corruption that was fixed by basically extracting the
content and pasting it into a new PowerPoint project. Converting it
to Captivate, everything then showed up just fine.

Similar Messages

  • InDesign CS3 and SL - Image Import Issue

    This one is fairly simple and there has been some discussion of it on the Adobe boards, but without any solid solution.
    Issue: If you are in InDesign CS3 and you are using Command+D to replace an existing image, or you are importing a new image, InDesign will freeze up.
    Work Around: Drag and drop the image into the image box directly from Finder.
    Notes: I do not like this solution because it takes up more time, but it has been working for me this weekend. I reloaded InDesign CS3 completely and applied all of the updates, but it did not fix the issue.

    Hi, Curtis,
    Just got SL today - am planning to put it on a MacBook Pro 17" intel that I share for work. We have C3 and had to replace another laptop recently so few $$$$ for upgrading problems until the economy picks up. We use CS3 and CS2 and a standalone InDesign 2 on three computers and so far use the CS3 for the final output. Here is the problem - if we place an image, it stays out of the ID file - our biggest client is fairly image heavy and they LOVE multiple minute revisions, so we don't want to have a bizillion copies of a developing doc with the extra heft of the actual images - esp when they want a lot of fine tuning on the images- by dragging and dropping don't you get an imbedded image? Did you find another solution since you first posted? Thanks

  • PPT Import Issues

    Captivate 2, Windows XP, PPT 2003 SP2
    I cannot import PPT slides into Captivate.
    I was able to do so at one time, but can no longer do so.
    I get to the screen where Capitvate notifies me that it is
    "Loading PowerPoint Project, please wait..." and then a window pops
    titles "Adobe Captivate - Info..." with the message "Could not open
    PPT File".
    Searching the official site, I followed the instructions on
    Adobe's 'official' site and uninstalled and reinstalled both
    Flashplayer and Captivate 2.
    No joy.
    A mild vent: this is the most frustrating piece of software
    I've ever worked with. Errors and glitches appear seemingly at
    random; I know computer software isn't 'random', but I can't detect
    any pattern.
    For me, Captivate just hasn't seemed to play well with the
    other programs in the sandbox. The frustrating part is that it
    enables solid end results--it's the getting there that is terribly
    untidy.

    Hello, Peter_at_FedEx,
    I just had this same problem (error message: 'Could not open PPT file') and, with careful isolation of variables, found the answer for my particular PowerPoint slide file. Here is what I checked, and then what succeeded.
    Problem:
    I could not open a particular PPT file in Adobe Captivate after opening many others and creating projects.
    Steps to recreate the problem:
    From Adobe Captivate: Record or create a new project > Other > Import from Microsoft PowerPoint
    Chose the slide file I wanted to make into a Captivate project.
    Error from Adobe Captivate: Could not open PPT file
    Important data:
    This was with Captivate on a Windows XP VM in Fusion, on a MacBook Pro.
    Microsoft PowerPoint 2004 for Mac, Version 11.5.1 (080707)
    Adobe Captivate 3.0.1 Build 589
    Troubleshooting:
    Tried these things, and they failed:
    •    Looked all over the web in forums on Captivate. Suggestions were to reinstall Captivate, reinstall PowerPoint, reinstall Flash. These made no sense to try, as it was only this particular slide file that was causing the problem.
    •    Another web suggestion was that the file name was too long. Shortened the file name; still did not import, therefore was not a file name that was too long. (And other longer file names were opening fine.)
    •    The file was not a bigger file size than other files that opened successfully.
    •    This particular instance of this error had nothing to do with permissions, as was suggested in another post.
    •    Looked for an update to my version of Captivate on the web, but there was none.
    •    One web suggestion was a virus. Did all current updates to Windows XP.
    •    Restarted Captivate.
    •    Rebooted the XP VM.
    •    Rebooted the host.
    •    Duplicated the slide file, renamed the old one, then gave the new file the same name as before. This file would not import into Captivate.
    •    Created a new slide file and copied all of the slides into the blank slide file. Still would not work.
    •    Tried creating a blank Captivate project and importing slides into that blank Captivate project with Insert > Slide > PowerPoint Slide. The slide file would not import.
    •    Placed the slide file on the desktop of the Windows VM to isolate any problems that could be from using the slide file from the shared folder on the Mac host; still the slide file would not import into Captivate
    •    Tried to open the slide file on another PC with another installation of Captivate. The slide file would not open.
    Solution:
    Finally tried this, and it succeeded:
    •    Created a new PowerPoint file and copied slides one-by-one into this new file. Saved the new file after each addition, then tried to import each incremental slide file into Captivate. After adding a certain slide, the import failed. When I again removed that slide, the import succeeded. I skipped this slide and imported each other slide. The slide file still opened in Captivate. Then I added the one problematic slide, and the slide file would not import again. I deleted that slide again, and the slide file would import into Captivate. Therefore, the problem is a corrupt slide.
    •    To narrow down what in that slide was giving a problem, I copied the slide text piece-by-piece into a slide in the new file. Isolated the problem to something in the slide notes. The slide itself was fine.
    •    The first bulleted item gave an import error. Skipped this sentence, and the slide file imported fine.
    •    Could import the slide file without this one sentence:
    For example, if the WarningPeriod is 5 days, ThinApp begins warning the user at 5 days before expiration about the impending expiration.
    Suddenly in Word (but not here on the forum interface), I could see a box rather than a space after the first ‘5’, but only in Word. In PowerPoint, I could not see the box—I just saw the space. Perhaps I pressed two keys at once to create this box, or perhaps PowerPoint did it on its own.  In PowerPoint, I highlighted the space, and I saw that the font for that space was actually an Asian font called ヒラギノ角ゴ ProN W3. So, I tried to change the space to Arial. But it would not change, even if I highlighted the words around it and changed the entire area to Arial; the space remained as this unwelcome Asian font. I was able to delete the space, then confirm that the compressed words around the deleted space  were Arial. Then I could add an Arial space. Recopied the sentence into the new slide file, and the whole slide file now imports fine!
    •    Conclusion: one corrupt character caused the problem, and Captivate refused to open the entire slide file.

  • Strange import issue .. no longer works in 2.6 or Beta 3

    Strange import issue.
    I use LR-2.6 everyday but have only played around with the LR-3 for a limited amount of time so the other day I decided check it out and tried to import a handful of RAW(canon) files on a SDxc-8g card via a USB card reader. I set it up to copy and convert to DNG, apply a few keywords and Metadata but when I tried it acted like it imported the first image and then froze. Card reader lights stopped blinking and just stayed on, program task bar doesn’t show any progress, not even for the first image. I then went to the folder that I was going to have the images copies to and it contained a file of the first image, but there is no indication that LR-3 even created it and it doesn’t show up in the catalog. When I tried to close out LR-3 is popped up the “in the middle of a task warning” so I just closed the program and tried it a couple more times to no avail.
    So I though o well I will just open up LR-2.6 and import them from there, guess what now LR-2.6 does the exact same thing!!
    I thought maybe my card reader was a POS but I was able to drag all the files to a new folder on my desktop and import them from there, nope. Tried rebooting a couple times, even opened a new catalog to test with, in both LR-2.6 and LR-3 and neither will work..
    I am stumped any ideas?

    Thank you for everyone's assistance
    I actually figured out what the problem was, like most issues it comes back to operator error, it seem I had inadvertently chose a "rename file on import" template that I had set up to name the files based on a custom fill-in field in the Meta Data, I normally only used that template when I was exporting images that had been completely edited, so being these images were new imports that field was blank, hence it would import the first image and then do to " don't import subjected duplicates" being checked it would just stop the import process.

  • LR 4.4 Import Issues - Missed a Cure?

    Hello Everyone,
    Since upgrading to 4.4, I have experienced a number of new issues. 4.3 was solid as a rock in comparison.  4.4 is causing me to need to manually terminate and/or restart the application numerous times daily, sometimes numerous times hourly.  It clearly needed more bake time.
    I am posting this thread because, after reading numerous similar posts (I find I'm hardly alone) and hundreds of responses, it is not clear to me there are any solid solutions.  If there are, and I missed them, I am hoping someone will simply point me toward the appropriate URL.
    My primary issue surrounds Import.
    The Import function has been repeatedly (not just once or twice, but interiminably):
    Hanging, becoming unresponsive after telling it to execute the Import.  This is frequently noticed immediately, at file #1.
    Incredibly slow, eventually grinding to a halt after a handful of files.
    Sources are dropped. Initially all sources are listed. Then, especially with sources (e.g. card reader, smartphone) having > 100 files, the source simply is removed from the listing.  You can toggle the arrow on other sources (e.g. to expand file folders), but nothing happens other than the arrow toggling up/down.
    Only solution, restart (frequently requiring manual process termination) and try again.  I have seen discussions regarding smartphones. It was never an issue with 4.3.  With 4.4, my iPhone 4S will populate the preview grid, but after about 2 minutes, it disappears and the grid goes blank.
    Importing large number of files (regardless of source) will populate the grid but frequently have the exclamation mark with a number of the preview images.  Only solution I've found, delete effected files from catalog, then reimport.
    Modifying import settings, such as my copyright or related info, will terminate LR altogether, about 30% of the time.  This happened to a number of us at a LR training class this past weekend (different machines, OSes).
    Importing 764 JPG from my iPhone (while writing this) has been going about :30 and is 1/3 (indicated) complete.  We're at the point of about 1 image imported ever ~5 seconds, reinforced by the entire grid object being refreshed each time.  I would consider importing a handful of files at a time, but if I do much more than select the iPhone as source and hit Import as soon as the grid populates, the source is lost, and everything starts over.
    One instance of an 'insufficient memory' error.
    There are other niggling issues but Import is a major mess.  From what I've read (and, again, I see I'm not alone), these issues are common for both Windows and Mac, newer PCs and older, and in all manner of mixed environments.
    My own situation is a Windows 7 Ultimate, Dell E6400, 4GB RAM, LR 4.4.  In all cases I am reading my cards via the built-in card readers.  Primary cameras are a Canon SX260 (JPG only) and Konica Minolta Maxxum 7D shooting (almost always) RAW (.MRW).  My content is solely pictures, no video.
    With regard to the smartphone discussion, I have experienced these problems with the laptop docked, undocked, with or without smartphone attached.
    The only relief I have found is, when working with a memory card having >100 images (not many, in the grand scheme), to copy files to a local hard drive, then import from there.  The impression I have, is that the speed allows quicker execution, getting ahead of any resource contention issues.  Purely a gut feel thing based on observed behavior. Nonetheless importing from HD rather than SD does work better.
    Clearly 4.4's Import has issues. Any word of a service patch or 4.5?

    Uninstall 4.4 and re-install 4.3 is the normal process for downgrading.
    Others don't necessarily have the problems you're seeing, so to me it's less likely a fundamental flaw of LR 4.4 that wasn't tested well enough, and more likely a hardware or driver issues that LR 4.4 is bringing to light. 
    It may be that LR 4.4 is using different USB libraries or different OS-level functions to interact with the removable devices, perhaps to resolve other issues reported in previous versions, so something working differently wouldn't be unexpected.  It is less expected that whatever LR 4.4 is doing would cause problems on a particular computer, though.  It might be wise to figure out what is wrong on your system when LR 4.4 is in use, but obviously you also need to have a functioning workflow as well. 
    For experimentation, I think it is possible to have both LR 4.3 and LR 4.4 installed at the same time, if your rename the LR 4.4 program folder to something completely different before doing the install for LR 4.3, and then rename it back when you're done.
    You also might want to try the beta for Lightroom 5 at Adobe Labs http://labs.adobe.com/ to see if it works any better and report any issues to the LR5-beta specific discussion forum (not here).

  • Image quality issues in PS - word to PDF

    Hi,
    I am having major image quality issues when trying to make my word document a clean, clear PDF. Images become distorted. Borders for tables and text that are equal px size look like they are different sizes throughout the document.
    I have searched the internet, read help, and tried many different things:
    Word 2007 - Changed image %, image size, export options, adjusted px for borders, used different styles
    Acrobat 9 Pro - Changed import settings, import options, print options, tried press quality, high quality, etc.
    Photoshop CS4 - Changed ppx, file format, compression options
    What can I do to get a clean, clear PDF file with the images and borders preserved?
    Thank you.

    In converting a MS Office file to PDF, Photoshop cannot help in any way and will likely cause more harm as it may rasterize vector data. Expect your ideal answer in the Acrobat forum.

  • Importing issues with Final Cut Pro X. Green flash and twitches while play back

    Hello, I'm having some importing issues with Final Cut Pro X and I can't find any solution whatsoever. Perhaps my importing settings are wrong?
    Anyways, I've done a lot of recordings on eye TV and HD PVR with some videos that are about 3 hours long. I exported them into H.264 files, which turns them into mpeg-4 files with AAC audio. Then I import them into final cut pro X and I notice it takes a long time for them to render the videos and I notice that there are some green screens and twitches while I play through the video.
    Here is a screenshot of the green screen that I'm talking about:
    [URL=http://imageshack.us/photo/my-images/688/screenshot20130409at338.png/][IMG]http://img688.imageshack.us/img688/4537/screenshot20130409at338.png[/IMG][/URL]
    Could it be my 2 video graphics card that is causing this kind of issues? Or is there any solution to fix this?
    In the past, I've used iMovie 09 and it worked out perfectly. However, the new iMovie 11 is terrible because it automatically optimzie my 3 hour long videos into making the importing process to (144 hours long to import). Is there any way to get iMovie 09 back or am I stuck on dealing with this Final Cut Pro X issues?
    More information:
    My Hauppauge HD PVR settings are set to custom. Video Constant Bit Rate, the average bit rate: 13.5 Mbps. The audio is AAC.
    My project settings for video properties is set to custom, 720P HD Format, 1280 x 720 Resolution and 30P Rate. The audio and render properties is set to custom, audio channels is stereo, audio sample rate is 48kHz and the Render Format is Apple ProRes 422.
    I export the video as a quicktime movie. The export setting is H.262.
    The summary of the export is:
    File type: Quicktime movie
    Estimated size: 397GB
    H.264, Width and height: 1280 x 720. Framte rate: 30 fps

    My Hauppauge HD PVR settings are set to custom. Video Constant Bit Rate, the average bit rate: 13.5 Mbps. The audio is AAC.
    My project settings for video properties is set to custom, 720P HD Format, 1280 x 720 Resolution and 30P Rate. The audio and render properties is set to custom, audio channels is stereo, audio sample rate is 48kHz and the Render Format is Apple ProRes 422.
    I export the video as a quicktime movie. The export setting is H.262.
    The summary of the export is:
    File type: Quicktime movie
    Estimated size: 397GB
    H.264, Width and height: 1280 x 720. Framte rate: 30 fps

  • Import issue with Lightroom

    I upgraded to LR5.2 2 weeks ago from 4.3. Install went fine, but I'm now having issues when importing my photos, Lightroom hangs partially through the import.  The only choice I have then is to force quit the program, which then freezes my computer.  Getting to be an invredibly frustrating exercise.
    I have an iMac with OSX10.8.5 (Mountain Lion)
    Lightroom 5.2
    Importing & converting CR2 files (5DMkIII) to DNG.
    Images being imported to an external hard drive.
    Nothing has changed in my workflow or software except for the installation of LR5.  I did read in some of the forums that there was import issues that appear to have been fixed with the latest release, however, whilst I DEFINTIELY have the latest release of LR5,  this is still occurring.  Any ideas? Another bug?
    Cheers
    Sarah

    sure did. All permissions are admin & I'm it.  I haven't tried DL via image capture - LR4 gets me to the same end goal, tis just rather onerous to have to muck around with this twice.  Appreciate your taking the time on this 

  • More Image/stylesheet issues

    Hello again,
    Just wondering if anyone could give me some quick style sheet issues, have an img class that looks a little something like this:
    img {
    border: 5px solid #adadad ! important ;
    padding: 5px ! important ;
    margin: 4px, 4px, 4px, 4px ! important ;
    -moz-border-radius: 15px;
    -webkit-border-radius: 15px;
    border-radius: 15px;
    Which works like magic for getting me a nice curved border in most modern browsers.
    Now there are one or two small icon type images that I need to not have a border as they are actually within the text - can anyone think of a way of setting up RH9 so that I can have an image that doesn't follow these styles?
    I am sure it will be to do with over riding these styles but not sure how to do this because it is not like I am selecting a style for the image files - they are just getting their styles from the img selector...
    Anyone got any suggestions?
    much 'preciated.

    Hi Willam
    I'm a bit confused by what you suggested. You seem to be implying that this won't work and the image paths will break. But I've not found this to be the case. I just tested by creating an image and later creating some nested subfolders and using the variable in topics in each of the subfolders. I then generated WebHelp and viewed and I had no broken images at all. RoboHelp was able to manage the relative pathing to the image without issue.
    Have you noticed otherwise?
    I'm a believe in erring on the side of caution, but it would seem that (for me anyway) the worry is unfounded.
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7, 8 or 9 within the day!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • Images imported via card reader from Eye-Fi chip are garbled

    Laptop is g580 20157, factory installed windows 8
    Eye-Fi Pro x2 8 GB WiFi
    When using the Eye-Fi via the sd media reader, imported images are garbled. Some thumbnails look ok, others not. All images when previewed are bad.
    When using the Eye-Fi sd to usb converter, images import just fine. When using usb cable to import from camera, images import just fine. When using a non-Eye-Fi sd chip, images import just fine.

    Hi JayWilson,
    Thanks for posting and welcome to the Lenovo Community,
    I’d like to ask you to share with us the status of using the wireless connection is it stable with you and working fine?
    And I’d like to advise you to try to contact the service provider for your Eye-Fi card as i need to share with you the
    requirements for the Eye-fi card that you have:
    Computer with Windows 7/XP (SP3)/Vista or Mac OSX 10.5+ (Intel only) and 100MB of free space.
    And as I understand from your post your machine came with windows 8.
    Hope the information helps. Let us know.
    Regards
    Soha
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Still images importanted are much smaller Why?

    Because of the snow storms that have hit the Mid-Atlantic region, I wanted to save some photo images off the Internet and made a 'movie' of them.  I saved a couple dozen to a folder on my hard drive, then imported them into Premiere CS3 just as I do with video clips.  However, after dragging and dropping them into the Video One track, when I played them I discovered that many of the clips were not full screen in the monitor... they were much smaller with black areas surrounding them.  Is this an image size issue and if so, how can I make adjustments?  I've attached an example of what I see in my monitor... I appreciate the help.

    Yeah, I'd probably have black surround the actual image with a 2" image in a 12" frame. I checked the file size (in KB, using Properties) and found that the images which were too small (and surrounded by a black box) were in the area of less than 60 KB while the ones which were above, say, 120KB seemed too big... Cuz they appeared to be zoomed in on. One image which seemed just right had a size of 90.6KB.
    I'll need to go back in to each file and see in the properties report will state the pixel size... Then I'll get back to you.

  • Limited image import from scanner

    I find only limited image import options under Photoshop CS5 and CS6. Under CS3, I have a number of options which I have used frequently, regarding preview, zoom, desceening, filtering, stretch, noise removal, fading, grain, etc. None of these seem to be available under either CS5 OR CS6. In fact, under CS5, under "FILE>IMPORT", I I don't even GET the Canoscan 8400F opton. This is pretty basic stuff, getting good quality off a scanner. What's up? Do I need to go back to CS3 for everything? It actually worked.

    Hi there, I'm sorry you aren't able to scan.
    What operating system are you using? There are known issues with scanning while running Mountain Lion, in particular. If this is the case, Adobe engineer reccommends trying Image Capture:
    Image Capture is a utility program in the Utilities folder inside the Applications folder, and is a standard part of Mac OS X. As far as I know, Image Capture does work properly in Mountain Lion.
    ImageKit refers to the underlying Cocoa frameworks (programming interfaces) used by Image Capture as well as by Photoshop and other applications to perform scanning. For reasons I won't go into here, these are not working correctly in Photoshop, but are in Image Capture, which is the problem we're working to resolve with Apple.
    The scanners that work with Image Capture/ImageKit are also a standard part of Mac OS X, which means that users do not have to go to a different web site (e.g. Epson's web site) to download and install drivers for their specific scanner, which you do have to do with TWAIN. Scanner support (numbering in the hundreds) through Image Capture/ImageKit is already included in Mac OS X "out of the box".
    We added support for ImageKit scanning to Photoshop CS6 because we recognized it was unlikely that scanner manufacturers would go back and rewrite their TWAIN drivers to work in 64-bit mode (especially older scanners that are no longer manufactured).
    One advantage is that as improvements are made to ImageKit and as more scanners are added by Apple to their Mac OS X releases over time, Photoshop users get those "for free", so to speak. Unfortunately, changes to ImageKit made for Mountain Lion have had the effect of breaking this feature in Photoshop, but we are confident this will get sorted out.
    Here is an article talking about known issues with scanning in CS6, and some workarounds. It suggests downloading a TWAIN driver (more information here) or using your scanner's scan utility (although this might not be the optimal solution for you, considering you came to the forum).
    I hope this information helps!

  • IMPORT issues: Works with iMovie 3 but not iMovie 6 ???

    Okay, still trying to get my import issue resolved.
    I have a SONY HDR-HC3 DVmini.
    No problems with iMovie 3 on my Powerbook.
    iMovie 6 on my MDD will let me control the camera, but the screen stays BLUE with no IMPORT.
    My buddy thinks it might be a Quicktime issue.
    He said to download Quicktime Pro, that might resolve this issue.
    I can copy the iMovie 3 file to my machine with iMovie 6 and do the editing, just not the importing...
    THANX

    Hi
    Can be so much.
    Often Camera has to be connected to Charger/mains during Capture.
    An majority is a faulthy - badly connected FW-Cable (USB don't work at all)
    My list on this
    *NO CAMERA or A/D-box*
    Cable
    • Sure that You use the FireWire - USB will not work for miniDV tape Cameras
    FireWire - Sure not using the accompany USB-Cable but bought a 4-pin to 6-pin FW one ?
    • Test another FW-Cable very often the problem maker.
    Camera
    • Test Your Camera on another Mac so that DV-in still works OK
    • Toogle in iMovie pref. Play-back via Camera (on<->off some times)
    • Some Cameras has a Menu where You must select DV-out to get it to work
    • Camera connected to "charger" (mains adaptor) - not just on battery
    Does Your Camera work on another Mac ?
    Sorry to say it is to easy to turn the 6-pin end of the FW-cable 180 deg wrong.
    This is lethal to the A/D-chip in the Camera = needs an expensive repair.
    (Hard to find out - else than import/export to another Mac ceased to work
    everything else is OK eg recording and playback to TV)
    Connections
    • Daisy Chaining most often doesn’t work (some unique cases - it’s the only way that work (some Canon Cameras ?))
    Try to avoid connecting Camera <--> external HD <--> Mac but import directly to the Mac then move
    the Movie project to dedicated external hard disk.
    Mac
    • Free space on internal (start-up) hard disk ? Please specify the amount of free space.
    (Other hard disks don't count)
    I go for a minmum of 25Gb free space for 4x3 SD Video - and my guess is 5 times more for 16x9 HD ones
    after material is imported and edited.
    SoftWare
    • Delete iMovie pref file may help sometimes. I rather start a new account, log into this and have a re-try.
    • Any strange Plug-ins into QuickTime as Perian etc ? Remove and try again.
    • FileVault is off ? (hopefully)
    Using WHAT versions ? .
    • Mac OS - X.5.4 ?
    • QuickTime version ? (This is the heart in both iMovie and FinalCut)
    • iMovie 8 (7.1.?) ?
    • iMovie HD 6 (6.0.4/3) ?
    *Other ways to import Your miniDV tape*
    • Use another Camera. There where tape play-back stations from SONY
    but they costed about 2-4 times a normal miniDV Camera.
    • If Your Camera works on another Mac. Make an iMovie movie project here and move it
    over to Your Mac via an external hard disk.
    (HAS TO BE Mac OS Extended formatted - USB/DOS/FAT32/Mac OS Exchange WILL NOT DO)
    (Should be a FireWire one - USB/USB2 performs badly)
    from LKN 1935.
    Hi Bengt W, I tried it all, but nothing worked. Your answer has been helpfull insofar as all the different trials led to the conclusion that there was something wrong with my iMovie software. I therefore threw everything away and reinstalled iMovie from the HD. After that the exportation of DV videos (there has not been any problem with HDV videos) to my Sony camcorders worked properly as it did before. Thank you. LKN 1935
    from Karsten.
    in addition to Bengt's excellent '9 yards of advice' ..
    camera set to 'Play' , not rec/computer/etc.?
    camera not on battery, but power-line?
    did your Mac 'recognize' this camera before...?
    a technical check.
    connect camera, on, playback, fw-connected...
    click on the Blue Apple, upper left of your screen ..
    choose 'About../More..
    under Firewire.. what do you read..?
    More
    • FileVault - Secure that it’s turned off
    • Network storage - DOESN’T WORK
    • Where did You store/capture/import Your project ?
    External USB hard disk = Bad Choise / FireWire = Good
    If so it has to be Mac OS Extended formatted
    ----> UNIX/DOS/FAT32/Mac OS Exchange is NOT Working for VIDEO !
    mbolander
    Thanks for all your suggestions. What I learned is that I had a software problem. I had something called "Nikon Transfer" on my Mac that was recognizing my Canon camcorder as a still camera and was preventing iMovie from working properly. After uninstalling Nikon Transfer and doing a reboot, everything worked great.
    I never liked the Nikon Transfer software anyway--I guess I'll get a cheap card reader and use that to transfer photos in the future.
    *No Camera or bad import*
    • USB hard disk
    • Network storage
    • File Vault is on
    jiggaman15dg wrote
    if you have adobe cs3 or 4 and have the adobe bridge on close that
    or no firewire will work
    see if that halps
    DJ1249 wrote
    The problem was the external backup hard drive that is connected, you need to disconect the external drive before the mac can see the video camera.
    Yours Bengt W

  • Images imported from QT exported image sequence have jagged edges

    Hi
    I've come across something strange which I'd like to resolve.
    I export an image sequence from QuickTime.
    I then import this into Aperture.
    But the images imported into Aperture now have jagged edges where there has been any movement in the original footage.
    The images originally exported from QuickTime look absolutely fine when viewed with preview, they have the expected blurring on moving objects, but no jaggedness.
    Now, a bit more detail.
    The footage I'm exporting from was shot by me and came from a Final Cut Pro edit.
    The codec in the QT movie is Apple Intermediate Codec and this is interlaced.
    The jagged edges on movement look to me like the problem of interlaced not being converted to progressive.
    However the exported images from QuickTime don't display this when viewed in Preview, it is only when viewed in Aperture that the jagged edges become apparent.
    I have tried exporting from QuickTime to jpg, png and psd, but the problem is identical no matter which format I use.
    I really want to now use Aperture to improve these exported images, but with this jagged edge problem I can't.

    Hi JNorris--
    Sounds like you need to apply the deinterlace filter (Effects tab: video filters: video: deinterlace) to the stills your exporting.
    See if that makes a difference to start.
    T.

  • Star Rating bar does not appear with images imported from file

    Using Elements 11, cannot get the Star Rating bar to appear under images imported from file, although the intro to the program shows this as happening automatically.
    Hope this goes through, as I have also created an account, but the question does not seem to be get a post.
    Help!

    Have you enabled Organizer to show details? You can enable show details by checking View > Detail is not already checked

Maybe you are looking for