I try to render to a preview and a performance screen.

It should be a basic task for a jitter patch.

Of course the "drawto" message can only draw to one destination at a time.

My patch should be able to use either the preview or the performance screen, or both.

@shared_context only permit to share context, not to choose first destination, second, or both.

Things aren't very clear in the doc, and there is no trace for @shared_context in jitter tutorials.

Forum archives gives complexes solutions which are contradicted.

I spent much time on them without satisfaction.

Could someone clear the way, the simplest one to have a "double" rendering with choice of configuration.

I try to render to a preview and a performance screen.
It should be a basic task for a jitter patch.

Of course the "drawto" message can only draw to one destination at a time.
My patch should be able to use either the preview or the performance screen, or both.

Forum archives gives complexes solutions which are contradicted.
I spent much time on them without satisfaction.

should-be-a-basic-task

It works fine in argb colormode, not in uyvy.

Hi, sorry to insist
It works fine in argb colormode, not in uyvy.
I don't see any reason for.

You're lucky that argb was even working. It wasn't for me. You were

badly abusing textures in your patch. You had the same texture as

both a copy destination for jit.gl.render and a copy target from

jit.qt.movie/jit.gl.slab. This is bad! The texture was getting

You're lucky that argb was even working.  It wasn't for me.  You were
badly abusing textures in your patch.  You had the same texture as
both a copy destination for jit.gl.render and a copy target from
jit.qt.movie/jit.gl.slab.  This is bad!  The texture was getting
corrupted.  Here's a fixed patch:

On May 3, 2007, at 10:44 AM, derrickgiscloux wrote:

> jit.gl.slab perf @file cc.uyvy2rgba.jxs;

Also, you probably already know this and were just making a quick 

example patch, but just in case, you need to use the "@dimscale 2. 

1." attribute when doing the above conversion in a shader to make the 

half size X axis of UYVY into the correct size of RGBA. It won't look 

Also, you probably already know this and were just making a quick  
example patch, but just in case, you need to use the "@dimscale 2.  
1." attribute when doing the above conversion in a shader to make the  
half size X axis of UYVY into the correct size of RGBA. It won't look  
as nice.

These suggestions gives me some orientation.

... though I'd like and will wait for "in-depth" clarifications at next jitter release tutorials ... perhaps ...

Okay, thank you very much.
These suggestions gives me some orientation.
... though I'd like and will wait for "in-depth" clarifications at next jitter release tutorials ... perhaps ...

Don't expect too much in the way of "in-depth" clarifications in

J1.6.3. If you have any questions, ask now. The basic thing you were

doing wrong was reusing a texture that was being filled with video

data and then having the rendered scene copied to it. The shared

context thing makes texture resources available in multiple contexts.

jit.gl.render @copy_texture simply specifies a texture for the

rendered scene to be copied to when the buffer swap occurs.

> These suggestions gives me some orientation.

> ... though I'd like and will wait for "in-depth" clarifications at next jitter release tutorials ... perhaps ...

Don't expect too much in the way of "in-depth" clarifications in
J1.6.3.  If you have any questions, ask now.  The basic thing you were
doing wrong was reusing a texture that was being filled with video
data and then having the rendered scene copied to it.  The shared
context thing makes texture resources available in multiple contexts.
jit.gl.render @copy_texture simply specifies a texture for the
rendered scene to be copied to when the buffer swap occurs.

On 5/3/07, derrickgiscloux  wrote:
>
> Okay, thank you very much.
> These suggestions gives me some orientation.
> ... though I'd like and will wait for "in-depth" clarifications at next jitter release tutorials ... perhaps ...
>
> Thanks again.
>
> Derrick
>


>These suggestions gives me some orientation.

>... though I'd like and will wait for "in-depth" clarifications at 

>next jitter release tutorials ... perhaps ...

You don't have to wait very long. Tutorial 1 explains to you on its first page

what the default behavior of a QuickTime movie loaded into a jit.qt.movie

object is, and it even tells you how NOT to autostart playback.

You can find a description of the rate message in the section of Tutorial 4

(Controlling movie playback) labeled "Starting, Stopping, and Slowing

Down." Or, you can use the "stop" or "start" commands described in the

on the floor there's a long wooden table/on the table there's an open book/

on the page there's a detailed drawing/and on the drawing is the name I took

>Okay, thank you very much.
>These suggestions gives me some orientation.
>... though I'd like and will wait for "in-depth" clarifications at 
>next jitter release tutorials ... perhaps ...

You don't have to wait very long. Tutorial 1 explains to you on its first page
what the default behavior of a QuickTime movie loaded into a jit.qt.movie
object is, and it even tells you how NOT to autostart playback.

You can find a description of the rate message in the section of Tutorial 4
(Controlling movie playback) labeled "Starting, Stopping, and Slowing
Down." Or, you can use the "stop" or "start" commands described in the
first paragraph of that section.
-- 
on the floor there's a long wooden table/on the table there's an open book/
on the page there's a detailed drawing/and on the drawing is the name I took
Gregory Taylor http://www.rtqe.net


> Tutorial 1 explains to you on its first page

what the default behavior of a QuickTime movie ....

ah! ok! thank you, what is the link with my texture destination problem ?

> Tutorial 1 explains to you on its first page
what the default behavior of a QuickTime movie ....

ah! ok! thank you, what is the link with my texture destination problem ?


> ah! ok! thank you, what is the link with my texture destination problem ?

Can't I shared_context with others than the one specified with by ??

shared_context messages get no responses :

Can't I shared_context with others than the one specified with by ??
shared_context messages get no responses :

by "attribut" (sorry arobas doesn't seems to appear)

Hm. I can't get it to work either. I'm going to have to take some

> by "attribut" (sorry arobas doesn't seems to appear)

Hm. I can't get it to work either.  I'm going to have to take some
time to look at this later.

On 5/3/07, derrickgiscloux  wrote:
>
> by "attribut" (sorry arobas doesn't seems to appear)
>
