10.2 Breaks FCPX

Beware of 10.2. I installed it and now the Inspector is broken. No parameters show up. And Importing doesn't work. On both my Macs. I spent two hours on the phone with a senior Apple FCPX tech and he couldn't help. We did everything. Including a complete reinstall. It must be a plugin conflict. I'm going through removing plugins but they're located in so many places I have't found all of them yet. Bummer. FCPX needs a plugin manager control panel.

Mitchell Rose wrote:
The next step the Apple Tech was going to try was partitioning my boot drive and install the OS and FCPX in it, but we ran out of time. Once I've removed all my plug-ins I'll try that. Not hopeful though, since the problem exists on both my Macs. And I don't want t have to reboot to a dedicated FCPX volume every time I want to work.
Actually, I don't think it is that surprising that the problem is the same on both macs.
I have often used Migration Assistant as an easy way to bring a new mac up to speed. It is extremely convenient and lets you pick up where you left off.
The problem is that any cruft that was in the older mac now lives also in the new one.
That is precisely why testing on a clean new system installation is useful. And then the path ought not to be to reboot to a different drive or partition; it would rather be: take advantage of this crisis to slowly rebuild your important stuff on the new system, and leave the cruft behind. The App Store works marvels for this, as there is no longer the need to fetch dvds, enter serial numbers, etc. Need to reinstall apps? Go to your purchases in the App Store and click a button.

Similar Messages

Issues importing tapes into FCPX

Hi. I have tried importing some miniDV tapes for the first time into FCPX (latest version). I have had a number of issues:
Tape number 1 - Importing the video directly into an event (rather than creating an archive) seemed to split up the shots on the tape incorrectly, and dropped some frames. Creating a camera archive worked for that tape. However when I tried to import the clips from the newly created archive, FCPX crashed, and I had to open again. This time round, I could import the clips into the event from the archive, and they were split up into shots correctly.
Tape number 2 (which is one long recording without timecode breaks), FCPX split the first minute where some titles dip to black into seperate clips. It should have been captured as one long clip. I decided to try and create an archive again. Second time round, it correctly created an archive with one long clip and I imported into an event!
Tape number 3 - again it split some opening titles which dip to black into seperate clips in the archive. I haven't tried this one a second time yet.
Tape number 4 - creating an archive reached the end of the tape displayiong the 'end of tape' message. When I clicked ok, FCPX crashed. When it opened again, the archive wasn't displayed and I could not open the archive (it appeared greyed out). I am currently trying this one again.
Has anyone got any tips on getting around these problems? I like the camera archive idea, and the way it splits shots up (when appropriate) and logs them according to the recording date and time). I wish you could till it to not split up the clips also. I am worried about how it will cope with my VHS collection, when I connect via a AV-DV adaptor (like the Canopus ADVC55). Will these be split up into seperate clips every time there is a dip to black, or some noise on the picture? Also, will it stop creating the archive after the 3 hour tape has come to an end, or will it keep archiving a blank screen? (in FCP7 there was a limit capture option, so I could tell it to stop after 2hr and 10mins for example).
Sorry there are a lot of questions here! Any advice would be appreciated.

When I capture in Quicktime Player 7 this is the info:
16-bit Integer (Little Endian), Stereo (L R), 48.000 kHz
DV, 720 x 576 (768 x 576), Millions
When I import that clip into FCPX, it is playing audio through LEFT and RIGHT channels.
The same clip when captured in FCPX directly (not using a camera archive) also plays audio through both LEFT and RIGHT channels.
16-bit Integer (Little Endian), Stereo (L R), 48.000 kHz
DV, 720 x 576 (768 x 576), Millions
When using the camera archive feature in FCPX, there is only sound on the LEFT channel (nothing coming through right speaker). Although this time, the sound is extremely faint even on the LEFT channel - the same clip is fine when captured as above. I also get this faint audio when playing it back in FCP7
DV, 720 x 576 (768 x 576), Millions
16-bit Integer (Little Endian), Left, 48.000 kHz
16-bit Integer (Little Endian), Unused, 48.000 kHz
I think this is a specific problem with the Camera Archive feature when archiving miniDV tapes. It's a shame, since I've capture 20 already!

Best Practices for sharing media with iMovie and FCPX

So I've a large iMovie Events directory, and would like to use that media with both iMovie and FCPX projects.
I'd rather not duplicate the media, so would prefer to import as references into FCPX.
The dilemma is that I see that it's possible to modify or move media from within the iMovie application, and therefore break the reference to that media with FCPX.
I only see two options: (1) Never Ever modify the location/name of media in the iMovie Events file (even from within the iMovie app) since I would break an FCPX link if that media is referenced, or (2) always import (copy) the iMovie events into the FCPX Event Library making an independent original so that I can confidently operate on those media files in either application.
I'd surely rather not have to do (2 )(e.g. doubling my storage demands) to gain the flexibility of using either application to edit the video, but really don't want to live with the restrictions of (1).
Thoughts / Solutions? What might you consider as options or best practices?

Unless there is some other reason, users should own the right to share their mailboxes - it shouldn't be something that demands administrator management (if only so that the administrators aren't swamped by user requests for sharing their mailboxes).
For true shared mailboxes, when the mailbox is created, full access is granted by an administrator.

How do i import my iMovie event library to FCPX when the iMovie library is NOT in the home folder.

my situation:
my MBP is running two drives: a 160gb SSD that has my home folder, OS and all apps, and a 500gb HDD for data and non-essential software.
the HDD used to be my OS and home folder, so I used to run iMovie off it. but after installing the SSD, i am now running Lion off it, and it is now my new home folder.
so my iMovie events are now marooned on my ex-home folder, on what is now my HDD data drive.
I can import iMovie events no problem, as FCPX prompts for where the project files are. but FCPX doesn't prompt for the location of the iMovie events library, so how do i get those old iMovie events in?
i suppose i could copy all the events over to my SSD, then do the import, and then delete them. but that would take up a lot of space, and id rather not be copying and deleting so much data on the SSD.
is there any other way?

It is definitely to your advantage to use the FCP command to Import your iMovie Events all at once. The reason is you will not double up on space. FCP will create a hard lingk to your events so you can access them in FCP without altering the iMovie Event in any way, but without doubling the space.
So there are several ways you could approach this.
1) If you are not using iMovie anymore, you could simply move them to the iMovie Event folder at the top level of either your old drive, or any attached drive that is formatted correctly (Mac OS Extended (journaled). This would likely break any iMovie Projects that you currently have, so it is not recommended if you will continue to use iMovie.
2) If iMovie is still working, you can use iMovie to move the Events to a proper drive. Click VIEW/EVENTS BY DISK in iMovie, and Command-Drag in iMovie to Movie Events to the drive you want while maintaining your project links. This option is probably only available to you if you have set up your old drive as your official Home directory.
3) As long as you set your "old" drive to be your Home Folder in OSX, you can just leave them where they are. OSX lets you have the Home folder on a different drive than your startup drive. This is not ususally recommended, but it is useful when you have an SSD. When I got my current Mac with an SSD, I moved my home folder to the internal hard drive but OSX and my Apps are on the SSD.
To do this, I followed the advice of longtime poster Pondini, who has a great website that walks you through this.
Here is a link.
Link to Pondini's site. http://pondini.org/OSX/Home.html
Link to Pondini's post on your topic. http://pondini.org/OSX/SetupOther.html

My positive experience with FCPX.

In an effort to present the other side of the coin on this forum, that FCPX can work very well, here is my story.
For the last 8 years I've been using Final Cut Express on an older Macs. It worked fine for my various projects, although the incessant rendering would be very frustrating. (I never did find the proper format to prevent it.) When Final Cut Pro X was released, I read about it's shortcomings, so I passed.
Five months ago I was planning to video my nephew's wedding so I looked closely at Final Cut Pro X, but was very daunted by how completely different it was from FCE. A few days later I was in my local Apple Store asking their video expert about the rendering in FCE, basically he said to get FCPX, which not only handles many formats, but renders in the background when needed, and has a lot more features than FCE.
I went home and looked at my first FCPX tutorial online and thought, OK, it looks like I'm going to have to start from scratch to learn it. My MacBook Pro was going on 6 years old, so I also decided to buy a new one that could handle FCPX. I had to stay on Snow Leopard OS 10.6.8 for one vitally important application that was not being upgraded, so I went to the Apple refurb site and found a 17" 2.2Ghz i7 late 2011 that fit the bill (I wanted the ExpressCard slot), marked down from $2600 to $1900, I grabbed it.
I immediately installed 16 GB of RAM, and replaced the internal drive with the one in my old laptop, a fairly new Seagate XT Hybrid 750 GB/16 GB HD/SSD. I then bought FCPX. (After completing one small project, I actually replaced the 750 hybrid with an OWC 960 GB dual platter RAID 0 internal SSD, wow, is it fast. I work my current project there, then when complete, move it to the 750 hybrid or a 3 TB I put in a Seagate GoFlex Thunderbolt adapter .)
I have to admit that it took me a couple of days to let go of FCE and get used to the FCPX Events/Projects system, but I got through it. I did look at tutorials, but actually learned far more by exploring the menus, panes and icons, experimenting, trial and error, and reading this forum.
I finished the wedding video (32 minutes long) in about a week (learning as I went). It was shot with one camera, which forced me to do some creative editing by lifting, moving and zooming various pieces (and cutting around a very oblivious professional photographer), which gave me a multi-camera look. I added a title, transitions, adjusted dark scenes, leveled the audio in many places, diminished airplane and wind noise, and dropped in a sound effect of my nephew breaking a glass under foot (which did not actually break at the time).
I shared the wedding video to my AppleTV2, and to DVD (3 copies), and to YouTube, without any overt problems. Yes, each operation had it's learning curve, but I accomplished them all in a rather short time. The first time I uploaded it to YouTube, it took about 8 hours for a 1080 2.8 GB version, but when it was done, the YouTube site had a message that it was too long, I had to register to have longer than 15 minute videos. I then used FCPX to upload a 720 version (the actual original format), 985MB, which took about 2 hours (even with a 1 mbps upload internet service). It looks great via the YouTube app on my AppleTV2.
The only overt problem I have is a crash once in awhile either at launch or very shortly after, but I delete the prefs and continue on. I also installed some free plugins that seemed to cause some crashing, so I removed them, but the next time I opened the wedding project, I had all kinds of warning triangles. Turned out I used some of the plugins and FCPX warned that they were missing. It took a few minutes of searching this forum to learn how to get rid of those effects, I didn't even have to ask anyone.
I just bought two new 1080p AVCHD video cameras and really look forward to using them for a festival on Sunday where I'm playing with a ukulele orchestra (which I also took up a few months ago). I'm going to tackle the multicam operations with that project (something I did in my own way with FCE, even though it did not actually have that function).
My view of many of the posts on this forum is that either they have a system/hardware problem outside of FCPX, or they do not make enough of an effort to learn and understand FCPX. It takes diligence and patience, which in my experience, really does pay off. I used to dread doing tweaks in FCE, now I look forward to it in FCPX.

I'd just like to add my positive-ness with FCPX! I've used it from 10.0.1 and, since 0.3, I have loved it and raved about it when anyone asks. The multicam feature is amazing! I used to use Vegas MS for some casual editing and the biggest annoyance with FCPX at the start was the magnetic timeline but after a day or so I got used to it and now can't imagine using anything else. I've had the odd crash but they are few and far between. I won't say I haven't sworn at it a few times but the fault is usually mine in the end!
I use an upgraded 2012 MacBook Pro with 16GB memory and a Seagate Hybrid XT disc for my more "beefy" projects but I've found my 2011 MacBook Air works great with smaller projects (4GB RAM and 256GB SSD). Interesting article on fcp.co about MBAs and FCPX if anyone is considering purchasing one.
I tend to learn things as I go along; I know what I want to achieve and then work out how to get there, often with the help of the nice people in this forum . With FCPX, once you understand the basic structure it's not too difficult.
It seems one of the common themes is problems with importing AVCHD / MTS files. Since 0.3 I've never had any problems as long as I follow my basic rules -
Format the SD card in the camera just before use (use "low level" if offered for the first format) and shoot your footage. Use the same quality format on that card throughout the shoot.
Remove the card and plug it into the computer's card reader. Do NOT interfere with or modify the files in Finder in any way!
In FCPX create an archive from the card on a separate external disc. (If the card doesn't show up then try another card reader - there can be differences in USB chipset implementations).
Import to the events from the archive. Once done, repeat from 1.
Phil

Fcpx, Blu-Ray & toast 11 = Burn both files in the img?

Looking to burn a Blu-Ray that is compatible with a standard home Blu-Ray player.
short:
On a FCPX Blu-Ray IMG, do you include both files in the burn or just the BDMG?
Long:
Job is all 5D mark 3 footage.
I have FCX 10.0.8. & output finished job to "share" BLU-Ray.
Result is a .IMG that when opened holds a BDMG file and a folder labeled CERTIFICATE.
I have a Mac Book Pro with a Blu-Ray burner.
Also have Toast 11 with the DB add-on.
What I don't have is a standard home Blu-Ray player to test the burn.
I do have a Blu-Ray player on my Mac but it's not the same as testing a standard home Blu-Ray player because on a home player when you put the disc in it either plays or doesn't.
Anyone experionce this before? And knows the solution to this diddy?
Thanks!
I would spend hours searching all the... results, as I normally do, but need to get it out tonight :-}

I think I found the answer. Looks like Both go in the burn.
1st, sorry for the short hand speech and typos. (BDMG should be BDMV)
In videohelp form it was suggested that both the BDMV and the CERTIFICATE should be in the burn.
http://forum.videohelp.com/threads/325212-How-to-burn-a-BDMV-folder
Incase someone is searching for this same question, I thought I'd give the answer I found and break it down a little further.
Q: How do I output to Blu-Ray in Final Cut Pro X? I don't see a Blu-Ray option.
A: In 10.0.8 that option is hidden from the main "share" menu.
Here is Apples "how to" page on how to find it, along with other info on Destination Prefs:
http://support.apple.com/kb/PH12718
Basically you select Share, then the plus sign "Add Destination" located at the bottom of the list, then Blu-Ray.
When you select Blu-Ray, in the preference window, the first pref. is "Output device" with two options your burner or hard drive. If you pick hard drive you get a .IMG that you would open and place the contents into a burn.
Q: What Blu-Ray burner is in your Mac?
A: a Panasonic UJ267
Very overpriced and had to modify (voided the warranty) in order for it to fit in my 15-inch, Mid 2010 MacBook Pro.
I switched one of the covers on the Panasonic with my existing to get the right fit. One screw hole had a "no tamper" label that I destroyed, so that voided my warranty.
Q: why not an external?
A: I have one but it's big and needs AC power so it's not easy to move.
This is soooooo much easier because it's so mobile.
24 Gig backups of all my stuff for a $1 per burn is priceless.
Best of luck!

FCPX newest 10.0.6 update = NICE! ... Do I stay or do I go?!

For all of my ranting and raving about certain issues with Premiere CS6, I have found it to be REALLY great in many ways. With a very helpful forum here its been a fairly easy transition coming from Final Cut Pro 7 last month. Since I edit full time 6 days a week finding just the right NLE for me was REALLY important. I did the 30 day trial of both FCPX and CS6. It took me WAY longer to figure out FCPX, but I gave each a full 30 days and they BOTH had their strengths/weaknesses. But ultimately there were just more features missing from FCPX that drove me nuts and since CS6 was an "easier" transition, I chose CS6. And now this... FCP just released a massive new feature rich update 10.0.6 that fills in several of the HUGE features that were missing that originally drove me away. So what the hell do I do now? Here are my reasons for staying and going as of right now:
Why stay with Premiere CS6:
It's easy. Not much different than what I was used to with FCP7.
It ties in nicely with Encore which I use often.
Adjustment layers and Warp Stabilizer (my favorite 2 features of Premiere CS6)
I've already hired 2 editors to work with me and made them both learn Premiere CS6 over the last month for my projects. This is huge for me because FCPX would be much more difficult to teach them or have them learn since they too came from FCP7.
This forum. I'm still finding new features every week that make my workflow easier and faster.
FCPX is much more confusing of a transition. After watching hours of tutorials on it sitting down to work I felt like I needed a Warp Stabilizer of my mind. Its an entirely different way of working and thinking about how you edit (granted, many of the things I didn't like are now fixed or added in this latest update)
Why go to FCPX:
I'm a Mac user and whether its true or not I've always felt that Premiere is optimized for PC users (more cards supported for GPU acceleration, etc. which makes it all run better) Don't get me wrong CS6 works on a Mac, but FCPX is definitely Mac optimized. This and the frequency and size of updates are the two biggest things for me in my leaning toward using FCPX.
While it's a more difficult transition, like I said above, many things I felt were missing have been added back in the latest update.
In many ways, I found FCPX to be so simple, almost too simple. Once I got over that simple doesn't mean that its not good, I found it to actually be a better way of doing things...for MOST (not all) .
Updates, updates, updates. They come fast and often and I love that. They are usually feature rich and the newest 10.0.6 is no exception. FCPX in just over 1 year has gone from "what were they thinking" to "wow" through all these added updates. And its not just adding in things that should have been there from the start, its adding them in a way that is even better and more streamlined than any other NLE.
Errors/Bugs in CS6. Premiere CS6 is a fantastic step for Adobe but I've had more "errors" and "bugs" than I ever thought was possible in just a few projects. Maybe its my computer (the most suped up 2011 iMac available), maybe its my files (AVCHD) but by the end of a recent project I had 7 versions of the same project because it crashed so much and I had to rename it upon re-opening it. Granted, there are many helpful people in this forum that provide great workarounds, but still the issues are there. I'm sure Adobe is working on them and a new program will always have bugs but its been a up and down ride so far. Almost went out and bought a PC the other day just to see if it would be better.
I already have (and totally understand) Compressor and other programs that integrate with FCP. Granted there's a lot to like about AME, I'm just saying.
Multicam is great in both but hands down better (in my opinion of course) on FCPX (especially with this update and the audio channel enhancements). Since I work with multicam edits a TON, this is important to me.
Damn. I thought I had made up my mind and now I don't know what to do. I'd say I'm 55-45 leaning towards staying but that's cuz I'd have to re-learn much of what took me so long to figure out the first time around. And I dread having to tell my editors okay, now learn this. Maybe I'll do another 30 day trial and see (can you do that?) if its worth switching. Maybe its not. I'm probably forgetting 5 things that drove me nuts about FCPX that made me say "that's it, I'm using Premiere!" I know asking this question "Do I stay or go?" in an Adobe forum is kind silly...but I figured why not. One things for sure...when it comes to making this switch, I know it will eventually become a permanent switch and for that reason, I'm totally indecisive.

oh and I just remembered another thing that bothered me in my FCPX experience: memory management. As someone in another forum put it...
"...one thing that FCPX needs is LOTS of memory. One of the main reasons is that there is a memory leak in FCPX, in which FCPX does not release unused accrued memory. As such your memory usage keeps adding up until you get the spinning pinwheel of death."
Yeah, I remember that sucked. With 16gb of memory, I had times where I checked and I had 14-15gb of "inactive" memory and things would slow way down. I had to use a 3rd party app like FreeMemory to release it and make it available/free again to FCPX so it would speed up. But it would just drop back down soon enough. Maybe its been fixed. Maybe it was my OS (10.6.8). Maybe it was the program. Who knows. But I do remember that not being fun.
Also I've read that if you are having issues with FCPX, then maybe "make sure you work with clips of 20 mins or less". What?! So if I have an hour long clip of an event, people suggest to break it up into 20 minute segments and then piece it back together later? This baffled me. PPro has its bugs no doubt and they cause it to freeze and crash but I remember now these things bothered me to no end in my 30 days with FCPX.

Is the prores file that FCPx creates when importing c300 .mxf files stable/quality enough to then copy to other drives for further use? Are there any quality disadvantages to doing that?

Im wondering if I can directly copy the prores files fcpx creates when importing c300 .mxf files from the "original media" folder, reimport them for another project to and use them that way. Is there any problem with working that way? I'm doing this bc I want to have an organize finder structure for a client but cant break the c300 card structure to split clips on a card into different "scenes" to make it easier for them to understand what they're looking at. This is all to stay NLE nuetral--we like fcpx but they might want to edit somewhere else and more details in the finder level seems like the best solution? Suggestions on any of that? Thanks.

Thanks for your response. Are you sure that FCPx is working with .mxf/c300 natively? I thought it was just a background sort of repackaging or transcode into prores that it does without you having a choice? And bc of that, for me, it's sort of a "back end" feeling file: I'm curious if it's bad to get into the package contents folder to copy it over? Not about copying prores in general-- specifically, is the prores created of c300 footage in fcpx more of a fcpx, high quality alias file? Maybe I'm just feeling a little uncomfortable grabbing things from the inside/finder level of fcpx.

OS/X 10.8.3 - Any Issues with FCPX?

Has anyone found any issues with FCPX after upgrading to OS/X 10.8.3? Everything's working fine on my machine with 10.8.2, and I don't want to break anything...
Thanks.
Dan

Ben - Thanks for the reply!
BenB wrote:
I've been using it with no issues at all. Be sure you upgrade the CUDA driver to 5.0.45 in your Mac, also.
http://www.nvidia.com/object/mac-driver-archive.html
I thought FCPX doesn't use the CUDA driver. Some people on the "freeze" thread were fairly adamant that it doesn't. Am I wrong?
Dan

Folder created with the same name as a fcpx library

I recently moved to a new Mac Pro with a Pegasus 2 array from an old machine. I copied my old library across since I couldn't migrate because the old machine was a server.
now every time a run FCPX I get a new folder created with the same name as the fcp library. Inside is library with a timestamp as a name, and inside that is a folder structure which matches the true folder structure in the real library. The contents of the subfolders are empty (original media, eg). This parallel folder/library structure remains when I exit fcpx. Nothing of valuie is put in it. A new clip or still gets put in the correct place in the true library.
If I delete this parallel stuff it gets created again next time I run fcpx. The permissions look ok, the user id is 501.
Anybody have any suggestions as to what I should do?
Chris

Sounds like the folder of back-up libraries. If so, they take up a tiny amount of space and could prove to be very valuable if a project breaks. Does it look similar to this?
Russ

Fonts get switched between FCPX and Compressor

I edit my video, make some simple intro and outro titles with specific fonts (Gill Sans, Adobe Garamond Pro) and although the fonts look fine in Final Cut Pro X when I send the video to Compressor 4 FCPX swaps out the fonts. It's driving me nuts.
I've run Font Book and verified the fonts and they pass. I've done the share to Compressor twice and both times it swapped out the fonts, each time for different fonts.
Anyone have this problem or have a solution?
The video I'm editing hasn't been brought in and optimized, it's H.264 video in place, no audio. Very frustrating.
Here's a link to the video, you can see three different types of fonts due to the fonts being lost between FCPX and C4. http://www.hawaii247.com/?p=56608

I spoke with Apple Tech support, the first line told me if I had Adobe CS 5 installed on my system it would break the fonts, and suggested I create a new user, install fcpx under that user, and do my editing from there. I asked to have the case escalated.
The second line tech support indicated they have had no reports of this issue, however he was able to duplicate the problem 100% of the time using his "clean system" running Snow Leopard. He said he woulde further escalate the bug to the engineers.
As as work around he suggested I creat all titles in motion (alpha chanel only) and then bring into fcpx as a .mov file. Great, I only have a few hundred titles..
I suggest every user that is experiancing this either make a bug report via FCPX or call apple tech support and report it, otherwise it might be way down on the list of fixes.
So it is a bug, and has nothing to do with fonts, prefs, or Adobe products.

FCPX 10.0.4 crashes when trying to import media

I updated to FCPX 10.0.4 the other day and just tried to check out some 1080p24 footage I shot with my Panasonic GH2 this morning. Some clips seem to work fine, but a couple are causing problems. I use transfer from camera, select a clip or part of it, and select transcode to proxy. It seems to copy it to the Original Media folder, but crashes. Nothing ends up in the Transcoded Media folder. I reopen FCP and it shows the clip as missing, because I have selected to use proxy media. If I switch to Original, or try to intiate a transcode manually it crashes. I can remove the clip manually form the Original Media folder to get going again, but same thing happens on that clip. I just tried again without transcoding and that doesn't seem to work either. It just doesn't like something about importing these clips. They play back fine when I view them in the Original Media folder, so they don't appear to be corrupt. Any ideas?
Unforunately, I don't have another system available I can check these clips with, is there a way to roll back to 10.0.3 to try it?

I still have the trial 10.0.3 download, but unforunately can't run it because it's expired.
There's another guy here that seems to be having similar issues importing AVCHD (same as my GH2).
https://discussions.apple.com/message/18147371#18147371
I removed the problem media and was able to continue for awhile without it on my macbook air while I was away. Now that I'm back home on my 2009 era mac mini I have since imported more footage and encoutering the same thing on this system (also, unfortunately updated to 10.0.4). It was at a point where it'd crash everytime it opened. After a few times it wouldn't crash on opening, but I found that if I scrolled up through the clips in the event viewer, as soon as one particular one started to appear it would crash. The problem clips seem to probably be higher bit rate because they have more motion like steadicam or slider in front of moving trees.
There's stuff related to AVCHD in my crash reports. I looked inside the app package and saw this file. I compared it to the files inside the package from the trial and it's definately been updated. I haven't experimented yet, but I thought about trying to copy the old AVCHD plugin to the new version and see if it can handle my footage better, but I don't know what else breaks if it's expecting access to new features or something.
0x11a9f0000 -
0x11ac87fef com.apple.AVCHDPlugin (2.0.0 - 1014.5.29) <02B6EE1F-C8BA-EB46-14BE-17330045B3C8> /Applications/Final Cut Pro.app/Contents/PlugIns/RADPlugins/AVCHD.RADPlug/Contents/MacOS/AVCHD
I've got several saved, I can post the full thing, but I know nobody likes scrolling through it all.

How to break a long project in 3 smaller timelines and assembling them back

Hi,
I'm presently working on a big project (a 90 min long documentary). I took advantage of tips from other user to speed up FCPX but now I'm at a point where I fell in need of a radical switch to give breath to my mac (btw I just switched to a new iMac with 16gb of Ram)
I've been wondering about an advice which was gave me from Russ H on this forum: I'm presently at minute 60, he suggested me to create another timeline for the last 30 min.
I think I have to go further ahed, I need to break the exisiting timeline in two, so to have two 30min long TL. And then I have to create a third TL with the last 30 min.
Here we go with my questions: 1) to have new timelines I need to create/duplicate projects? Or I can just associate more timelines to the same one?
2) If not I think I have to duplicate my project three time and then cutting the 30'min segment which I don't need to be in that project...and then of course I have to start building my third edit in the third 30min TL
3) Here is the point which make me worried the most...At the end of my work how can I put everything back togheter? Is there any "merge TL" function? I should just export 3 masterfile and then assemble them? I should just put the 3 file on XDCAM disc as clip to be playied in a row?
Thank you in advance for your help,
Nico

As I recall, the suggestion to create separate projects was one of several to address increasingly sluggish performance as your project grew in length. The idea was that by opening and working on shorter timelines, you would place less of a processing burden on your machine.
Now that you have a newer, more powerful iMac, it may not be necessary to break up that project.
If you still think it is desirable to break up the project, I would stay within the existing library and create a new project for the last part of the doc. If you are still working on the first 60 minutes section and you want to work in smaller projects, create two more empty projects. Then select two sections of the original and paste them to the new projects' timelines. When you have finished all three sections, create a fourth project and paste copies of the three into it.
There is no merge timeline command, but copy paste is pretty bullet proof. Click in the timeline window to make it active. Hit Command-A to select all; Command -C to copy, Open the empty project and hit Command-V to copy. Just make sure that your playhead is at the last frame of the sequence before you paste any more sections into the "omnibus" timeline and it should go quite smoothly.
Russ

Angle Editor Not Showing Up in FCPX

Hi,
I'm running FCPX 10.0.7 and am having difficulties with my multicam clip.
It's in the timeline and for some reason I simply cannot get it to open in the angle editor. I ctrl-click the multicam sequence and select "Open in Angle Editor". For some reason, it simply won't open up. I just click it and nothing happens. The multicam sequence is inside a compound clip i created. I tried copying to a new project and got nothing. Also tried breaking apart the compound clip and still nothing.
If somebody knows a way to fix this, that'd be amazing. Thanks

Try opening the multicam clip in the event browser. Should update to 10.0.8.

In the middle of editing a project in FCPX and render ceases to work

Hi,
Editing, then took a break and left computer to sleep for a couple hours. Came back to find, FCPX isn't rendering my clips, at first it showed there were
segments needing to be rendered, but the background task was all in idle. Then I added transitions, nothing, then I highlighted the segments and clicked
Render Selection....now for that past 10 minutes the render has sat on 0%. It is a very small segment so I know the render would only be a minute or
two....curious?

ashambeck wrote:
Is this something that will happen occasionally.
I haven't run into this – even occasionally. Restarts and/or reboots are often all it takes to clear up flaky behavior.
Russ

10.2 Breaks FCPX

Similar Messages

Maybe you are looking for