VFB2 further improvements - your help needed!

[matanov]

1 - Better Color Correction layers (the closer to Camera Raw the better)
2 - Ability to export the CCs to a LUT (like in Next)
3 - Adding the frame number to the history (requested months ago, no change still)
4 - Old behaviour back of splitting the CCs from the Lens Effects and the Denoiser (requested also by several people)

1 - We could add some extras but it will be very useful to know which corrections there you use/need the most.
2 - Already done, you'll see it in Update 1
3 - In the to-do list, with a little luck it will be ready for Update 1
4 - Please check this thread - https://forums.chaosgroup.com/forum/...render-element

[matanov]

I think making capabilities similar to Photoshop's Camera Raw Filter is a great place to start. We tend to use that the most because of the amount of tools in there.

But specifically:

1. One of our main reasons we bring out images in photoshop is to manually desaturate, brighten, and darken individual items. Being able to mask out and set individual adjustment layers like in photoshop would be super helpful.
2. Also use photoshop for different sharpen effects. Having some sort of sharpen/ blur/ soften built into the frame buffer would allow us to skip that step.
3. Filmic Tonemap - Its clear there is a lot of power here but I find some of the settings to be confusing to understand what each does. If there is a way to make it clear what each setting does, something like the camera raw filter in photoshop as someone has mentioned, it will go a long way.
4. Add a histogram (Provides useful info)
5. Add ability to add vignetting in the frame buffer instead of camera would help alot as well. It may not be physically accurate but sure gives extra freedom
6. Add a custom color option to White Balance - similar to how using a custom color in the white balance feature for the vray physical camera
7. Lightmix temperature - Add option to set the temperature of the lights instead of only by color
8. Lightmix changing color by absolute or relative values - As of right now if you have a warm light rendered and wan't to change it to be cooler, you have to add blue in the light mix. I think this is not very intuitive in every situation. Having the ability to set a lights color based on an absolute value as opposed to adding a relative value to get the right result would make it easier.
9. Adjusting individual colors across the image would be helpful as well (etc. adjusting all green values to be more cyan or yellow, see camera raw filter)
10. Maybe adding a film grain filter and post effect chromatic aberration. Not as critical.

I can send a "typical" photoshop file that we have done here if you think that will be helpful to see.

Let me know!

1. Masking is coming in Update 1.
2. In the to-do list, will come eventually.
3. For closer tweaks to Camera Raw filter we need to know your most desired options from there.
4. We already have histogram in the Curves layer. We can "get it out" somewhere to be visible all the time?
5. Could be done if there are enough requests
6. Like 5
7. Already done, you'll see it in Update 1
8. The problem here is there a lot of scenarios where they will be more than 1 light per LightMix entry and this is why it has to be a multiplier.
9. We'll check it out
10. Someday
11. Just use the "to Composite" button in LightMix and you'll have the freedom adjust layer by layer
12. Can't you use the Curves layer instead? Levels is kind of a simplified Curves layer.

[Moriah]

1 - We could add some extras but it will be very useful to know which corrections there you use/need the most.

Yes sure. So from Camera Raw i would like:
- HSL with tone sliders
- Color Grading Wheels
- Sharpening / Blur
- Post Vignetting
- Grain Presets (Kodak, Digital, etc)

Also another small request regarding Lightmix, ability to click a light inside lightmix and select that light in the viewport (even better if we could do with several lights). Also possibility to organize lights into groups/folders inside the Lightmix.

[matanov]

1. Additional render info stored in History(vrimg), like sampler min/max/threshold , can just be exr metadata loadable with right click as it is now.
2. VFB settings menu, with configurable defaults for VFB. For example default color profile( sRGB, ACES, LUT), defaults what panels are visible, like history or color corrections, or just plain image.
3, Configurable shortcuts aka shortcut editor, for all available VFB commands. Some people like doing exposure up/down with F keys, some with +- etc, let us choose.
4. Fullscreen view mode with/without panels. For example nice to compare AB render in full screen mode, no control panels, just swap the images with keyboard shortcut.
5. Alpha background style. Black or checkboard.

1. When we get the image info back, we can add those as well.
2. Could be done but it will take some time until we get there.
3. Same as 2
4. This was planned for the initial launch but there were some issues and we left it until cleared
5. Could be done for sure

[vmulhem]

Hi,

The new VFB is a great step improvement.
We would generally use VFB to do initial post and look dev.
We then use Fusion for our final post production and repeatability.

So what would be amazing is either:

-a way to export the adjustments from VFB to other compositing software e.g. Nuke, Fusion, AE. As a minimum LUT but it would be better if we could translate as nodes in the compositing app for further adjustments.
-or if someone from Chaos could post the code for the main adjustments - curves, filmic tonemappers, etc so that we could perhaps write our own importer and tools in Fusion.

Thanks

[M.Max]

Almost all my wishes are already mentioned, so I will just vote for them to help rising the priority : ))
1- Sharpening / Blur
2- Post Vignetting
3-Absolute or override mode for the light mixer so we can ignore the current colors and add our own colors. I know this one would be tricky with textured lights but I can live with supporting solid colored lights only .
4-Access for VFB shortcuts. some of them are really annoying like Shift+Q that will make a comparison instead of rendering even with "Keyboard shortcut override" is off.
5-custom white balance color and (inverse) color picker option would be great.

[Jiri.Matys]

Sharpening and Camera Raw in PS. Sometimes for saturate/brightness/hue but only for some colors in Camera Raw. Works great. And sometime just cloning repairing some parts. And sometimes add vignette in post.

[Crayox13]

To me it's just camera raw abilities, especially "clarity" like function.

[fixeighted]

Possibility to add light materials to the Light Mix?

[DanSHP]

It's really simple actually.

Give me PS in VFB.

[matanov]

It's really simple actually.

Give me PS in VFB.

We are very far from the idea of fully replacing professional post processing softwares. This is why I'm asking for most used functions, so we can only implement the essentials.

[Joelaff]

Bring back Frame Stamps.

We don't use VFB for much more than previews and LightMix, and the occasional Lens Effects (saved to separate channel). So for us it is the little productivity things rather than duplication of compositing software, which we do in, well... compositing software.

Frame Stamps would be very helpful indeed. We need to burn in the render node name, scenename, render time, peak memory usage, etc.

I'd love to have the BG image support image sequences so that the BG image is updated depending on what frame is rendered.

It would be great if the saved images in the history saved entire presets for the renderer, and we could then re-load the settings from a previous render. In a perfect world we would be presented with a dialog where we could choose to load specific settings. For instance, we could load the Light Cache settings from a previous render without changing the Sample settings, etc.

Perhaps the history could also save the light settings as a way of sort of reverting LightMix changes. In a perfect world we could load the settings for each light independently to, for instance, revert Light3 alone.

[DanSHP]

We are very far from the idea of fully replacing professional post processing softwares. This is why I'm asking for most used functions, so we can only implement the essentials.

I was joking :P

Sharpening is a must. HSL sliders from CR PS too.

[matanov]

I was joking :P

Sharpening is a must. HSL sliders from CR PS too.

I know that you are joking but there might people reading this thread that should know our general intentions

[matanov]

Bring back Frame Stamps.

We don't use VFB for much more than previews and LightMix, and the occasional Lens Effects (saved to separate channel). So for us it is the little productivity things rather than duplication of compositing software, which we do in, well... compositing software.

Frame Stamps would be very helpful indeed. We need to burn in the render node name, scenename, render time, peak memory usage, etc.

I'd love to have the BG image support image sequences so that the BG image is updated depending on what frame is rendered.

It would be great if the saved images in the history saved entire presets for the renderer, and we could then re-load the settings from a previous render. In a perfect world we would be presented with a dialog where we could choose to load specific settings. For instance, we could load the Light Cache settings from a previous render without changing the Sample settings, etc.

Perhaps the history could also save the light settings as a way of sort of reverting LightMix changes. In a perfect world we could load the settings for each light independently to, for instance, revert Light3 alone.

Frame Stamps are coming.

"Load V-Ray settings" and "Compare V-Ray settings" are already in the builds and should work as before (right click on an image from History). Partial loading of particular settings might be a little too much