Cinematize 2 files crashing FCP

I recently purchased Cinematize 2.06. The self-contained QT files of about 10 minutes play perfectly in QT 7.4.1 but crash (with or without the spinning beach ball) my computer when I edit in FCP 5.1.4. I've used Cinematize's recommended settings for FCP export and tried uncompressed, DVcPro and DVCpro50, same results. The crashes are so bad that I have to power off since com/option/esc doesn't work. I've re-installed OS 10.4.11 and FCP 5.1.4, same results. I've used FCP and this computer for years with no freezes but all my editing has been from captured footage from the cam. I've got 4GB ram and no other programs are running. Any ideas?
Thanks,
Henrik

I've been having the same issue with importing AVCHCD footage from my Sony NXCAM. Through some major digging, I discovered someone else in another forum recommend the program Clip Wrap 2 (which I see someone also recommended above). I downloaded it just now and it works GREAT for creating useable clips. Highlight recommend.
http://www.divergentmedia.com/clipwrap

Similar Messages

  • File Crashing FCP - Can import from different tape brand be at fault?

    I always use Sony Premium mini DV tapes and import my video through my Sony DSR-11 miniDV deck into FCP.
    I was recently handed a Fujifilm miniDV tape. The video imported fine. But once I dragged it to the timeline, rendering any transitions or filters caused big gray boxes to appear on the video. Sound also fell. I was able to make it work - but the exported file retained the boxes at different places each time I exported.
    Now the file doesn't open at all and it crashes FCP. All other files on my system still open and export fine except for this one.
    My question is 1. whether the change of tape brand can cause the import to go haywire.
    and 2. Is there any way I can open this file? I trashed preferences and restarted with no luck.
    Any suggestions ar emuch appreciated. Thanks!
    Dual 1.8 GHz G5 Mac OS X (10.4.8) 4 GB DDR SDRAM

    I've never had the same experience, so this is purely speculation.
    Changing brands used in the same camcorder has been reported as the cause of recording & playback problems. But, since the playback from the DSR was okay, I'm guessing the brand isn't the problem.
    Could be the camcorder settings don't match your FCP settings?
    What if you copied the Fuji tape to Sony tape in your camcorder. That way you would have control of both the tape and the camcorder settings.

  • AVCHD files crashing FCP using Perian

    Hi everyone, I'm wondering if anyone can help with a rather hard to pin down issue.
    AVCHD files on a SD card recorded on a Panasonic broadcast camera have started crashing FCP on random file transfers (log and transfer window), say I have 30 clips to transfer, it'll freeze then crash the system on clip 22 but the other clips will be fine.
    I have had a look at the report window and it says' Perian has unexpectedly quit' (why the **** are apple using third party software to do the job) and the log is just code to me.
    I first suspected the camera an AG HMC151 (150) because I have two so it was easy to just test the other one, but it does it on both.
    Then I suspected the cards, it does it on all of them.
    So I can only assume it's the macs, of which I have two, both have 10.6.6 and I'm running FCP 6.0.6. they are both about a year old.
    Because this is a random problem it's actually rather stressful as this is my living.
    If anyone has any good ideas or has experienced this please let me know, I think I have mentioned everything I know and apologise if I have left out some piece of vital info.
    Thanks

    I've been having the same issue with importing AVCHCD footage from my Sony NXCAM. Through some major digging, I discovered someone else in another forum recommend the program Clip Wrap 2 (which I see someone also recommended above). I downloaded it just now and it works GREAT for creating useable clips. Highlight recommend.
    http://www.divergentmedia.com/clipwrap

  • Project file crashes FCP

    I was editing last night saved the project and now it crashes FCP on launch on all our editor, and it's autosaves do the same thing. Other projects open fine. I have tried taking the media offline, restarting etc.

    Ok,
    Here is the log
    Date/Time: 2006-12-15 16:26:35.558 -0700
    OS Version: 10.4.8 (Build 8L127)
    Report Version: 4
    Command: Final Cut Pro
    Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Parent: WindowServer [60]
    Version: 5.1.2 (5.1.2)
    Build Version: 3
    Project Name: FCPApp
    Source Version: 609211640
    PID: 606
    Thread: 0
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000001
    Thread 0 Crashed:
    0 libSystem.B.dylib 0x9000ff50 __sfvwrite + 752
    1 com.apple.FinalCutPro 0x0047fbf8 SegmentStartEnd(KGDictInt**, long, long, double*, double*) + 172
    2 com.apple.FinalCutPro 0x00469728 GetNextClipInfo(PlayerSegmenter*, trackInfo*, double) + 232
    3 com.apple.FinalCutPro 0x00469be4 InitTracks(PlayerSegmenter*, KGListRecord*, long, unsigned char, KGDictInt*, trackInfo**, long*) + 428
    Model: PowerMac7,3, BootROM 5.1.8f7, 2 processors, PowerPC G5 (3.0), 2.5 GHz, 2.5 GB
    Graphics: ATI Radeon 9600 XT, ATY,RV360, AGP, 128 MB
    Memory Module: DIMM0/J11, 256 MB, DDR SDRAM, PC3200U-30330
    Memory Module: DIMM1/J12, 256 MB, DDR SDRAM, PC3200U-30330
    Memory Module: DIMM2/J13, 1 GB, DDR SDRAM, PC3200U-30330
    Memory Module: DIMM3/J14, 1 GB, DDR SDRAM, PC3200U-30330
    Modem: Jump, , V.92, Version 1.0,
    Network Service: Built-in Ethernet, Ethernet, en0
    PCI Card: firewire, ieee1394, SLOT-3
    PCI Card: ATTO ExpressPCI UL4D, scsi-2, SLOT-4
    PCI Card: ATTO ExpressPCI UL4D, scsi-2, SLOT-4
    Serial ATA Device: ST3160023AS, 149.05 GB
    Parallel ATA Device: SONY DVD RW DW-U21A,
    USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
    USB Device: Sentinel SuperPro 6.3.0, Rainbow Technologies Inc., Up to 1.5 Mb/sec, 100 mA
    USB Device: Apple Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA
    USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
    USB Device: Keyspan USA-28Xb, Keyspan, a division of InnoSys Inc., Up to 12 Mb/sec, 500 mA
    FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie FW800 Bigger Disk drive LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie d2 Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: LaCie Big Disk Extreme LUN 0, LaCie Group SA, Up to 800 Mb/sec
    FireWire Device: AJ-SD93, Panasonic, Up to 800 Mb/sec

  • *** Trying to re-connect files crashes FCP

    I have a FCP project that my editor has given me on an external HD with all the music on it. The songs need to be re-connected (showing up in the project in white) but when I either try to re-connect them on the timeline or in the browser, FCP crashes. I can't seem to find anyway to re-connect these tracks without FCP crashing. Has anyone had this problem and how did you solve it?
    Thanks in advance!

    Give us exact specs of the audio files and where they originated.

  • .motn file crashing FCP

    I created a Motion project and imported it into FCP 6.0.6 placed it on the timeline and began to render it. I have tried this a few times and all I get is spinning beachball so I have to force quit everytime.
    The sequence settings are the same. The .motn project does have quite a lot of information and does need a big render even when RAM previewing in Motion.

    Save the project file for Motion.
    Export the project file with settings consistent with your FCP sequence settings.
    import.
    Then you don't have these issues and don't to need to render each time things change in FCP.

  • Thumbnail view crashing FCP -- Kona3 the problem?

    For larger projects, running bins in thumbnail view crashes FCP.
    Most of the time, I'm editing 6 to 8 min. stories for a news magazine format show. We shoot on Sony XDCAM, so usually 2 or 3 disks per project (roughly 44 mins of HD viddy per disk, with anywhere from 20 to 120 individual clips on the disk).
    However, for our documentaries (either 26 mins or 56mins) we shoot between 30 to 45 disks full of content. When importing the disks into FCP7, we use a bin per disc, translating into an average of 80 clips per bin. Whenever a project is this big, I can only open 3 or so bins in thumbnail view. After that, the system crashes. Even if I only keep one bin open at a time, by that fourth bin, the system crashes.
    We are using a KONA3 card configuration.
    Anyone else seen this?

    PROBLEM IDENTIFIED (NOT SOLVED):
    I've had this problem with thumbnail images crashing FCP after opening bins for over a year now and when going back using footage from old projects it happens more frequently. I can open 2-4 bins before it will crash FCP completely.
    TROUBLESHOOTING IN THE PAST:
    - Dumped Prefs
    - Re-installed FCP
    - Formatted & Re-installed EVERYTHING (OSX included)
    - Increased thumbnail cache size
    - Created new projects & bins, etc.
    CONCLUSION:
    None of the above troubleshooting strategies worked. Increasing the thumbnail cache size may appear to work a little but problem persists with little improvement.
    HOW I IDENTIFIED THE PROBLEM:
    Only recently have I been working with other formats aside from XDCAM. I've recently incorporated more ProRes files into my most recent project of T2i footage from the Canon DSLR camera. If I open a bin and display thumbnails of the ProRes video clips everything works without a problem. Loading thumbnail bins with the raw .mp4 files also works fine. Only loading XDCAM files will cause FCP to crash. The problem has nothing to do with the Kona card. If you read the posts carefully here and elsewhere you will see the common denominator is the XDCAM encoded video files being displayed as thumbnail icons.
    I am using XDCAM EX files at 1080p 30fps. To further isolate this problem as something having to do with the XDCAM files, another user posted on another thread:
    *"I am having similar issues with two separate projects. The only commonality between them is XDCam.*
    *To possibly isolate it I reinstalled FCP on one system, and installed latest Blackmagic driver on the the same. Both systems are up to date visa vi OS, FCP, and QT.*
    *Both still crash with the same regularity as described here."*
    Apple, this problem has persisted for more than two years and is a major problem. Just search the forums including this one. Any further upgrades of Final Cut Studio or OS X are worthless until this problem is fixed. A brand new body and interior won't fix a car with a broken engine. Please help!! Please solve this issue with the XDCAM footage in FCP!
    If anyone has any solutions or work arounds please notify me. I need it!
    [email protected]
    /\/\ichael
    Message was edited by: MichaelRev1412
    Message was edited by: MichaelRev1412

  • Word files in FCP -Formatting problems

    Does Anyone know if there is a better way to import MS- Word files in FCP. Everytime I copy and Paste it needs to set lines and formating. I only get 1 line with all the doc's information. It takes forever to format in FCP. Any Sugestions would be apprieated....

    Well hopefully somebody has a better answer than I do, but I find that it's sometimes smartest to format the text in word to match what I'm looking to accomplish in fcp. Also, I find that sometimes that word formatting can cause fcp to crash. I sometimes find it necessary to copy the text into text edit and then bring it in to fcp. By the way, I'm usually using title3D.

  • Log and transfer inevitably crashing FCP

    We're editing a couple of music video in FCP 6.0.1.
    we shot with an HMC150 so the clips are being uploaded from an SDHC in an AVCHD folder via log and transfer. the first video went relatively fine barring several problems with log and transfer (files not matching thumbnails, files corrupting, FCP crashing) the problems seem to be random and inconsistent, as issues like a misplaced thumbnail or corrupted import could be reopened and fixed so there was no way to tell exactly why each thing was happening. eventually it all subsided and work went smoothly.
    went on to finish video number two and after several imports the log and transfer feature has decided to be the death of the project. Choosing log and transfer inevitably leads to an almost instant crash of FCP unless all drives it's reading from are disconnected. reinserting any drive means an instant crash. the drives are not corrupt and function just fine with any and all other programs, even imovie.
    why in the world can't i get FCP to stay alive when i open the log and transfer? please help.

    Right - I've solved this one. It turned out that I'd recorded some 1080p50 footage. The mere presence of this on the card freaked Log & Transfer. The camera doesn't make it easy by hiding that footage when you're looking at 1080i25 (or whatever "normal" mode is).

  • Sequences crash fcp

    so we're transitioning from fcp 5.0.4. on a g5, 10.3.9 to fcp 6.0.4 on an intel, 10.4.11. i've got all my old fcp sequences transfered over along with all the necessary files. however, there are some projects that have troublesome sequences that crash fcp whenever i try and open them. the projects are updated and open fine. but when i try and open up certain sequences, they'll open up in the timeline and immediately crash fcp.
    i tried copying all the files in the project to a new project. i deleted the old project file and resaved it under a new name. i saved and restarted fcp. still have the exact same problem. what's going on? am i never going to be able to open these sequences again? cause they're kinda important.

    so your guess is that it's an operating system issue? and you don't think it could be anything else? i suppose that does make sense since the issue makes no sense at all, but just wanna confirm before thinking about spending more money.

  • Can't import audio files in FCP after snow leopard update

    i've recently updated to snow leopard. and i'm running Final Cut Pro 6.0.6
    i opened a .fcp project i created a long time ago. i tried to import a .aif file and final cut crashes. i converted the .aif file to a .mp3 file. tried to import it, and final cut crashed.
    i then went and deleted the preference files for final cut pro, reopened final cut, tried importing both files again, it still crashes.
    does anyone have a legitimate answer for why this is happening?

    BenB wrote:
    1st, FCP does not officially support MP3 audio files, so don't even use them. I'm running FCP 7 on Snow Leopard, no problems with audio files.
    1- How are you encoding them? What software is creating these files?
    2- Are you running on an external FW800 drive?
    3- How much RAM are you running?
    And as my final observation is, NEVER run Final Cut Pro 6 on Snow Leopard! Huge no-no! If you upgrade to Snow Leopard, only use FCS3. I've updated lots of systems for my students and clients, and I've seen lots of FCP6 on SL problems.
    Message was edited by: BenB
    I agree that you shouldn't use MP3 files with FCP, the manual tells you that somewhere If I recall properly, but it shouldn't cause Final Cut to crash, at least that has never been my experience, it has just caused a skipping problem, or not playing the complete song.
    I don't really understand wht a FW800 drive or the amount of RAM have to do with it, it would sure be interesting to hear your comments on that.
    However, in all due respect, to make the statement that one should NEVER run Final Cut Pro 6 on Snow Leopard seems pretty "out there" would you be so kind as to provide your rationale for such a drastic statement as that. Has there been anything official from Apple along those lines?

  • Dragging a large still image from the browser into the viewer crashes FCP

    Okay, I've not seen this problem until just a couple days ago but was wondering if it was just me or if everyone has this problem? I've found a work-around, but let me explain the problem first.
    I'm creating a growing up photo montage. I scanned all of the pictures myself at 300 dpi (as I've always done in the past) and saved them as TIF files. Some pictures as relatively small, i.e. 3.5 mb is size and do just fine, but it appears anytime I drop a picture into the viewer in preparation for the the timeline, it will crash FCP if the image file is any larger than about 5 or 5.5 MB. Now I know there is a limit on the resolution of a still and it shouldn't be any larger than 4000 pixels in either direction, but that is not my problem, the problem appears to occur with large files. I've used large still files before in past projects without any problem, so this is why I'm stumped. I've went as far as trashing my preferences, but that didn't change anything. I've even tested a still image from a past project that was something around 9 MB (or was it 19 mb?) in any case, it also crashed FCP but... I've used that picture before in past projects without any problem. I even created a new test project just in case my project file itself had a problem.
    My work-around is to simply drop the still image from the browser directly into the timeline, thus bypassing the viewer. This works every time without a hitch. I can even double-click on the still now setting in the timeline to load it into the viewer so I can add effects or keyframes or whatever without any problems (thank goodness). So, has anyone else experienced this problem or is it just me?

    Is this image saved in a colorspace mode that is anything other than RGB?
    CMYK & Grayscale images will cause problems.
    Some light reading regarding your choice of 300 dpi: http://www.scantips.com/no72dpi.html
    Unless you plan on panning and zooming your images, the best procedure is to use one of the video preset templates in Photoshop and paste your content into it. Scale and position using the Transform controls. For best results save as a TIFF without compression. Don't forget, always in RGB colorspace.

  • Bloated Project Files in FCP

    Hi,
    I've noticed that project files in FCP tend to become bloated, thus significantly slowing down the editing process, especially when autosave is activated.
    EXAMPLE:
    1. My project file, project.fcp, has reached 150MB.
    2. I copied the old sequences from project.fcp to a new file, backup.fcp, and deleted them in project.fcp.
    3. Ironically, the resulting backup.fcp is an even bigger 175MB, while project.fcp remains at the same 150MB.
    4. I then copied the entire content of project.fcp to a new file - newproject.fcp.
    5. newproject.fcp, which has the EXACT same contents as "project.fcp" is only 42MB.

    I have an old project that got very large (300+Mb !) This resulted in frequent crashes and very slow operation.
    I trimmed the project down but it was still in excess of 200Mb, but I was able to finish.
    I have just been required to edit another couple of sequences from the same material. So I did a "save as" and deleted all but the master clips I needed. The project size was still 239 Mb.
    I had removed all of the old sequences and there were very few render files, which I deleted.
    I then made a new project and tried to drag the master clip folders across. My MBP crashed each time. (17in with 4Gb memory)
    I then in a new project cut and pasted the required clips with success.
    The project now contains the same clips as previously, but is now only 2.6 Mb.
    Can any one explain that?

  • HUGE JPEGs crashing FCP

    Ok, I'll start off by admitting I made a nubie mistake scanning photos in at exorbitant PPIs resulting in TIFFs that were hovering around 1GB, yes that GIG, and the largest file being 1.58GB. I've since gone through, and exported them to JPEGs resulting in file sizes about 10% the originals. However, that largest file is still giving FCP problems. Most other jpegs, from 2.7MB to 65.7MB results in a green render bar under Unlimited RT on my 2.16 Core Duo MBP with 2GB of RAM. Now when I go over that, with the 3 files that are 77.3, 86.6, and 115.8MB, the images get an orange render bar and result in crashing FCP. I read in a previous thread that it was a memory issue, and that was confirmed when I went to play one of the images in the Viewer and I get Error:Out of Memory. So I jacked the memory, all of it. Application was always listed as 100%, but now I have Still Cache also set to 100% and Disk set to 10,000K and RAM at 1,000K, but this still hasn't fixed my issue. I've tried every way I know of to render this image, and they all quit FCP. Before I raised the memory, just placing the file in the timeline would cause a crash, so at least now it gets past that. If I let it auto render, crash. If I do it manually, crash. If I make a new sequence like David suggest in a previous thread, you better believe it crashes. The interesting thing is despite raising FCP's memory usage, Activity Monitor still shows 1.04GB of free RAM, so if FCP is Out of Memory, why doesn't it just use up that 1+GB? Does anyone know why FCP can't play with such large files?
    I guess I'll just need to recompress the few images again, but it's VERY annoying. At least I'm not trying to work with the 1.5GB image.
    -Brian
    By the way, I am on Final Cut 5.1.4.

    You can reduce the cache levels and history states in Photoshop's memory preferences. This will buy back some memory. You should quit and restart Photoshop after each major image resize. This will also keep the app from building up too much cache.
    I'll assume these are PSB format, rather than PSD. PSB's don't work the same as PSD's with scratch disk. You may need a separate scratch disk if you keep getting errors. Designate your fastest largest drive to do this.
    You really need to get them down to around 1000x1000 pixels to be truly fast in FCP.
    Don't forget that Photoshop has a new tool called Image Processor under File/Scripts/ that can size documents without really having to rasterize them. It works much faster than opening the file then running a resize. But be careful to just run 1 or 2 at a time, since I've found that it doesn't do a great job at purging the memory after each image. You will run out of memory quickly if you have too many files at once.
    Remember to quit and restart Photoshop, or even you machine if it really slows to a crawl. These are signs your hard drive is full and relaunch and reboot will clear all the temp files from Photoshop's scratch disk.

  • Calligraphy Crash FCP 4.5

    Hi, each time I tried to go in the style palette in either Title 3D or Title Crawl, it crashed FCP. Does anyone got this problem before, if yes how did you fixed it?
    Thanks
    G4 500   Mac OS X (10.3.9)   384 of RAM

    I think I found the problem. I edited one of the stills, adding a transition, and the 3 second change took 32 minutes to render. Then I made a similar change to another still and it rendered in less than a minute. I then checked the size of the files, which were provided to me as TIFFs. The slow rendering photo is 33 Megs, while the quick one is only 1 meg. I'm going to go back and reduce the size of these in Photoshop. Hopefully that is all it takes. The 33 meg photo must be some poster-sized giant. Thanks to all of you. Great to have a community like this. I learned some new things, and I love FCP Rescue --gonna keep that puppy handy. The more I learn, the more I hope I can become a resource like all of you.
    PowerMac G4 MDD Dual 1Ghz   Mac OS X (10.4.5)  

Maybe you are looking for