tutorial 42jSlab-compositeDV

Sep 15, 2006 at 5:47am

tutorial 42jSlab-compositeDV

Hi,

In the 42jSlab-compositeDV tutorial there is a message box that says “read
nothing” which gives a “can’t find” error when I try to use it. Is this
supposed to work? Let me put it another way, is there a way to clear the
jxs file from a jit.gl.slab or bypass the the slab by sending a message to
it?

Uning Jitter 1.6.1

thx!

bbw

#27639
Sep 15, 2006 at 12:59pm

maybe a [gate 2] just before the slab to route the jit_matrix or
jit_gl_texture messages around it?

On Sep 15, 2006, at 1:47 AM, bart woodstrup wrote:

> Hi,
>
> In the 42jSlab-compositeDV tutorial there is a message box that
> says “read
> nothing” which gives a “can’t find” error when I try to use it.
> Is this
> supposed to work? Let me put it another way, is there a way to
> clear the
> jxs file from a jit.gl.slab or bypass the the slab by sending a
> message to
> it?
>
>
> Uning Jitter 1.6.1
>
> thx!
>
> bbw

#83775
Sep 15, 2006 at 3:26pm

hello again.

seems that nobody ever tried to play HDV video files on jitter-windows.

anyway: i am also runing into performance issues on a mac.

playing back Apple HDV 1080i50 files (1920×1080) takes about 55 % of
the cpu, if played back with quickTime, and 90% with jitter.
(according to ActivityMonitor on a dual 2Ghz G5)

are there possibilities to get down to around 60% with jitter?
i just want to play back those files without any processing.

what is the cause for the performance differences?

thanks for ideas!

mkl

#83776
Sep 15, 2006 at 3:55pm

Are you using direct-to-window mode?

jb

Am 15.09.2006 um 17:27 schrieb michael strohmann:

> hello again.
>
> seems that nobody ever tried to play HDV video files on jitter-
> windows.
>
> anyway: i am also runing into performance issues on a mac.
>
> playing back Apple HDV 1080i50 files (1920×1080) takes about 55 %
> of the cpu, if played back with quickTime, and 90% with jitter.
> (according to ActivityMonitor on a dual 2Ghz G5)
>
> are there possibilities to get down to around 60% with jitter?
> i just want to play back those files without any processing.
>
> what is the cause for the performance differences?
>
> thanks for ideas!
>
> mkl

#83777
Sep 15, 2006 at 6:28pm

On Sep 14, 2006, at 10:47 PM, bart woodstrup wrote:

> In the 42jSlab-compositeDV tutorial there is a message box that
> says “read nothing” which gives a “can’t find” error when I try to
> use it. Is this supposed to work? Let me put it another way, is
> there a way to clear the jxs file from a jit.gl.slab or bypass the
> the slab by sending a message to it?

Sorry. I’ll update this patch for future releases, as well as the
help file and html reference file. The correc way to do this is the
“dispose” message.

-Joshua

#83778
Sep 15, 2006 at 6:39pm

Also, you should be using UYVY color and try compressing using
Photo-JPEG. That could possibly buy you a bit more fps.
Cheers,
Andrew B.

#83779
Sep 15, 2006 at 6:57pm

On Sep 15, 2006, at 8:27 AM, michael strohmann wrote:

> seems that nobody ever tried to play HDV video files on jitter-
> windows.

I haven’t. In general I stay away from this (and any inter-frame
compression based) codec which exhibits much more expensive time to
decompress than an intra-frame only codec (prefer PhotoJPEG over all
others), especially with random access and playback speeds outside
the range 0.-1.

> anyway: i am also runing into performance issues on a mac.
> playing back Apple HDV 1080i50 files (1920×1080) takes about 55 %
> of the cpu, if played back with quickTime, and 90% with jitter.
> (according to ActivityMonitor on a dual 2Ghz G5)
> what is the cause for the performance differences?

It is pure speculation for us without an example patch. As *always*,
please provide a stripped example patch illustrating your issue so
that others can provide you with informed assistance.

In the absence of such a patch, and in addition to Jeremy and
Andrew’s comments regarding direct to window mode or UYVY colormode,
I would also suggest that you make sure that you are not over
clocking the movie (i.e. using a fast metronome, which will keep
sending duplicate frames and consuming as much CPU as is available).
One useful attribute of jit.qt.movie is @unique 1, which will not
send duplicate frames if over-clocked.

-Joshua

#83780

You must be logged in to reply to this topic.