Forum Replies Created

Page 4 of 15
  • Jim Blokland

    May 7, 2009 at 4:30 pm in reply to: Kona 2 downconvert Pro Res in Real Time?

    Hey Walter:

    Thanks for this. Just spoke to Tony at AJA and he says it should work fine. Just gotta set up the control panel for secondary SD downconvert, as per usual.

    Thanks AJA. You guys rock!

    Best, JIM.

    OSX.5.6
    Dual 2.7 G5
    5.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 23, 2008 at 5:43 pm in reply to: Any/All Konas remove 3:2 pulldown on the fly?

    Thanks for this Jeremy. Good advice, as always.

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 23, 2008 at 4:55 pm in reply to: Any/All Konas remove 3:2 pulldown on the fly?

    Hey Jeremy:

    Thanks for your reply. One further question: if I’m getting ALE files from the transfer house, they would automatically make sure each clip begins on a A frame, right? if so, I could just batch digitize from that list once it’s imported into Cinema Tools and be good to go?

    Thanks in advance.

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 20, 2008 at 8:26 pm in reply to: Utilizing an assistant for feature film

    Hi Steven & Andrew:

    Thanks so much for your thoughtful responses. I’ve decided to hire an assistant and I look forward to sharing the workload with them — it will be a great learning experience all round!

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 17, 2008 at 2:41 am in reply to: Offline Specs for Super 16 Feature Shoot

    Guys:

    Thanks for the great feedback. I’ll see if I can pitch the 720p HD thing to all concerned. As you pointed out Warren, the numbers can be small along the bottom of frame, as long as they’re readable, should do the trick.

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 16, 2008 at 8:11 pm in reply to: Offline Specs for Super 16 Feature Shoot

    Hey Warren:

    Thanks for your reply. I’m definitely using Cinema Tools, but I also want the burn-in as backup (call me paranoid!). I guess there’s no way of cutting HD at 4×3, huh? Looks like I might be heading towards a DV50 codec at standard def…

    Oi!

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    November 16, 2008 at 7:56 pm in reply to: Offline Specs for Super 16 Feature Shoot

    Hi guys:

    Thanks for your responses. Perhaps I’ve been unclear. My concern is that, short of cutting at 4×3 letterboxed, I wouldn’t be able to get the window burn of the keycode/TC/feet and frames into any black area below the 1:1.85 picture area. On a 16×9 frame, there would not be enough black space below or above. Does this make sense?

    I’d really love to cut at 720p, because as David pointed out, the resolution and data rate fit perfectly. I’m just concerned about screening cuts with the window-burn on them — and I don’t want to rely solely on Cinema Tools to track the numbers correctly. I want a window burn to make double sure the numbers are correct.

    Any other words of wisdom?

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    June 22, 2008 at 1:25 pm in reply to: Quictime reference – Field order?

    Hello:

    I’m having the same issue. I’ve got material that was downconverted from HDCAM SR (24p) with pulldown added to DigiBeta, then digged from DigiBeta via SDI to MXF 1:1 on a Nitris.

    Now I’ve cut the material in Xpress Pro and am trying to output two versions: an H264 Quicktime for the web, and an 8-bit Quicktime to make an SD DVD. I’ve tried to use Cinema Tools and Compressor to remove the pulldown and get it back to 24P, but I can’t seem to find the correct cadence to get it to work in Cinema Tools — and in Compressor it works, but there seems to be a big hit in quality. There’s a kind of ‘ringing’ in the picture that looks awful.

    Any help to get the material back to 24P would be most appreciated.

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Hey Jeremy:

    Yes, I’ve had the same experience on a feature I cut. Unfortunately for me, 6.0.3 does not seem to solve this anomaly. Oh well. The SmoothCam option is pretty frickin’ good — and worth the re-render — I just saw some shots with the effect applied on the big screen at our Deluxe DI, and they looked pretty sweet. Nobody asking us to redo those shots on a FLAME or what-have-you…

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

  • Jim Blokland

    April 23, 2008 at 2:09 am in reply to: Feature shot on HPX-500 just finished DI

    Hey Michael:

    Congrats on your film. We’re just about to head into DI for a feature shot on the HVX200 — like you, cut on FCS and output via dpx files for the grade. My question is what means (software etc.) did you use to get the dpx sequences out of FCS? Were you able to preserve the ‘super-white’ values? So far in my research, I’ve found that only GlueTools can get these values out of FCP, and at that it’s a bit of a work-around for this feature.

    I’d love to hear about your DI process.

    Best, JIM.

    OSX.4.10
    Dual 2.7 G5
    3.5 GB RAM
    Radeon X800 XT
    Kona 2 / K-Box
    Seritek 1.5 TB RAID
    AVID XPRESS PRO/MOJO

Page 4 of 15

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