New VFB features

[Ondra]

We will start new VFB shortly. What features do you want to see?
Obvious ones are:

• render history with comparison
• render region
• renderer sampling focus painting

what else?

[maru]

based on feature requests:

-ability to load Corona exr into vfb

some more wild ones:
-more color mapping/effects (curves, glow, glare,...)
-re-lighting in vfb (re-light/light select pass)

[nehale]

Color correction tools like HSV or curves

[romullus]

I will go with more humble requests.

• add saturation and vignetting to ColorMap tab
• make smiley to turn anti clockwise when rendering interactively, so we can more easily distinguish between these two :]

[Chakib]

Maybe an Alpha transparency preview like in VFB+ would be cool.

[racoonart]

- I'd like to have a "normalize view" button somewhere (meaning all colors will be normalized to a 0-1 range). Useful for checking specific REs and highlight distribution in the rendering.

[Edit]
- even though I nearly never use it myself: loading and applying different LUTs.

[pokoy]

Not a feature for Corona's VFB directly but I'd love to see improved support for VFB+. It would be fantastic if Corona could feed data to VFB+ in interactive mode (which seems not to be possible yet) or if VFB+ could access Corona's output in every render mode so we can use its feature set directly.

[dubcat]

White Balance color picker like in Camera Raw



Auto Focus picker like in Octane

[Ludvik Koutny]

I've got an idea. Sometimes I play with color mapping settings, like exposure, HL compression, etc... Or i temporarily need to lower or raise exposure when i go from interior to exterior or vice versa. I occasionally forget the values I settled with and have to search for them again. It would be perhaps helpful if every spinner had a small square S button glued to the left of it. When right clicking this button, current value will save, and left clicking the button will recall the stored value.

[Alessandro]

My 2 cents.

I start from this: every static render I do needs to be passet in photoshop (or similar, Adobe doesn't give me any money for this), for a lot of reasons, often just to give some more contrast or to do some curve corrections, other times to have a more drastic post production. That's the reason why we need render elements.

I think all post production requests, like curves, vignetting, saturation, ecc.., are kind of post we can easily have in post (I mean in photoshop). Also, I actually prefer to have a "raw" render ready to be edit in post than to have an already edited image. One more, very often every shoot of the same scene needs some different editing, so every setting in vfb should be camera-depending to be significant.

I think developers should be concentrated in other kind of improvement, like region render in vfb, or ability to load Corona exr into vfb, or light remapping or any other tools we can't have in post.

Peace and love to everyone,
Alessandro

[agentdark45]

1. Glow / glare / lens flares (physically based if possible). For example, we get harsh white dots in certain reflections if we use Corona sun/sky, adding some sort of lens based glow/glare would smooth these dots out and give us some usable photographic looking highlights.

2. Some sort of built in color mapping / curve adjustments with save-able presets so users can share them / replicate settings easily.

3. Not sure if this is VFB related but it would be nice to have different forms of tone mapping, like filmic tone mapping or something completely novel and personalized to Corona perhaps?

[peterguthrie]

HOW EXCITING!!!!

in order of importance for me:

1. render region (and make it better than vray from the outset by adding shift-click to add to the marquee area (like in photoshop selection) and alt-click to subtract. Rectangular selections are fine but i think more complex selections would be AWESOME and so much quicker than having to make a custom render mask like you do in vray. It wouldnt require any additional UI elements at all but would make rendering regions (for small fixes on renders) so much quicker.
2. Curves (i'd use this instead of the current contrast spinner)
3. Vignetting
4. color temp - add 'tint' like in camera raw
5. lens effects
6. filmic tonemapping as an option (adding this in as i've heard Juraj talk about it - i still dont know much about it!)
7. A Histogram would be useful

EDIT: added number 7

[steyin]

Make it so holding down the render button to select IR doesn't end with clicking the DR tab since it collapses over it. Just a little nitpick of mine.

[Siahpoosh]

i think it will be awesome if we have a  tool for make region crop directly inside vfb

[romullus]

Some simple histogram preview would be more than welcome.

[juang3d]

Maybe is too much to ask but some zebras for overexposed and underexposed could be great, also an option to superpose one render element over the beauty render to check things, and finally the obvious option to save previous renders and have the ability to compare those renders between them.

Cheers.

[88qba88]

I'd like to be able to see 360 renderings properly (something like Google StreetView or other 360 rendering viewers). + for VR camera with the ability to switch between left and right eye.

[Siahpoosh]

also it will be great if we have a difference blending mode (something like photoshop) in render comparison , so we can find which things are changed in new render.

[fellazb]

It took me a little while to understand where the "clear VFB inbetween renders" was and it was also confusing since the same option is available in the performance tab under interactive rendering.

It would be quite obvious to have this option only available in de VFB display when rendering I guess and preferably unticked by default.

[chopmeister]

It took me a little while to understand where the "clear VFB inbetween renders" was and it was also confusing since the same option is available in the performance tab under interactive rendering.

It would be quite obvious to have this option only available in de VFB display when rendering I guess and preferably unticked by default.

This! It's a hassle to search for the Clear VFB and then find the right one at that. I don't particularly care where the option for IR clearing is, but please put a checkbox or something somewhere on the VFB.

Also, +100 for filmic tonemapping as mentioned previously. :)

[Tanakov]

I already wrote this but I was asked to paste this here.

https://trello.com/b/EfPE4kPx/corona-road-map-3ds-max

Hi I have noticed some FVB improvements, I would like to suggest one more.

CoronaMap tab, Is it possible to add the "CameraExposure" buttons like those in:
Basic photographic exposure.
DOF etc. In some subtabs there? It would come up handy, especialy the BPE, as it locks the exposure during render.

@@@@@@@

Other thing is that I would like to see this:

[atelieryork]

Exciting times! ;)

I'd like to see what everyone else here is clamouring for, of course, but also:

- Clear VFB Within Region Only option - currently it seems that if you clear VFB between renders it kills the entire VFB, not just the current region.

- Mark-Up Tool - just a simple red pen tool so we can make some marks and notes

- Multiple Regions at same time

- Dynamic zoom levels

- Zoom about cursor instead of centre

- Zoom buttons (useful for tablets/remote control)

- Set Region Off (and On) Toggle

- Big one for us: A proper realtime link so even when you are using CoronaCameraMod on your camera, you can still control those settings in the VFB. Currently they all get greyed out when you do this. In other words, for the VFB to pick up all the current settings from the CCM and then pipe them back into the CCM as you change them.

If we think of more we'll edit this post.

[Noah45]

- Multiple Regions at same time.....would be a dream feature.

[peterguthrie]

Alex, Noah,

What did you think of my 'hold shift to add' region marquee suggestion?

[Noah45]

like PS, natural

[atelieryork]

Alex, Noah,

What did you think of my 'hold shift to add' region marquee suggestion?

Sounds spot-on to me, yep.

[Frood]

I thought somebody already posted that but I cannot find it so:

- Zoom in interactive VFB

Edit:

- Panning not only with Mouse3 but additionally Photoshop style (SPACE+LeftMouse)

[antanas]

Hi all, as I've begun to write down some of the most needed features I can think of, I realized that one way or another most of them are already implemented in vfb+ so instead of doing some super-superlong and hardly readable post (doing which I usually end up with) I did some ugly infographics using vfb+ as a template )) https://flic.kr/p/DaNBaa

 Well first of all I completely agree with Pokoy's Reply #6 - yes it would be awesome and most surely compatibility between corona and vfb+ should be improved and as I've seen in Juraj's thread there is some discussion with Rotem (vfb+ developer) about that already

 As for the other request, well allmost all such features are allready implemented in VFB+ so I automatically agree with those too ) + of course I agree with the need of a multiregion render as well as the renderer sampling focus painting which would be totally awesome + I think the interactive renderer deserves a separate start button

 What I can suggest for post-processing capabilities:

- remixing the render channels directly in vfb - like making reflection\refraction\volumetric pass more prominent changing their tint etc. which probably, when enabled, needs to either automatically enable all those needed channels in render setup or just be useable only when the appropriate channels are enabled manually by user and thus it needs some pointing which ones needs to be in corona's warnings dialog - possibly this feature should come with some sort of per channel masking support which could use whatever b\w or even material ID channel

- lut, adjustments\color correction masking using z-depth channel as a mask - it can be quite useable and help produce very interesting results

- fog\volumetrics mixing\adding\masking by the same z-depth channel, probably for the best effect corona should have separate sss and fog\atmospheric channels but even now it could work great

- same z-depth powered masking for bloom\glare effects could be quite useable too

- per channel noise and firefly reduction in addition to ability to do that, like the VFB+ does, for the whole beauty channel

 well I think you get the idea, and yeah those are a Photoshop's capabilities inside Corona's vfb - no less )

Still I mostly agree with Alessandro in Reply #9 or at least with the last part about development concentration on unsupported\nonexistent renderer features rather than redoing already present ones, such as replicating a post processing features already present in vfb+\Photoshop\Lightroom etc. While I think Render legion can have their own reasons to consider adding such features in corona's vfb, most important of all I think is a similar cross platform capabilities of corona's vfb on all supported software where let's say vfb+ or similar plugins are not available, still it's quite hard to imagine Photoshop being unavailable to those users ...

So that's my thoughts and probably such post processing features can be implemented another way - by doing some sort of corona specific Photoshop plugin which could do all of the above using corona's vfb's EXR dump as a transfer format, well something similar to ArionFx is but better and with more features )) 

hell, I ended up with superlongpost again ...

[pokoy]

A simple but very useful thing that could be added is gamma control. I find it to be more effective than contrast and it would not clamp hdr values (which makes contrast useless in many situations anyways).

[Tarrin]

Hi CoronaTeam!

About CFB History

- autosave shot to history after ending/canceling rendering
- ablility to choose folder for history files
- memory limit for history files
- load all history after opening new scene (it`s very usefull when you need to rerender one of the objects in the scene after few days).

These features would be helpfull and great.
----------------------------

Also about White Balance picker as in Adobe Camera Raw - it would be very cool. I`m wondering about "Corona Camera Raw" with all features from ACR (exept model of lens detection maybe) and Knoll Light Factory plugin.

[romullus]

- autosave shot to history after ending/canceling rendering
- memory limit for history files

Already there.

[Tarrin]

- autosave shot to history after ending/canceling rendering
- memory limit for history files

Already there.

thanks, i`ve found it. Not habitually after vray=)))

[James Vella]

- Big one for us: A proper realtime link so even when you are using CoronaCameraMod on your camera, you can still control those settings in the VFB. Currently they all get greyed out when you do this. In other words, for the VFB to pick up all the current settings from the CCM and then pipe them back into the CCM as you change them.

If we think of more we'll edit this post.

Not sure how this works in 1.4 but in 1.3 - press 8, turn off exposure control. This should allow you to control in vfb again

[alexyork]

- Big one for us: A proper realtime link so even when you are using CoronaCameraMod on your camera, you can still control those settings in the VFB. Currently they all get greyed out when you do this. In other words, for the VFB to pick up all the current settings from the CCM and then pipe them back into the CCM as you change them.

If we think of more we'll edit this post.

Not sure how this works in 1.4 but in 1.3 - press 8, turn off exposure control. This should allow you to control in vfb again

I don't think this works when using a CoronaCameraMod when you are overriding exposure, which we need. But thanks for the suggestion.

[James Vella]

Unless im misunderstanding what u said wrote. I use the physical cam and mod for different  scenarios. By disabling the exposure control in max this enables u to use the one in the corona vfb instead. Its one or the other as far as i understand. Why would you need both?

[alexyork]

Unless im misunderstanding what u said wrote. I use the physical cam and mod for different  scenarios. By disabling the exposure control in max this enables u to use the one in the corona vfb instead. Its one or the other as far as i understand. Why would you need both?

What we are doing is simply using a CoronaCameraMod with exposure and tone mapping overrides on. What this does is instantly disable the CoronaVFB's own exposure and tone mapping controls (since it's taking those values from the CamMod). What we want is a dynamic link between the VFB and the CamMod so the VFB takes the values from the CamMod and then you can still tweak them in the VFB, with the new values then updating in the CamMod when you finish/cancel the render. In this way you can still tweak these values with a live render going on, which is hugely helpful. Currently we're kind of forced to use the IR to handle this, but it's not an ideal situation. Hope that makes sense.

[Juraj]

Unless im misunderstanding what u said wrote. I use the physical cam and mod for different  scenarios. By disabling the exposure control in max this enables u to use the one in the corona vfb instead. Its one or the other as far as i understand. Why would you need both?

What we are doing is simply using a CoronaCameraMod with exposure and tone mapping overrides on. What this does is instantly disable the CoronaVFB's own exposure and tone mapping controls (since it's taking those values from the CamMod). What we want is a dynamic link between the VFB and the CamMod so the VFB takes the values from the CamMod and then you can still tweak them in the VFB, with the new values then updating in the CamMod when you finish/cancel the render. In this way you can still tweak these values with a live render going on, which is hugely helpful. Currently we're kind of forced to use the IR to handle this, but it's not an ideal situation. Hope that makes sense.

I think we had this discussion about a year ago, I did suggest your solution :- ). I think it was technically impossible or something. To be honest though, I don't think Vray succeeded in doing this either or did ? I know Vlado contemplated live-link as well.

[alexyork]

Unless im misunderstanding what u said wrote. I use the physical cam and mod for different  scenarios. By disabling the exposure control in max this enables u to use the one in the corona vfb instead. Its one or the other as far as i understand. Why would you need both?

What we are doing is simply using a CoronaCameraMod with exposure and tone mapping overrides on. What this does is instantly disable the CoronaVFB's own exposure and tone mapping controls (since it's taking those values from the CamMod). What we want is a dynamic link between the VFB and the CamMod so the VFB takes the values from the CamMod and then you can still tweak them in the VFB, with the new values then updating in the CamMod when you finish/cancel the render. In this way you can still tweak these values with a live render going on, which is hugely helpful. Currently we're kind of forced to use the IR to handle this, but it's not an ideal situation. Hope that makes sense.

I think we had this discussion about a year ago, I did suggest your solution :- ). I think it was technically impossible or something. To be honest though, I don't think Vray succeeded in doing this either or did ? I know Vlado contemplated live-link as well.

Yeh we did I think :) I have no idea if it is possible. What I could imagine might work is if when you hit render, Corona shifts all the values from the CamerMod into the VFB and "disengages" them from the CameraMod for the render, allowing you to tweak them in the VFB. At the end/cancel of the render it could then pipe them all back into the CameraMod if they have changed and disable them again in the VFB.

[Javadevil]

Glow and Glare is my main wish.

[Christa Noel]

Glow and Glare is my main wish.

I'm not good in doing post production in 3rd party software and i hate whenever I realize that I need bloom/glare so much.
that's why I've been waiting for this integrated to corona VFB for so long long time :P

[Ondra]

give it two weeks ;)

[Christa Noel]

give it two weeks ;)

hooray! my daddy bought me an ice cream!! :D

[Noah45]

Using VFB+, an on/off checkbox is very helpful for preview/review purposes

[lmikkelb]

Hey, this is just a sugastion on the features of the post tab. Im not sure if all of them whould work:), but but the main feature of this
example is a on off switch for the post effects. Then you would not have to reset every setting manually :D

[PROH]

Another feature that World be a tremendous timesaver is direct acces to IR start (stop is the same as normal render). I'm using IR almost always, but there are so many situations where Max is freezing or getting redicously slow with IR activated + plus all those situations where you need to "restart" calculation, or where IR restarts by every tiny parameter change. Therefore I'm constantly turning IR on and off, and finding the roll down button very slow and irritating.

For every 1 time I use the normal Render button, I easily use the "start IR" 50 times. So why shall the most used button be the hardest one to reach?

[alexyork]

Another feature that World be a tremendous timesaver is direct acces to IR start (stop is the same as normal render). I'm using IR almost always, but there are so many situations where Max is freezing or getting redicously slow with IR activated + plus all those situations where you need to "restart" calculation, or where IR restarts by every tiny parameter change. Therefore I'm constantly turning IR on and off, and finding the roll down button very slow and irritating.

For every 1 time I use the normal Render button, I easily use the "start IR" 50 times. So why shall the most used button be the hardest one to reach?

Personally I would like IR controls in the actual viewport. E.g. start, stop, force refresh etc. maybe "freeze" which just holds the current pass until you resume... and most importantly a region and blow up button. Just some ideas.

But FYI for now you can always add the IR button to a toolbar, for 1-click (well.. 2 clicks).

[romullus]

Or assign keyboard shortcut to it and another shortcut to stop rendering. That way you'll be able to start and stop IR in VFB at lighting speed :] Unfortunately to start IR in viewport, additional mouse click is needed, but that's entirely Autodesk's fault AFAIK.

[PROH]

Yes, I too would like access to control of IR in a viewport. The cumbersome way it works now is actually the only reason I'm not using IR in a viewport. A simple double click in the viewport to (re)start and stop (freeze) would do it without any buttons.

And yes, I know there are ways to make this myself, but I can't see the logic in Corona wanting to be "user friendly" and "easy", yet lacking direct access to the most used controls (for me at least).

Hope this will be looked at in nearest future :)

[Ludvik Koutny]

Start stop make sense, although force refresh should not be there. If there is anything at all that doesn't refresh unless you restart IR, then that's simply a bug that should be reported and fixed. The entire point of comfortable and fluid IR experience is never having to restart IR when working... ever... :) That's one thing that differs Corona IR from something like V-Ray RT.

[PROH]

Sure, that would be the ideal situation - but I don't think that'll ever happen 100%. Using displacement just for one, will need recalculation whenever you zoom out or change the view angle. And then there are all those things that depends on Max, and can't be changed by Corona-team.

No reason not to have direct access to start & stop (freeze) even if they are going to be used less than now :)

[Marciortiz]

Focus picker like Octane has would be absolutely amazing

[Ludvik Koutny]

Sure, that would be the ideal situation - but I don't think that'll ever happen 100%. Using displacement just for one, will need recalculation whenever you zoom out or change the view angle. And then there are all those things that depends on Max, and can't be changed by Corona-team.

No reason not to have direct access to start & stop (freeze) even if they are going to be used less than now :)

That was discussed already long time ago. Conclusion was that there should be a button to refresh displacement. But just displacement, that's it. It would not be restart render button, just recalc displacement ;) Everything else should in ideal case update in realtime.

[PROH]

Yes I know it was discussed, but I don't agree with the conclusion.

In one of the daily builds the VFB drop down was staying at the last used option. That would do it for IR in VFB, but unfortunately it was changed back. Could this behavior be optional?

[johan belmans]

Hi Ondra,

can we have the option to save and load all the values of the items in the the post production Tab of the VFB?
For example into an xml file.
This would be extremely helpful, so I can save an xml file for each camera in my scene.

[Ondra]

definitely will be added at some point, can you create a feature request for it?

[johan belmans]

definitely will be added at some point, can you create a feature request for it?

done

https://forum.corona-renderer.com/index.php/topic,13033.0.html

[burnin]

an inspiration...
V-Ray VFB redesign (proof of concept)

ps
i don't know if it has been posted somewhere already, so please forgive my ignorance

[alexyork]

The weird blue UI is the worst thing about PDPlayer, so it's very weird that they've essentially copied it. Other than that, looks cool.

[scionik]

Please. Add the camera name to the VFB window. It could be helpful with batch rendering or animation sequence. Thanks

[pokoy]

Please. Add the camera name to the VFB window. It could be helpful with batch rendering or animation sequence. Thanks

QFA, always wondered why it doesn't display camera name or view type.

[alexyork]

Please. Add the camera name to the VFB window. It could be helpful with batch rendering or animation sequence. Thanks

QFA, always wondered why it doesn't display camera name or view type.

As long as it is somehow cleanly indicated which is which when you're rendering from multiple cameras in the same VFB e.g. via history. Could be confusing if you rendered cam01, load it into history A, then render cam02, load it into history B but the VFB reports that it's cam02. The name would somehow need to dynamically change depending on the history, I guess. Not that straightforward.

A simpler approach, although not ideal, would be to have it say "Last render from camXYZ" so at least you know that much.

[romullus]

As long as it is somehow cleanly indicated which is which when you're rendering from multiple cameras in the same VFB e.g. via history. Could be confusing if you rendered cam01, load it into history A, then render cam02, load it into history B but the VFB reports that it's cam02. The name would somehow need to dynamically change depending on the history, I guess. Not that straightforward.

A simpler approach, although not ideal, would be to have it say "Last render from camXYZ" so at least you know that much.

I don't think it has to be that complicated. It should simply display view to render info. Same as available in render settings. Dropdown menu to choose view, together with lock, wouldn't hurt either, although it could be hard to fit into already crowded VFB UI.

[JCdeBlok]

Haven't installed the new version yet, hard at work to meet a few deadlines..

But I did saw the the 1.6 video and it showed a feature where zooming in to the VFB all of the CPU powered got focused on just the visible area..

I usually zoom in during a render to check on noise levels and how details are emerging to get a feel for the amount of required passes and such. And right now I'm doing hires stereo renders (10k+) and I set the vfb to a 1:1 zoom to get a feel for the noise without zoom.  The new 'only focus on visible part of VFB' feature is a bit dangerous I think, is there a toggle to turn this on/off or is it only doing that during interactive mode?

[alexyork]

Haven't installed the new version yet, hard at work to meet a few deadlines..

But I did saw the the 1.6 video and it showed a feature where zooming in to the VFB all of the CPU powered got focused on just the visible area..

I usually zoom in during a render to check on noise levels and how details are emerging to get a feel for the amount of required passes and such. And right now I'm doing hires stereo renders (10k+) and I set the vfb to a 1:1 zoom to get a feel for the noise without zoom.  The new 'only focus on visible part of VFB' feature is a bit dangerous I think, is there a toggle to turn this on/off or is it only doing that during interactive mode?

Same concern here. Imagine how easy it would be to zoom in and forget to zoom back out again when you run for lunch, only to find you have 1000 passes completed on a vase and the rest of the image is still at 2 passes. Hope it's togglable!

[sevecek]

Haven't installed the new version yet, hard at work to meet a few deadlines..

But I did saw the the 1.6 video and it showed a feature where zooming in to the VFB all of the CPU powered got focused on just the visible area..

I usually zoom in during a render to check on noise levels and how details are emerging to get a feel for the amount of required passes and such. And right now I'm doing hires stereo renders (10k+) and I set the vfb to a 1:1 zoom to get a feel for the noise without zoom.  The new 'only focus on visible part of VFB' feature is a bit dangerous I think, is there a toggle to turn this on/off or is it only doing that during interactive mode?

Hi, this zoom feature is only for interactive rendering.

[cecofuli]

I don't know, but I never used IR for final rendering...
The VFB zoom is only inside IR and, believe me, it's really cool =)

[thilima3d]

Hey Guys, I would like to share some ideas to Corona Render VFB, I hope you like it (improve it please).

#1 VFB POST Settings for currrent camera (without need CameraMod)



The idea is to have a button on VFB [ CURRENT CAMERA ONLY] which when activated makes the VFB post settings to be applied just for that camera, Like CoronaCamMod does. So, why not continue using Corona Camera mod? 3 reasons:

• Work directly on vfb settings are faster than select camera, go to mod, make changes, select another camera, do changes, get back to vfb, etc etc.
• Every change on CoronaCameraMod restarts the IR, which is annoying as the same functionality on VFB doesn´t
• You cannot make changes on Final render (Not using IR) Exposure / Highlight Compress on the fly if you´re using corona Camera Mod.

On the right side of the image above I also included a load button, which could be used to load another CamerasOnly VFB settings, that you could load from a list of scene cameras (I don´t know if it would be necessary as we have the save/load overrall vfb seput on the top of the window, probably not.)


#2 Focus Picker (Like Octane Render)



Extremely handy!!!

#3 White Balance Picker (Like Octane Render)




Please let me know what you think about it. :)

[Bormax]

Would be nice to have       Render selected -> Disabled
                                                                   Include/exclude list
                                                                   Viewport selection
                                                                   Object GBuffer ID       switcher on VFB's frame and in the top right corner menu of docked IR window

It would be useful to have this switcher wile working with IR on some objects of the scene without the need to have Render dialog opened

[ihabkal]

Hey Guys, I would like to share some ideas to Corona Render VFB, I hope you like it (improve it please).

#1 VFB POST Settings for currrent camera (without need CameraMod)



The idea is to have a button on VFB [ CURRENT CAMERA ONLY] which when activated makes the VFB post settings to be applied just for that camera, Like CoronaCamMod does. So, why not continue using Corona Camera mod? 3 reasons:

• Work directly on vfb settings are faster than select camera, go to mod, make changes, select another camera, do changes, get back to vfb, etc etc.
• Every change on CoronaCameraMod restarts the IR, which is annoying as the same functionality on VFB doesn´t
• You cannot make changes on Final render (Not using IR) Exposure / Highlight Compress on the fly if you´re using corona Camera Mod.

On the right side of the image above I also included a load button, which could be used to load another CamerasOnly VFB settings, that you could load from a list of scene cameras (I don´t know if it would be necessary as we have the save/load overrall vfb seput on the top of the window, probably not.)


#2 Focus Picker (Like Octane Render)



Extremely handy!!!

#3 White Balance Picker (Like Octane Render)




Please let me know what you think about it. :)

+1 to all this

[Yarek]

Sharpening tool/blurring tool based on Z-depth from render elements.

I already submitted this idea via e-mail but maybe I will write more about it.

1.
Typically, I use Z-depth in Photoshop to mask the sharpened image so that only the front is sharp.. but it would be great if corona could automatically take the z-depth from elements and use it in VFB for sharpening and blurring.
For animations, such automatic sharpening tool based on maps would speed up the whole process.

2. In some cases, I would like to exclude some objects or some materials from sharpening. For example in some resolutions grass gets messed up after sharpening. Also some straight lines become jagged and you can see the steps when they are sharpened.

So I would like to be able to have a sharpening tool that ignores objects based on selection or based on material. (Just like the rerender function).

Hope you like the ideas and find it useful. Cheers.

[Bormax]

I think would be good to have the button with the name something like "Bake current VFB setting to the selected camera". Pressing this button you create CoronaCamera modifier with current settings from the VFB and ticked Overrides. With this it's possible to play with VFB tools after render has been stopped, or with image from the History and apply this settings to the camera. To make the work with cameras with ticked overrides in their CoronaCameraMods more comfortable would be good also to have button or maybe checkbox "Ignore CoronaCameraMod's overrides" which give you possibility to change settings in VFB tools and bake the new ones by pressing "Bake current VFB setting to the selected camera" button with no need to start IR and change settings inside CoronaCameraMod