Forum Replies Created

Page 188 of 235
  • Craig Alan

    April 24, 2011 at 10:38 pm in reply to: install disk images FCS 3

    Thanks Zane and Rafael.

    Zane, what I meant was that the CD/DVD master option created the image much much faster than read only option. Both without compression. Why would that be?

    If, therefore, I stay with cd/dvd master option, is there any difference in how I would use them?

    Open all images on desktop, launch the studio disk install, and it will load the others as needed? That’s how I installed FCS2.

    Also I have one of each kind of format now. Is mix and match ok?

    I want the most efficient way possible since we have a site license and I will be installing on several computers.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • gotcha.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • [Jeremy Garchow] “Nests work in almost every other app but fcs”

    What about nesting doesn’t work in the current FCS?

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    April 13, 2011 at 1:55 am in reply to: Snow Leopard – World of Hurt?

    Having a clone of your system is always a good idea. But to move to snow i would do it the other way. Do a fresh install on an external drive. Do fresh installs of all your apps. Move over your docs. and email etc. And test it out. When your happy, clone it over to your current system drive. Most of the FCP and media pros rec. a clean install when moving to a new OS or new version of pro apps.

    check this out

    https://www.kenstone.net/fcp_homepage/reinstall_osx_fcs_part_1_saraceno.html

    read through all 3 parts.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    April 13, 2011 at 1:34 am in reply to: Trackpad Funtionality 10.5.8

    MacBookPro4,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.5 GHz

    I can pinch zoom on 10.5.8.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    April 12, 2011 at 12:55 am in reply to: Rare audio problem in Final Cut Pro…

    do a simple google search. been covered including on the cow tons.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    April 3, 2011 at 6:16 pm in reply to: Audio coming into FCP low

    Wow!
    Thanks so much Ty.
    I always tell my students that if they were doing a low budget production and they had just enough coin for one professional, “hire an audio technician.”

    I no longer have the pd170s and XL2 to go back and answer your questions through testing. But I can tell you what I remember about capturing audio with them. On the xl2, like you mention, I used mic level in and calibrated my mixer as you mention and I got pretty good results. Still dependent on mic placement and talent and audio conditions. On the pd170, I think I used line level in and tried to keep the meters no more than a tad over -12 or the recorded sound would be distorted (in other words clipping).

    The advantage of the pd170 over the canon was its ability to record a really decent picture in all sorts of light. Great cam if you had no time for set up.

    Whenever I tried to ask folk about how to improve sound on the pd170, I was told to record double system or get a mod to bypass the audio circuits. I tried all sorts of different settings including line level and arrived at best I could do practices.

    There’s another thing that may come into play here. Some mixers can be altered to send, 0 dB, +4 dB or even +8 dB when they read 0 dB on their meters. The Sound Devices 442 is set stock at 0 dB, but it can be adjusted in the firmware. I leave it at 0 dB. Why is there +4 and +8 when the meters read 0dB? I don’t know the history.

    I wondered about this too. I had a shure mixer and called the tech department to ask about adjusting the output levels. The answer he gave was, “leave it alone. ” Why, I asked, would the manual go into details about changing it? His answer: If you need to ask, don’t worry about it.

    I know the camera meters are showing -6dB. I know this because I have watched both mixer and camera meters.

    So during sound checks: set the mixer levels using tone, then watch both mixer and camera meters to see if they remain in sync?

    With some cameras, even though my peaks are at -6 dB or below on the camera, I can plainly hear clipping.

    YES that was the case with brand new PD170s! I tried to keep the levels as close to -12 as possible.

    If you listen to the camera headphone output, you’ll hear the click or sometimes a sort of metallic clink.

    YES. I always got afraid when I heard that.

    When I run into this situation, I politely tell the camera op there’s a problem and he/she might want to get it checked out. In almost every case, this happens when feeding line level from the camera.

    FROM THE CAMERA??

    “In order to prevent mildly distorted audio, you really should even try to get close to 0 dB because we cheaped out. Thanks and have a nice day!”

    The unconfirmed opinion in its day was that the pd150/170/vx2000 had crappy audio in order to not have Sony take sales away from their own higher end cams.

    I can run up to 0 dB on my Canon XL2, but I do need to send it mic level.

    Yes my experience exactly.

    You said, my experience is that if the sound is recorded a little low but clean I have some room in post to increase the level without adding unacceptable distortion.”

    Why should you have to record “a little low?” Because the camera audio section is not designed properly? Well then I guess, as Peter Groom suggested earlier, you HAVE to. …

    When you bring up the level in post, you are also bringing up the noise floor, especially a problem if you’re recording only 16-bit audio.

    Yes it adds noise! Better than clipping.

    You asked: Can’t you test the camera by recording directly into the cam without a mixer and seeing in FCP if the levels match?

    You mean mics directly into the camera? Sure, but what are you trying to get at? Problems with the camera’s line level input or problems with the mixer?

    I was getting at your suggestion that the cam might not be calibrated correctly. Take the mixer out of the mix and see if the cam’s meters are true.

    In summary, yes, I’m bent when I run into cameras that cheat the audio. On a practical basis, as Peter Groom suggests, we need to be aware of them. Doesn’t mean we have to like them. 🙂 However, when they are broke, they’re broke.

    I think many of them are designed broken (cheaply).

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Craig Alan

    April 3, 2011 at 2:46 am in reply to: Audio coming into FCP low

    Ty, please dummy this down a little. You’re saying that even after calibrating a camera to the mixer’s tone and not hearing any distortion when monitoring with headphones using the camera’s headphone out and the meters indicating acceptable levels, the sound that is actually recorded can be clipped and distorted? My experience is that if the sound is recorded a little low but clean I have some room in post to increase the level without adding unacceptable distortion.

    Can’t you test the camera by recording directly into the cam without a mixer and seeing in FCP if the levels match?

    I know when I used to record with sony pd170s I was careful not to let the sound get too much over -12 or it would distort. On other cameras I could be a little more generous. But I assumed this was due to PD170’s poor preamp which added noise and distortion.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • New sequence. Exactly the same settings. Oh well. I’ll finish the project and do some trouble shooting later.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

  • Thanks Michael. I’ve never changed the sequence settings after setting up a project. If I change a property the entire sequence will just render to the new setting?

    I’m pretty sure when I first set up this sequence that final cut matched the clips.

    But either something is slowing the renders down or maybe its the fact that this sequence is longer than my usual. It’s almost 1 hr 45 min. 10 min clips are taking as long as an hour to render after some basic color correction.

    I’ll try your suggestion of dragging one of the clips to a new sequence and seeing what settings fc chooses.

    Not sure why I got an error message that the clips are not FCP compatible or words to that effect.

    OSX 10.5.8; MacBookPro4,1 Intel Core 2 Duo 2.5 GHz
    ; Camcorders: Sony Z7U, Canon HV30/40, Sony vx2000/PD170; FCP certified; write professionally for a variety of media; teach video production in L.A.

Page 188 of 235

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy