Illogical Dropped Frames driving me MAD!!

Hi everyone I would REALLY appreciate help with this as I'm ready to pull every single hair of my head out!
I get dropped frames when I try and play my sequence. So far my sequence is 1 minute long... Haven't been able to get much editing done cause of this problem! I can't play the sequence for more than 2 seconds before I get the dropped frames error message.
I can import absoultely fine. I can play the clips in the viewer fine. Only playing the sequence in the canvas is a problem.
Stats:
OS X 10.4.7
iMac G5 1.8ghz 512mb sdram
Final Cut Pro 5.1
QT Pro 7.1.2
Clips are 25fps, 1440x1080 HDV 1080i50
Data rate 3.5mb/s
48k 2 mono 16 bit sound
All kept on my 200gig (10 gig spare) external directly connected firewire harddrive MacOS Extended (journaled) format.
RT is set to safe. Not sure how to lower compression rate or rt audio tracks and concerned that will effect the quality (don't need to watch in full quality put want to be able to export project when finished in full quality).
Please can I have some tips for as to what to do so I can play my sequence? If you can give me details on how to change the settings as I'm not a complete whizz on FCP yet!
Thanks so much!!
Hannah

Glad you got it sorted, Hannah.
Extra RAM is well worth the money - but remember, with 22 GB free on your HD, you're really on the limit there. Have you used Render Manager to ditch unwanted render files?
Tools > Render Manager.
Render files can be very big and are soon redundant. They can also cause problems. If you remove them, It may take a while to re-render but it will do no harm and it will free-up space.
Andy
Can I offer you a tip?
When you go back and edit your post from the Preview on this Forum, delete everything after the last word you typed - that way your System Profile won't be repeated over and over again!
G5 Quad 8GB. 250+500 GB HDs. G-Raid 1TB. FCP 5.1.1. Shake 4.1. Sony HVR Z1E   Mac OS X (10.4.7)  
"I've taught you all I know, and still you know nothing".

Similar Messages

  • Dropped frames when playing section in the timeline w/audio, Viewer plays fine. Plays for 1 sec, no sound, nothing on audio meters. Problem out the blue, made no conscious changes. FCP 7.0.3. iMac, 2.7 GHz Intel Core i5. OS10.8.4. Thanx.

    New to FCP. Dropped frames when playing section in the timeline w/audio, Viewer plays fine tho. Plays for bout 1 sec with no sound, nothing showing coming through the audio meters. Problem came out the blue, made no conscious changes to settings. FCP 7.0.3. iMac, 2.7 GHz Intel Core i5. OS10.8.4. If any other info needed please let me know, will be happy to provide it. Thanx.

    Thank you for the help. Below is my Source footage and sequence settings.
    The other footage I have on the timeline is an mp3 file made in Garage Band and some footage I sent to Motion to edit. I do have some offline media on there since I switched computers but FCP had been working fine for a few months with it on there. I have not tried trashing my FCP Preferences. If I did would I have to back up my project?

  • Every cut I make in the sequence window leaves one remaining frame from its deleted neighbor clip. How do I turn off this feature - It is driving me mad.

    Every cut I make in the sequence window leaves one remaining frame from its deleted neighbor clip. How do I turn off this feature - It is driving me mad.

    Here are 3 pictures detailing what I'm experiencing.
    Picture 1; clip 1 tail frame.
    Picture 2; clip 2 head frame.
    Picture 3; clip 2 head frame is now tail frame of clip 1.
    does this help describe what is happening? Basically every cut I make
    leaves an unwanted frame as a ghost of the missing cut.
    best,
    Fred
    On Wed, Dec 10, 2014 at 4:50 PM, Kevin Monahan <[email protected]>

  • Jumpy timeline, dropped frames - please help!

    I am experiencing a persistent problem with a jumpy timeline that surges forward - (it looks like dropped frames). I have all of my media on an external hardrive with 160 GB to spare, I have formatted that HD as Mac OS extended "Journaled". I have made RT as "Safe" and video quality as "dynamic", frame rate as "dynamic". It seems to be unnoticable when I reduce the size of the canvas to below 50% but at that point I am going cross-eyed in trying to decipher the picture on the screen.
    Question 1:
    Do I need to reformat my HD without " Journalled" or is this not a problem?
    Any other ideas how to resolve?
    Question 2:
    What is Pulldown Pattern and what setting is best for my project (720 x 480 DV/DVCPRO - NTSC 29.97 fps)?
    Any help in these matters would be greatly appreciated. Thanks
    MacBook Pro   Mac OS X (10.4.8)  

    Thanks for your suggestions.
    All in all, I tried everything but to no avail. i suspect that in my trying to figure out solutions, i may have made some illogical formatting/preferences for my media and project on the hole. I ended up just starting from scratch with a new project, rudimentary preferences, imported my media - and it has been perfect ever since.
    For anyone with similar issues, I highly recommend reading this article. It troubleshoots everything having to do with this subject.
    http://docs.info.apple.com/article.html?artnum=58640
    Thanks for your help!
    Richard
    MacBook Pro   Mac OS X (10.4.8)   2.16 GHz Intel Core Duo, 2GB SDRAM, FCP 5.1.2

  • Dropped frames while capture

    Hey guys i have a 15" powerbook with 1 GB of RAM (No external drives) which i use pretty much soley for FCP 5. its only about 6 months old and has recently started dropping frames while capturing? anyone know what the problem could be? its been driving me crazy. cheers.

    Hello again Michael,
    Thanks for your comments but I was simply passing on my own experience and what I've personally been told by G-Tech here in the UK.
    Are you suggesting it's OK for users to move, allow to overheat, or switch the power off while using external HDs?
    I don't think so . . .
    As I said in another post, G-Tech were courteous and efficient with me and I have no grudge against them.
    I understand your discontent and we all get cross if we feel we've been let down, but I wonder if it's wise to use other people's posts to vent your feelings about one manufacturer when so many others clearly speak very highly of them.
    As far as your "I made enough noise to attract the attention of the ceo" (of G-Tech) is concerned, as I recall, you completely crashed my topic:
    http://discussions.apple.com/message.jspa?messageID=2840390#2840390
    and poured out your vendetta against G-Tech until you attracted Jerry Hoffman's attention and he suggested Creative Cow might be a more appropriate place to do it as the G-Tech ceo posts there.
    (Or did I misunderstand what was going on)?
    I can't help feeling that a polite post of your own on this forum - about your frustrations with G-Tech, might have attracted Jerry's attention more quickly and you could have posted on CC much without wrecking someone else's topic.
    But here we go again . . . (Do we?)
    Andy
    G5 Quad. 8 GB. 250 & 500 GB Internal HDs. G-Tech G-Raid 1 TB. FCP 5.0.4 (Studio)   Mac OS X (10.4.7)   Sony HVR-Z1E.
    You can't educate pork . . ..

  • Full screen preview drops frames

    Hi all,
    A continuation of the thread I opened here (with hardware specs for information):
    http://forums.adobe.com/thread/657008?tstart=0
    Whilst I resolved the tearing issue secribed in the previous thread I still can't get smooth playback on the third full screen preview display and I'd like some basic advice as to what I could do:
    A couple of things I have tried - firstly I tried a basic sequence with a spinning graphic (in order to rule out any issues with disk/network access), and then also tried two screens rather than three (so only one graphic card was in operation), a 60p/30p project with screens set to 60Hz and a 50p/25p project with screens set to 50Hz.
    All to no avail - the full screen preview drops frames, especially with 50p content - 25p is better but every 20 seconds or so frames are dropped. Audio is always fine, regardless of the source, BTW.
    As a reminder, this is a 12 core i7 with 2 x Quadro FX3800, all unnecessary services disabled, 12Gb RAM, CS5 5.0.3, latest WHQL Nvidia drivers.
    Not sure if 5.5 improves this in any regard as I'm still waiting for my licence key.
    Video playback outside of premiere is perfect, 1080p50 plays fine full screen on any display through windows media player/VLC.
    Any suggestions please - again I wonder if a Blackmagic Intensity or similar would help?
    Has anyone else seen this behaviour? Could anybody have a go a reproducing the issue (a simple spinning or sliding jpg demonstates the issue easily and simply)
    Thanks all
    Sacha Goodwin.

    There exist no 12 core i7's. The max is hexa-core, but in your previous thread you said Xeon X5670. So what is it?
    Well spotted, my bad - it is indeed 2 x hexa-core X5670's - which of course is 12 cores in total.
    I still suspect your Editshare NAS.
    I'd say unlikely since - we've replaced it with something else, also:
    I tried a basic sequence with a spinning graphic (in order to rule out any issues with disk/network access)
    and at any rate I tried it as a local project on local disks and it made no difference.
    For graphic read plain color matte and basic SD res JPG (same results with either)
    What happens when you increase memory to 24 GB?
    No idea as I don't have access to any - strikes me as odd though to think anyone would need 24Gb or RAM just to display a rotating still smoothly.
    Premiere is showing 300Mb of RAM, total RAM in use when everything is loaded and running is 3Gb, 9Gb free sitting there twiddling it's virtual thumbs.
    BTW I should also mention that this happens even on SD projects, not just HD ones. Also watching the task manager shows virtually CPU usage, no disk and no network access during playback (as I would expect). No peaks in any graphs correllating with the dropped frames. Also enabling/disabling MPE Hardware assist makes no difference.
    Sacha.

  • Digitizing Pre-Logged Clips: Drop Frame/Non-Drop Frame Discrepency

    I have about 100hrs of DV NTSC footage that has been logged and now I need to capture it.
    Everything seemed good to go:
    • I ctrl+click the clip intended to capture
    • Select 'batch capture' (it initializes)
    • Settings are (apple setting) DV NTSC 48kHz
    • I click okay and I get an error message that reads:
    "WARNING: You are about to capture drop-frame media to a non-drop frame clip. If you proceed, you may experience changes in logged in and out points, problems relinking media, or removal of master clip relationships."
    Now, the setting noted above is set at 29.97 not 30.
    I tried to see if there was anything I could select/deselect in the logged clips and came up dry.
    I made duplicated the apple setting and changed the fps to 30. This yielded no error message but did on the second clip I tried.
    Does anyone have any idea on how I should be troubleshooting this?
    Due to the high volume of footage, and workflow schedule, I'd really rather not screw this up.
    I turn to you my faithful FCP gurus.
    Thanks.
    Ian
    p.s. I'm running FCP v.5.1.4

    Just check your timecode accuracy before you get any further... i.e. does the timecode in the captured clip match the code that's on the tape. If so, you're good to go on... if not, I'd recapture using the proper TC... it's pretty easy if you do it from the tape in the Log and Capture window.
    Jerry

  • Constantly dropping frames

    I am randomly getting lots of dropped frames when recording with OnLocation on lengthy recording sessions (1-2 hours). Like, several seconds will be missing. Sometimes this happens frequently, sometimes (but rarely) not at all. And sometimes recording even stops, as Windows says its lost the connection to the camera.
    I'm using OnLocation on a MacBook Pro Core 2 Duo. I've used it under new installations of XP and Vista with Boot Camp. I've tried recording to a 3rd partition setup as FAT32 or NTFS, as well as to the Macintosh partition with MacDrive. And I've tried two different firewire cables.
    Sometimes the buffer bar will be full, or it will say the hard drive is not fast enough, but I want to say this isn't always the case (but I'm not 100% positive as I can't watch OnLocation the whole time I'm recording).
    What could be the problem??
    Thanks
    Zach

    Wow, Ultra on a MAC,,,, Are you recording to tape or direct to disk? Are you recording HDV? m2t files have a long GOP structure, only 2 I frames per second. this means if you drop one I frame you loose a half second of video. I would try using new tapes made for HDV and cleaning the tape heads. If your doing regular DV, then I'd say it would have to be the MAC, Bootcamp not working right with Ultra as almost any computer these days will record DV direct to disk or clean tape heads and new tape. Danny

  • Dropping frames in QT export from CS3

    I just got CS3 for my PC and I was all excited about the new
    feature that lets you export dynamic/actionscripted/MovieClip
    content. I do animation targetted at TV, so everything needs to be
    rendered to AVI or Quicktime, so I figured that this new feature
    would let me use a dynamic camera symbol as I've always wanted to.
    I've run into a problem, though: the export process seems to
    drop frames! As far as I can tell, Flash is rendering and recording
    the frames of the animation in real time (or perhaps just close to
    real time). If the computer has any hiccups because of another
    process demanding some processor time then the resulting quicktime
    will have frozen bits where the renderer couldn't keep up.
    You can see what I'm talking about by looking at the
    quicktime and an AVI of the same scene here:
    http://www.pinkandaint.com/flasherror/bad.mov
    http://www.pinkandaint.com/flasherror/good.avi
    To test this theory, I tried witching applications a bunch
    during a render. Sure enough, there were long sections in the
    resulting quicktime where the renderer missed frames. The quicktime
    is the right length and number of frames -- it just repeated the
    same frame over and over where it couldn't keep up.
    That's not the only problem, though. When I look at the
    exported quicktime file in either Quicktime Player or Premiere pro
    (version 1.5) it reports a framerate significantly lower than in
    the original FLA. In the file I'm looking at right now, the FLA's
    framerate is listed as 29.97 but the MOV file reports a rate of
    19.29 (which is, incidentally, different than the framerate I got
    any other time I exported the same scene). In premiere, when I tell
    it to interpret the footage as having 29.97 fps the clip gets
    significantly shorter than it should be -- in this case 161 frames
    rather than the 208 frames that it is in the FLA.
    I'm pretty sure this is the same way that the various
    SWF-to-video programs do things. I thought it was an interesting
    kludge to use those external programs but I was sure Adobe would be
    able to do something more elegant and sure-footed with this new
    export feature. Couldn't they have somehow guaranteed that each
    frame would get captured? It seems like they could have just
    modified the Flash player to play with artificial time, where the
    time to render each frame was always reported as 1/framerate.
    Oh, and there's one more problem. The Quicktime renderer
    seems to do something different about the order of execution of
    actionscript or something. In the rendered quicktime movie the
    first frame displays my camera symbol even though I explicitly made
    it invisible with actionscript on the first frame of its timeline.
    When displaying in the Flash player the first frame does _not_
    display the camera symbol....
    Has anyone else encountered these problems? If so, have you
    figured out a workaround? I tried setting the framerate really low
    (I was at 29.97, so I set it down to 10) but it still seemed to
    miss frames.
    -David

    I can understand your frustration with this feature as it
    tries to capture in real time what's being
    compiled in the player - but your last line is a bit unfair:
    "...it
    > exemplifies the Flash team's disregard for animators in
    favor of web developers."
    Copy Motion and Copy Motion as AS3 are useful new additions
    for animators. I will add however that I
    myself have a list of animation oriented features I would
    love to see added in flash but for now
    have you checked out www.flashants.com and their SWF2Video
    tool? It exports an SWF to AVI with
    flawless results. Worth looking into if you have the need to
    output any kind of flash content to video.
    Chris Georgenes
    Animator
    http://www.mudbubble.com
    http://www.keyframer.com
    Adobe Community Expert
    *\^^/*
    (OO)
    <---->
    animator_geek wrote:
    >
    quote:
    Originally posted by:
    Newsgroup User
    > [...]
    > Turn off other applications. When recording, Flash uses
    all of your system's
    > available resources as much as possible, so any
    interference of the system
    > performance affects the result of the recording. We
    recommend you exit other
    > applications while exporting to a video.
    >
    >
    > So you're telling me that Flash makes my computer
    completely unusable while
    > it's rendering? Sorry, I thought we left that kind of
    limitation behind with
    > DOS. Particularly for something like this, where the
    rendering process should
    > be
    completely independent of real-time. The renderer should go
    exactly
    > as fast as it needs to in order to capture every frame.
    Whether I set the
    > frame rate to 1 or 1000 should make no difference in how
    many frames are
    > dropped in the rendering process.
    No frames should ever be dropped I
    > mean, what's going on here? You guys have access to the
    actual source code of
    > the renderer. Can't you adapt it so that it when it's
    rendering non-real-time
    > the SWF thinks that it's executing at exactly the frame
    rate it desires? You
    > could just set the renderer's "clock" to whenever the
    render was started, then
    > increment it 1/fps seconds every frame. The program
    would never be the wiser.
    > You could even let the timer run (or simulate it
    somehow) for 1/fps seconds
    > between rendering each frame, thereby handling any timer
    events that need to be
    > sent while the SWF is running.
    >
    > Clearly I'm not privy to the inner workings of the Flash
    player but as a user
    > there's a certain standard I expect, particularly when a
    company touts this
    > great new feature. It's supposed to work as advertised.
    This feature clearly
    > does not.
    >
    > Now I've been a software engineer in the past and I know
    that sometimes
    > workarounds have to be made but this is just too much.
    To me as a user, it
    > exemplifies the Flash team's disregard for animators in
    favor of web developers.
    >
    > -David
    >
    >
    quote:
    Turn off audio. The audio in a Flash movie may also slow the
    performance
    > possibly causing dropped frames. Turn off the audio, if
    you have many
    > dropped frames in the first attempt. Other video editing
    tools can be used
    > to add the audio to the video after export.
    >
    > Reduce frame rate. If the movie dimension is a full size
    NTSC video, 740 x
    > 480, and frame rate is 30 fps, you are more likely to
    have dropped frames.
    > Reduce the fps of Flash movie increase the chance of
    grabbing all the
    > frames. Other video editing tools can be used to adjust
    the frame rate of
    > the video after export.
    >
    > Optimize your animation. Try to avoid a lot of screen
    motion. The greater
    > the area of change on the screen, the more likely
    slowdown will occur. Also,
    > if possible, restrict your use of transparency and alpha
    channels as they
    > too can cause poor performance.
    >
    > Use ActionScript 3. Animation created by ActionScript 2
    and ActionScript 3
    > are different in play back performance. Convert the
    ActionScript in your
    > animation to ActionScript 3 for optimized performance.
    >
    > Dimension settings in 2 places. The dimension settings
    in Export Settings
    > dialog sets the dimension of the SWF movie to be
    captured. The Size settings
    > in QuickTime Settings dialog sets the dimension of the
    exported MOV files.
    > If the SWF size is smaller than the exported MOV size,
    the picture quality
    > will be degraded; if it is larger than the exported MOV
    file, you may have
    > better picture quality. For best quality (and often
    performance) these
    > settings should match.
    >
    >
    >
    > "animator_geek" <[email protected]>
    wrote in message
    > news:[email protected]...
    > >I just got CS3 for my PC and I was all excited about
    the new feature that
    > >lets
    > > you export dynamic/actionscripted/MovieClip
    content. I do animation
    > > targetted
    > > at TV, so everything needs to be rendered to AVI or
    Quicktime, so I
    > > figured
    > > that this new feature would let me use a dynamic
    camera symbol as I've
    > > always
    > > wanted to.
    > >
    > > I've run into a problem, though: the export process
    seems to drop frames!
    > > As
    > > far as I can tell, Flash is rendering and recording
    the frames of the
    > > animation
    > > in real time (or perhaps just close to real time).
    If the computer has
    > > any
    > > hiccups because of another process demanding some
    processor time then the
    > > resulting quicktime will have frozen bits where the
    renderer couldn't keep
    > > up.
    > >
    > > You can see what I'm talking about by looking at
    the quicktime and an AVI
    > > of
    > > the same scene here:
    > >
    http://www.pinkandaint.com/flasherror/bad.mov
    > >
    http://www.pinkandaint.com/flasherror/good.avi
    > >
    > > To test this theory, I tried witching applications
    a bunch during a
    > > render.
    > > Sure enough, there were long sections in the
    resulting quicktime where the
    > > renderer missed frames. The quicktime is the right
    length and number of
    > > frames
    > > -- it just repeated the same frame over and over
    where it couldn't keep
    > > up.
    > >
    > > That's not the only problem, though. When I look at
    the exported
    > > quicktime
    > > file in either Quicktime Player or Premiere pro
    (version 1.5) it reports a
    > > framerate significantly lower than in the original
    FLA. In the file I'm
    > > looking at right now, the FLA's framerate is listed
    as 29.97 but the MOV
    > > file
    > > reports a rate of 19.29 (which is, incidentally,
    different than the
    > > framerate I
    > > got any other time I exported the same scene). In
    premiere, when I tell
    > > it to
    > > interpret the footage as having 29.97 fps the clip
    gets significantly
    > > shorter
    > > than it should be -- in this case 161 frames rather
    than the 208 frames
    > > that it
    > > is in the FLA.
    > >
    > > I'm pretty sure this is the same way that the
    various SWF-to-video
    > > programs do
    > > things. I thought it was an interesting kludge to
    use those external
    > > programs
    > > but I was sure Adobe would be able to do something
    more elegant and
    > > sure-footed
    > > with this new export feature. Couldn't they have
    somehow guaranteed that
    > > each
    > > frame would get captured? It seems like they could
    have just modified the
    > > Flash player to play with artificial time, where
    the time to render each
    > > frame
    > > was always reported as 1/framerate.
    > >
    > > Oh, and there's one more problem. The Quicktime
    renderer seems to do
    > > something different about the order of execution of
    actionscript or
    > > something.
    > > In the rendered quicktime movie the first frame
    displays my camera symbol
    > > even
    > > though I explicitly made it invisible with
    actionscript on the first frame
    > > of
    > > its timeline. When displaying in the Flash player
    the first frame does
    > > _not_
    > > display the camera symbol....
    > >
    > > Has anyone else encountered these problems? If so,
    have you figured out a
    > > workaround? I tried setting the framerate really
    low (I was at 29.97, so
    > > I set
    > > it down to 10) but it still seemed to miss frames.
    > >
    > > -David
    > >
    >
    >
    >
    >
    >
    >

  • DV NTSD drop-frame vs. non-drop-frame??

    My impression has always been that DV NTSC is non-drop frame. I'm having to capture a 100 hours of DV tapes from a Sony WV-DR7 deck. FCP capture is giving me this warning:
    "You are about to capture Non-Drop Frame media from a device currently detecting or configured for Drop Frame media. If you proceed, you may experience changes in logged in and out points, problems relinking media, or removal of master clip relationships."
    The Sony is all in Japanese, and the rough translation manual does not mention drop frame \ non-drop frame setting choices on the deck.
    Would anyone have any suggestions or recommendations?
    Ben

    Sorry to be confusing~~~~
    What I meant was, since I wasn't sure if the VTR you are using actually shows the timecode window, or just a timecode counter (the Sony DSR-11's display does not show the colon/semicolon difference in the display that is supered on the non-digital video outs), I thought the quickest way to assess what flavor of TC you had was to play the tape and use "Capture Now" to capture a few seconds. Then you can look in the bin, check the media start column and see if there are semi-colons or colons. This would be helpful particularly if FCP is balking at capturing from your logged marks.
    The other thing I was talking about was a case where I had been given DVCam copies of camera masters, to use for a rough cut. Because these tapes were work prints, they used old DVCam tapes. One of the tapes had originally had DF material on it. When the tape op made the workprint, he started recording the new NDF material about 10 seconds into the tape, he therefore left 10 seconds of DF bars at the head of the reel (the old material). I put the tape in a DSR-11, fast wound up to picture, and started logging. When I was at the end of the reel, I hit rewind on the machine so it would rewind while I was clearing up spelling errors, etc. The machine backed all the way to head of the tape, into the DF area.
    So when I hit batch capture, the machine reported back to FCP that it had a tape with the correct name loaded, but the time code was in the incorrect format - the message you received. It took a while to figure it out, but when I wound the tape forward, so that it was in the picture portion of the reel, the machine was then outputting the code that FCP was expecting. So by "parking" the deck in the picture portion of the tape, it would cue correctly from the logged point.
    Hope this explains it. hope you have a simple solution, too.
    Message was edited by: Meg The Dog to fix typo

  • Records alternate between non drop frame and drop frame...

    I am seeing a pattern with Premiere records, that alternate the records from being non drop frame to drop frame.  So one day we recorded 7 segments.  The records ended up coming out like this (without any changes being made between records):
    Segment 1 - non drop frame
    Segment 2 - drop frame
    Segment 3 - non drop frame
    Segment 4 - drop frame
    Segment 5 - non drop frame
    Segment 6 - drop frame
    Segment 7 - non drop frame
    Is this from a hidden setting we can't find, or is this a known bug?

    Hi Angela,
    I'm following up with you from your Tweets on Twitter. As I mentioned there, we have seen similar issues in Premiere Pro CC (7.0.1) but they were fixed. It is possible that they could be rearing up again, so I would encourage you to file a bug report: http://adobe.ly/ReportBug
    Further, I would contact AJA support. They have released new drivers very recently, which may assist your issue.
    You are also free to contact Adobe support. When you are connecting via phone or chat, ask for the video queue: Contact Customer Care
    Thanks,
    Kevin

  • Dropped frames during playback from timeline...help asap!

    I'm running Final Cut Express 4.0.1 (I've checked and installed latest updates) on a 24" Intel iMac (2.66 GHz Intel Core 2 Duo, 4GB ram) which I purchased on August 2009.
    Before I purchased my new iMac I would use FCE on my 15" MacBook Pro (purchased April '08, similar specs to my iMac) and it would work just fine.
    Now here's the problem with running it on the iMac...Everytime I playback any video from the timeline, it would immediately drop frames in less than 3 seconds (even without any effects or filters) and reveal an error window:
    "One or more frames were dropped during playback
    If this occurs frequently, try:
    -Turning off Unlimited RT
    -Lowering your compression data rate
    -etc..."
    However the video in the "Viewer" window plays back videos just fine. I've tried changing scratch disks from an external drive to the internal HDD (both of which are more than 70% free) to no avail. I used to always use Unlimited RT without a problem when I used FCE on my MacBookPro with an external drive. Am I missing a setting that I used with my MacBookPro? I've even opened FCE projects I made using my MBP, and the iMac drops the frames when I play them back.

    Here are some screen caps of the item info windows:
    http://img263.imageshack.us/img263/1696/screenshot20100608at115.png
    http://img43.imageshack.us/img43/1696/screenshot20100608at115.png
    I'm using an external HD, an Iomega 1.5TB - Mac OS Extended (Journaled). However it's USB and not firewire (which again wasn't an issue with my MBP). I've also switched to the iMac hard drive and the problem persists.
    Let me know of any other info you'd like me to pull up for you.

  • DROPPED FRAMES ERROR

    After converting my footage from H.264 to Apple Pro Res 422 LT, and getting a brand new super-charged iMac, my footage is still experiencing dropped frames every 5-6 seconds. The error message tells me to turn off UNLIMITED RT and even after doing that, I am still getting the same errors. I know it cannot be the computer, especially having got the new iMac with 16GB of RAM and a 2TB hard drive. ** All the footage is on the internal hard drive and not on an external. Does anyone have any ideas? I'm almost ready to ditch FCP and start re-editing in iMovie tonight.
    Thank you in advance.
    Stan

    It was previously on an LACIE Firewire 800 External Drive and I was advised to move the footage to my internal HD for better playback. Perhaps the problem is not the drive, since I now have a 2TB internal ..... maybe the problem is the format it is in. I converted the footage to APPLE PRO RES 422 LT, imported into FCP and when I was editing it on my previous iMac, I did not experience the dropped frames as much. After getting my new iMac, the problem resurfaced .... which made no sense to me since I got a mush faster + beefed up iMac.

  • Dropped Frames -- Releted to Capture?

    I was quickly working on a project for old friends, which I have now easily been able to finish to satisfaction, but got some dropped frames warnings during the process, which it did not hurt to ignore. Now I want to analyze why this happened?
    I had some previously footage on DV tape that had been copied from VHS, via VCR to camcorder in VTR mode -- no problem with these in FCP, utilizing In/Out timecodes. However I had to quickly review a lot more old VHS tapes, and chose to use my Canopus ADCV 110 to allow for rapid review and selective capture. Furthermore, it seemed much easier to do this in iMovie HD, capture selectively, and then export as QT dv, and import into FCP. All this seemed to work, and I could edit. But exclusive to those clips captured in iMovie and exported, I started to get this warning about dropped frames.
    Was this caused by the path of capture/export directly, or did the fact that I exported to the same scratch disk drive as those clips captured directly in FCP matter? Although using my new Mac Pro, I was still using my LaCie FW 800 disk as capture scratch. Is it the lack of timecodes on those assets captured via the Canopus, and should I expect the same issues if I capture via the Canopus, but in FCP? Part of the reason I used iMovie to capture, was I couldn't figure out how to monitor the sound from the VCR, which had no headphone jack, if reviewing via the Canopus and FCP.
    I love the Canopus, but have not made extensive use of it in this situation. However, I believe it actually gave better quality than "remastering" to DV tape, first, btw.
    Ernie

    I have also come to the same conclusion. I've been capturing video just fine and now I get this "dropped frames during capture" error message.
    SAME computer
    SAME external 7200 rpm drive for capture
    SAME fire-wire cable
    SAME camcorder
    SAME mini-dv tape
    I upgraded to OS 10.4.9 and iTunes 7.1.1 a few days ago and only now am I receiving this error message. Does anyone have any suggestions?

  • Dropped Frames & Firewire Busses - A Discussion

    A side discussion broke out on this recent thread:
    http://discussions.apple.com/thread.jspa?threadID=231733&tstart=0
    and because this discussion is OT to the thread, I thought it might be helpful to start a new on-topic thread.
    A number of FCP users have experienced dropped frames when capturing or outputting to tape while using a DV VCR/camcorder and a firewire drive for media on the same FW bus. There are many causes for dropped frames, but this discussion centers on the relationship between FW drives, DV devices, and using a single firewire bus.
    Some say that having the DV device and the firewire media drive on the same bus can be a cause of dropped frames with some systems. Others disagree. I'm in the first camp, so I'll leave it to others to explain the other side.
    I'm starting this thread to pick up where the side discussion on the thread linked above left off.
    In response to Hughes Video:
    If I'm reading your post correctly, my opinion is that your testing doesn't adequately address the real world situation. In practice, the FW port on the DV device is receiving data at 3.6MB/sec and buffering. Then it sends a data stream to the FW bus at about 12MB/sec, where is again buffered before being sent to the destination drive.
    The benchmark test results you noted don't predict what happens in the real world when capturing a DV stream from a VCR/camcorder to a FW drive. To do that, you need to be able to report in a time graph what the throughput is for every 1/30 of a second while capturing.
    I'm not sure that's what Adam Wilt has done, but he's told me that he's done thorough testing that proves the points he's made. I don't know what testing that entails.
    I do know, as I posted in the other thread, that when those who are having dropped frames separate the DV device from the FW drive on separate busses, their problems resolve. I don't know the technical reason for that, but I theorize that it has to do with the data moving and buffering in both directions on the same bus simulteneously. If the bus speed is decreased when both devices are on the same bus (whether daisy-chained or on separate ports), I don't know. But I know the problem resolves when you separate them.

    this begs the question though: how do users of an
    imac or a mini get around the limitations of one
    internal harddrive and one firewire bus?
    zeb
    They can't. iMac's are a consumer (and terribly sexy) computer. Make no mistake, if you are doing this for a living you need a PowerMac. Want less headaches with dropped frames and FW? Then take a closer look at better drives. G-Raid, Weibetech, and Granite Digital make the best out there, and invest in another FW 800 card for 'em. End of story.
    Want to avoid dropped frames forever and ever with any video format? Forsake FW drives for fibre. SCSI is dying a slow but steady death IMHO.
    Yeah, it all costs more, but you GET more (speed). Faster drives don't drop frames. Nothin' new there...
    There is a tendancy with new users of NLE's to cut corners. Don't do that, because it results in unhappy NLEing.
    Do I use FW drives? Of course I do, and use exclusively the above brands, I've clients who want to keep all media ever captured. (also a good idea) but I include in my invoices the cost of buying more FW drives to do the job. It works, I don't drop frames, have happy clients, and drop frame free system. I'm using the G-Raids for uncompressed storage and FW 800 Weibetech and Granite digital rigs for DV res storage. It works beautifully.
    Jerry

Maybe you are looking for