Mattijs

I am looking into the edit commands of jit.qt.movie.

Is there a way to detect whether an edit operation is ready, similar to the "read blah.mov 1" after a read operation?

I am looking into the edit commands of jit.qt.movie. 

jit-qt-movie-edit-commands-how-to-know-when-operation-is-done

On May 24, 2007, at 8:30 AM, Mattijs Kneppers wrote:

> I am looking into the edit commands of jit.qt.movie.

> Is there a way to detect whether an edit operation is ready, 

> similar to the "read blah.mov 1" after a read operation?

AFAIK, they are synchronous in the low priority queue, so they will 

be done before you another event can be processed: i.e. "t b editop" 

bangs after editop is done provided that the event is generated from 

> I am looking into the edit commands of jit.qt.movie.
>
> Is there a way to detect whether an edit operation is ready,  
> similar to the "read blah.mov 1" after a read operation?

AFAIK, they are synchronous in the low priority queue, so they will  
be done before you another event can be processed: i.e. "t b editop"  
bangs after editop is done provided that the event is generated from  
the low priority queue.

This is correct, and why the batch processors in the examples/jitter- 

Am 24.05.2007 um 17:44 schrieb Joshua Kit Clayton:

> On May 24, 2007, at 8:30 AM, Mattijs Kneppers wrote:

>> I am looking into the edit commands of jit.qt.movie.

>> Is there a way to detect whether an edit operation is ready, 

>> similar to the "read blah.mov 1" after a read operation?

> AFAIK, they are synchronous in the low priority queue, so they will 

> be done before you another event can be processed: i.e. "t b 

> editop" bangs after editop is done provided that the event is 

This is correct, and why the batch processors in the examples/jitter- 
examples/demos folder work at all.

>
> On May 24, 2007, at 8:30 AM, Mattijs Kneppers wrote:
>
>> I am looking into the edit commands of jit.qt.movie.
>>
>> Is there a way to detect whether an edit operation is ready,  
>> similar to the "read blah.mov 1" after a read operation?
>
> AFAIK, they are synchronous in the low priority queue, so they will  
> be done before you another event can be processed: i.e. "t b  
> editop" bangs after editop is done provided that the event is  
> generated from the low priority queue.
>
> -Joshua


Ok, I briefly had the idea that the edit operations weren't synchronous, thanks for confirming they are. It was probably a mistake in my patch.

Quote: jkc wrote on Thu, 24 May 2007 17:44

----------------------------------------------------

> > I am looking into the edit commands of jit.qt.movie.

> > Is there a way to detect whether an edit operation is ready, 

> > similar to the "read blah.mov 1" after a read operation?

> be done before you another event can be processed: i.e. "t b editop" 

> bangs after editop is done provided that the event is generated from 

Quote: jkc wrote on Thu, 24 May 2007 17:44
----------------------------------------------------
>
> On May 24, 2007, at 8:30 AM, Mattijs Kneppers wrote:
>
> > I am looking into the edit commands of jit.qt.movie.
> >
> > Is there a way to detect whether an edit operation is ready,  
> > similar to the "read blah.mov 1" after a read operation?
>
> AFAIK, they are synchronous in the low priority queue, so they will  
> be done before you another event can be processed: i.e. "t b editop"  
> bangs after editop is done provided that the event is generated from  
> the low priority queue.
>
> -Joshua
>
----------------------------------------------------


jit.qt.movie edit commands - how to know when operation is done?