vvvv differences from Jitter?
Hi everyone,
Probably the wrong forum to ask this on but has anyone on the list used vvvv? If so, I'd be interested in your thoughts on the differences between it and Jitter, not so much as which one is 'better', but maybe which one is better 'at what' if that makes sense, and what makes them distinct etc.
Thanks,
Bill
hi bill.
I would search the forum, since this has been discussed before, but in
my opinion maxMSP/Jitter excels at designing the logic behind a patch,
whereas vvvv is a lot leaner when it comes to working with "spreads" - a
fantastic system, which can be emulated with jit.gl.multiple
Andreas
Bill skrev:
> Hi everyone,
>
> Probably the wrong forum to ask this on but has anyone on the list used vvvv? If so, I'd be interested in your thoughts on the differences between it and Jitter, not so much as which one is 'better', but maybe which one is better 'at what' if that makes sense, and what makes them distinct etc.
>
> Thanks,
>
> Bill
>
> .
>
>
Hi Andreas,
Thanks, I did read those forum posts and they were good but I'm still scratching my head about what the big deal is about spreads etc. I'd like to use vvvv just as an alternative (sometimes doing the same thing with different tools opens up creative avenues that don't present themselves otherwise) but maybe I've used m/m/j and pd too long to wrap my head around something that's different but not different enough to not be confusing? Seems like there's a basic low level conceptual difference between the two that I'm just not getting yet. Sort of reminds me when I first tried to use Pd about 10 years ago before they got their documentation sorted and I barely was able to get a sinewave to play :)
Bill
jitter historical roots are in the world of video processing (as in applying
filter and manipulation of video images by controllers, sound, sensor etc)
in a linear stack top-down fashion.
its cross platform opengl 3d capabilities (vvvv works on directx and so is
win only) were added in the last few years and so generative 3d imagery
(multiples, spreads, etc) inherit some of the mind set of its video roots.
as-in, its easier to manipulate single objects/models and pass thru filters,
shaders etc then operating in a multi-node mindset. both dont acxel at
recursivity.
not that you cant do everything with matrices, with complete control and the
speed of jitter, but its more complicated and mathy, a brave patcher can
probebly duplicate the notion of spreads, or even find a better method.
i think vvvv has done a good job in creating a lively website, which is fun
and inviting while deep. wish cycling web presence would be more colborative
then it is, currently its wiki attributes are somewhat dormant. vvvv has
also a funny licencing agreement and i quote "When asked you will say
politely that you actually don't like the music" - then use the commercial
version. note this doesnt seem to work that well as they unofficaly attest
thier commercial user base is tiny.
might be repeating myself and others... my two cents.
On Sat, Nov 8, 2008 at 6:16 PM, Bill wrote:
>
> Hi Andreas,
>
> Thanks, I did read those forum posts and they were good but I'm still
> scratching my head about what the big deal is about spreads etc. I'd like to
> use vvvv just as an alternative (sometimes doing the same thing with
> different tools opens up creative avenues that don't present themselves
> otherwise) but maybe I've used m/m/j and pd too long to wrap my head around
> something that's different but not different enough to not be confusing?
> Seems like there's a basic low level conceptual difference between the two
> that I'm just not getting yet. Sort of reminds me when I first tried to use
> Pd about 10 years ago before they got their documentation sorted and I
> barely was able to get a sinewave to play :)
>
> Bill
>
Actually that makes a lot of sense about Jitter having its roots in 'video' and I guess vvvv is more of a generative/algorithmic approach? Some of the examples of the work by artists using it are impressive which is why I'm so intrigued by the program...
Bill