-
Okay to change settings within existing sequence rather than cut and paste into new one?
I’ve been working on a feature-length documentary for a very long time now and I have started to run into issues – lots of dropped frames, out of memory, FCP 7 crashing. Everything was working just fine until two weeks ago when trying to render a heavily-effected clip. When trying to diagnose the problem, a couple people here suggested to me that the culprit is the system settings, which are as follows:
1440×1080, 23.98 fps, HD1080p24, 48 KHz, 32 bit Floating PointThose people told me that these are outdated, basically awful settings, and that I need to change all the settings of the project. I’m not wholly convinced this is the culprit, but, from what I gather, my sequence settings are in fact yucky and could eventually make this very large project untenable, and will be improved in several aspects by correcting them. Therefore it’s very good idea, if possible, to switching the settings, regardless of if it solves the original problem. The settings I’ve found to be more appropriate is the highly recommend ProRes422, and then HD 1440×1080 for both pixel aspect ratio and aspect ratio (are these good, healthy settings overall?). But when I cut and paste an old sequence into the new sequence, all the audio becomes firmly mixed, as several video clips play with the wrong IN and OUT points – basically it’s a nitemare. Considering there are dozens of very densely-edited long sequences, to sort out this mess with individual clips is daunting, and would be extremely time-consuming – as in months. If I can avoid this in any way, I’d practically give the world for it. Now, when I change the original sequence’s settings to the new settings, everything is just fine, no-one gets hurt. So one question I have is: Is it okay to change the settings that-a-way? Is it the same difference? If so, that would make things soooo much easier. Any help is much appreciated – this project has basically stalled due to these issues, which’s been a real bummer. Thanks.