Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Problems with TV playback and FCP

  • Problems with TV playback and FCP

    Posted by Rob Hindley on October 2, 2008 at 7:05 am

    I am trying to playback through a television (PAL SD) through a VCR using a DataVideo DAC200 converter. However all I am getting is a green screen! I have set the dip switches correctly as per the DataVideo site and FCP recognises the device through FireWire. My Mac is a dual G5 with 4Gb RAM and 24Gb of space left on the drive. My footage is coming of another firewire external HD which is functioning correctly.

    I have checked all connections, set the DAC200 to DV but to no avail.

    And it all worked perfectly yesterday!

    Any help would be appreciated…

    Rob Hindley replied 17 years, 7 months ago 2 Members · 2 Replies
  • 2 Replies
  • Rob Forsythe

    October 2, 2008 at 12:23 pm

    This is written for monitoring via a “camcorder” but just assume your DataVideo DAC200 converter in place of the camcorder.

    This list contains virtually everything to try to enable:
    a. External Monitor VIDEO and AUDIO via FireWire & DV deck or camcorder.
    b. Viewing in the Canvas window on the computer screen.
    c. Being able to record on the external FW DV deck or camcorder.
    d. Being able to capture from a FW device.

    If working this list doesn’t cure the problem… you may have a serious PROBLEM!

    Try things in this order until you find the “cure”:

    1. Make sure you have only ONE (1) FireWire deck, camcorder, DV capture “card”, or D-to-A converter or video device attached to the computer at a time. Any more than one DV device can cause loss of signal and control.
    2. Make sure you have View (Menu) > External Video> All Frames set.
    (If the ALL FRAMES option is grayed-out… jump to step 6 below and continue.)
    3. Make SURE your Canvas window (right window) in FCP is set to “Fit to Window”… AND that it has not been “pushed off” the edge of the computer screen or “pushed into” other windows.
    4. Make sure your CANVAS View Menu (Box Icon with broken sides) is checked on Image or Image+Wireframe… NOT just Wireframe.
    5. Make sure your CANVAS View Menu is checked on RGB… NOT just Alpha.
    6. Make sure your Final Cut Pro (menu) > Easy Setup… is set for DV-NTSC (or DV-PAL, if that’s where you are).
    7. Some camcorders/decks work better under “FW (NTSC/PAL)” -or- “FW (NTSC/PAL) Basic” control (in the capture settings). Try either setting to see which works best for your device.
    8. Make sure your Final Cut Pro (menu) > Audio/Video Settings > A/V Devices (tab) > Mirror on Desktop > must be CHECKED. (If not, playing video will not appear in the Canvas.)
    9. Make sure the “Log and Capture” Window is CLOSED and not just “hidden” behind other windows.
    10. Make sure you have chosen FW output for A/V:
    Final Cut Pro (menu) > Audio/Video Settings… >
    Video Playback: Apple FireWire NTSC (720 x480)
    Audio Playback: FireWire DV
    11. Turn off the power to the Camera/Deck/Converter Box, then turn it back ON.
    12. Make sure the camera is in VTR mode… or the deck is in DV (DV, iLink, or FW) input.
    13. On a Sony camcorder or deck, make sure the menu setting “A/V > DV Out” is set to OFF.
    14. Re-check that your FW cable is well-connected at both ends (or try a new cable).
    15. Important: Quit FCP, then Restart FCP.
    16. Now again, make sure you have View > External Video > ALL FRAMES set…

    If it still does not work. “Trash” the FCP Preferences on the Mac
    “FCP Rescue” is a free Apple Script that will Trash the Preferences.
    It will also restore your user settings afterwards.
    Download:
    https://www.macupdate.com/info.php/id/14729

    If you have “lost” your entire FW connection between the Mac and the device, go HERE:
    https://docs.info.apple.com/article.html?artnum=301852

    >Then, start again at my “step 1” above.

  • Rob Hindley

    October 2, 2008 at 11:20 pm

    Thanks for your exhaustive reply Rob. Awesome!

    I found that trashing the preferences and the cached files did the trick.
    And switching off my processor-intensive screensaver!

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