Black strobe glitch / dropped frames on rendered, exported video

I'm editing a sequence with 30+ clips and multiple layered tracks in Premiere Pro CC 2014. I've added multiple effects through Adjustment Layers, sometimes multiple layers where masked videos + track matte was needed to add further elements. After a fresh render a weird thing started to happen - black 'strobe' starts to appear on the video, like some frames are dropped and it fades in and out to and from black 2-3 times within a second. This is visible after rendering a preview and also if I export.
Here is an example:
adjusment_prob
If I remove all Adjustment layers, everything's back to normal and it renders fine (this is visible in the video).
I've tried removing all third party effects from the timeline and from PP altogether.
I've tried resetting all preferences, now even reinstalling Premiere Pro CC.
The weird thing is after it happens, of I try a completely fresh project and sequence with a clean video and drop an adjusment layer on it the problem appears again! Like my whole system or a codec or something else is corrupted.
I'm struggling with this issue for 2 days now without solutions and it's becoming very frustrating.
Any suggestions?

Wow! Actually I didn't try software only, however your suggestion brought me to the realisation that my Mercury hardware acceleration was set to OpenCL instead of CUDA! I switched it to CUDA and I believe it's all fine now! Thanks!!

Similar Messages

Export Issues: Green and black flashes and dropped frames

Hello,
So I've been having in issue in the last week exporting videos in Adobe (CS5, Premiere 5.0). It's happened both in AME and direct exports from Premiere. The sequence settings match the footage settings (1280x720 (1.0) 23.976fps MTS files). I'm using a mini matrox mxo2 hardware accelerator to speed up my export times. The sequences start with 5 seconds of a still image with a simple Title laid over it in Video two (the person's name, city etc. that is the focus of the video) which then dips to black into the footage. Everything plays back fine but after I output the sequences within the first 5 seconds (while the still img is up (a .jpg) there are flashes of green and black as well as dropped frames. It only happens a few times but it does happen in each video, only while that title is on the screen.
I've made hundreds of similar videos with the same export settings, same sequence settings, same footage settings. I know because it's a lot of the same cameramen and I've made templates for my projects, sequences, and export settings.This has never been an issue before this week.
I've tried mining Google and forums for an answer but can't even find other people having very similar problems.
Any help on ideas to troubleshoot this would be much appreciated and let me know if you want any more info from me.
Thanks!

Thank you for the reply J_Heffernan.
So my understanding of the issue is more clear. The green fields is from a rendered clip, not from playback.
Please try the following:
- in control panel, go to user accounts, and locate your account, and confirm its UAC level is all the way down, reboot if required
- if you downloaded the Matrox driver with another browser, besides IE, then redownload it again, with IE. Once completed, right click the file, go to properties, if there is a message stating its blocked, click the unblock button
- uninstall the MXO2 driver, reboot and reinstall it
- go to http://www.intel.com/p/en_US/support/detect?iid=dc_iduu let it scan to see if there is an intel chipset driver update availalble, and install it, reboot
- lets try with a brand new project - select matrox.avi as your capture mode
- select a matrox HD/SD sequence - try HD 1080i 29.97
- give a new name
- place colour bars on the timeline and streach it out
- now do a file export, use a Matrox h.264 option, and let adobe media encoder export it
- after it is completed, how is the playback?
Typically you can have premiere and media encoder open at the same time.
Regards
MTS

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
> >
>
>
>
>
>
>

[..\..\Src\pp\\PPixHandleUtilities.cpp-114] Dropped Frame CS3 Rendering Error

So, I recorded a small film (~15 minutes) on a Kodak Zi8 camcorder. I loaded it all into Premiere Pro CS3 fine, and I have it all in the timeline just fine... except I can't export it.
The Zi8 recorded in 720p H.264 mode, and when I try to export the whole timeline, the computer gives me the [..\..\Src\pp\\PPixHandleUtilities.cpp-114] error, then says a frame was dropped. I thought the length of the clips was the problem, so I broke them up into 3/4 minute chunks. Still same problem. It'll stop whenever - not always at the same spot, give the error, then stop rendering. I'm trying to export it as a Quicktime H.264 HD video.
I have a Dell Inspiron 530s running Windows 7 Professional, Core 2 Duo 2.53Ghz, 3GB RAM, 320GB HDD, ATI Radeon HD 3450 video card.
So far, I tried making the video into 3-4 minute clips, but that didn't help. I also tried dropping a transparent video layer on top of the whole thing (in case it had something to do with a dropped frame) but it still gave me the error. I also changed the rendering mode to "Memory" instead of "Processor" but to no avail...
I'm stuck. Part of me thinks it's just because I don't have enough memory to render, but I close out of every other program while I'm rendering. Plus, this is a relatively new computer. I purchased it back in November of 2008, and it has a dedicated video card.
Any suggestions? This video is for a class project and it's due in a couple weeks!
Thanks in advance guys,
Christian

I am nearing my last strands of sanity. This project has been due two days ago has been giving me fits with the same error message. My system wotks on AMD Athlon, 64 X2 Dual Core, 3 GHz with 8 GB RAM. Working with Premiere Pro CS3. I have an external 1TB drive with 200gb of available space. This is my first foray into the world of DSLR. I am editing with a combination of my regular Mpeg files from my Sony ZIU and MVI files from a Canon 5D DSLR. Editing the project was painstaking slow because I had to render all the MVI files even before I could use them. The error message [..\..\Src\PPixHandleUtilities.cpp-114] came up quite often but clicking on okay made it go away without closing my project. Come encoding time to Encore it will stop at the 43.3% mark. Have tried transcoding to a DVtape, no luck. Tried encoding to Mpeg2, uh uh. Always stopped at the 43.3% mark. One blogger here had posted that gaps on the video track might cause this.......I have been editing on Premiere for 10 years and that is the 1st time I have ever heard of that. I have always placed gaps on my video track and this particulare project is no exception and have never experienced this. I tried converting the MVI files to Mpeg but could not find a converter that would retain the same file size of the original files. Suffice it to say that my level of frustration is on red. Did you solve your issues? Any idea on how to fix mine? Guys? Anyone? Anything?

Dropped Frames / Odd Rendering

Hello,
As background, I recently completed a project (DVCPRO HD 720p) at a workshop on an iMac. I don't have the specs on the iMac but it's at least a year or two old. I wanted to continue working on this project at home so I have purchased a brand new Macbook Pro 2.0Ghz i7 - 8GB 1333 Mhz DDR3 RAM - AMD Radeon HD 6490M 256 MB. I've installed Final Cut Pro 7.0.3 and I'm using the same GRaid Mini 500GB (Raid 0 - FW800) drive I used in the workshop which is writing at 65MB/sec and reading at 76MB/sec. I'm now getting requests to render clips as well as dropped frames messages where I never did on the iMac. I've spent hours scouring forums (this one, Creative Cow, DV, etc...) and the only suggestion that's made any difference was pumping up the number of real time audio tracks on playback, but most of my problems seem video related. I've turned off the energy saver features, tinkered with render settings, memory, etc..., although I stopped short of modifying the RT Software Enabler file. I'm just not sure what else to try or if I'm even looking in the right place. I have to believe this Macbook should blow the doors off that iMac but maybe I'm wrong. Any help is appreciated.

OK, your problems are:
You are tying to edit with video that is in the H.264 codec.
H.264 is a recording and delivery format, it is not designed for editing, as it is very, very processor intensive.
Your clips are also in a different frame rate than your sequence 29.97 and your sequence is 23.98.
The source clips are a non-standard frame size 540 x 360.
It would be tough going for any computer to play this combination of incorrect item properties back in real time on a timeline that has a 23.98 frame rate and a DVCPRO 720P60 codec.
This is a perfect storm of miss-matched material.
Is your sequence setting because you have camera footage shot in that format? Is the camera material 23.98?
What format material do you have the most of?
What are you intending to do with this once you have completed it (Make DVD, post to web site, make Blu-Ray, etc.) ?
MtD

Premiere Pro CC 2014 - Black flickering lines during playback and when exporting video

I am fairly new to Premiere and have recently started using creative cloud on my new MacBook Pro retina - 2.3 GHz Intel Core i7 - 16GB Memory - OSX Version 10.9.4
I shot a music video using my friends camera and all the shots were absolutely fine, I dropped them into Premiere and started editing the video together.
Some of the clips are perfectly fine during playback, although sometimes my playback stutters a little, but some of the clips have strange horizontal lines that flash through them when I watch it back. I have only used basic things such as the highlight/shadow and sharpen tools in Premiere. I thought that it maybe fine once I exported the video but when I open up the exported file on my desktop in Quicktime the little black flashes/glitches are still there in some of the shots.
Here is a screenshot you can see a line halfway between the top of my head and the top of the screen, when you watch the video there are lots of these flashing about.
Could this be something that I have set up wrong?
CPU/GPU related?
Thanks,
Jordan

Hi there,
thanks for the reply!
GRAPHICS = NVIDIA GeForce GT 750M 2048 MB
I tried that but it didn't work unfortunately, Mine was already set to the one you said, I tried the other but no change

Drop Frames when Printing to Video

I know there are a lot of topics on drop frames, but I couldn't find any that met my specific set of circumstances.
My video plays fine and there is no red bar indicating that something has to be rendered. However, when I try to print to video, ten seconds in, the project is aborted and a drop frame error is given.
Is there anything I can do to get around this?
Thanks.

I don't know the specs of your machine however...
Alternatevely you could open the RT dropdown menu
and turn playback video quality and playback frame rate to the minimum and close
other projects.

Keynote dropping sound when rendering to video

I am running Keynote 6.5 on the Yosemite 10.10.1 operating system in a MacBook Pro 1TB HD with 16 GB of Ram. I am having the problem of sound completely dropping off after about 2 minutes and 6 six seconds when exporting a slideshow to video. The operating system has been replaced and reinstalled, Keynote was deleted and reinstalled and I duplicated the problem on my second MacBook Pro.
After all of this it has been determined to be an Engineering issue and happens to be a problem that is apparently affecting Keynote on all MacBook's, at least within the sated system preferences.
Does anybody have any advice or knowledge pertaining to this matter? Or know when Apple may resolve the issue?
James

we tried the custom settings being adjusted and leaving them as it is.
Therefore you did not use custom settings?
I currently have 10.10.1 with Keynote 6.5 and 10.9.5 with Keynote 6.2.2, both these versions export without issue to Quicktime when using custom settings.
This is an example of a custom QT export for HDTV 1080p:

Strange frames appear in exported video

Okay, I have a DV NTSC sequence in FCP 6.0 with some 320x240 dv clips and some 640x480 qt files made from iphoto slideshows. When I export>quicktime movie>current settings, the resulting file has some random frames with bright colors in the 'tv snow' pattern with a trace of the intended image in there. When I repeat, the anomalous frames appear in the same locations. Any ideas, fellas?

let me add: the sequence is 320x240. In trying to work around, I can export to quicktime conversion without the strange frames appearing. Also, I've reimported the qt version back into a FCP timeline and tried to ripple delete them out, but FCP quits repeatedly when I scroll onto the weird frames (6 times).

How can I get rid of this time code bar at the top of my rendered/exported video?

This is the video after I rendered:
This is the setting I used:

That problem has nothing to do with format settings. It is a burn-in, which is set in the view settings (timeline panel), and also you can deactivate in the render settings.

Why SDK always generates non-drop-frame clips?

I've created a sequence in Premiere: NTSC DV, Codec: DV NTSC, 29.97fps, 720x480, Drop-Frame Timecode.
When I try to render a clip with MXF OP1a preset file (DV25 NTSC) by SDK, it always generates non-drop-frame clip.
If I use 'File->Export->Media...' with same preset file, it's drop-frame exactely.
'Drop-frame' seems to be an option from sequence and there is no place to config it in preset settings dialog.
How can I generate drop-frame clip by SDK (exporter controller)?

I also meet the same problem.
I have created a 'Export Controller' plug-in. when export media using this plug-in, and choose the preset 'DV 25 NTSC', MXF OP1a.
Confirm that sequence setting is 29.97 drop-frame.
But export mxf file is always NDF.
However, using Export->Media, and choose MXF OP1a + DV 25 NTSC, will export DF mxf file.
Could you help to double check it?
I have check from code, it will get correct result (DF or NDF) after call function 'GetTimecodeDropFrame' in 'Sequence Info Suite' , so what's the problem would be?
Thanks,
Iris

Multicam with dropped frames

Hi,
I have a few clips with some dropped frames that I need to sync for multicam, but
I cannot recapture the footage.
The only thing I can do is export a 'repaired clip' and sync that.
I have marked the 'long frames'
Can anybody tell me how to 'repair' the clips so that when I export the 'repaired' clip and reimport them, they will stay in sync? (hope i've made sense)

I just finished a multicam project which had a ton of dropped frames over 8 cameras, and I didn't set it to start a new clip on dropped frames. It was a live concert.
What I did was, once I got the audio mix from the band, I laid it out on the timeline and locked those tracks. Then I dropped the first camera onto it, synced it up at the beginning, and hit play. When I saw a dropped frame, I sliced the video track and slid it down the timeline until the remaining footage was in sync. I inserted color bars instead of the slugs Randy recommended. That way it's easier to see in the multiclip 9-up view when a dropped frame area comes up, and I knew not to use that angle. But I'm getting ahead of myself. Once I went all the way through an angle, I would export a new self-contained QT movie of that angle and import it into the project. Then I'd duplicate that sequence, remove the video, and bring in the next camera. Shampoo rinse repeat.
Once I had all the angles done, I created a mutliclip with all my new clips. By locking the audio and duplicating those clips, each new QT movie had the same timecode, and I was able to sync by timecode, instead of in point on my multiclip.

Ex. device detecting dropped frames (from tape) and breaking clips!

I am using a Panasonic mini-dv camcorder to capture footage with on Final Cut Pro and the camera is being pretty sensitive to any glitches/dropped frames and is messing up capturing clips. When I try it multiple times it will sometimes not stop/find glitches, but this is very time consuming (have about 80 hours to go through!). I have gained some access to a mini-dv deck and that is working, but I also need to use the camera due to deadlines.
Is there a way to make this sensitivity in capturing turn off? Any suggestions/tips? (I've already gone into User Preferences and deselected 'Abort Capture on Dropped Frames' and that didn't change it).
Thanks!

#12 Dropped frames on capture/playback
Shane's Stock Answer #12: Dropped frames on capture/playback
http://docs.info.apple.com/article.html?artnum=58640
1) Do not capture to your main system drive. Since it is busy reading the operating system and application files, it will intermittently drop frames during capture. Capture to a separate internal drive, or external hard drive (firewire and eSATA for example).
2) Deactivate any anti-virus/filesaver software, including Norton and Virex. For some reason these programs think that the large files created when you capture media are in fact caused by some sort of virus, and they try to prevent this.
3) Check the format of the drive you are capturing to. It should be Mac OS Extended, journaling off. If it isn't, copy your files from it and re-initialize it. If it is any other format, you will encounter problems. If not at first, then eventually.
4) Trash the FCP preference files. Use FCP Rescue available here:
http://www.fcprescue.com
5) Make sure that the hard drives you are capturing to are fast enough to handle the footage being captured to it. A regular firewire 400 drive cannot capture uncompressed HD, or even uncompressed standard definition. A RAID array of drives might be in order for these formats.
Shane

Avoiding dropped frames?

So I'm trying to switch from iMovie back to FCP. In trying to capture an entire tape (hitting the play button and Capture Now button) I notice that there were five clips where there were dropped frames. In reviewing the tape I notice (with the naked eye and ear) no digital drop-out. So, in my deduction the dropped frames is occuring in either the computer and/or program. How can I eliminate dropped frames and have one clip to work with?

Are you capturing to your system drive? Do you have any antivirus software installed and active?
Search is your friend, and will bring up just about every solution you could imagine for getting your system to the point where it won't drop frames. There's also a full troubleshooting section in the manual devoted to it (at least in the Final Cut 5 manual).
Post what you've tried to fix it, that'll help narrow down the responses you'll get.
Edit:
Shane's Stock answer #12
Shane Ross, "Stock Answers" #40, 07:59pm Mar 8, 2005 CDT
Dropped frames on capture/export
Shane's Stock Answer #12:
1) Do not capture to your main system drive. Since it is busy reading the operating system and application files, it will intermittently drop frames during capture.
2) Do not under any circumstances run any anti-virus/filesaver software. Including Norton and Virex. Sure, Apple doles out Virex for free, but FCP doesn't cooperate with it very well.
If you absolutely feel you must keep Virex installed on your system then use Kevin's script to shut it off before you use FCP:
Kevin Mamajek, "Capture Now and Virex 7.5.x", 08:02am Mar 5, 2005 CDT
3) Check the format of the drive you are capturing to. It should be Mas OS Extended, jornalling off. If it isn't, copy your files from it and re-initialize it. If it is any other format, you will encounter problems. If not at first, then eventually.
4) Trash the FCP preference file:
Home/library/preferences/FCP user data/Final cut Pro Preferences
For all the stock answers, click on this link:
Shane Ross, "Stock Answers", 02:58pm Jan 13, 2005 CDT

Jerky playback with dropping frames after iPod/iPhone Conversion

Hi!
I have a problem converting quicktime hd material to iPod/iPhone H.264. I know that there are iPhone Trailers available on the Apple Movie Trailer Page, but lets take a trailer as an example video source, because they are free to use and are leading to the "dropping frames" problem.
Source video data:
H.264/MPEG-4 AVC
23.976 fps
5755 Kbps (VBR)
1280x720 (16:9) / Progressive
Converted video data:
H.264/MPEG-4 AVC
23.976 fps
1472 Kbps (VBR)
640x360 (16:9) / Progressive
While the source video playback is smooth in quicktime, the converted video drops frames and the playback is very jerky.
The problem occurs with every single trailer i tried (e.g. The Curious Case Of Benjamin Button).
I also tried to convert the material with visualhub (ffmpeg/vlc) - same result.
Has anyone ideas how to solve this problem? Thanks in advance!
Message was edited by: florian.kloppe

The issue could very easily be insufficient hard drives. You really should have a minimum of three internal drives for editing. A single 5400 RPM drive is bound to cause lags.

Black strobe glitch / dropped frames on rendered, exported video

Similar Messages

Maybe you are looking for