Dropped Frames/Processor

Hey,
I just installed FinalCut Studio 2 on my Macbook and whenever I try to capture footage (hd dvc 720p60) I get dropped frames. I am also unable to open projects of the same format. I have set the sequence and capture settings according to the footage but this hasnt worked. Someone suggested that the processor on my computer isn't fast enough and that I need a new computer. Is this an accurate assessment?

Someone suggested that the processor on my computer isn't fast enough and that I need a new computer. Is this an accurate assessment?
Probably not the issue but then it's hard to say since, we can't tell what computer you have from here.
rh

Similar Messages

Warning: Sometimes Final Cut exports a non-drop sequence as drop-frame

Just a heads up. This has been maddening for me. On occasion I will export my program for compressor and it will be drop frame when it should be non-drop.
These are sequences which have exported fine before. There is no rhyme or reason to it. Tonight I've lost about 2 hours because of this. At least I knew to check it before compressing the file and sending it out to our contractor because it has happened in the past.
By the way shutting down FCP and opening it up again seems to cure the problem.

System req's for fcp 5
General System Requirements
Macintosh computer with 867MHz or faster PowerPC G4, PowerPC G5, Intel Core Duo processor, or Intel Xeon processor
HD features require 1GHz or faster single or dual processors (authoring HD DVDs requires a PowerPC G5, Intel Core Duo processor, or Intel Xeon processor)
512MB of RAM; 1GB of RAM for HD features (2GB recommended)
Display with 1024-by-768 (or higher) resolution
AGP Quartz Extreme or PCI Express graphics card (Final Cut Studio is not supported on systems using the Intel Extreme Graphics 950 GMA)
Motion requires the standard graphics card found in any Mac Pro, MacBook Pro, iMac Intel Core Duo, Power Mac G5, iMac G5, a 1.25 GHz or faster PowerBook G4, or a 1.25 GHz or faster flat-panel iMac.
Mac OS X 10.4.4 or later
QuickTime 7.0.4 or later
4GB of disk space to install all applications
Additional 42GB to install all optional templates, loops, content, and tutorials (may be installed on separate discs)
It would seem that you've been reasonably lucky thus far running 10.3.9

Dropped Frames in the Xsan environment

Hello Everyone, I have just setup a SAN network and have been experiencing dropped frames when capturing HD Pro Res 422 on my two client computer at the same time. I have been successful capturing on one computer at a time and playing the same capture scratch footage on both systems at once with 5 streams of video playing on both system with effects, opacity changes and have experience no problems with that.
Let me backup and give all the information I can about our setup.
We did a clean install on a G5 with the latest version of Leopard and 3Gb of Ram for our primary MDC. We have 2 client computers (1 acting as the backup MDC) These computers are both Brand new G5's with 6Gb of Ram and Dual 3Ghz processors. All CPU's are Running the latest version of Leopard.
We are using Xsan 2.1 for the admin, a 16-drive Vtrak Promise RAID system for storage, and qlogic 5600 Sanbox for the Fiber Switch.
For RAID'ing the storage together, we following the Apple spec's for setting up our arrays in conjunction with the Promise Drives. We have 2 drives in RAID1 for our metadata LUN with additional drive tasked as a spare to this LUN. We then RAIDed 6 drives together in RAID 5 (3 from each RAID Controller), we then repeated this process to create 2-6 Drive LUNS. Out last drive was tasked to be the backup for both of these LUNS.
We setup our volume with the RAID 5 Drives Arrays to be Our Data (Video Capture) and the RAID 1 drive to store our Metadata and Journal Information. If any more info is needed to help you answer my issue, please let me know and I'll answer you as best I can.
In my testing of the system, I setup our two client computers to capture as we would in a Real World 2-editor project. Everything was going fine until I tried to capture on both systems at the same time with the PRO Res 422 HQ codec. Am I pushing the system too hard? I wouldn't think so as two streams of that footage should be topping out at 50-60mb per sec, and with my AJA speed Test I am getting write speeds of 300mb per sec and read speeds of 400 mb per sec.
Also in my Vtrak Promise Logs, I see a "Entering Critical Mode" warning just as the dropped frames occur.
There is also no consistent point at which the dropped frames occur, sometimes it's 30 seconds in, sometimes 15 minutes in, and both systems drop the frames at the same point one system never keeps on going if the other drops frames.
In my Xsan Admin I have the folders that I am capturing to set to the "Video" affinity so I know that the footage should be headed to my Raid 5 drives.
Sorry about the long post, just wanted to give as much info as I could on the first go around, any help is greatly appreciated! I'll be working this problem all day tomorrow, Hope to have the system up and running next week, but I want to really test this out as much as I can in the meantime, thanks in advance!!
-Casey

Just wanted to report that the dropped frames issue has been solved for the time being.
I contacted Promise Support and in viewing the logs discovered we had a faulty drive, even though we had a backup drive tasked to the array where the bad drive wasm we had PDM enabled on each array so the Promise Tech guy said that would lead to performance issues.
So even though the SAN would work, if you put a lot of stress on it, it would fail. So here's what we did:
1. Initialized the fauly drive and tasked it as the spare to the new Metadata LUN
2. Disabled PDM on each array
3. Hook up fiber connectivity between previously empty ports on our Promise Box to our fiber switch.
I have been capturing 2 streams of HD Pro Res 422 HQ for the past 30 minutes on both systems with no issues,
I really want to put the system through the wringer and make sure our current setup can handle some demanding stresses. Is there a good test that anyone can recommend? We only have 2 clients on our SAN.

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

Drop Frame Timeline with 59.94 Editing Timebase

I'm working with DVCPRO HD footage for broadcast television. My Editing Timebase is 59.94 and under the Timeline Options tab the checkbox to select a Drop Frame timeline is grayed out. I have a sequence that needs to be EXACTLY 22 minutes in running time, but I can't find a way to change to a Drop Frame timeline. I have found this to be the case for all 59.94 sequences. Any suggestions?
Final Cut Pro 6.0.1
MacPro1,1 Mac OS X (10.4.10) Dual-Core Intel Xeon, 3 GHz, 2 Processors, 4 GB memory

Most TV shows that are broadcast are cut in NTSC, non-drop frame.
I think that you'll find that to be incorrect. The SEQUENCES are always drop frame...because we need to know the proper show times. It is the CAMERA MASTERS that are mostly shot NDF...for the clean lists. IN the past (and still currently I suppose) when dealing with onlining on a tape to tape system or sometimes with an Avid Symphony, you needed NDF masters for the clean workable EDL. That is becoming less of the norm lately, but it is still wise to shoot one format...DF or NDF, instead of mixing. NDF camera masters are the norm.
But DROP FRAME NTSC sequences are the norm. Although NDF HD sequences are the norm lately, but I wonder if that is due to the NLEs that don't offer DF timelines. Which is stupid, as the decks are DF capable.
Shane

Dropped Frames Problem

I am helping a friend edit a project in FCP 7.0.1. He has a slightly older iMac with 3GB RAM and a 2.16GHz Core2Duo. The footage is HD and is on an external HDD and is conncted to the iMac via Firewire. The footage plays fine in the Sequence until one clip ends and a new one begins. Then FCP hiccups and generates a dropped frames error. Any idea what is causing this?

It turns out the compression used by the camera was H.264. This compression is not designed for editing and is processor intensive, that is why there was stuttering issues. You have to convert the footage to something easier on an NLE such as Apple's ProRes. Use Compressor to change the files (or edit the sequence with stutters, then render it out with ProRes) and you should be good to go.

Dropped frames on MultiCam editing with Canon XF305 Footage

Hello,
I recently purchased three Canon XF305 series cameras and have been conducting a series of tests to determine the best recording format and editing workflow. First, does anyone have experience with these new Canon cameras?
Using the log and transfer utility, I've been bringing the files into FCP natively using the canon codec (which is actually mislabeled as a Sony codec). Once in, the footage looks good to edit, without requiring rendering.
However, when I setup a multiclip sequence with the three cameras, the render bar turns green and I'm getting all kinds of dropped frames on playback. Is this a computer processor issue, drive speed, or codec? The multiclip is the only time I have trouble -- once I collapse the multiclip, I can edit fine without any drop frames.
I've done tests using 5400x and 7200x drives using both firewire 800 and eSata, no changes. I believe that rules out drive speed.
Is this a processor issue? What can I do to resolve this, as our workflow involves 100+ hours of footage from 3 cameras.
Thanks in advance

but my experience with the 305's in ProRes is that it makes it a bigger file(more than double)
Of course it will. XDCAM is a highly compressed format. ProRes is a larger file type, higher data rate. It will be larger. Did you not notice that the ProRes footage from the 5D were also about 5 times larger?
and still needs to render.
If you worked in a ProRes timeline, then you shouldn't need to render. If you still do, than something is wrong. Create the file...make a new sequence, cut this into that sequence...FCP will make the settings match. If it does this, and you STILL need to render....you did something wrong.
when I actually converted to ProRes, it seemed like it was more taxing on the computer, took up twice the hard drive, and more than three times the time to transcode compared to native.
It is less taxing to actually edit with. GOP formats require the computer to constantly process the GOP footage to show you frames...since there are no real frames in any GOP format. Well, there are 3 frames every second, then a bunch of pictures, and the computer has to guess what is next by looking at the frames, and then the pictures, and make up the in-between. PRORES is a full frame format...no guessing, no computing. And larger files are not more taxing on the computer...they might require faster hard drives...and larger ones, but they are less taxing. Yes, longer to convert than native, but when that is done, things are easier.
But, do what you want. I just gave a suggestion.
Shane

Problems with dropped frames in FCP 4.5 Log & Capture

Thanks for the advice on my previous post regarding sound problems - those are now sorted, but I am having problems with dropped frames in Log and Capture. I am using FCP 4.5 with OS X 10.4.10 on a Powermac G4. CPU 867 mhz dual processor. L2 Cache 256 kb, L3 cache 1 mb. Memory 1g. Bus speed 133hz. I am capturing from a Canon XM1 via Firewire. The scratch disk is a 500gb Seagate FreeAgent USB 2.0, 7200rpm.
Basically, the video and audio are fine while playing back in Log and Capture and I can control the device, but any attempt to capture, whether Capture Now or Clip result in a very jerky picture and aborts with dropped frames after a few seconds. The sound is ok for the few seconds before it aborts. There do not appear to be any problems with the timecode.
My capture preset is DV Pal 48hz.
Any advice or pointers gratefully received.
Thanks, Ally

Well quite. I have just tried it in the internal hard drive and it works fine now. I am going to have to capture everything to my small hard drive and move it across to the external. Then, when I have finished I am going to bang my head against the wall and buy an external HDD with Firewire.
Thanks,
Ally

Final Cut Pro dropped frame rate issue

Hi there, i currently shot a short film on the canon 5d mark II 30fps and i am trying to edit it in final cut studio 2. I have recently bought the new macbook pro 15inch 2gb module.
Now the canon footage is h.264 but when importing the clips into final cut pro 6 there is a lot of dropped frame rate issues but I thought this machine could handle HD footage?
Can someone more advanced than myself recommend what i am doing wrong or a work flow that i can work with to stop dropped frame rates and render times.
Last piece of information, the project will be entered in film festivals in the spring its only a 3 minute short and i have 5 folders of footage under 4gb each which was taken from the camera
Thanks for your help.
Michael

You are missing a huge conceptual point. If the file can not spool off of the hard drive fast enough, you get dropped frames. It isn't a processor or ram issue right now, it is a hard drive speed issue. Your system drive is overtaxed trying to run OSX, applications AND spool video. It just can't keep up. Changing the graphic card isn't going to help (and how do you change the card in a laptop?)
Get an external esata drive - with the new MacBookPro you'll need an esata Expresscard34 adapter for the computer to connect the drive. Firewire is not an option with that machine and USB2 will not cut it with high data rate formats like ProRes.
When you drop in the ProRes clip to the timeline and it tells you there is a mismatch, this means your preset for the timeline is something other than your clip. You WANT ProRes and you need the sequence to match your clip - tell the program to CHANGE the sequence to match the clip.
Video is not easy and it isn't inexpensive. Time to open up those manuals and your wallet!
Good luck,
x

Dropped frames on Brand New Macbook and Final Cut Express!

I have recently bought a New Macbook, and installed Final Cut Express HD 3.5 on it. I have Quicktime Player 7.3. My Macbook is a 2GHz Intel Core Duo processor. Memory is 1GB 667 Mhz. I have already used up a lot of Hard Drive on my Laptop with other applications, and in my capture window it says that I have 24.5GB space (109 minutes). Could this be the problem - not enough space?
I have looked over past discussions on this and in some cases I see that a downgrade to the old version of Quicktime has been necessary. As I have a new Macbook and new Final Cut Express HD, could this still be the case?
Also I have been reading the manuals, and wonder if the frame rate or time code settings could be affecting the dropped frames? Does anyone know where I can check this?
I'm a total newbie to FCE so be gentle....
Appreciate all advice

You are quite frankly, a genius. I have just managed to capture my footage after a gruelling few days of trying just about anything. Your recommendations regarding settings and also the external hard drive have fixed my problem.
I'm going to have a large glass of wine now to celebrate my victory - and then I'm going to try and figure out how you actually use FCE after that.... er hem... now where did I put that manual..?
Thanks loads

[..\..\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?

Multiclip Dropped Frames/Data Rates from from FW 800, 7200rpm Drive

I am using an external Lacie 7200 rpm "Little Big Disk" .. Editing DV Multiclips in Final Cut (3.6 MB/sec data rate per clip... 7 clips/streams) But it won't play back all at once, anything over 15 MB/sec data transfer rate (as I watch Activity Monitor) it starts choking and dropping frames til it just freezes. Lacie claims that this drive handles a steady 80MB/sec transfer rate... All I need to do all these streams is 26 MB/sec (That's the speed it does at work from an XSAN and no problem playing back 7 streams of DV) Is the bog down in my system the FW800, my RAM, processor, or the Cache of the drive? (16MB)

Do you have any other FireWire devices (incl. cameras) plugged into other ports on the computer or on the drive itself? There's only one FireWire bus on a G5, and it's shared between the FW800 port and the FW400 port on the back in addition to the FW400 port on the front.
If you have other devices plugged in, they can cause the entire bus to slow down to the speed of the slowest connected device.

MBPro C2D 2.33GHz/3GB RAM drops frames playing H.264@1920x1080

I've been trying to watch with a MBPro C2D 2.33GHz/3GB RAM a movie (in .mkv container) coded in H.264@1920x1080 (a blueray rip actually), but both Quicktime (I have Perian installed) and VLC would drop frames time to time.
Processor never goes over 100-120%.
Do I have bad codecs installed? Some ideas? I thought my mac would do the job...

H.264 is a complex video CODEC, and there can be many factors in the implementation process which would effect what you're seeing here. It would be nice to see some H.264 analysis tools in order to give us more information about the video stream-- I plan on embarking on some live H.264 video projects for doing live educational video delivery, and access to such tools would be a real plus.
It seems as if the costs in H.264 hardware encoders are dropping rapidly now, with a standalone hardware device (e.g. from Mango in Israel) which does encode/decode audio and video over ethernet coming in at about 5-600 USD. There are even standalone set-top box style decoders for under 200 coming out of China now.
Golan.

Fx5700vtd128 drop frames

hi, i had some issues trying to capure video, with virtual dub and my video card i don't know hot to configure properly "something" to avoid the dropped frames, at maximun resolution 500xsomething it' very low wors if i capture with some compression, using the bundled win dvd creator resolution is very small even if i change quality, 320x240. and show jagged edges(i did not know if that word is correct to describe the effect) with msi media center deluxe 2 the capture had good quality but sometimes the quality go down and look pixelate, i supose that it's because my processor or hard disk are not enough faster and to avoid the frame drop the quality get low, may be using faster hd and/or with more amount of cache, and a faster or more powerfull porcessor can i get better the capture, this nvidia card do not have video processing and then the processor had to do "the hard work" i dont know. somebody can help me, or give me some idea
duron 1600 applebred
msi k7n2delta ilsr
256mb memory at 400mhz (running 233mhz)
msi fx5700vtd128
hd 1: maxtor diamond plus 80gb 7200rpm 2mb cache ata 133
hd 2: seagate 20gb 5x00rpm 512kb cache ata 66
windows xp pro service pack 1 and 2

mmm... no one got to say something??
maybe i write bad...mmmm

720p60 P2/HD Dropped Frame Issue

I'm having a dropped frame issue in FCP with some P2 720-60p footage. I can't get it to play through a sequence without freezing and giving me a warning. We've narrowed it down to an apparent processor issue. There are two tracks of audio (a stereo pair), and two tracks of music (again, a stereo pair). When we turn off the music, the sequence plays fine. But when the music goes back on, the sequence chokes. The funny thing is, I just did an HD project shot in 24p/n with several tracks of audio and several tracks of video and, aside from needing to render certain things, it played fine.
Any ideas?
Here are the specs:
P2 footage originated in 720/60p
AUDIO/VIDEO SETTINGS:
Sequence Preset: DVCPro HD 720p60
Video Playback: None (there isn't an output card for this computer).
SEQUENCE SETINGS:
Frame Size: 960x720 (HD 960x720 16:9)
Pixel Aspect Ratio: HD (960x720)
Editing Timebase: 59.94
Compressor: DVCPro HD 720p60
Audio Rate: 48 kHz
Depth: 24
Config: Default
Any ideas here?
Thanks,
Tim Walton
KVIE Public Television

Then it's pointing at a throughput problem between the RAID and the server I'll guess. Trouble shooting that could be interesting. Can you move the media to a local drive?
I'd also be interested to see what AJA's read/write speeds are on that RAID from your station...
Post the gear between your mac and the server etc.. whose RAID is it, How is it formatted? Got a model number of each of the devices involved? Mac Server?
Jerry
You've selected the "Easy setup" for the format you're editing too, right?

Dropped Frames/Processor

Similar Messages

Maybe you are looking for