Forum Replies Created

Page 1 of 3
  • Jeremy Belzer-adams

    August 7, 2012 at 7:02 pm in reply to: Resolve 9b crashes on grab a still command

    Another option when you are in a pinch like this is to create a new project, bring in your media and timeline (xml or edl) and then just colortrace from your old project.

    I’ve had a few projects corrupt in 8.2.2 and now whenever I start a new project I save out a base conformed version. If I ever have a problem with the project I can quickly colortrace to the base version and get back to work in a very short time.

  • Jeremy Belzer-adams

    April 6, 2012 at 10:55 pm in reply to: Advice on Mac Pro build for Resolve Lite

    Thanks, again! It sounds like there may be power supply issues with using both the 8800 GT and the GTX580, do you know what people are doing to bypass that?

  • Jeremy Belzer-adams

    April 6, 2012 at 9:21 pm in reply to: Advice on Mac Pro build for Resolve Lite

    Thanks!

    The GTX 580 will work with the Mac without being flashed? Does this have to do with the new driver just released for Lion?

    If so, if I boot my machine into 10.5 or 10.6 (lots of boot drives) will the GTX 580 in slot two give me any issues?

  • Jeremy Belzer-adams

    March 7, 2012 at 8:39 pm in reply to: Frames Dropping on unrendered Text

    I’m having the same problem on 10.6.8. Have you found a solution?

  • Joseph,

    Did you ever solve this problem? I’m having something very similar happen on my mac pro. I’m on a fiber SAN, so disk speed is not the issue.

    Jeremy

  • No I hadn’t tried that as I have found exporting quicktime movies to be much more reliable. It did seem to solve the problem though, at least before compression. I’m compressing a new file right now and I’ll let you know what happens.

    Thanks for the reply!

  • Jeremy Belzer-adams

    April 22, 2010 at 7:25 pm in reply to: DSLR Organizational Headache

    We did slate with a smart slate and the synching has been super simple. I’ve found the EOS log and transfer plugin to be really slow and somewhat un-reliable. It has improperly named files and sometimes even trims files when there is no in/out point even after I’ve trashed preferences.

    The time of day timecode that it gives me isnt that helpful either because I cant jam sync the two cameras and I still need to create auxiliary timecode.

    My workflow has been to convert to ProRes with mpeg streamclip (with three edit bays this is easily batched over night). Then I’ve synched both angles on the same timeline and exported each as its own new quicktime file.

  • Jeremy Belzer-adams

    April 22, 2010 at 6:47 pm in reply to: DSLR Organizational Headache

    You’re absolutely right. I will make self-contained movies. I was trying to save time up front, but only headaches will come from it. Thanks, David.

  • Jeremy Belzer-adams

    February 18, 2010 at 11:36 pm in reply to: Ideal Compression for Transcription Window Burns

    Yep, this is what I do. I make h.264 Quicktimes, usually at about half the size of the original frame.

    I’ve found that a data rate around 400 is plenty to let them read the timecode.

    There are two ways to burn timecode, one is laying the clips into a FCP sequence and then using the TCR filter. The other is using the filter in Compressor. When using compressor I tend to change the text to white and put it in the bottom center.

  • I would also hesitate to attempt to deceive History like that if you want to continue working with them…

Page 1 of 3

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