Crashing with psd files

Hi everytime I add a .psd file then FCPX crashes instantly.
Anyone knows about this?

.psd file is a regular 1080p transparency, RGB display, square pixel. The same ones I used on my Retina before with which I had no problems what so ever.
I have this probleme since I use it on a brand new Mac Pro.
Version of FCP is 10.1.1 and system version is 10.9.2.
I contacted Apple care also and they were pretty surprised by the problem and they are looking into it also!

Similar Messages

  • CMS crash with core files and multiple report output generation

    Happy new year to everyone,
    Our BOXIR3.1SP6FP2 env has recently started behaving weirdly by triggering multiple output to users inbox and email notification out of scheduled reports. Also we have noticed the CMS crash with core file (almost 4GB) generation at the time of multiple report output.
    Most of the times, CMC crashes and recycles itself. At few times, CMS services alone went shut down.
    OS details: RHEL 5.5, 32 GB RAM, 8 core processor on each of the clustered node, Oracle 10GR2.4 CMS DB server, 11GR2.4 oracle reporting DB server and oracle 11.1.0.6 client.
    2015/01/21 23:54:37.946|>=| | |28123|1534131088|{|||||||||||||||DBQueue::Read
    2015/01/21 23:54:37.946|==| | |28123|1496185744|
    |||||||||||||||(OracleStatement.cpp:156) Prepare: SQL: SELECT ObjectID,
    Version, LastModifyTime, CRC, Properties FROM CMS_InfoObjects6 WHERE ObjectID
    IN (1004050) ORDER BY ObjectID
    2015/01/21 23:54:37.946|==| | |28123|1496185744| ||||||||||||||(OracleStatement.cpp:183) Prepared statement Execute
    2015/01/21 23:54:37.965|==| | |28123|1496451984| |||||||||||||||SResourceSource::LoadString 50293
    2015/01/21 23:54:37.966|==| | |28123|1496451984| |||||||||||||||SResourceSource::LoadString Unknown exception in database thread
    2015/01/21 23:54:37.967|==| | |28123|1496451984| |||||||||||||||SResourceSource::LoadString 33007
    2015/01/21 23:54:37.967|==| | |28123|1496451984| |||||||||||||||SResourceSource::LoadString CMS is unstable and will shut down immediately. Reason: %1...
    2015/01/21 23:54:38.506|==| | |28123|1496185744| |||||||||||||||(OracleStatement.cpp:156) Prepare: SQL: SELECT ObjectID,
    Version, LastModifyTime, CRC, Properties FROM CMS_InfoObjects6 WHERE ObjectID IN (1009213) ORDER BY ObjectID
    2015/01/21 23:54:38.506|==| | |28123|1496185744| |||||||||||||||(OracleStatement.cpp:183) Prepared statement Execute
    2015/01/21 23:54:38.512|==| | |28123|1455592672| |||||||||||||||(sidaemon.cpp:549) SUNIXDaemon::run: server restart flag is 1..
    2015/01/21 23:54:38.513|==| | |28123|1455592672| |||||||||||||||(sidaemon.cpp:552) SUNIXDaemon::run: in abort ...
    2015/01/21 23:54:38.513|==| | |28123|1455592672| |||||||||||||||(sidaemon.cpp:555) SUNIXDaemon::run: doing the WithAbort case ...
    2015/01/21 23:54:38.520|==| | |28123|1496185744| |||||||||||||||(dbq.cpp:1357) DBQ: Time required to read 1 objects: 20.000000 ms
    Thank you,
    Karthik

    Hi Denis,
    I'm trying my best for the last few weeks to understand the core issue along with SAP however it is still a mystery.
    >Ulimit -a
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    scheduling priority             (-e) 0
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 270335
    max locked memory       (kbytes, -l) 32
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 1024
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    real-time priority              (-r) 0
    stack size              (kbytes, -s) 10240
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 270335
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited
    Below is the observation as part of troubleshooting:
    1. CMS breaks at threshold of 3.9 G.
    2. CMS DB sits in a different Linux server than BOE server.
    3. All core files were generated by boe_cmsd process and are almost 4GB in size (same as max threshold which it breaks).
    4. Shell script which I've added in the BOE servers shows that the CMS DB is available/connecting at the time of CMS crash.
    5. SAP analysed the Core files and skeptical about the below lines.
         #3  0x58687b80 in skgesigCrash ()
          from /opt/oracle/product/11.1.0/client_1/lib32/libclntsh.so
         #4  0x58687e0d in skgesig_sigactionHandler ()
    I'll continue troubleshooting with a hope to fix it at the earliest.
    Thanks,
    Karthik

  • CS3 Still Very Slow with psd files

    I'm still having terrible performance issues with CS3 and imported CMYK psd files containing spot colours. I have a 9MB psd file with two spot colours imported into a layer in Illustrator, with some illustrator line work on top. Just zooming in give me a 5 second screen redraw, everything is very sluggish and occasionally I get a crash. I still get these weird alert box saying "Generating Pixels" now and again when importing the psd files.
    G5 Dual 2.0GHz, 2.5GB RAM, OSX 10.4.11, Illustrator 13.02, Photoshop 10.0.1.
    I'm not having these issues on a different mac running CS2.

    I'm thinking it might be RAM, I have Photoshop and Illustrator open at the same time. I have around 100GB of scratch disk space.
    But weirdly the slowness is not apparent using CS2. Things are just dead slow with a Photoshop file placed in Illustrator CS3. These files are only 30MB, but contain 3 spot channels + CMYK. Even with preview mode switched off, it's still very slow and I mean everything slows down.
    There is a lot of disk activity going on, so maybe my hard disks on this 3 year old mac are just getting too long in the tooth.
    What drives me nuts is I remember doing the same kind of work in Illustrator 8 on a G4 running System 9 and everything was MUCH faster.
    Oh, and I'd better not mention how fast Freehand was for this kind of work...

  • Transparency Issues with PSD files in FCP 7

    I'm having some weird file layer transparency issues with FCP 7. I'm working on a project that's made up entirely of graphics drawn in Photoshop CS5. They Photoshop settings were done to match an HDTV 1080i (16:9) sequence in FCP. In FCP, the pixels were set to square, field dominance to none, frame rate to 29.97 and compressor is Apple ProRes 422.
    I exported my PSD files out of Photoshop, with each layer being exported to its own file. In general, things were fine, but there were a few files where you could see the outline of the character against the background, but mind you that this is only visible once the video is rendered out in the FCP timeline. Nothing is visible in Photoshop, nor is it visible while viewing from the Browser in FCP. I told this to the artist and he went back and made corrections, making sure everything was on a transparent background, but the result was still the same - once I rendered the graphics out in FCP, these edge lines were visible.
    I then went back into Photoshop, opened all the files that were giving me trouble, clicked on the "foreground color" and changed it to a color other than white, then back to white and hit ok. That seemed to work - even when rendered out, I was getting no artifacts, until I tried enlarging the graphics over 100%.
    Also, with some of the same graphics, I was trying to layer them so that a guy was in the foreground with other people and a van behind him in the background. Once again, no problem in Photoshop, but once brought into FCP, the background people were actually being displayed over the main foreground character.
    I'm pretty baffled - what to do? I'll attach a photo of the weird lines around the characters. It might be hard to see at this size, but if you download and enlarge it to 300% or so, you'll see what I mean.

    Just saw that Adam's original post was an older one.  Will keep this here anyway to maybe help the most recent poster.
    Sharon
    Adam, did you try what David said about pointing to the root folder?  Did that work?
    When I copy the SD card, I name a new folder on my hard drive something specific, like Smith Wedding.  Then I copy everything inside the SD card to that new folder.  The first level inside my new folder now has folders for
    AVF_INFO
    PRIVATE
    and on down from there.  When you open Log and Transfer, point it to the Smith Wedding folder (of course whatever you have named yours).
    ClipWrap2 also works great to convert the files beforehand if you want.
    What camera are you using?  I have the Sony NX30 and it was giving me fits because the .mts files don't ingest if the clips are longer than 11 min. My problem is that I'm still on FCP 6.0.6.  I think 7.0.3 fixed that.  But I did find enough work-arounds to keep the camera. 
    This is a link to the full discussion if you are interested.
    https://discussions.apple.com/message/19085158#19085158
    Sharon
    Message was edited by: SSteele

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • Photoshop - Difficulty with psd files

    I use CS5.  All of a sudden I can't open psd files.  They all look like the image below with this almost checkboard like appearance on them.  jpgs open fine.  This is happening with files on multiple EHDs so it doesn't seem to be an issue with one file or set of files.    If anyone knows what night be causing this or how to fix it, I'd be most grateful.  I tried reinstalling CS5 but the problem remained.  Thanks in advance.

    Clearly it's a display problem as the Layers panel thumbnail is okay.
    Christoph is exactly on point, the display driver is faulty.  Perhaps you got a new one via Windows Update.  The drivers that come through Microsoft that way often cause problems.
    Go to the web site of the maker of your video card and download and install their latest version for your hardware and OS.  Make sure to carefully follow their instructions, as the installers for drivers are particularly tricky.
    -Noel

  • Aperture is unable to reconnect with PSD files

    I used Aperture's 'Consolidate Master' command to move some files from Referenced to Aperture's managed Library. Aperture didn't locate some PSD files with edited in external editor badges and left them behind during the file move.
    The files that got abandoned are PSD files with quite a few layers. The actual file sizes are much bigger than Aperture reports in its EXIF information for the files.
    I have tried using 'Manage Referenced Files' command. I locate the proper master file but Aperture won't reconnect. Has anyone else experienced this problem?

    Fortunately I have never made the assumption that editing a file externally preserves a fully fledged master copy in Aperture.
    I always save externally edited files from Photoshop to a desktop folder intially, then import that folder when all the external editing for that shoot is complete. Only then am I convinced that I will have a Jpeg (or Psd or whatever) as a grade 1 master file.
    Also, mixing file types any folder or album always seems a bit dangerous to me.

  • CS4 (PS 11) constant crashes with larger files -

    I am encountering persistent program crashes with Photoshop 11 (CS4) when I have multiple layers (four or more) and the file size exceeds 75 mb. The error message that Photoshop has encountered a problem and is closing appears without further details. When I reopen PS, I then get the message about "Photoshop encountering a problem with the display driver and disabled GPU enhancement" despite the fact that I previously unchecked enable OpenGL drawing in the preferences-performance tab. It is blank on that tab after "Detected Video Card" whereas in CS3, it correctly notes the following video card. My video card is nVidia GeForce 7600 GT with the latest driver dated 10/07/08.I have 4 GB of RAM, however in the performance tab of preferences it notes 1.633 GB AM available and Photoshop using 960 mb. I also have CS3 (PS10) and do not encounter the same problem. The OS is Vista.

    Please search the various threads in this forum pertaining to OpenGL issues. Updating to the latest driver 178.24 is inevitable. Also check for the "Old GPU" enabling registry hack. The prefs only get saved on program exit, so it's natural the old options are in place after a crash. Disable OpenGL, exit the program, relaunch it and only then start working with it.
    Mylenium

  • Adobe Premiere CS6 'Create new Trimmed Project' Crash with .MXF files

    Yesterday I started to back up all our students work, and found that the "Create New Trimmed Project" no longer works in CS6 with .MFX files.
    Adobe Premiere CS6.0.3,  crashes when I try to "Create New Trimmed Project" under "Project Manager"
    This only happens when there are .MXF files in the Sequence.
    As we use Panasonic P2 cameras at this university, this is a problem, as this is the format that they shoot in.
    As a test I have made a Project with only one .MXF file placed on the sequence, and it crashes.
    This happens on my Macs and Windows machines with Adobe Premiere CS6 .
    Adobe Premiere CS5.5 works fine, and does not crash.
    Unfortunately I cant save a CS6 project as a CS5.5
    If you don't have any .MXF files to test this,
    You can make your own .MXF files by exporting any video file as "MXF OP1a" or "P2 Movie" Format, (the Preset setting is irrelevant - any preset will cause it)
    P.S.
    Using "Collect files and Copy to new Location" under "Project Manager" works fine, but does not reduce project size as much.

    I also discovered this behavior last summer.  Unfortunately the best (lame) answer I could find was that "Some formats, such as Long GOP based media files, cannot trim media, or add handles."  Source:  http://help.adobe.com/en_US/premierepro/cs/using/WS1c9bc5c2e465a58a91cf0b1038518aef7-7c72a .html
    That's not very specific, but in my case at least (and it sounds like in your case, too) .MXF may be another file type that cannot be trimmed.  If I remember correctly, the answers I got from others was that they were able to export fine.  My machine (and maybe yours) has an issue that nobody else seems to have encountered.  So none of the prescribed remedies allowed me to move forward in this regard.
    After much searching, asking and several suggestions from various Premiere communities, I gave up and moved on. 
    Use Remove Unused and then Collect Files and Copy to New Location.  At least that can help you if you have a lot of clips.  In my case, it didn't help much, because my very short clips were edited from very long takes, so as Premiere sees it, not much was "unused".
    Be aware that "Project Manager does not copy and collect After Effects compositions that are dynamically linked to an Adobe Premiere Pro project. Project Manager does save the Dynamic Link clip in the trimmed project as an offline clip, however."
    Wish I could offer you more.

  • Photoshop cc does not associate with psd files?

    I have a simple answer to the problem of photoshop cc not being able to associate psd files and not showing in the options window when you try to associate it with the psd file? How do I get it into the forum where it belongs?

    Photoshop does associate with PSD and PSB files on both platforms.
    It sounds like your OS is confused about the available file associations.
    Which OS version are you using?

  • Random unsupported image format problems with .psd files

    this is driving me nuts...just finished retouching 6 files....same as always...color, tones, basic stuff in aperture, images-edit with- CS4....work in PS CS4...come back in aperture...3 of the 6 files show the maroon screen...all files have several layers, all files are about the same size (500+mb)....this just does not make any sense at all....it also did not happen with 10.5/aperture 2.1.1 (or whatever the last 10.5 version was)....
    bad enough that raw files aren't supported but are .psd files now also considered not professional enough for a DAM?
    any input welcome.....

    The only way 'around' it is to upgrade to the required Aperture and/or OS version.  So you will need to wait for that to happen. In the meantime you could shoot Raw+JPG, use the JPGs now and when (and if) the camera is supported (or you move to a different program) you will have the Raw files.
    As for camera updates in Aperture, no one here can say what Apple intends, we;re just users here like yourself and even discussing this is technically against the TOU of these forums.
    But I think it is safe to assume, as Apple will continue to support Raw processing and that the Raw processing is done at the OS level and they have said they will support Aperture at least through Yosemite's life cycle that any new Raw format added to OS X will reusable by Aperture. But that's only a guess.

  • Importing XMP sidecar with PSD files

    I've got a boatload of PSD files in Aperture with keywords and other metadata. I want to import these into LR5.
    Aperture will not (AFAIK) write the metadata I have in Aperture to the files themselves since they are PSDs. But it does write to XMP files, so I exported a test batch, PSD + sidecar of same name to a folder. I go to import that folder into LR5 and it works, except no metadata.
    I checked the metadata in the sidecars with a text editor; it's there.
    I tried the Metadata>Read Metadata from File menu; nothing.
    What's up?

    Thanks. One problem is that Aperture doesn't seem to put things in the XMP that I'm interested in, or in places I wanted in sidecars. I didn't get too far into it, but it seemed to write a more complete set of data into the tiffs than into the sidecar for the same file. I didn't really care if it was in XMP or exif or IPTC or wherever as long as it was useful in LR. As it turned out, exporting to tiff with the metadata from Aperture was the fastest way to go for thousands of files.
    BTW, anyone have a nice chart with where various bits of metadata are stored by common applications? Although each has it's own standard there doesn't seem to be enough agreement about where a "keyword" or "tag" winds up in exif, IPTC, XMP, xattr, etc. Annoying. Supposedly Mavericks in the MacOS is gonna have some support for tagging (gee, welcome to the 21st century) in lieu of labels; wonder if they'll make any use of any of the formats we use.
    BTW, Graphic Converter 8 was very helpful in massinging metadata and reorganizing in the move from Aperture to LR. After all these years it still proves to be super useful.

  • InDesign CS5 crashes with every file. Is anybody out there?

    Hello. Can someone help me with this? I have a magazine to do, i didn't sleep for the past two days and today suddenly when i was setting up the file to send it, indesign crashes, first only that file, now all of them. It opens the recovery files always no matter what. But then crashes. Please any help would be appreciated! So much to be done.. I've read posts on this matter but nothing i do seems to work. The Sing stuff, Mark II, preferences, library.. unnistall, install.. i even moved one file to open with a windows computer and indesign also crashed, last version.
    I need somebody. Please help. Thanks in advance
    http://pastebin.com/aC0Y5L4z
    Peter Paxx

    2. Feb 6, 2012 11:19 PM (in response to mckayk_777)
    3. Feb 6, 2012 11:25 PM (in response to Peter Paxx)
    bump!
    Bump after 6 minutes? Geeze! That's a bit excessive.
    You're running:
    Version:         7.0.0.355 (7000)
    Upgrade to 7.0.4.553 and come back, reposting the crash report if you still have one.
    There are a huge number of fixes in 7.0.3, and also some in 7.0.4, which you need.
    Your crash is clearly related to preflight. If you get another crash with preflight turned off, please post that.

  • Pb export/import keywords with psd file

    While working with export and import of metadata, I found the following strange behavior with LR1.3.1:
    0) Initial keywords
    1) In LR, I modified keywords of a psd file
    2) Export of metadata
    3) Remove all keywords of the picture in LR
    4) Then, reload of keywords.
    => I should get keywords defined at the step 1
    and I always get initial keywords (step 0). It appears than something is not working as I would expect when importing, just exported data.
    Any help to understand this behavior or workaround would be welcome.
    Thanks all,
    PH

    As Curt stated, the keywords are written to the file itself and will not be cleared using the clear and import function in Keywords.
    Using the clear and import option is useful if you want to get rid of the default keywords or have a better new list for import at hand. If you already have assigned some of these old keywords to files and they are not present in your current list then they will show as italic in the keyword panel (usually at the bottom under "Other keywords") once a file with this old keyword is selected in Bridge.
    When a keyword is in italic then you have the option to make it again persistent in your new list using right mouse click menu or leave it as it is. Using the find option in the menu should provide you with the result of all present keywords in the files you are searching in, regardless if they are in the list or not.

  • LR4 crashes with video files

    LR4 crashes when I try to go to loop view with video file (MOV). Message "Load library failed with error 998". Lates version of LR4 win7 64 bit.

    Hello,
    Can you try following the steps on the TechNote below?
    Inserting a Windows Media Player in a web page:
    http://www.macromedia.com/go/tn_15777
    HTH.

Maybe you are looking for