Rich

HI guys, yes! yet another annoying beginner with no idea calling on the superior intellect of the community!

I want to set up a video wall, and once someone walks past their shadow creates a mask that fades out as they walk past, reveiling another underlying video.

HI guys, yes! yet another annoying beginner with no idea calling on the superior intellect of the community!
I want to set up a video wall, and once someone walks past their shadow creates a mask that fades out as they walk past, reveiling another underlying video.
how on earth do i start to do this??
any help would be greatly appreciated!
peace
Richard from belfast


using-shadow-as-mask-between-2-videos

The first place to start would be the tutorials.

When you're through, you'll know quite a lot more

about how Jitter works, and you'll have at least

a good start at sussing out things like keying of

various sorts, you might have a passing acquaintance

with filters like jit.slide, and you'll certainly

be able to ask considerably more focused questions,

which will, in turn, get you lots more focused and

In addition to that, you also have a whole archive

of posts you can search through in addition to the

wealth of doc stuff at your disposal. Some people 

actually find that looking in those places first 

saves 'em some time [and is good signal/noise hyiene,

I'd start with Tutorial 10 on Chromakeying, and

you'll find stuff on setting up live input in 

Tutorial 21. Take a looksee at the jit.slide object

for your wake, And if you find yourself just randomly

connecting patch cords, then go back and actually do

the tutorials from the beginning - a sure cure for

The first place to start would be the tutorials.
When you're through, you'll know quite a lot more
about how Jitter works, and you'll have at least
a good start at sussing out things like keying of
various sorts, you might have a passing acquaintance
with filters like jit.slide, and you'll certainly
be able to ask considerably more focused questions,
which will, in turn, get you lots more focused and
helpful answers.

In addition to that, you also have a whole archive
of posts you can search through in addition to the
wealth of doc stuff at your disposal. Some people 
actually find that looking in those places first 
saves 'em some time [and is good signal/noise hyiene,
too] 

I'd start with Tutorial 10 on Chromakeying, and
you'll find stuff on setting up live input in 
Tutorial 21. Take a looksee at the jit.slide object
for your wake, And if you find yourself just randomly
connecting patch cords, then go back and actually do
the tutorials from the beginning - a sure cure for
cargo cult patching every time.

thanks gregory - very kind of ya to take the time, getting stuck into the tutorials, was hoping to find some patches to deconstruct, but you are right, walk before i run - all the best

thanks gregory - very kind of  ya to take the time, getting stuck into the tutorials, was hoping to find some patches to deconstruct, but you are right, walk before i run  - all the best


> ...was hoping to find some patches to >deconstruct, but you are right, walk before i run - all the best

Since the tutorial patches are Max patches

themselves, you can use *that* as your raw

material. Same for the help patches - open

them, copy out what you need and paste into

a blank patcher window, and off you go [NOTE:

those help files don't tell you EVERYTHING

about what an object does - use the Reference

On the grand continuum of things, Jitter is 

more an environment in which you learn to 

program rather than a bunch of prefabbed units

that you use or tweak at a high level [a la

something like Reaktor]. Learning about the

messages and data types that Max uses and how

Jitter uses matrix-based data will mean that

you can do things considerably more complex

than what you've described, that you'll spend

less time looking at other people's patches

like a cow at a passing train, and that when

the time comes to ask questions about what you

specifically want to do, you can do so with a

degree of specificity that [in my experience

anyway] nets you lots more answers in public.

It's worth it. As the Oblique Strategies say,

> ...was hoping to find some patches to >deconstruct, but you are right, walk before i run  - all the best

Since the tutorial patches are Max patches
themselves, you can use *that* as your raw
material. Same for the help patches - open
them, copy out what you need and paste into
a blank patcher window, and off you go [NOTE:
those help files don't tell you EVERYTHING
about what an object does - use the Reference
Manual for that].

On the grand continuum of things, Jitter is 
more an environment in which you learn to 
program rather than a bunch of prefabbed units
that you use or tweak at a high level [a la
something like Reaktor]. Learning about the
messages and data types that Max uses and how
Jitter uses matrix-based data will mean that
you can do things considerably more complex
than what you've described, that you'll spend
less time looking at other people's patches
like a cow at a passing train, and that when
the time comes to ask questions about what you
specifically want to do, you can do so with a
degree of specificity that [in my experience
anyway] nets you lots more answers in public.

> > ...was hoping to find some patches to >deconstruct, but you are right, walk before i run - all the best

> Since the tutorial patches are Max patches

> themselves, you can use *that* as your raw

> material. Same for the help patches - open

> them, copy out what you need and paste into

> a blank patcher window, and off you go [NOTE:

> those help files don't tell you EVERYTHING

> about what an object does - use the Reference

> On the grand continuum of things, Jitter is

> more an environment in which you learn to

> program rather than a bunch of prefabbed units

> that you use or tweak at a high level [a la

> something like Reaktor]. Learning about the

> messages and data types that Max uses and how

> Jitter uses matrix-based data will mean that

> you can do things considerably more complex

> than what you've described, that you'll spend

> less time looking at other people's patches

> like a cow at a passing train, and that when

> the time comes to ask questions about what you

> specifically want to do, you can do so with a

> degree of specificity that [in my experience

> anyway] nets you lots more answers in public.

> It's worth it. As the Oblique Strategies say,

> knowledge is not enough/science is not enough/Love is dreaming this equation

use cv.jit.ravg which you can get from
http://www.iamas.ac.jp/~jovan02/cv/ and threshold it in some way to
create a mask.

On 10/26/06, Gregory Taylor  wrote:
>
> > ...was hoping to find some patches to >deconstruct, but you are right, walk before i run  - all the best
>
>
> No problem.
>
> Since the tutorial patches are Max patches
> themselves, you can use *that* as your raw
> material. Same for the help patches - open
> them, copy out what you need and paste into
> a blank patcher window, and off you go [NOTE:
> those help files don't tell you EVERYTHING
> about what an object does - use the Reference
> Manual for that].
>
> On the grand continuum of things, Jitter is
> more an environment in which you learn to
> program rather than a bunch of prefabbed units
> that you use or tweak at a high level [a la
> something like Reaktor]. Learning about the
> messages and data types that Max uses and how
> Jitter uses matrix-based data will mean that
> you can do things considerably more complex
> than what you've described, that you'll spend
> less time looking at other people's patches
> like a cow at a passing train, and that when
> the time comes to ask questions about what you
> specifically want to do, you can do so with a
> degree of specificity that [in my experience
> anyway] nets you lots more answers in public.
>
> It's worth it. As the Oblique Strategies say,
>
> Always first steps
>
>
>
>
> --
> knowledge is not enough/science is not enough/Love is dreaming this equation
>


using shadow as mask between 2 videos