Never mind - i've got it the wrong way round, haven't I? The data only goes as
far as (r-1)?
Might explain why my plugins often crash...
--
Colin Alway <colin_al...@yahoo.com>
________________________________
From: Colin Alway <colin_al...@yahoo.com>
To: Nuke plug-in development discussion <nuke-dev@support.thefoundry.co.uk>
Sent: Friday, 20 May 2011, 10:38
Subject: Re: [Nuke-dev] Artifacts in drawIop
Don't you have to add a '1' before the multiplier? Because it's columns 'x' to
'r' inclusive. ie:
memset( buffer +x, 0, (1+r-x) * sizeof(float));
Colin
--
Colin Alway <colin_al...@yahoo.com>
________________________________
From: Colin Doncaster <co...@peregrinelabs.com>
To: Nuke plug-in development discussion <nuke-dev@support.thefoundry.co.uk>
Sent: Thursday, 19 May 2011, 18:07
Subject: Re: [Nuke-dev] Artifacts in drawIop
It sounds like you need to zero out the row ( nuke doesn't do this for you )
prior using it - thus you're memset is heading down the right path you're call
is wrong,
memset( buffer +x, 0, (r-x) * sizeof(float));
you have to remember that although the pointer is pointing to [0] that may not
be safe if Nuke's only managing x to r.
This should hopefully avoid the crash.
cheers
--
Colin Doncaster
Peregrine Labs
www.peregrinelabs.com
On 2011-05-19, at 12:28 PM, Stephen Newbold wrote:
Hi,
>
>I'm wondering if you guys can give me some pointers in where I might look to
>iron out a glitch in my DrawIop. So everything is generally working as I want
>it, but I'm getting very small glitches in the output. Could be in my code
>but I'm noticing the glitches change when I use any knob, even those
>unconnected with the output which is a bit odd. I've even added a null knob
>that does absolutely nothing just to test this. Change this knob and my
>artifacts change.
>
>So, what I'm trying to do first is work out why my output (albeit with
>artifacts) is changing when I move unrelated controls. I'm assuming certain
>things get updated on any knob change? I know it hard without seeing code,
>but have you guys got any ideas what is called/updated each time a knob is
changed? If it helps, things don't change when changing to a different frame,
only when using a knob. Also, the change in artifacts will change
consistently, in other words if I move a slider back and forth, the result will
change consistently back and forth, same artifact pattern for each value.
>
>I've also tried emptying the output buffer with memset for each row before
>filling it again to see if this affected things, but this is crashing nuke,
>
>memset(buffer, 0, (R - X) * sizeof(float));
>
>This has kind of got me stumped.
>
>Steve
>
>--
>Stephen Newbold
>Compositing Lead - Film
>MPC
>127 Wardour Street
>Soho, London, W1F 0NL
>Main - + 44 (0) 20 7434 3100
>www.moving-picture.com
>
>_______________________________________________
>Nuke-dev mailing list
>Nuke-dev@support.thefoundry.co.uk,
http://forums.thefoundry.co.uk/
>http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
