Bugs in FCP 7.0.2????

I'm having the most peculiar issue, and was wondering if anybody else out there is experiencing the same? When I create new sequences, or exchange sequences between my assistant and myself, some of my add edits disappear, and sometimes some audio rubberbands as well. The effect is drop out of some sound or weird sound cuts in the sequence. We have experienced this on two different shows (one hour narratives) at different work places, and it is really frustrating.

I suspect that the rendered video (Control+R) on your computer differs from your assistant's computer, when your assistant plays it on her computer (on her FCP), her FCP might be playing from the un-updated cache of rendered files. In other words, did your assistant rerender each time you gave her an updated FCP project?
If not, to fix this, on your assistant's computer, copy the updated project, go to Tools->Render Manager and click on Remove for all the files listed. Then click on OK (and OK to the warning) and then Control+R again.
I encountered this problem a couple of times myself and this fixes the problem for me. Basically FCP dosen't detect the conflict/update sometimes.

Similar Messages

  • Graphics render bug in FCP 6 and 7 - Dare to prove me wrong?

    I have an issue with an HD video that contains red and purple text and graphics in the edit. I've looked for an answer tirelessly online, with friends, and through trial and error for a good 7 hours before giving up. Here's the deal,
    Sequence settings: HD 1440x1080 16:9, 23.98, HDV 1080p24 for editing the canon7d footage that came in - this however doesn't matter because i tested with every setting imaginable including animation raw and ended up with the same results for the graphics problem I'm having (kind of unrelated to the actual footage).
    I need to output this 9 minute edit I have to an HD file 1280x720 for youtube upload. So, it has to be under 2gb (youtube's limit) but for client purposes, it needs to be crisp and great looking as you would imagine.
    I have a bunch of PSDs, each show a different line drawing of a brush. For each one, the line is a different color. For any of the colors that aren't red or purple, they render crisp and wonderful in final cut pro over top the video. However, the graphics that have the lines that are red or purple, come out pixelated and blurry no matter how i try to render them. The only solution that worked was to render and output them with the animation codec. ProRes HQ worked too but not as well. However, this makes a file way too big. Whenever I went from animation to h264 or from FCP to h264, or any other web friendly format, graphics come out way pixelated. It makes me frustrated as to why all the graphics that were exactly the same except not red or purple came out perfectly crisp. Also, why is animation codec the only codec out there (besides uncompressed obviously) that will create clean edges in these red/purple graphics?
    Conclusion: Found that reds and purples are the only colors that seem to be effected when rendering the graphics. Everything else comes out nicely. Animation and pro res codecs aside, any codec making the video small enough for the web (less than 2gb) resulted in the problem of pixelation with the red and purple graphics. Based on extensive research I did online, I was surprised not to find many people posting about the exact same problem. For the issues I did find that seemed related, people concurred that HD nor regular DV video do a good job rendering bright reds or variations of red. Because I found no solutions online or from all the things I tried in the list below
    -re-rendered the PSD's in Final cut pro with variation of sequence setting to see if that would make any difference - it didn't. Tried all kinds of different settings in export for h264, keyframes, max quality, etc. no luck.
    -tried rendering to "Animation/uncompressed" as far through the process as possible. For instance, I outputted a perfectly crisp "Animation" file that was perfect looking. As soon as I re-exported to h264, mpeg4, or sorenson, or any other codec dropping the file size down, all results returned pixelated results for the reds and purple graphics.
    -made sure photoshop settings were all good, even copied and pasted psd into new 1920x1080 project, played with DPI up to 300 to see if it did anything, saved as different formats TIFF, png, eps, layers, flattened, 8-bit, 24-bit, 36-bit, etc., none of the formats worked correctly.
    -outputted my own purple and red graphics and text and rendered in final cut to see if the file had anything to do with it. same problem with my red and purple graphics and text.
    -Tried adding slight moving grain to the graphic in Final cut to try and trick FCP to thinking it was a video instead of a graphic and therefore render it smoothly.
    -consulted with 2 other video editors/media experts, ended up frustrating them as well (and hurting their ego a little since they were sure they could figure it out)
    -Ran the shot and graphic through after effects and premiere pro separately (different video programs) to see if final cut pro was causing the problem, same problem with those programs.
    -tried rendering on a different mac, still the same.
    -Actually upgraded my final cut pro version to the new version (now Final cut studio 3). Ran tests on new version of final cut pro, same exact problem.
    -added black edge to purple graphics to see if that did anything different to the rendering. Didn't help
    -Changed the hue of the graphic to anything other than red or purple. Wouldn't you know...That fixed it.
    Here is a link to the Animation Output of a half second of the edit with a sample red graphic crisp as can be for you to test (12.7mb) -
    http://www.robinsonhope.com/downloads/makeup_animationtest.zip
    Here is a link to view screenshots before and after to show you what rendering does to the graphics.
    http://www.robinsonhope.com/downloads/makeup_ss.jpg
    In case you'd like to try and find a solution, please download the link to the HD animation half-second clip and output to h264 or any other web friendly codec that would show these red graphics clean and not blurry and pixelated. Other rule is after doing the math, a 9 minute video with the compression you choose would need to be under 2gb. This shouldn't be too much of a problem because even a 1280x720 h264 at max quality for a 9min video is still under 2gb.
    The first person to show me that you are truly a FCP guru and can solve this, post a link of your successful solution, I will praise you as genius all over this forum. I will also be eternally grateful. Live in LA? I'll also buy you dinner, Haha. But seriously...

    Welcome to this forum,
    Sorry to hear you so struggling with this issue.
    And I doubt whether I can solve this for you, but I can say a few things.
    The title of this thread is:
    Graphics render bug in FCP 6 and 7 - Dare to prove me wrong?
    I'll prove you are wrong. Or actually you've already proved yourself wrong in your post:
    -Ran the shot and graphic through after effects and premiere pro separately (different video programs) to see if final cut pro was causing the problem, same problem with those programs.
    Seams that I try to annoy you, but I'm not. It's not a joke. The fact that other applications can't handle it as well AND the fact that Animation Codec (Which is pretty lostless) does not have this problem, tells you that the problem is likely the low compression you want OR the footage itself. And I dare say it's BOTH.
    I downloaded your testfile and have opened it in FCP and I can see in the Vectorscope that your color Red is too hot.
    [Click here|http://i843.photobucket.com/albums/zz356/rienkL/Screenshot2010-04-02at1324 20.png] to see the vectorscope of your picture?
    You also see the small boxes (clockwise)
    Red, Magenta, Blue, Cyan, Green, Yellow. The signal of your picture should stay somewhere between those boxes. You should read [this article|http://www.larryjordan.biz/articles/lj_scopes.html] (two third on the page) about the vectorscope. Also has a picture with the range to be broadcast safe.
    So back to your picture and your vectorscope. You'll see that just along the right side of the R in the vectorscope there's a peak which goes way out of the range. And that's exactly the color of your graphic.
    I tried isolating that color, reducing the saturation, and then do an export, but that failed. You should adjust that within the PSD's first and then see how exporting goes.
    So now you are thinking: My client wants his own colors! Sure he does. But those colors were probably designed for print, which does have another colorrange. Simple technical story. You're bound to specific saturation. Going over that means troubles....
    And I'm not claiming that your problem will be solved when you adjust this. It is still possible that h264 just doesn't like red too much. Maybe that's on purpose. Our eyes are most less sensitive to red, so that gives the compressor some extra room to compress in the reds (Don't know if this is what compression developers do; just thinking out loud, just an idea...)
    Hope this helps at least a little.
    Rienk

  • Copy and Paste bugged in FCP 7??

    Is anyone else having problems with copying from one seq to another?
    Everytime i paste an item into my main seq it changes the name of my seq to the pasted item.
    Its doesnt stop me working just quite confusing and annoying..

    Thanks the the suggestion, already had trashed the prefs.
    Description of workflow is easy.
    Load two seqs. (say seq 1 and seq 2)
    1.copy a clip (lets say, named 'clip 1') using 'apple c' from seq 2
    2.paste into seq 1 using 'apple/shift p' (or from edit menu) into seq 1
    seq 1 is now named 'clip 1'
    this has only happened since upgrade to FCP 7, it didnt happen in 6.0.5.
    OS reinstalled 2 months ago and updated to 10.5.6 and fresh install of 6 updated from start to 6.0.5
    then updated monday to FCP 7.
    If no one else has this problem, then i will do another os reinstall and a clean install of 7.
    Such a odd bug had to post.
    Thanks
    new features are great and i expected to hit a few bugs as FCP 7 is hot off the presses

  • A BUG in FCP 7: Multiclip Markers slip when copied from project to project

    Alas, not all things are great with multiclip markers in FCP 7.
    We are shooting multicam on a show with dual system sound. Individual camera angles are synced to the production sound (broadcast .wav) and merged to create new master clips that use the stereo production audio instead of the original camera audio, then the new synced/merged clips are made into multiclips using In points set on the slate claps as the multiclip synchronization method. Markers added to the A angle and B angle do indeed stay attached when added in the viewer (thanks for that bug fix, Apple). The assistants are marking the beginning of each take and all resets on each angle, so that both Angle 1 (A camera) and Angle 2 (B camera) have the exact same markers on the exact same frames.
    Problem is, when the editor opens the dailies project and copies the bins with the marked multiclips into his editor project, or his or her version of the dailies project is updated, the markers on Angle 2 (B camera) all shift in time (like they were all slipped). All Angle 2 markers in each individual clip slip the same amount, but every multiclip's markers slip a different amount. Copying clips from one bin to another IN THE SAME PROJECT yields the same slippage, and what's more, even messes up the markers in the original master multiclips (as if the copies were not affiliates but literally the same master clip as the multiclips). To make matters even worse, sometimes it's the A camera (Angle 1) that has markers slipping.
    This bug does not affect multiclips that are made from the clips using original camera audio. Since the production has, thus far, been unable to properly jam sync the audio and camera timecode, each merged audio multiclip can have, potentially, three different timecode numbers associated with each track, Angle 1, Angle 2 and the stereo audio. Clearly FCP has no idea what to do when it attempts to recreate the clips in another bin or project, but the offset (i.e. how much the markers slip) is not directly correlated to any timecode offset between the different tracks of the multiclip. How weird is that?
    It's forcing the editors to mark their own footage, which is really the assistant's job. At least in FCP 6 you could mark the original angles prior to multiclipping and the markers would stay as you switched angles, or you could mark the original angles and then replace the angle in the multiclip with the marked angle and, again, the markers would stay affixed to the angle when you switched from angle to angle. Now that doesn't even work.
    Help!
    Any workaround out there?

    Actually the 4:2:2 smoother is for prepping footage in a 4:2:2 color space for chroma keying (it prevents stairstepping due to the blocky chroma values). It is the right setting for DVCPRO HD.
    Sure about that? because it already is in a 4:2:2 color space, and there are no stair steps. Only DV has those ugly stair steps. I believe this is for DV. I have never used it, and I have comped a lot of DVCPRO HD.
    am using the Chroma Keyer filter from FCP (possibly derived from Primatte?
    Nope...Primatte is a NEW filter in FCP 7. The built in Chroma Keyer in FCP downright *****. I use DV Matte Pro for simple stuff in FCP, and Primatte or Keylight for the more complex ones, and in AE or Motion. But Primatte is now in FCP 7...well, a "lite" version called Primatte RT.
    If chroma smoothing is causing that issue...don't use it.
    Shane

  • Bug? FCP x cannot mix 24/25 fps correctly

    Earlier this week, we had a 4 camera shooting, all in full HD but some in 24 fps and some in 25 fps.
    According to Apples marketing copy, FCP X handles different fps with no problems at all.
    We experienced this:
    When putting 24 fps and 25 fps on the same timeline, they run out of sync.
    If we clap in start of recording and in end of recording and sync from the first clap, the later claps will be out of sync.
    I called Apple and ended up talking to a guy called Andrew in Apple UK that told me, that it might be due to us not transcoding at IMPORT but later on, but this made no difference to us.
    After this, I emailed Andrew / Apple directly several times, giving them a lot of tests and details and also showed, that mixing different fps doesn't give any problems in neither my Premiere Pro nor in my FCP 7.
    After several emails to Apple this week, I haven't heard a single word back from them

    Hi,
    I have the same problem as you Kenneth. I found a little work-around. I created new project in 25fps, imported to timeline all my 25fps clips, and then I placed few clips which are 24fps on timeline. Then I slowed down 24's to 96% manualy by retime, not by conform option. I hope it'll help you. Btw. I'm a fan of FCP, but X has got too many bugs... C'mon Apple...
    Edit: It still doesn't work in longer clips. I have like 15sec clip and I need to put it to 91% of original speed to keep movement of mouth and voice together :O

  • Bug in FCP 5's dip to color dissolve with text?

    Dear all, I'd likle to know if this is a genuine bug or some problem with our setting/system that we haven't yet figured out.
    The problem appears when a dip to color dissolve is applied a text clip.
    The symptom is what looks like compression artifacts appearing around the text as it dissolves. It is noticeable with normal text but looks really bad with drop shadow applied. It renders this transition unusable and it's a problem as it's part of our show's regular style. It can be worked around but this is not good enough for a pro broadcast application...
    We are running FCP 5.0.1 on a dual 2.7ghz G5 with OS X 10.3.9 and working in DV PAL.
    Any help appreciated

    Welcome to the discussions, Robert. Do you have your rendering set to Fast (linear)? There was/is a bug that causes problems if it is set to medium or high.
    Patrick

  • Bugs in FCP-Motion workflow/Render Files lost

    Hi
    There seems to be an issue with Motion files going off line in FCP 6 when a project is closed and then reopened.
    In one sequence, the render bars were (wrongly) showing up as if the motion files were fully rendered. However, on playback they were clearly playing in 'unlimited' RT mode. When I copied and then re-opened the sequence, these files were then showing up as unlimited.
    Any ideas?
    Cheers,
    Ant

    Interesting...
    I'm having the same problem when I use FCP's Smoothcam filter. I will render it all, save, close the project and the next time I open it those render files are gone. It wasn't consistent though. Sometimes they'd stick and other times they wouldn't. To work around it, once I rendered a shot with that filter I exported it as a self-contained QT movie,re-imported it and replaced the shot. Kind of a pain of a work-around, but a work-around nonetheless. (And I didn't have a duplicated sequence but was on-lining a film that was cut in FCP 4.5 - so maybe that was where my little bug arose!)

  • Dropped frames from XDCAM EX HD (1080/24p) - Seems like a bug in FCP 6.

    We're editing XDCAM EX HD (1080/24p) using the built in easy setup and dedicated built in drives as scratch disks. We have run all software updates and have the latest builds of final cut...
    We keep on experiencing dropped frames on playback, but only on our NEW 8 core Mac Pro not on any of our other Mac's including our MacBook's.
    Through a painful process of elimination, we found out that if you go to System Settings/Playback Control and you switch Gamma Correction from Accurate to Approximate it solves the problem. We have no idea why and would love an answer from Apple on this.
    Moreover is this a bug or do we need to amend something on our system. As a note we've already matched pairs on the RAM and done all the other obvious stuff.
    Regards
    Daniel

    Having the same issue with same format footage (1080/24p), the proposed solution works (a little). I can definitely playback a longer duration but it still drops frames. Even when putting a filter on and rendering it still drops frames.
    Mike

  • FCP 6 bug importing P2 media

    After running into a problem where DVCProHD media recorded at 24pA was coming in at 29.97, i found this post on creative cow:
    http://forums.creativecow.net/readpost/8/940441?
    Seems there is a bug in FCP 6 that a lot of people are experiencing. Importing the media works correctly in FCP 5, so in the short term that is what I will have use to acquire the media.
    Can we expect a bug fix soon??? This is really a pain to work around!

    Sorry, been away all weekend.
    I have never tried this. I tried the database and didn't like the way it handled things (wither that, or I was just too lazy to learn it well.) but I think that you can export QT files out of the database can't you?
    Also, and I know that this doesn't help this time but, this is a great example of why I always copy the entire contents of the card to a backup drive before I do anything else. I know that it takes time but I haven't lost any footage yet either.
    Hopefully someone will stop by that knows database better.
    ooooooooo, what version of QT are you running? The database only works correctly up to 7.2.6. If you have upgraded past that I think that you are asking for trouble.
    K

  • P2 24pa FCP bug, I think.

    OK, I shot some footage at 1080i 24pa and I am having problems with the imported footage. It should be 24 frames per second but it is playing back at 30 fps in the TC. The footage says 23.98 but the TC goes to 29 and then to 0 again. The information of the clips says 1080 p30 even though I shot 24pa. I am playing the clips back in a DVCPRO 1080 24p time line.
    I think this is a bug with FCP. 720 works the way it should but 1080i does not.
    Any news on this problem???
    Thanks,
    -Lars

    Thanks for your response, Tom.  Are you an Apple FCPX agent (looking at your thumbnail image)? 
    The video media is all imported into the library as optimised ProRes 422 and it's 40 minutes in length.  There are quite a few stills overlaid, also imported and optimised.  It was a two camera shoot and I've edited it from synced multi cam clips. 
    My point is that an MP3 export worked flawlessly from the less complete but still full length previous edit (same specs, except for the stills which were added since) in FCPX 10.1.4, before I upgraded to 10.2 on Friday.  Now it doesn't.
    Looking forward to hearing more...  And thanks again.

  • Smooth Cam not exporting properly in FCP 7.03 - please help

    Hello
    I have a 30 minute video edit. A small number of clips have the smooth cam filter applied with default settings. When I export the finished project to a number of varied settings - pro res, pro res LT, apple tv, iphone etc... All the smooth cam clips are jittery and juddering -  and are not working for some reason.
    I have done a bit of research and apparently it's a bug in FCP 7.03 with interlaced footage (progressive works fine, apparently). All the source footage was transcoded to pro res.
    Someone said that putting the clips in motion and smoothing them out in optical flow would work and people had results. However I have no clue how to do this..
    Can someone please help me - I need to render a finished project today..
    Thanks in advance
    Nick

    Apparently it's a bug with Smoothcam's handling of interlaced footage in FCP 7.0.3 ... there's a post over on the Creative COW website detailing using Motion instead as Finnur mentions above.  Here's my own quick summary of that for those that aren't used to it :
    In FCP select the clip instance and choose FIle > Send To > Motion Project (or right click and choose Send To > Motion Project) and save the Exported clip to your scratch disk 
    The exported clip will open in Motion. Click the clip to select it and then from the toolbar at the top of the main window choose ➀ Add Behavior > Motion Tracking > Stabilize
    Next choose ➁ HUD (heads up display), and in that window ➂ set Method : Smooth, Borders : Zoom, and select Adjust : Position & Scale, and click the Movement : Analyze button
    When the Analysis is complete, choose Motion menu > Quit, and press "Save" when prompted. 
    When you return to FCP the smoothed Motion project (.motn) should be sitting in the sequence in place of the original clip ... it'll probably need rendering .
    Personally, I'd be inclined to just try adding the Shift Fields filter (Effects > Video Filters > Video > Shift Fields) to the jittery Smoothcam shot in FCP first, and see if that works, before jumping through the Motion hoops.
    Hope it helps
    Andy

  • FCP X: DV AVI import fails

    Hello forum,
    I have DV AVIs which were captured on a Windows XP PC with the Miro DV500 capture card. When trying to import a given AVI file into Final Cut Pro X 10.0.1 (latest available update) I get an error message:
    "No importable media - None of the selected files or folders could be imported. Change your selection and try again"
    (I have the german version, so the above is just a rough translation)
    I tried also with unchecking all import dialog checkboxes, to no avail. The same import failure happens on an iMac running 10.6.8 Snow Leopard and FCP X 10.0.1 (latest update) and on a MacBook Pro running 10.7.1 Lion with the original FCP X 10.0.
    I copied the files onto the Mac harddisk. The size is nothing extraordinary, the smallest file is just about 172 MBytes.
    The files import just fine into my Final Cut Express 4.0 version! They also play fine with QuickTime or any other application such as VLC on my Mac.
    I found this entry here: https://discussions.apple.com/thread/3152268?start=0&tstart=0 which talks about (large) MJPEG AVIS from a Pentax K-7 camera. The same workaround described there works with my DV AVI files as well: I open the AVI with Quick Time 7 Player (on my Snow Leopard), "Save as" and then "Save as reference" ("Als Referenz sichern" in my german QT). This produces a very small *.mov file which I then can import into FCP X!
    (Unfortunatelly I haven't figured out yet how that works on Lion with QT 10.1, since the "Save as" has gone (bummer!) and the Export doesn't seem to provide a "Save as reference" anymore - unlike the original post claims: "...and save the file as a movie with the media in the same format." - how?)
    Anyone else is having trouble importing DV AVIs into FCP X?

    Ops, sorry, yeah, wanted to post this to Final Cut Pro (X) forum! Sorry about the noise!
    Anyway, thanks for your reply: I consider this a bug in FCP X and if possible would like to avoid to transcode the movie (I could live with copying the streams 1:1 and simply re-writing the AVI header, or copying it into a MOV container, without any re-compression loss - any such program known? Tried quickly VLC, but that only seems to support transcoding into MPEG etc., not copying the content 1:1...).
    Anyway, will re-post this into the proper Final Cut Pro forum... if you're interested, please continue there.

  • Geometry not translating into FCP

    Hi, all. Just curious if anyone has figured out an FCP-->Color-->FCP round trip workaround scenario that includes Geometry room parameters. I'm striking out.
    The media was shot on 16:9 720P/24, and I'm cutting it in (amazingly, in real time--nice work, Apple) with a ProRes HQ 4:3 NTSC sequence. After a round trip, everything else looks great: primary/seconday color settings, pulldown insertion, etc. However, I've done a number of repos and small camera moves in Color, and they disappear back in FCP. Experimenting with the first :30, I've got to say the autofeathering keyframes LOOK GREAT in Color, (very natural, quick and easy to set up, and smooth) but they do not come back in after rendering, no matter what I try.
    It says in the manual and on the FCPS 2 site that Geometry room settings get translated into FCP motion parameters. That's not happening. Is this a known bug? FCP's motion control is so clunky, I'd be more likely to do it in After Effects, but that's a pain, since the controls are right here in front of me in Color.
    Many thanks.

    I realize this is an old thread, but here's the solution:
    Just delete the .xml file from your project's container. You'll have to right-click on the project, choose "Show Package Contents", then delete the .xml file that's in there. Actually, maybe move it some place safe, even though it is a clone of the file you actually did use.
    Once it's gone, Color is fooled into thinking that you didn't import this form XML, and you're good to go.
    You might also have to delete the line in the project's .PDL file that has the <IMPORTFROMFCP> tag, I'm not sure. It was the first thing I tried and it didn't have any effect, but since I never put it back I can't be sure you don't need to do both things.
    And I respectfully disagree about doing it there way or the highway. Since FinalTouch 1.x I've been doing all sorts of XML hacks and workarounds to make it do some things MY WAY I still can't get it to 4K with this DALSA footage I'm on right now, though
    Tyler Hawes, DI Colorist
    Liquid DI
    www.liquidcompanies.com

  • Nested Sequences Bug is finally fixed?

    I just noticed that Apple seems to have patched a significant bug in FCP with the last update.
    According to my own tests, Nested Sequences now update automatically and consistently without having to be re-added or refreshed in the timeline.
    Nesting is when a sequence is placed into another sequence. Complex projects may involve several layers deep of nesting, but FCP users have been wise to avoid this useful technique because it just didn't work right.
    For example, if I were to build a neat animated logo sequence, then nest it inside a standard footage sequence, the animation would play through and be scalable like any other footage. This allows for a simpler "master track" timeline based workflow where everything is not placed into the same huge sequence.
    In the past, the sequence containing a nested sequence would not get updated if one made a change to the nested sequence after placing it. So if I were to change the animated logo sequence mentioned above, the change would not show up in the footage sequence that hosts it. I believe this has finally been fixed in 5.04
    The nested sequence bug is a very old issue that dates back to version 1 of FCP and has been a real problem for me because of my high-volume workflow. I've been reporting the problem at Apple's feedback site and it appears they finally listened.
    Why nest? Nesting is also very useful when format converting or adding letterbox, etc. I mostly use nesting because I have 100's of TV commercials that are identical but use different phone #'s. For this I nest the nearly completed spot into new sequence where the phone number is added. I can then have 100's of sequences that only contain the stuff that changes. I don't have time to explain why this works better than just rendering the master track for me, but it does.
    Has anybody else noticed this fix, or am I just dreaming here? I really am excited about this.

    It was fixed as I described until about a month ago, when I noticed the problem was back. This could have coincided with an OSX update. It also might have been the update to QuickTime or Pro Applications Support as well. I don't know. But the problem is back and I noticed it "the hard way" during a dub. Sorry for not amending my post when I noticed this.
    This is a problem that Premiere and Avid users NEVER experience, FYI. It is a critical bug in my opinion. I believe Apple could fix this with just a few lines of code, but it seems like it just isn't on the priority list. We need to get busy with the Apple Feedback forum requesting the a fix (again). Please everybody that reads this should post a request at that forum for a fix. Thanks!

  • FCP Audio Issues

    For some reason I have an AIFF audio file in my project whose volume is constantly increased at a point in my edit. I have not increased the volume at this point yet even when I replace the audio track completely and re-render it still does the same thing.
    Is this a bug in FCP? It feels like it.

    I'm using a 2ghz Dual Core Intel Xeon with 5gb ram.
    OSX 10.5.6
    FCP 6.0.5
    QT Pro 7.5.5
    My sequence settings are 720x480, NTSC DV(3.2), NTSC CCIR601, Lower Even, 29.97, DVCPRO, audio: 16-bit, 48khz
    The AIFF file is 16-bit 48khz
    The video codec being used in the timeline is 720x480, 29.97, Lower Even, DVCPRO50, 48khz, 16-bit
    There are a total of 8-tracks of audio.
    No filters on audio or video.
    The video and audio are being monitored directly from the system. No cards.
    Let me know if there is anything else you need.
    Thank you!

Maybe you are looking for