OK, I just found the solution!
Winaero Tweaker:
http://winaero.com/download.php?view.1796
(Click the link that says, “Download Winaero Tweaker”, right above the Donate
button section.)
Here’s morte info with screenshots:
http://winaero.com/blog/winaero-tweaker-faq/
It works without an installat
I found that as well, but it brings the window to the FG which isn't something
you always want to do.. I would prefer it worked like OS X and X/11. I think
you can hack the registry to make it work like that but I tried it and it
didn't work for me.
I'm not sure why it works for Alpha but not t
Thanks alot Rich, will keep this for future reference :)
Am 29.04.2015 um 16:06 schrieb Rich Bobo:
> Just did a search and found the Windows 7 solution on Stack Overflow...
>
> Control Panel->Ease of Access->Change How Your Mouse Works->Activate a window
> by hovering over it with the mouse
>
Just did a search and found the Windows 7 solution on Stack Overflow...
Control Panel->Ease of Access->Change How Your Mouse Works->Activate a window
by hovering over it with the mouse
Ahhh… So much better!! 8^)
Rich
Rich Bobo
Senior VFX Compositor
Armstrong White
Email: rich.b...@armstro
This behaviour seems completely normal to me.
My guess is that to have this work the way you wish (which is also the
way I use it), you hace to configure your system, wether linux or
windows, to have the focus follow the mouse...
That's how I do it and it works for me.
---
"beam me up scot
I would prefer having one window spread over two monitors as well. But.
On windows, the layout was never saved correctly, resulting in a slightly too
big or small window. I could never get it right. And i think there was a
problem with the start bar, that couldnt be left exposed, which i want
I remember trying that but something about it annoyed me so I reverted. I even
tried setting both monitors to be treated as a single monitor in the nVidia
control panel but (from memory so I could fullscreen it) but that was worse.
I just tried to set it up as a single spread out window but now
Hm, thats strange behavior Charles. I don't have Nuke9 , so i cannot check. I
just had the experience that not even A works when floating over the viewer,
in older Nuke versions though.
Am 29.04.2015 um 13:26 schrieb Charles Bedwell:
> I'm using a multi monitor setup, viewer floated to second
This is why I use a single window spread over two monitors as a layout.
Unfortunately since Nuke9 it doesn't get saved properly anymore (scales to just
one screen). So first thing when launching Nuke is always resizing the window
over both monitors I hate it (even more as it worked just fine in
I'm using a multi monitor setup, viewer floated to second monitor, Nuke 9.05
and Windows 7.
When hovering the mouse over the viewer and tapping A I get to see the alpha.
If I type R I get a read node. G for Grade. B for Blur. It's a little
inconsistent in how it works. If the mouse is back over
I remember i had the same behavior on windows too. Its because i always put the
viewer into a separate window to move it onto the second monitor.
Good tip for the linux setting though, thanks.
Am 25.04.2015 um 16:08 schrieb Howard Jones:
> Just a thought…
> If you have floated the viewer, on a m
Just a thought…
If you have floated the viewer, on a mac you will have to click on it but on
linux as long as you set focus follows mouse in the Xwindows settings it should
work.
Otherwise you should have been ok.
H
> On 25 Apr 2015, at 13:22, Daniel Hartlehnert wrote:
>
>
> >>On 1 April 201
On Linux its an OS thing. You need to activate the "focus window on mouse move"
or something like that in the windows preferences.
--
Bruno-Pierre Jobin
> On Apr 25, 2015, at 8:22 AM, Daniel Hartlehnert wrote:
>
>
> >>On 1 April 2015 at 17:04, Daniel Hartlehnert wrote:
> >>
> >>Because it a
>>On 1 April 2015 at 17:04, Daniel Hartlehnert wrote:
>>
>>Because it also means to constantly click in the viewer before pressing "A" to make sure it has the focus.
>You don't need to click in the viewer, just have the mouse hovering over it.
Somehow that never worked for me. Maybe its an OS
Hi Frank,
Nice to meet you mate. I'm aware of the auto label functionality and
channel indicators in Nuke but reading the channels a node is affecting on
its label or indicators isn't the same as figuring out what that node is
actually doing, hence the request for a Roto only node at that time. It
Hey
On 1 April 2015 at 17:04, Daniel Hartlehnert wrote:
> Because it also means to constantly click in the viewer before pressing
> "A" to make sure it has the focus.
>
You don't need to click in the viewer, just have the mouse hovering over
it.
On 18 April 2015 at 05:55, Diogo Girondi wrote:
This was requested (by myself and others) during a beta when moving from
the old Bezier node to the "new" RotoPaint, it was purely a request for
workflow/customization and readability reasons.
Using a RotoPaint for masks implies on more clicking around, prevents you
from having a default that work
Hi,
Am 01.04.2015 um 12:55 schrieb Frank Harrison:
> Hey,
>
> just because i am too lazy to switch the viewer to display the alpha channel
> Did you know that when you press the "A" key in the viewer it allows you to
> switch between Alpha and RGB? :)
Yes, i know this. Even too lazy to do "tha
So I was right. Accept for overhead part (kidding joking, smart ass alert)
I just remember a lot of people asking in like V5(or 6?) when the first new
paint node was added that a clean roto node exist, and as some point it
was added.)
Randy S. Little
http://www.rslittle.com/
http://www.imdb.com
That rotopaint render bar i think is a lie. That is it comes up but isn't
necessarily the bottleneck. I've seen scrips where people frame blend the
output of an rp node (never a good idea) so the Rotopaint bar takes ages but of
course it's everything above the node as well that is dragging its f
Hey,
just because i am too lazy to switch the viewer to display the alpha channel
>
Did you know that when you press the "A" key in the viewer it allows you to
switch between Alpha and RGB? :)
On a side node: If i, lets say use a blur node set to use rgba, but
> downstream only use alpha from tha
Oh, i forgot to add that i have only worked with v7 so far, no experience with
8 or 9 yet.
Am 01.04.2015 um 11:17 schrieb Frank Harrison:
> Hey Daniel,
>
> That's fascinating to hear, I wonder if it does relate to the bumber of
> channels they use by default?
>
> There are various things yo
Hi Frank,
hmm, number of channels. I tend to set Roto to use rgba instead of alpha only,
just because i am too lazy to switch the viewer to display the alpha channel.
Even though i might just need alpha downstream. Kind of going against my own
agenda of keeping everything simple as possible :)
Hey Daniel,
That's fascinating to hear, I wonder if it does relate to the bumber of
channels they use by default?
There are various things you can do to make Roto and Paint appear slower,
such as use excessive numbers of expessions or view a node downstream of a
Roto with lots of comptationally e
Thanks Frank,
good to know :).
---
Simon Björk
Compositor/TD
+46 (0)70-2859503
www.bjorkvisuals.com
2015-04-01 10:24 GMT+02:00 Daniel Hartlehnert :
> Hi Frank,
>
> thanks for an "official" answer :)
>
> My experience differs though, so i don't have any "metric" to
Hi Frank,
thanks for an "official" answer :)
My experience differs though, so i don't have any "metric" to base it on,
Marten. Only common sense and experience. Therefore my answer i gave before.
Am 01.04.2015 um 10:00 schrieb Frank Harrison:
> Hey Guys,
>
> Under the hood the two Nodes are
Hey Guys,
Under the hood the two Nodes are exactly the same, they just cater to
different work flows.
As a result, the only time RotoPaint should be slower is when you have
paint/clone/smear strokes interleaved with bezier/bspine shapes.
F.
On Wednesday, April 1, 2015, Daniel Hartlehnert wrote
eh? what's your metric to claim that roto paints are much faster and
smaller memory footprint.
Using Nuke 9.04 & nuke.startPerformanceTimers() shows the same memory and
cpu usage.
Both nodes have a equal values on a 4K/100frame test: 5.22MB, cpu=9423ms
On 1 April 2015 at 20:26, Daniel Hartlehne
Isn't it obvious? Roto node has much less functionality, hence it its much
faster to process and has a smaller memory footprint. Bugs from the paint part
of Rotopaint cannot destroy your script, Rotopaints with more than 100 strokes
tend to slow down your script (if i ever see that progress bar
Roto is just a subset of rotopaint, as users wanted a lighter tool.
If you're not painting use roto. You can always drag the shaped into a rp node
to 'promote' it.
Howard
> On 31 Mar 2015, at 22:57, Ergin SANAL wrote:
>
> it works without premultipication, need to choose source as backgrou
Well there you go then, you only have to deal with the extra UI and that's
the difference but it is for sure processing the same data as the paint
node without the paint part. They aren't different much beyond that and
how they default load UI wise. Its just got UI and knobs turned off.
According
Where's the overhead? Info on a roto node and rotopaint both says
'Total Memory Usage: 0B'
On 1 April 2015 at 11:08, Randy Little wrote:
> huh? output can be whatever you tell it. Pre-Multiply is directly
> under output. Set output to none and premult to RGBA and you get your RGB
> input
huh? output can be whatever you tell it. Pre-Multiply is directly under
output. Set output to none and premult to RGBA and you get your RGB input
Premulted by whatever roto you have drawn in the node with only 2 nodes
instead of 3.
If you set paint node up the same way it does the same thing.
it works without premultipication, need to choose source as background and
replace the alpha. premult is distractive time to time.. cheerz
On Wed, Apr 1, 2015 at 12:46 AM, Randy Little
wrote:
> Roto node will output RGBA (or anything) I premult inside the roto node
> all the time so its just i
Roto node will output RGBA (or anything) I premult inside the roto node all
the time so its just inline no extra premult step. (not always a best
practice fyi) but I do it :-/
Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/
On Tue, Mar 31, 2015 at 5:30 PM, Ergin SA
rotopaint's output is rgba and roto's is only a.
that means with rotopaint, nuke has to deal with 3 more channels.
maybe thats why there are some performance issues.
actually there are no difference between 2 nodes except output channels and
place of the sliders. (feather,opacity etc.)
On Wed,
clean UI. No accidental painting. bigger memory footprint maybe?
Randy S. Little
http://www.rslittle.com/
http://www.imdb.com/name/nm2325729/
On Tue, Mar 31, 2015 at 2:21 PM, Ron Ganbar wrote:
> No idea about performance, but I do love the fact that when I use the O
> hotkey instead of the
No idea about performance, but I do love the fact that when I use the O
hotkey instead of the P hotkey, I can immediately start drawing a shape, as
the Bezier tool is on by default.
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ron
For some reason I always reach for the RotoPaint node instead of the
regular Roto node. I'm not sure why I got into this habit, but it might be
(if I'm not mistaken) that the RotoPaint node was introduced before the
Roto node back in 6.0.
Anyway, does anyone know if there's a difference in perform
39 matches
Mail list logo
