-
PNG stills crashes FCP7
Hello everyone,
I’ve done my trolling of the archives, to no avail.
I have a very strange glitch…I have a handful of scratch PNG stills downloaded from Getty. These are not purchased as of yet, so they have a watermark and are fairly small in size, the largest being 640×360.
When I double click the PNG file in the Browser to open in the Viewer, it crashes my FCP7. EVERYTIME. Weird, right? These are small files, kept on my RAID 0, I have plenty of processing power. I also fiddled with the App and Stills cache (it is currently 80/30 – 2048MB Apps, 569 MB Stills). It still crashes the application at different cache settings, including default. All my system settings are as it should be, everything pointing to my RAID 0.
I don’t think this matters much, but I’m editing in a ProRes 444 sequence, with a mixture of 444 and 422 HQ video clips, at 1920×1080, 23.98fps. The PNG’s are listed as 29.97fps, but that’s the usual default for stills I’ve noticed. I just wanted to open them in the Viewer and preview them before dropping into my sequence. I can’t even get there. HOWEVER, I can drag from the Browser directly to the sequence, with a green render bar of course. When I render then I double click from the sequence, it opens fine in Viewer and I can adjust from there.
Is this a Browser bug? Am I missing something about PNG’s that the general public knows about? Like PNG’s generally suck and doesn’t jive well with FCP7? I’m used to using PSD and TIFF files, which can be cumbersome, but I haven’t had this sort of problem before.
I guess I could just go into PS and save the PNG’s as JPEGS or something. But I just wanted to see if anyone might have any insight to this weird behavior.
Thanks in advance,
JosephMac 2.66 GHz Quad Intel Xeon
OSX 10.6.4
FCP 7.0.2
AE CS4
Quicktime Pro 7.6.4
8GB RAM
2x1TB RAID O (All Media Scratch Disk)
Blackmagic Intensity Pro
ATI Radeon X1900
Panasonic Lumix GH1, Panasonic HVX200A, Panasonic DVX100A -
3 Replies
-
I’ve never had a problem with pngs and I use then almost exclusively. Have you tried trashing prefs and repairing permissions?
John
MacPro 8-core 2.8GHz 8 GB RAM OS 10.5.8 QT7.6.4 Kona 3 Dual Cinema 23 ATI Radeon HD 3870, 24″ TV-Logic Monitor, ATTO ExpressSAS R380 RAID Adapter, PDE enclosure with 8-drive 6TB RAID 5
FCS 3 (FCP 7.0.2, Motion 4.0.2, Comp 3.5.2, DVDSP 4.2.2, Color 1.5.2)Pro Tools HD w SYNC IO & 192 Digital I/O, Yamaha DM1000, Millennia Media HV-3C, Neumann U87, Schoeps Mk41 mics, Genelec Monitors, PrimaLT ISDN
-
I have the same problem with PNG crashing FCP 6. Dual Quad core Intel Mac Pro 2008.
Did you ever get a solution to the problem? -
At the time of this original posting in 2010, no I didn’t find a solution. However, a while later I had a different problem with frame rates being incorrect for stills and audio and I came across this article by Matt Lyon:
https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
This is likely the culprit, importing assets incorrectly into FCP (I’m usually very conscientious about this, but sometimes you forget to set your sequence and capture settings properly after you have to do the inevitable pref trash…). If you don’t signal FCP to import at a specific frame rate in sequence settings, your stills and audio come in at default or what was set in a different previous project. In my OP, I did notice that the PNGs were reading as a different frame rate from my project settings, but at the time I didn’t think it was a big deal. I’ve changed my practices since then.
Report back if you try it.
Reply to this Discussion! Login or Sign Up