Forum Replies Created

Page 9 of 12
  • Nat Jencks

    February 23, 2014 at 4:21 am in reply to: LUT relinking

    Indeed, Indeed 🙂

    The question remains though, why does this hidden .LUT folder exist, and when does resolve place LUTs in there? The LUT in question was one that I installed by hand and certainly never moved to the .LUT folder… how do LUTs get moved in there and why? Perhaps this is where the system places LUTs when projects have been saved with the LUT check box checked, and then get imported to a new system?

    HMm..
    best-
    -Nat

  • I should have mentioned that I need SDI output, so VLC is a no go. I’ve had issues with sound drifting in Scratch, but maybe thats a non issue anymore.

    Is your experience that Scratch is more reliable for playback than resolve?

    BMD Media express seems fine, but a bit of a pain since I can’t edit reels together in it.

    Thanks folks!
    -N

  • Nat Jencks

    February 16, 2014 at 3:14 am in reply to: tangent element or mc color?

    FWIW, I have owned both the MC Color and the Elements. I had constant problems with the euphonics ethernet connection, despite repeated calls with support, physically replacing the unit, clean installs, the works. Same issues with both Resolve and Scratch. Similar issues at the one facility I freelance at the briefly had the MC Color.

    Obviously some configurations of the MC Color work well and without issue. Others don’t. This is a real issue that I have personally seen in many installs.

    Other than that my opinion is that the MC color is a great little panel, but the buttons are too small. The idea with a control surface is that you should be able to use it without looking at it. the buttons on the MC color are way too small targets to use easily without looking down, in my opinion.

    I like the elements, although like everyone else, agree that the mapping is atrocious.

    best-
    Nat

    p.s.
    get the full set of elements not piecemeal. If you can’t afford it get the wave.

  • Nat Jencks

    February 15, 2014 at 6:40 pm in reply to: Resolve V10 feature requests

    1. Add Flip / Flop to inspector in edit page. These are needed in the conform process when comparing to the offline. Clicking back and forth between the color page to do this is very cumbersome.

    YES +1

    3. New Power window features in v10 are great but are still lacking the ability to Add to one another, Subtract, Intersect etc without the use of a Key Mixer. This would be a time saver.

    5. We need fixes for the tracker not working correctly when a clip has a negative retime applied. Tracker needs to track forward when at the beginning of a clip regardless of whether or not a clip is reversed or not. Currently it needs to be tracked backwards!

    YES, this qualifies as a bug fix, not a feature request in my opinion.

    6. If the clips has a flip or a flop applied this should Not Invert the Power Window Controls on the panel. Try doing this in font of somebody and making a fool of yourself because your taking it in the opposite direction of where you were try to take it.

    YES, this qualifies as a bug fix, not a feature request in my opinion.

    8. Scroll wheel in the Edit Page should zoom the playhead not scroll the timeline up or down. No need to reinvent the wheel here. Zooming is much more useful!

    YES. In fact, match keyboard and mouse functionality to FCP 7 better. This has regressed somewhat. Command+L used to link and unlink clips, but no longer? Defintely +1 on zooming functionality. Don’t reinvent the wheel, take advantage of the immense user base who for better or worse have FCP7 keyboard shortcuts hardwired into their brains.

    9. Resolve saves the window layouts and column sorting with the session or per user.
    YES!

    13. Keyboard shortcut for Log Grading (or make this part of the paid application) not 30K panel!
    15. Make a decision, either give us custom 3rd party panel mapping, a cheaper BM panel or at the very least a really well thought out Factory mapping. Current Elements mapping is very poor, sorry but in its current state its like Chinese torture!

    Yes, for the love of god yes. I work at my own studio and also freelance at other spots. Buying a Full set of panels for every place that I work out of is not a valid option. The current situation with the panels and keyboard/ panel mapping is just insane. This is truly terrible and infuriating way way to segment the product line. If need be, charge more $ more more features, that makes perfect sense, but don’t cripple non panel users in weird ways by making the user experience horrible.

  • Nat Jencks

    February 15, 2014 at 6:31 pm in reply to: Resolve V10 feature requests

    +1 for edit page request. e.g. up down arrow should go to next shot even if track is locked. Current implementation forces me to keep all tracks unlocked at all times which nullifies the point of having locks.

    best
    -Nat

  • Nat Jencks

    February 15, 2014 at 6:24 pm in reply to: OFX plugins not very stable… Other experiences?

    Yes, performance is typically pretty poor, but thats to be expected in my opinion since these are typically fairly CPU intensive. Actually I’ve been fairly impressed with film convert’s performance when switched to GPU, I get realtime grain generation. I prefer this to Cinegrain.

    I’ve been using Sapphire a ton. Even simple effects like “transform” are useful, since I can use a transform and draw a mask around it to do basic “clone tool” paint jobs.

    Also, simple glow effects and lens flares in sapphire can be nice.

    Neat noise reduction is amazing, although honestly I’ve been using it way less now that temporal noise reduction is built it. I find neat to be marginally better, but the built in is so much more convenient that I’ve been using that more recently. Beauty Box is just ok. sometimes better than selective blurring by hand, sometimes not. But definitely worth having so you can give a shot with tricky beauty fixes.

    Best-
    -Nat

  • The real issue is just that the “sort state” is not maintained between sessions. If it just kept the current sorting (by name or other) between sessions that would be fine, the issue is that it constantly re-arranges back to the original sort order which is very frustrating.

    best-
    -Nat

  • Nat Jencks

    February 13, 2014 at 3:47 pm in reply to: Easiest way to raise and clip black levels?

    Yes indeed, curves work decently for this, but it takes a little patience to create a flat toe on the curve and ride it up and down to elevate or lower the floor…

    What I would really like is just soft clip but with more range to allow for more stylized looks (matching old vintage poor quality transfers).

    Honestly I’ll just keep using my 3 node approach w/ a soft clip to clip and pull values out of floating point.

    thanks everyone for the great suggestions.
    best-
    -Nat

  • Nat Jencks

    February 10, 2014 at 11:38 pm in reply to: Input LUT vs Output LUT vs Node LUT

    As you have discovered, it makes a huge difference if a LUT is on input or output, in other words if you are grading before the LUT of after.

    If you want more control, just use the out as a node in your node tree and either place your grades in front or behind it.

    That said, I would suggest doing a bit of research on this, and using LUTs as they were designed to be used, either as input or output LUTs.

    Typically an input LUT is designed as an input transform to move a specific type of footage into a known working space. For example to take Sony Slog and put it into a film log (cineon) working space, etc. An output LUT is typically designed to take a graded input from a known working space and transform it, targeting a specific display color space. If you disregard these factors and just throw LUTS on randomly irregardless of how they were designed, what color space they were designed to be coming from, going to, input vs output, your results will likely not be great.

    Not an instagram filter 🙂

    good luck!
    best-
    -Nat

  • Nat Jencks

    February 9, 2014 at 10:02 pm in reply to: Color Trace – Using version 1

    I have to say, the only using the “default version” (v1) screwed me up in the past, but it seems to be working as I would expect currently. Just got thrown for a loop since the manual describes the old behavior.

    Best-
    -Nat

Page 9 of 12

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