Jump to content

Search the Community

Showing results for tags 'resolution'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Mistika Boutique
    • Releases
    • Tutorials
  • Mistika VR
    • Releases
    • Tutorials
    • Webinars
    • Rig Presets
  • Mistika Workflows
    • Releases
    • Tutorials
    • Python Scripting
    • Bugs & Feature Requests
    • Templates
  • Mistika Review
    • Open Beta
    • Tutorials
  • Mamba FX
  • Open Forums
    • News
    • Demo Reels
    • Jobs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 1 result

  1. Hi, It'd be pretty interesting to include a simple node that modifies the resolution on the metadata thru the stream so we can setup "proxy" levels. This way, it would make visually easier, for the workflows operator, to identify/build structures on the graph in cases like the following: The graph above shows the following scenario: If we wanted to use workflows a a system to receive renders from a department, and create all the proper full/low-res exr/movs versions for the studio to use,, at the moment, the output resolution has to be set in each of the "output" nodes, which makes the graph difficult/slow/obscure to read & modify. In case we had a longer graph built, where we include burnings to the low res, but not the thumb nor the full, and metadata injection only to the full, etc etc... having this proxy nodes at the beginning of each branch would help in clarity, ease of reading and debug of the graph. This is a pretty simplistic example, but f think it show clearly the potential of this mini nodes and their modification of the metedata. Cheers. Miguel
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.