AE plug in's for shake?


#21

After I posted my reply, I had a look through to figure that one out (as I knew you’d ask…)

haven’t got a clue, I’m afraid - might be worth asking the Foundry about it (in fact, I’m probably going to be seeing some of the guys from there tomorrow, so I’ll ask them myself…)


#22

Plz do because thats not the only one I can’t find hell I can’t find any of the so called OLD ones’

edit

they really need to update the fuc*ing support page there sell’s page and answer the E-mail’s when people like me put the word BUY in the topic and never get a reply… :rolleyes:


#23

ok I give up…just how did you do that? I have spent about 10 hours on that and I can’t seem to figer it out…
:cry:


#24

T_Etch1 = T_Etch(0, 0, 10, 10, 0.5, 5, 2, 50, 10, 3, 15, 15, 1,
1, 1, 1, 0, 0, 0, 0, 0, 1, 0.5, 0, “screen”, 50, 100, 100,
“reflect”, “reflect”);

// User Interface settings

SetKey(
“nodeView.T_Etch1.t”, “0”,
“nodeView.T_Etch1.x”, “462”,
“nodeView.T_Etch1.y”, “255.5”
);

“Everything from Tinder 1 is still available in Tinder 2, but a lot of nodes have now been combined into one”

hmmm I dont think so. :smiley:
Please elaborate


#25

I have no idea what the above code is maybe someone can de code it for me…

here is a E-mail I got from them

Thank you for your email. Sorry to hear that you have emailed us before,
but have not received a reply.

Tinder for Discreet, After Effects and AvidDS have proved very popular
with customers. However, Tinder 1.0 for Shake was never taken up in the
same way. I think there were a number of reasons for this. Some Tinder
effects can be constructed from Shake nodes and wrapped up in macros.
Most Shake users at the time were working on films and Tinder plug-ins
were less applicable to the work they were doing (unlike Furnace which
has proved very popular on Shake). Also the Tinder 1.0 plug-ins did not
support floating point. The cost of supporting 50+ Tinder 1.0 plug-ins
across multiple versions of Shake on up to 4 different operating systems
proved not to be viable and support for it was dropped some time ago in
favour of a more manageable and reduced set of plug-ins. Although there
are only 9 plug-ins in Tinder 2.0 they are much improved versions of the
ones in Tinder 1.0 and they also support rendering in floating point.
The plug-ins we chose was based on customer feedback and T_Etch is not
one of them.

The Shake customer base is changing and we continue to monitor this
market and requests from customers. If the demand is there for more
Tinder plug-ins on Shake we will schedule the development in. But at the
moment, we have no plans to port more Tinder plug-ins to Shake.

We wrote our Tinderbox plug-ins specifically for After Effects. We have
not had the resources to be able to properly support customers on
Combustion. However, we do have some customers who have tried Tinderbox
for After Effects on Combustion and are happy with the results. Having
said that, we do have plans to improve our Tinderbox plug-ins and as
part of that work we intend to support other hosts like Combustion. We
have just taken on another software test engineer and are in the process
of hiring another software engineer. This should allow us to properly
develop for and support these additional platforms.

We recently updated our web site to make it clearer and quicker to
navigate and we also incorporated a web shop to allow customers to buy
(or rent) plug-ins. I’m very disappointed you don’t like it and your
reasons are not clear to me. We are constantly striving for customer
satisfaction, please can you tell us how we should improve it.

Your comments and feedback are greatly appreciated but I’m sorry we
can’t help you with T_Etch on Shake.

Kind Regards

Rob


#26

thank you for forwarding the message…

i like the answer

“Some Tinder effects can be constructed from Shake nodes and wrapped up in macros.”
Well i am not sure if that would be that efficient to do Etch equivalent in a macro… i think it is better to use a precompiled plug in for that (it’s not just the outline made of edge -> turbulance there are also some random long lines which looks precomputed in the middle of shapes… It’s possible to do something near though)


#27

I was assing on something I’d heard from someone else here when we moved up to Tinder 2. I was wrong. My apologies for that.


#28

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.