Forum Replies Created

Page 7 of 8
  • Bill Portune

    June 13, 2005 at 1:47 pm in reply to: Is Q-Rez Dead?

    That is extremely disappointing to hear. Q-Rez was one of the “promised” features that influenced my decision to go with the Kona2 – I had planned to use it with my HD workflow since it’s compression is less heavy-handed than DVCPROHD.

  • Bill Portune

    June 6, 2005 at 2:46 pm in reply to: Automatic Duck Pro Import and Tiger

    …Also on 10.3.9 the ProImport plugin crashed the plugin folder for FCP 5.0 until I removed it.

  • Bill Portune

    May 31, 2005 at 4:15 pm in reply to: FCP 5 capture stopping early.

    Thank’s Ron, that was indeed the problem!

    I’ve been capturing A/V separately so that when I use MediaManager to trim down my media the A files don’t end up with V at the same time…

  • Bill Portune

    May 26, 2005 at 1:46 pm in reply to: FCP 5 capture stopping early.

    Happened on 2 seperate masters on 2 different machines, so I’m confident it isn’t a time code break.
    The Video file is 19.94 Gigs, and audio is 894 Megs, so possibly it could be a file limit to 20 Gigs. I can’t find anything in FCP 5 that limits overall file size – I wonder if it could be a QT7 issue?

  • Bill Portune

    May 23, 2005 at 9:23 pm in reply to: FCP 5 Plugins not recognized

    Thanks, saved me a bunch of time. It turned out to be the Automatic Duck Pro Import that was crashing the plugin folder.

  • Bill Portune

    May 14, 2005 at 4:02 pm in reply to: Bill Portune: Pls advise IO and Kona2 together

    Hi Sam,

    It isn’t anything that complicated; be sure you have all the latest driver/firmware updates and Io control panel app.
    The decks I have hooked up are: BetaSP, JVC D9, DigiBeta, HDCAM, DSR-45 DVCAM, VHS for dubbing.
    If you’re working only with BetaSP, just hardwire the component connections between the deck and the Io. The audio I run through a Mackie board, but I suppose you could hardwire the audio also and monitor via the deck.
    Then just connect the Io and Kona2 via SDI.
    For monitoring I use the S-Video out of the Io to my monitor and the composite out to my scopes.
    When you are trying to use the Io control panel to select inputs, be sure you don’t have it set as the output for FCP – Kona2 should be your output device. I also use the RS422 from the Kona2, and you may need to play with your capture/playback offsets to find what works best for you – converting through the Io adds a frame to both, but it’s easily adjusted.

    This is my setup only – there are many ways to do it and others will have differing opinions on how it should be done…

    For the last year I’ve been using the Io for all my SD needs and have been extremely happy. If you are using BetaSP/SD you might want to just keep it simple and use the Io by itself – you won’t gain that much by adding the kona2 into the mix.

    Hope this helps – Bill

  • Bill Portune

    May 14, 2005 at 3:51 am in reply to: Bill Portune: Pls advise IO and Kona2 together

    Hi Sam,

    I’ll be in the office in the morning and I’ll give you a rundown of my setup then.

    Bill

  • Bill Portune

    May 2, 2005 at 3:11 am in reply to: H.264 Online?

    Thanks!

  • Bill Portune

    April 30, 2005 at 10:11 pm in reply to: Frame Accuracy

    5 sec preroll 20/20 good attempts

    3 sec preroll 17/20 good attempts – attempts 8, 16, 19 the first cut after in-point occurred 1 frame early.

    This was with Mastering with no bars, slate, or black prior to first frame of program. On the DVW-2000 I set the TC to int/preset and black the head using FCP. Accuracy on the machine has been flawless with both assemble and insert edits. It’s just the FCP material that’s been 1 frame early at times.

  • Bill Portune

    April 29, 2005 at 9:58 pm in reply to: Frame Accuracy

    Great tip (should have thought of that myself).
    I’ve also found that lengthening my preroll time to 5:00 instead of 3:00 has improved accuracy/consistency.

    Thanks again!

Page 7 of 8

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