Forum Replies Created

Page 4 of 7
  • Matt Riley

    February 8, 2008 at 5:55 pm in reply to: Timecode issue with Compressor 3

    I just verified the same problem with P2 material I imported last night. 🙁

    -Matt

  • Matt Riley

    February 8, 2008 at 5:53 pm in reply to: Black Magic RGB to AJA RGB

    I’m not sure of the QT version they were captured under. I’ll have to ask.

    I have verified the problem with 3 systems now:

    – G5, 10.5.1, Compressor 3.1.2, QuickTime 7.4
    – Mac Pro, 10.5.1, Compressor 3.1.2, QuickTime 7.3.1
    – G5, 10.4.11, Compressor 3.1.2, QuickTime 7.3.1

    The only thing common to all these systems is the version of Compressor.

    I just imported some P2 material last night, straight from the cards and when I drag those clips into Compressor the timecode is not correct, either. Arrr!

    I still have some ideas to kick around. I’ll post back if I find out anything.

    -Matt

  • Matt Riley

    February 8, 2008 at 3:04 am in reply to: Black Magic RGB to AJA RGB

    Good idea. I may have to use that as a workaround very soon. I’ve got about 3 hrs of dailies headed my way and I don’t think I want to push around the full-res. stuff for editorial so I’ll need to make proxies. Thus the need for accurate timecode.

    One thing that doesn’t help with, though, is that I can’t really use compressor’s timecode filter then to burn in the timecode on the picture (very useful for wrangling multiple editors and fx houses).

    Grrr… This should, um, work fine. But it’s not. Argh. 😉

    -Matt

  • Matt Riley

    February 8, 2008 at 3:00 am in reply to: Timecode issue with Compressor 3

    Black Magic 10 bit RGB (4:4:4) at 23.976 fps, 1080.

    Shouldn’t be anything funky with it, I guess.

    I’ll maybe have time to do some more tests with it tomorrow but right now I’m stumped.

    -Matt

  • You might need to tell fcp manually to use the alpha channel after you’ve imported your targa files. Check the properties info for one of the targa files and set the alpha attribute to straight or black matte and see if that works.

    -Matt

  • Matt Riley

    December 20, 2007 at 3:46 am in reply to: Timeline Scanning Feature?

    If you have a scroll wheel on your mouse (or a nifty trackball with a scroll ring) then you can hold the shift key and move the wheel to scroll your timeline horizontally. Works a treat.

    Also, just to echo, hit “h” on the keyboard to activate the hand tool, which will let you drag the timeline around as you please. Hit “a” after you’re done to get the arrow tool back. Pretty quick.

    A nice feature would be to have the h key work only when holding it down so that releasing it would return to the previous tool. My other edit suite is an Avid DS and its timeline pan feature works exactly like this (except with the x key). It’s just a little nicer than having to hit a key to turn it on, then another to turn it off. Plus, I’m lazy. But then again, most of us editors are. 😉

    -Matt

  • Matt Riley

    November 30, 2007 at 4:13 am in reply to: dropping frames ONLY when Kona is used for viewing

    Hmmm…

    I guess that would make sense, although it sure doesn’t appear to be dropping frames in digital cinema desktop mode. Audio stays in sync and things look normal as far as the motion goes.

    I uninstalled/reinstalled the drivers and it didn’t help. I then purchased a defrag program and set it to run overnight tonight. Hopefully it’ll finish before tomorrow morning. Otherwise, the last thing left to test would be a fresh format of the RAID, which means wiping over 2 TB of data and restoring from backup after that. Ugh.

    I’ll let you guys know how it goes. For now I’m limping along with dcd and at least the ability to output uncompressed SD via the Kona for DigiBeta dubs.

    Matt

  • Matt Riley

    November 28, 2007 at 9:46 pm in reply to: dropping frames ONLY when Kona is used for viewing

    Kona 3, version 4 drivers (Intel Mac Pro) FCP 6.0.1

    RAID averages around 200 MB or so read/write, which is fast enough for my media.

    I haven’t done anything with the drivers yet. This machine is rather stable, so it just makes zero sense that anything like that would’ve gone wrong. I haven’t upgraded any software on it in a while – certainly not since this problem showed up.

    I guess that’s my next course of action, though. Ugh. I hate mucking with drivers. 🙂

    -Matt

  • Matt Riley

    November 28, 2007 at 9:27 pm in reply to: dropping frames ONLY when Kona is used for viewing

    I thought so too, but everything matches like I’ve been doing for months.

    My footage is 1080/24p 10 bit uncompressed. I use the Kona preset in FCP that says 1080psf 23.98 10 bit and this gives me real-time (no render) when I drop a clip into the timeline. For my playback settings under the view menu, I choose the matching Kona output 1080psf 23.98 10 bit. This is what I’ve been doing for a while now without issue.

    I get nothing but green and blue lines in the Kona control panel, so everything seems to match up there as well. It doesn’t seem to matter if I have downconverting enabled or not.

    It just feels like something is clogged between the Kona and the rest of the system. I think the big red flag here is that I can play the material fine using digital cinema desktop, so that would seem to indicate that my storage is performing adequately.

    -Matt

  • Matt Riley

    November 21, 2007 at 9:36 pm in reply to: corner pin & motion blur

    Thanks for the suggestion. I just may grab the CC HD demo and see if the data translates.

    I’m going to try posting on Imagineer’s boards, too, just to see if I have any better luck there.

    -Matt

Page 4 of 7

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