Florent Ghys

jit.movie reference mentions that if the video engine is not specified "it is determined by the Video Engine Max preference"

how come an attrui connected to a jit.movie does not reflect changes?

jit.movie

message

attrui

is it actually changing its engine as it is supposed to do? 

For example, selecting of "hap" video engine and then clicking on jit.movie's left yellow arrow and then attributes shows "engine (viddll)" despite the change

Hello, 
jit.movie reference mentions that if the video engine is not specified "it is determined by the Video Engine Max preference"
how come an attrui connected to a jit.movie does not reflect changes?


is it actually changing its engine as it is supposed to do? 
For example, selecting of "hap" video engine and then clicking on jit.movie's left yellow arrow and then attributes shows "engine (viddll)" despite the change
thanks
Florent


Hello, 
jit.movie reference mentions that if the video engine is not specified "it is determined by the Video Engine Max preference"
how com

jit-movie-engine-change-without-writing-in-the-max-box

you can not change the video engine dynamically, you must re-instantiate the box to load the updated video engine pref. That's what's meant by "This argument can only be set in the max box".

I was actually talking about jit.movie objects that don't have an @engine argument: do they change their engine according to Max Preference Video Engine as described in the Reference? 

thanks Rob,
I was actually talking about jit.movie objects that don't have an @engine argument: do they change their engine according to Max Preference Video Engine as described in the Reference?  
 

only when re-instantiated. the point is, once a jit.movie object box is created the engine unalterable. you must destroy and recreate the box to update the engine.

OK I got it! thanks for the clarification

jit.movie engine change without writing in the Max box