Hi Fredrik,
i see. Totally understand your idea behind that decision.
I think the Yes/No dialog is a good idea. But i think it should then
create the Read with the same frame range as the Write that it's being
created from.
What do you think?
Cheers,
Holger
On 25.05.2016 16:42, Fredrik Averpil wrote:
Hi Holger,
I see what you mean.
I’ve made readFromWrite v2.x a lot more robust than in v1.x, by
requiring a filepath to exist which can be used to figure out the
framerange properly. As previous posters have mentioned, there are a
lot of “read from write” scripts out there which fail to get the
proper framerange in certain scenarios. Actually, the script doesn’t
even expect the selection to be a Write node, which makes
readFromWrite not only work on Write nodes (you can read more on that
here
<https://fredrikaverpil.github.io/2016/05/23/nuke-script-read-node-from-write-node/>).
So, in a way, you can say that this is a tradeoff to more accurately
acquire the framerange.
I could look into implementing what you’re asking, but that will give
you a Read node with framerange 1-1 and which you’ll have to enter
yourself, unless you entered the range in the Write node.
If so, I’m going to show that same dialog as now, but with the option
(Yes/No) to create the Read node anyway. Would that be useful?
// Fredrik
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Holger Hummel - hol...@celluloid-vfx.com
Celluloid Visual Effects GmbH & Co. KG
Paul-Lincke-Ufer 39/40, 10999 Berlin
phone +49 (0)30 / 54 735 220 - m...@celluloid-vfx.com
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
