Emma Mcneill
Forum Replies Created
-
FCP4.5 is not a Universal Binary, your MacBook is an Intel Mac and tries to run PowerPC software via the Rosetta emulation mode which it can’t do with FCP. Time to get that crossgrade old chap.
;o)
Emma
-
If the source video is clean then it’s the compression that’s making a mess of things. Try using Compressor (it comes with FCP so should be on your HD somewhere).
Use one of the high quality presets. Toast can make a fully operational DVD Discs from the MPEG2 and Audio files you get from Compressor.
Emma
-
There is no way to visually show the full time code on the video window unless you burn it onto the file. Full time code is available in the ‘info’ window by pressing Apple ‘i’, or CTRL ‘i’ on a Wintel.
Emma
-
https://www.coffeysound.com/product.php?productid=377&cat=0&page=1
can’t be waterproof because of the heat but it should survive some knocks on the boat without too much hassle and it’s bus powered.
;o)
Emma
-
The ‘myth’ that is perpetuated is that you ‘shouldn’t’ or ‘can’t’ capture DV or other video onto the system drive of a laptop. You perpetuate that myth when you repeat that the OS is to blame (maybe/maybe not) when it could be a dozen other factors.
I’m a professional shooter and editor, have been for 9 years and not once did I ever recommend to someone don’t capture to the internal drive. Instead of living with the problem that your machine can’t do it, try and discover the source of the problem. You don’t have to dig into the OS to do, Activity Monitor provides most of the information you need.
Like I said before, there is no technical or practical reason why any Powerbook from the last 6-7 years cannot capture DV to an internal drive. iMovies DV Streams are much more data intensive (at least they were haven’t used iMovie in a long time) than DV-Pal/NTSC. If what is written above were true then Apple’s prime time video editor for consumers wouldn’t be reliable at all, yet apparently it is.
Let’s just say your in a fix, your out on a shoot, need to capture some footage straight off your camera but your Firewire drive was trodden on by an elephant, then what?
Better to resolve the issue before that happens.
-
Computers are not temperamental, if it’s not working then there is a reason for it, better to solve the issue then perpetuate the myth that you ‘shouldn’t’ do it.
Emma
-
I’m sorry if this sounds harsh, rude or unfair but as a long time lurker around here I cannot in all honesty read this nonsense about capturing to internal or system drives any longer.
I used the first Powerbook G4’s (400MHZ 10GB Drive) back in the day to edit DV footage on the road with no issues. The data rate for dv (3.5-4mb per sec) was nothing to an internal drive back then, today it’s a joke.
Jeff, if your system is dropping frames on the internal drive switch on Activity Monitor and see if any other mini app or OSX process is hogging read/write to the internal drive (it shouldn’t be the case since OSX is not a disc thrashing OS, unlike Windows) IF a process is misbehaving force quit it, don’t worry if it essential to the system it will restart all by itself. Some OSX processes are know to run amok (in particular the ones related to Spotlight).
Chances are something is causing the read write to be interrupted. If you can’t see anything create a new user account on your Powerbook and try the capture process from there. If the same thing happens then there may be an issue with the drive which is preventing it from capturing the footage, drives fail all the time so it’s no big deal.
For the record I’m using the exact same system as you, capture DV to the internal drive all the time whilst playing iTunes and browsing the web (let’s face it acquisition is the most boring part of what we do). There is no practical or technical reason why you shouldn’t be able to capture DV to your internal drive. Luck is not an issue.
Emma