I’m just wondering what is the plan for the way Touch projects will be delivered.
For example, with touch 17 and its predecessors, I could make a synth that could be played on touch player that could be given to a client for free, or, if I needed to use sockets or MIDI, I could get them to buy a Touch Mixer license.
Now Greg’s Mixxa project runs as an executable but is able to be opened in touch Designer.
will it be possible for us to also package a touch project as an executable program?
We are still working out the details, but we will announce the different tiers of Touch products closer to release. We have some ideas we think you’ll be very excited about!
I really like the way the general set-up encourages a sharing community. that’s what has made Max/MSP so successful.
I think the wiki will make a big difference but I am a little concerned about info being spread thinly between the official docs, the forum and the Wiki. I am not sure how to more tightly integrate them.
Also it’s good when you have a client, such as the kids’ museum installation you guys worked on, for whom you just want to give a running version wihtout the authoring environement.
I am curious about the old business model where people could buy just touch Mixer and then downloaded available synths. did that work for you? or did they just buy other VJ tools instead?
How do you see the competition?
Jitter uses message boxes in much the same way we use DATs to write shaders in either CG (good for directX) or GLSL (better for OGL)
vvvv is a bit clunky but it’s free and can do a lot of stuff that touch can do - including GCU stiff I believe.
My guess is that, like me, you just don’t have time to sit down and really use the competitions’ products.
that said, I have become a rabid touch fan-boy, so I can not rationally compare anymore.
