Motion 2 Corrupting Images

I am stacking 3 to 6 screen grabs saved as TIFF files. One image is display, it fades out after 30 frames and a new one pops-up in the exact same X/Y location. It looks like animation (it's a application tutortial).
Randomly Motion will crop the 5 or 6 left most pixels, the image shift 5 ot 6 pixels to the left, and then Motion appends the cropped the pixels to the right edge of the image. You can see this error in the real-time preview and when the movie is exported.
If I click on the image in the time, then it pops back to its correct location. I have 3 animation sequences like this. Sometimes the first 2 will be perfect, but the 3rd is corrupted. So I go to the 3rd sequence, click on each image via the time-line and they pop back to the right location. I just selecting the image, nothing else.
But then either 1st or 2nd sequence will then have the bug. Correct those, then the 3rd may it again... When I first open the project - usually - all the sequences are fine. But after the slightest edit, then they bug out...
I've tried grouping the images, tried .PSD, .JPG and .TIF versions of the images, tried aligning left edge and top edge... Nothing works. Checked the properties via Inspector - all have the same x/y location, same magnification, etc.
Has anybody else had this problem? I've been beating my head on the desk for 10 days trying to solve this...

I considered that a couple days ago. I added several new layers and moved each sequence to its own layer. It still happens...
I don't think it's a video card issue because the problem also happens when the project is exported. Tried H.264, Animation and Sorenson3 codec's and all 3 showed the images shifting...
There are actually many more image sequences, so I started doing each sequence as its own project, exporting to H264 at the highest quality and bring the sequence back in as a clip. I don't care for this work around because you lost alot of flexibility in editing and the video clips had a notable loss in quality. I could have sworn I saw a lossless compression, but now I can't find it...
Oh, and the video card is a ATI X800 XT, so adequate horsepower and VRAM.

Similar Messages

  • Attempting to upgrade to Firefox 3.6 (using an ancient Mac OS 10.3), but received an error message (corrupt image file) when downloading - any way to correct this with my current OS?

    I'm currently trying to update a few programs on my good old (VERY old) Mac Powerbook, but I ran into an error when downloading Firefox version 3.6...I'm currently running Mac OS X 10.3.9, which isn't compatible with the most recent versions of Firefox (or anything, for that matter), but it should still allow an upgrade of version 3.6; however, once the file finished downloading, an error message popped up indicating there's a corrupt image file. Is there any way to work around/correct this problem, or am I stuck with my old version of Firefox until I bite the bullet and upgrade my OS??? Any help is greatly appreciated!!

    Firefox 3.6 requires at least OS X 10.4, the last version of Firefox that runs on OS X 10.3.9 is Firefox 2.0.0.20 available from https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

  • Checking for corrupt image or element

    Hi
    Hoping someone may be able to help, I have a 256 page book which I created in InDesign CS3, the book is made up of several documents.
    I need to export to a PDF, each time I try it fails as there is a corrupt image. Is there anyway I check the documents for corrupt elements before I create the PDF?
    Any help appreciated.

    You need to "Divide and Conquer." It's not unusual to have a failure exporting to PDF with low disk space, but that might not be your problem. In either case the first step is the same. Divide the document in half during the export process and see if each half will export separately.
    If you can export both halves, you may need to live with that and simply recombine them in Acrobat. I don't recall any definitive answers for what to do fix this. Deleting temporary files may help.
    If you still get a failure, divide that section in half and try again (see below). If both sections fail, it could be either a bad font or more than one bad image.
    Make a copy of the document and change all the fonts to something simple and reliable, like Times New Roman, and see if that works. If it does, make a new copy of the original and eliminate fonts one by one, starting with cheap or freebie fonts from the web, and test after each replacement.
    If only one section failed it's more likely an image, and you should be able to isolate the page by continuing to divide the section that fails. Once you know which page, make a copy, and remove images one by one, starting with .eps if there are any.
    If you find a bad image, try resaving it and replacing with a native .ai or .psd.
    Peter

  • Corrupted Images in Pages, now unable to open file

    Pages 2.0.1 has lost the ability to open any pages documents with images on my computer. Some image files are corrupted, but other documents with no corrupted images still will not open and crash Pages if I try. Also, the Dock changed unexpectedly after the first crash, removing my Final Cut Pro icon and restoring the iLife icons. Any suggestions?

    Hello Sahu,
    I too had a very similiar experience with one of my clients. There is nothing to do with missing authorizations.
    Ask him/her to set the resolution of their display to 1024 by 768 pixels. This is because some high display resolutions are not supported by SAP Front end. Believe me, I was amazed to discover that something like this exits.
    Have a nice weekend...............
    Shashi kanth

  • Corrupted images captured by new 5D Mark III

    Hi,
    I got two corrupted images while shooting with my new 5D Mark III..I was using 45mbps sandisk extreme SD card and the mode was only JPEG(fine). After getting two corrupted images I shoot 1k images but no problem there after..Later I copied those images in my HDD except two corrupted images all are looked nice.. My y question is what was the actual problem?Thank you in advance..
    Solved!
    Go to Solution.

    I'd advise at least doing a quick in-camera format each time you insert a memory card (or right after downloading, if you use the USB cable to transfer your images).
    The in-camera format preps the memory card for use, configuring it with some needed file structures and writing over old files.
    If you ever format in computer, always re-format it in your camera before shooting. It's possible that the computer won't configure the card in a way that will work properly in the camera.
    Usually corrupt images are due to card issue or connectivity when downloading. If you are seeing the corruption in the camera, then I'd first suspect the card (either it's faulty, or it's configured incorrectly, or something on there is causing a conflict).
    I once corrupted a number of images on a Compact Flash by opening the memory card door and pulling the card out too quickly, while the last image or two were still being written. It corrupted about 1/3 of the images on the card, not just the last one taken. Initially all the images on the card were unreadable, until I ran a recovery program. That was able to repair about 2/3 of the images... roughly 200 out of 300 images, if I recall correctly.  
    The worst corruption issue I've had (in ten years shooting digital almost exclusively, nearly 20 years shooting some digital), was due to connectivity issues. I had a card reader connected to a USB hub. Took it off the hub and connected it directly to the computer's USB port and the problem was solved.
    It's possible, but pretty rare that the camera itself causes occasional corrupt files. Usually if the camera starts throwing off corrupted files, it's most or all images... not just an occasional one. I'd keep an eye on it and if it continues happening, try a different memory card first. If it continues to happen with a different card, have the camera looked at.
    Alan Myers
    San Jose, Calif., USA
    "Walk softly and carry a big lens."
    GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
    FLICKR & PRINTROOM 

  • Any new fixes for corrupt images in Lightroom 4.4?

    I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
    Drive and Memory:
    Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
    I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
    To rule out the card reader:
    When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
    Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
    This is quite annoying and I would like to get things fixed.

    jproductions111 wrote:
    Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
    I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
    jproductions111 wrote:
    I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
    OK - thanks.
    jproductions111 wrote:
    I know you don't believe its software
    ~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
    jproductions111 wrote:
    maybe Lr 4 was causing some sort of bug to make the hardware malfunction
    Although theoretically possible, I'd still venture to guess that's not what happened.
    jproductions111 wrote:
    this is not happening to my in Lr5.
    Didn't you also change your disk drive situation around just before you started using Lr5?
    jproductions111 wrote:
    But I am keeping my fingers crossed.
    Me too - please keep us posted...
    R

  • Cannot load 3.6 - disk image failed to mount - reason: corrupt image

    Tried to load 3.6 and get the msg: disk image failed to mount. Reason: corrupt image.
    == This happened ==
    Every time Firefox opened

    *Firefox 4 versions and later do not run on a PowerPC Mac.
    *Firefox 4 and later require at least OS X 10.5 and an Intel Mac.
    * http://www.mozilla.com/firefox/6.0/system-requirements/
    For an unofficial Firefox 4 compatible version (TenFourFox) that runs on PowerPC Macs with OS X 10.4.11 or OS X 10.5.8 you can look at:
    * http://www.floodgap.com/software/tenfourfox/
    * http://tenfourfox.blogspot.com/2011/08/601-now-available.html
    Firefox 3.6.x (Mac OS X 10.4 and later) can be found here:
    * http://www.mozilla.com/en-US/firefox/all-older.html

  • The message: corrupt image showed so that I can't upgrade the new version. how can I fix it?

    when I try to upgrade Firegfox in my iBook G4 with Mac OS X . The message always came out: corrupt image.

    Which version of OS X? <br />
    Firefox 2.0.0.20 is the last ever release for Mac OS X 10.3.9 and earlier versions. Get it here:
    https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

  • Corrupt Images after syncing Photos

    Has anyone experienced corrupt images after performing a sync?
    After activation and at some point during my first sync my machine blue screened. After a reboot it appears that everything is running smooth, however, I notice that most of the pictures that are synched are corrupted and many didn't synch at all.
    I removed all synch images and re-synched but I'm still experiencing the same problem.
    I'm hoping its an issue with Vista or iTunes and not my phone. Looks like I'm going to have to go out and get that Mac Book Pro after all

    Are you saying that the photos are appearing in the wrong albums, or that the photos are in their correct albums but are displayed in the different order within them ? If they are in the wrong albums then try deleting the photo cache from your computer and re-try the sync - the location of the cache, and how to delete it, is on this page http://support.apple.com/kb/TS1314
    If the photos are displayed in the wrong order in the albums, then they will be displayed by capture date order unless you are syncing via iPhoto or Aperture on a Mac. To get them in a different order you will need to manipulate their capture dates : http://support.apple.com/kb/HT4221

  • Corrupt image

    What does corrupt image mean on download

    If you downloaded an installer file, then it means that the download file is corrupted.  Download it again.
    If you need more help, please provide your operating system details.

  • Hdiutil: verify failed - corrupt image

    problem: sparseimage is not mountable and verify ends with a "hdiutil: verify failed - corrupt image".
    cause: tiger crashed and the image was mounted. the only way to boot was power down the machine. after the reboot the image was not mountable anymore.
    thats the verbose output:
    hdiutil verify -verbose conti.sparseimage
    hdiutil: verify: processing "conti.sparseimage"
    DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
    DIBackingStoreInstantiatorProbe: interface 1, score -1000, CRAMBackingStore
    DIBackingStoreInstantiatorProbe: interface 2, score 100, CCarbonBackingStore
    DIBackingStoreInstantiatorProbe: interface 3, score -1000, CDevBackingStore
    DIBackingStoreInstantiatorProbe: interface 4, score -1000, CCURLBackingStore
    DIBackingStoreInstantiatorProbe: interface 5, score -1000, CVectoredBackingStore
    DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CUDIFEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
    DIFileEncodingInstantiatorProbe: nothing to select.
    DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
    DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
    DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 3, score -1000, CUDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
    DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
    DIDiskImageInstantiatorProbe: interface 7, score 1000, CSparseDiskImage
    DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
    DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
    DIDiskImageInstantiatorProbe: selecting CSparseDiskImage
    DIDiskImageNewWithBackingStore: CSparseDiskImage
    DIDiskImageNewWithBackingStore: instantiator returned 103
    hdiutil: verify: unable to recognize "conti.sparseimage" as a disk image. (corrupt image)
    hdiutil: verify: result: 103
    hdiutil: verify failed - corrupt image
    the problem is not that i dont have a backup of tha date within this 7GIG imagefile. the problem is now that i dont trust this format anymore. i do have a couple of AES-secured sparesimages FOR backup-reason (including one on my iPod) and if something happens to them i might be in serious trouble.
    so now my question: is it possible to rescue this AES-secured spareseimage or is this kind of methos unsafe for important data?
    thanks
    klaus

    Regular tools like Disk Utility and DiskWarrior
    didn't solve anything. I was wondering if it is
    possible to rescue some files by manually decrypting
    the image with some low-level tool.
    Did you have any succes? Given all reports on the
    web, it seems a bit hopeless, but I like to give it a
    chance.
    no success at all, sorry.
    i dumped the images now and also went back to some backups.
    but i definitly don't use filevault anymore
    cu

  • CS3 corrupting images

    I am using CS3 in OS X 10.5.  All of a sudden my photos are getting corrupted.  I can see an image in Bridge, but when I click on it the image becomes completely distorted.  It becomes colorful horizontal lines.  I tried removing CS3 and re-installing it, and the corrupted images looked ok after this, but again when I clicked on them, they would get distorted again.  I have no idea what's causing this, but I'm hoping someone can tell me, so I know how to fix it and avoid it in the future.
    Thank you!
    Tom

    Thanks for the reply Chris!  That was one of my guesses.  I ran disk repair on the drive and it didn't come up with any errors, is there a test for the RAM?  I've called Apple before with photoshop issues and they've said they can't really help with 3rd party apps, but this is a fairly new iMac.  I will be sure apple care is extended for it and work with them.  In the meantime, I deleted all the files that seemed to be having issues and will watch to see if any others have problems, but it seems to be limited to one folder so far.
    Thanks,
    Tom

  • Corrupted image shown when horizontal elasticity set to "contract"

    Hello.
    Using Forms and Reports 10.1.2.3.0
    I have a report where I try to show images horizontally centered in their surrounding frame.
    For this I created an image-item inside the frame (a repeating-frame, because the images are fetched from the DB), manually centered it inside the frame, attached it with an anchor to its surrounding frame, and set its horizontal elasticity to "contract" (vertical elasticity is set to "fixed"). This is actually the preferred method for doing this and a few threads in this forum recommend it.
    What I got in the resulting PDF was a corrupted image under certain circumstances.
    To narrow this down I created three different images (width*height)
    1. 1000*666
    2. 1000*750
    3. 1000*800
    loaded them into the DB, and tried to run the PDF. You can see the result in the following screenshot:
    When I set the horizontal elasticity to "fixed", the image is not corrupted (this is not a solution since the image gets left-aligned then).
    Setting the OUTPUTIMAGEFORMAT to something different than the default (JPEG) didn't change anything.
    Interestingly enough the Foxit PDF-Reader shows it correctly, while both AdobeReader X and XI and even Inkscape show the image corrupted (not only on my PC).
    We tried this with several images/photos, and the only ones being shown correctly seem to be images with an aspect-ratio of 4:3 or higher. I was not able to pinpoint exactly at which ratio this behaviour manifests itself.
    Anyone got an idea what may have caused this?
    Thanks in advance
    Markus

    Addendum:
    Setting the vertical elasticity to "expand" fixes it too, but since we often have images with an aspect-ratio of 3:4 or even higher I can't use this, since they would use way too much vertical space (and would negatively impact our layout).

  • CS6 Mini-Bridge showing corrupt image

    I didn't know whether to post this in Bridge or here since Mini-Bridge is called from within CS6.  I've rarely used Mini-Bridge in the past because it required Bridge to be running, so I didn't see the need.  A discussion on another forum had me take a look at Mini-Bridge.  It now appears to run without Bridge, though it appears to make some sort of connection to Bridge and have it run in the background.  I pointed it to a folder and noticed several corrupt images.  I then opened Bridge and they looked fine.  I did a screenshot and the image appears corrupt in Mini-Bridge, but fine in Bridge (5.0.2), ACR (7.3), and CS6 (13.0.1).  Mini-Bridge will show several of the images corrupted, while they all look fine in Bridge or any other program.  I'm running Windows7. 
    The following screenshots show the problem.  Any thoughts?
    Thanks, Dennis

    Mini Bridge always requires Bridge to be active for showing the content of the Bridge files. If you start mini bridge in PS without having Bridge itself zctive a message should appear that you have to launch Bridge and also a launch button to do the task for you.
    In Bridge first select the file that appears corrupted in MB and with right mouse click menu choose 'purge cache for selection'. If this is not working first try a reset of the preferences for Photoshop ( on a Mac this is restart PS with holding down shift, option and command key, should be something similar in Windows)
    This might work for MB but also resets the other PS prefs to factory default so you have to set your custom wishes again. Not a big deal but you have to be aware of this :-)
    Same can be done for Bridge itself with restart Bridge and holding down control key and choose reset preferences. But if your first attempt with purge cache for selection works you can choose the menu tools in Bridge and while having the folder content of the problem files in the content panel choose cache/ purge cache for folder and let it rebuild.

  • I am not seeing placeholders for missing or corrupt images. Is there an option to turn these on or off, or does Firefox not display these by default?

    I am a web designer. I use FF as my default browser for everything--including work. When viewing pages containing broken image links or corrupted images, no placeholders show to indicate the problem.
    I have to use another browser to check my work. Placeholders are such basic elements that they should appear without having to switch browsers or search for options.
    Thinking I may have accidentally unset an option for viewing image placeholders, I have looked everywhere in the options (including Web Dev tools) and have searched support. I have found absolutely nothing to solve my issue.
    Firefox--whatever version I had installed prior to a computer reformat and browser reinstall--was doing the same, so please don't suggest a FF reinstall or reset as a possible solution.

    In order to change your Firefox Configuration please do the following steps :
    # In the [[Location bar autocomplete|Location bar]], type '''about:config''' and press '''Enter'''. The about:config "''This might void your warranty!''" warning page may appear.
    # Click '''I'll be careful, I promise!''' to continue to the about:config page.
    #Search for browser.display.show_image_placeholders and make sure it is set to true.
    That was a configuration that was from a very early on version of Firefox, so if this does not make a change there is more:
    What is interesting is that there is also a css that allows the styling of the broken images: [https://developer.mozilla.org/en-US/docs/Web/CSS/-moz-force-broken-image-icon]
    This was an inter sting hack for the personal profile in Firefox : [http://megashare.altervista.org/blog/2012/08/enable-broken-image-placeholders-in-firefox/]
    Please post back with your results, thank you!

  • Corrupt image files cause upgraded iPhoto to crash

    I have been spending some time trying to find and remove corrupt image files from my iPhoto library. These are not just scrambled images when viewed they crash any and every program you view them with. Including Finder. I accidentally put one on my desktop and finder went into a auto restart cycle I could not stop. until I removed the file with pathfinder. I have found about 30 of these so far (my library is about 25,000) Many of these are in the data file but some are not. They are of all types (jpg,tiff,psd) Thorsten Lemke, (Lemke Software) tells me it is a quicktime issue.
    Here is a link to one of these files. Warning it will crash safari if you try o view it.
    http://vincentdavis.net/try/try.jpg
    Here are my questions.
    1. is there some way to fix these
    2. is there some efficient way to find and remove/fix them?
    3. how did this happen? I had no problem before update (that I knew of)
    Thanks
    Vincent

    I did try the link, and as you said - it crashed Safari. However, I have google searched and also searched the Apple Support sites for 'fix corrupt images' with no luck. I'm sorry but I think the only way of knowing is to try and open each of them.
    However, I did read on Macworld's site once that sometimes photoshop or other image editing programs can open the corrupt files.
    Sorry for not being much help here - I hoped that my first suggestion would have done the trick.
    Sam

Maybe you are looking for