Closed fPaglia closed 10 years ago
Great suggestions!
The only thing I'd comment on there is that hitting G should drop a Grade node, and there should be some other key for ColorCorrect node.
Great suggestions. Will see if we can do all this for the v1: that's a lot of work;)
thank you guys! :) As said by Hyperfx G should be for grade (that's also way better than ColorCorrection node for most of the tasks)
2014-07-07 23:55 GMT+02:00 Alexandre Gauthier notifications@github.com:
Great suggestions. Will see if we can do all this for the v1: that's a lot of work;)
— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/93#issuecomment-48246508.
Francesco Paglia Vfx and Production Supervisor
mobile +39 347.82.12.473 e-mail f.paglia.80@gmail.com
I would set L for RGBLut. As i heavily use curves.
Also for viewport (if a mouse if its area) 1 - 100% 2 - 200% Ctrl+1 - fit to viewport as Gimp and Krita have it.
to fit viewport there's already F used by many tools (blender too use it) I like a lot 1 for 100% 2 for 200... we should consider also the opposit I propose ALT+2 50% ALT + 3 33% and so on..
@fPaglia no problem :) but i would move Fit to Alt/Ctrl+1. We can use F for other cool tools.
Ahh. I take my words back. F is realy ok for fitting. As it fits nodes too.
It would also be great to have a keyboard shortcut for Muting a node. Disabling it without having to unhook it from the node tree.
Yes it would be definitely needed!
2014-07-08 0:55 GMT+02:00 hyperfx notifications@github.com:
It would also be great to have a keyboard shortcut for Muting a node. Disabling it without having to unhook it from the node tree.
— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/93#issuecomment-48252078.
Francesco Paglia Vfx and Production Supervisor
mobile +39 347.82.12.473 e-mail f.paglia.80@gmail.com
I recommend using the other color correction nodes, since RGBLut can get quite slow (the transfer function for each floating-point sample has to be computed separately). I optimized it a bit by taking 1000 samples on the 0.0-1.0 color range and interpolating between them, but superblacks and superwhites are extra-slow, and everything else is much slower that a simple Grade or ColorCorrect node.
fred
Le 8 juil. 2014 à 00:01, mifth notifications@github.com a écrit :
I would set L for RGBLut. As i heavily use curves.
— Reply to this email directly or view it on GitHub.
And what do you recommend instead RGBLUT? I use Curves heavily. Is there Curves in other plugins which are optimized (commercial for example)?
I also would like to suggest such shortcuts: Ctrl+Q - exit Ctrl+N - new project Ctrl+O - open a project Ctrl+A - select all (nodes, curve points) Ctrl+D - deselect all (nodes, curve points)
Exit didn't have its shortcut set correctly. It's fixed, but there is a bug in Exit: it would only close the current project. That other bug will eventually be fixed.
I added a "Close Project" menu entry (shortcut should be ^W)
see https://github.com/MrKepzie/Natron/commit/aa5dbb0cbb888fedcba8ce3851815cd5d7019261 for details
Le 13 juil. 2014 à 17:51, mifth notifications@github.com a écrit :
I also would like to suggest such shortcuts: Ctrl+Q - exit Ctrl+N - new project Ctrl+O - open a project Ctrl+A - select all (nodes, curve points) Ctrl+D - deselect all (nodes, curve points)
— Reply to this email directly or view it on GitHub.
@devernay Thank you!
I just did a major clean-up of the Nodegraph and it can now supports multiple selection (and edition) via a usual selection rectangle. Regarding selection of nodes what do you suggest, that I make the click tolerance to , for instance 10 pixel around the bounding box of the node ?
Also could you describe in depth the issue with "Rendering out an WriteOCIIO completelly freezes the computer... as render starts everything seems going smooth but after a bit of time the computer seems going to crash but in fact this is not, render still goes ok but PC becomes completely unusable until it ends" please ?
Hi Alex, In fact latest statement seems mine from an old post. Latest version of natron render out smoothly
2014-07-24 16:50 GMT+02:00 Alexandre Gauthier notifications@github.com:
Also could you describe in depth the issue with "Rendering out an WriteOCIIO completelly freezes the computer... as render starts everything seems going smooth but after a bit of time the computer seems going to crash but in fact this is not, render still goes ok but PC becomes completely unusable until it ends" please ?
— Reply to this email directly or view it on GitHub https://github.com/MrKepzie/Natron/issues/93#issuecomment-50028458.
Francesco Paglia Vfx and Production Supervisor
mobile +39 347.82.12.473 e-mail f.paglia.80@gmail.com
From that list here's whats implemented so far:
I added the rearrangement for the nodes. This has been tested for easy graphs and might contain bugs for more complex graphs, I'll let you guys give feedback during the next build
It's all been implemented
Hi perhaps you already thought to many of the next suggestions but let me add them here so people can participate in the discussion. I'd like to report some annoying issue from an user point of view:
A reroute would be much appreciated to clean up the graph
there's no border selection, no way to select more than one node per time
It would be awesome if we could select ascending or descending branches starting from a selected node
Hitting tab once you start typing the wanted node the field shows the complete name but it is not possible to navigate with arrows one node up or down from the selected... it always shows the first node of the list, if would be much appreciated a focus on the list's element
Dual monitor setup (like mine) sees the TAB node list always on the same monitor it doesn't follow the cursor nor the interface, it just stays on the main monitor...
Once a node (or group of nodes) is copied in the buffer it would be incredibly better if we could be able to paste it where the mouse pointer is in the node graph editor
parameter icons aren't all of the same size and the bigger seems one seems just to big... I'd recommend to set the proportion of any icon/button to the size of the "set keyframe button"
Color represented in the color picker (in the color wheel panel) looks like it's represented in linear color space since it never looks like the color on the viewer (try with a constant node and set a saturated, 0.7 in light, color you'll notice the difference)
That's all for me... if anyone wants to add is voice it's very welcome :)