I get these as well, though it's usually condensed to say "this line was repeated 131 times"
It's eventually followed up with an error:
Final Cut Pro error: FigTimeGetSampleNumber t.timescale == 0 || Non-Numeric(t) || Invalid(t) || sampleDuration.timescale == 0 || sampleDuration.value == 0 (t=inval, sd=0.041667(100/2400))
But only the programmers can really interpret this in the context of what they're trying to do. A "loss of precision" might be harmless, depends what's happening.
I suppose that the warning repeated 100's of times, might be an issue in itself.
My machine is a 4GB iMac 2.8 GHz dual core. The FCP problem is not only related to spilling the log, but it is hanging up my system constantly, be it during editing or exporting. The only way out is a forced reboot. Pitty, because during the scarce moments it is working, it looks like a really nice program, but in the state it is in now, I wouldn't dream of buying it. Apple don't seem to take the problems seriously, so a soution is not to be expected.
Uhhhh, I am editing a video.....
Format is HD, length app. 10 minutes. Should work on my machine according to system requirements. I accept some slow response, but not hangs, crashes, system locks and all sorts of other unexpected behaviours. If it can't run on a machine my size, Apple should say so.
I give up. FCPX is too buggy. It eats up all RAM (there are messages about memory leaks). Today I tried to export a 2 hour movie and all memory is steadily eaten up by FCPX and at 86% it just dies. After rebooting it appears it has created a 103GB !!!!! movie, which obviously cannot be opened. So its back to iMovie for me
Yes I agree. These bugs make a good product unreliable.
I also had repeated issues with encodes stalling at 66% - even with short 8 minute HD ProRes programmes.. I had tried export, share via compressor, share using compressor settings - yet none could bypass the issues. I troubleshot by removing certain parts of the timeline and trying to encode. Eventually I managed to get a non-stalling encode.. so added back the clips sequentially. Found one clip that seemed to be a cause.. eventually re-ingested it and the encodes were successful. Encode times are routinely 3 times realtime on a modern MBPro.
Not a great way to run a professional edit facility.
A colleague suggested moving FCP7 into a separate folder so that it didn't reside alongside FCPX. That may have helped.
This FigTimeHalve issue is so frustrating. If only we had just an inkling of what it relates too we could at least have a chance of isolating and working around. Are there no Apple logs of such issues and what FigTime relates to?
Dang.... same issue with the thousands of "Final Cut Pro: FigTimeHalve: WARNING: Halving FigTime 1943889373/1581300000 is falling back to FigTimeMultiplyByFloat64 - loss of precision" in my console.... usually preceeding yet another beachball of death.
I have been getting Open GL ERRORS (documented by others in other threads) in the console for days. Randomly ending in a beachball hang.
It is just today that I started seeing the Loss of Precision errors that now fill the console log when I run FCPX.
I notice the Open GL errors whenever I mouse-over a thumbnail, when I apply an effect, when I use the slip tool in the timeline.
This is a big problem in that I need to get my work done, and today is the final day of the project.
Mac OSX 10.7.5
ATI Radeon HD 5770:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 4
L2 Cache (per Processor): 4 MB
Memory: 26 GB
Bus Speed: 1.33 GHz