Forum Replies Created

Page 8 of 13
  • Chris Hall

    September 9, 2011 at 3:39 pm in reply to: Black Border around R3D renders

    Yeah I’ve had the same issue with the .r3d’s and the black border. I always add an output scale of 1.002 on zoom to correct for the problem… but shouldn’t need to do that. Its a bug.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    September 8, 2011 at 4:08 pm in reply to: 1080p Project/Session, 2K Output – RED MX feature

    In response to your original question Toby, yeah working at 1080 is great for your output monitors, and then swtiching back to 2K for final deliverable output works just fine (all power windows and resizing are adjusted automatically). I’ve done this on a couple of features and have had perfect results.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    September 8, 2011 at 4:03 pm in reply to: Render cache

    Here here on the render cache function upgrades. Especially useful for noise reduction renders on Red RAW material (even with a rocket card these take forever to cache, and bog down my entire timeline).

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    August 31, 2011 at 3:36 pm in reply to: Maintaining differing scales from FCP sequence

    Alas, I’ve run into this issue on a bunch of projects and haven’t found a great answer to mixed resolution round-tripping. I always default to doing all frame resizing in resolve now and wiping the scaling information in fcp on the return trip (unless of course the key-framing is too impossible to duplicate in resolve and then I’ll hand export those clips back). This is definitely a feature request for future versions of resolve(to do resolution independent source rendering of clips out of resolve).

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    August 18, 2011 at 3:54 pm in reply to: FCP7 xml round trip

    Resolve only supports rendering to a standard single resolution for a project as well, so if you have multiple formats that were resized and repositioned in fcp, they will come back from resolve with different resolutions (based on your project configuration in Resolve, ie 1080p, 2k, whatever) and you will have to redo your repos in fcp. If everything in your project is the same resolution (like all 2K red material), then your resizing will be fine in fcp. I recently had a project with tons of different formats and resolutions that when brought into resolve defaulted everything to 1080p upon render; when brought back to fcp all the resizes and repos on anything not 1080 were all over the place (2K film scans were off, and lower rez standard def stuff was way off now). So its not a perfect “roundtrip workflow” you have to take care of resizes before and bake them in (in fcp), or do everything in resolve and wipe the resizes in fcp afterwards.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • couldn’t agree more on the “remembering” the cache rendering suggestion by Jake. This would be a huge benefit, as any additional editorial changes will clear the cache as well, having to start the whole rendering process all over again. Would love to open a project and see all those nice green bars waiting me from the previous day’s work.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    August 12, 2011 at 3:04 pm in reply to: Fields

    Sascha, have you tried outputting via the Decklink card to another source (such as a deck or another computer with a decklink installed) and recording that instead of rendering the output file in resolve. For all standard def stuff (including DV conversions) I’ve used this trick and it works perfectly for standard def field problems in resolve every time. Every time I render interlaced standard def in resolve I’ve gotten similar issues that you’ve been discussing in both PAL and NTSC, but the output via the decklink has always been perfect.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    July 28, 2011 at 8:59 pm in reply to: Desk for colorgrading

    Check out Edit 5 Consoles in Burbank, CA. They’re fairly cheap for the build quality and design. I have the large multi-level desk with two of their R13 rack mount units on either side. Takes up a lot of room but looks/works great.

    https://www.edit5consoles.com/products_e51.html

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    July 20, 2011 at 9:39 pm in reply to: A Couple of Cubix Questions – Looking to Upgrade

    Robbie, thanks for sharing regarding your experience with the red rocket in the Cubix 2. That’s exactley what I was worried about. I’m definately feeling like the 4 double wide option is worth the extra $500 at this point. Thinking 2 x GTX 285’s is probably the best bang for the buck here being that I already own one. I’m assuming (after a little bit more digging around in old threads) that the 480 would default to the same number of GPU’s as the 285 if installed with one (as in DaVinci will only recognize the lesser number of GPU cores on a card if two different cuda cards are installed for processing). Anyone know if this is correct, or am I making it up?

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

  • Chris Hall

    July 20, 2011 at 3:49 pm in reply to: Creating a LUT for HDLink

    I use a lut in my Decklink box created by DaVinci to balance my client monitor (a 50″ Panny Plasma) a bit closer to my Flanders Scientific 2461 LCD. Its not exact but it sure is pretty darn close and only really scrupulous DP’s can tell the difference (producers and directors think they look the same). So yes it works and it really isn’t hard at all, use Dwaine’s link to the other thread for directions.

    Chris Hall
    Colorist – Basher Films
    Pasadena, CA

Page 8 of 13

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