[Chimera-users] Movie recording does not stop

Elaine Meng meng at cgl.ucsf.edu
Tue Jul 22 09:31:54 PDT 2008


Hi Jean-Paul,
It also works for me on Mac OS 10.5.4 / X11 (of course, using a  
different directory and output location).  I get 60 frames in PPM  
format and the movie file.  Besides what Tom said about the "wait" at  
the beginning, some other things to check:

- are you using a recent version of Chimera?  Tom and I are using  
releases from this month.

- it's probably the e-mail software's fault for breaking it up, but  
the entire "movie encode" command should be one line

- it is not necessary to put ";" at the end of each line... that is  
only needed as a separator, between commands that are on the same  
line.  However, I tried the script both with and without all the end- 
of-line ";" and it did not seem to make any difference (for example,  
"movie stop" instead of "movie stop;")

- your bitrate is extra-high - did you try just using the default?  Or  
did this high value work in other movies?

Also, I don't think we have heard of a script stopping unless there is  
some error in a command.  In that case, however, there should be some  
error message in Chimera.
Elaine


On Jul 21, 2008, at 8:32 PM, Tom Goddard wrote:

> Hi Jean-Paul,
>
>  The script you sent works for me with Mac X11 Chimera 1.2540 on Mac  
> OS
> 10.4.11.  I open two maps and the resulting movie is correct.
>
>  You don't have any motion going on like a "roll" do you?  Because the
> first line of this script "wait" with no frame count means that
> subsequent lines of the script will not be executed until all motion
> ceases.  Likewise you have wait command with no frame count on the  
> first
> two transparency setting lines.
>
>    Tom
>
>
> Jean-Paul Armache wrote:
>> Thank you for the reply. It seems that I have today a lot of  
>> questions.
>> There is one more:
>> I have a script. When not in movie recording mode, it works fine.
>> However, if I input movie record and at the end movie stop and  
>> encode,
>> then at some point the script stops. Once it stopped with the labels,
>> so at the end I removed the labels. Now I have one map visible and  
>> I want
>> it to slowly get transparent to a point when it is no longer visible.
>> And here lies the problem. The script is fairly easy:
>>
>> wait;
>> movie record directory /Users/jean-paularmache/tmp-chimera;
>>
>> volume #1 transparency 0.0; wait;
>> volume #0 transparency 0.0; wait;
>>
>>
>> volume #0 transparency 0.05; wait 3;
>> volume #0 transparency 0.1; wait 3;
>> volume #0 transparency 0.15; wait 3;
>> volume #0 transparency 0.2; wait 3;
>> volume #0 transparency 0.25; wait 3;
>> volume #0 transparency 0.3; wait 3;
>> volume #0 transparency 0.35; wait 3;
>> volume #0 transparency 0.4; wait 3;
>> volume #0 transparency 0.45; wait 3;
>> volume #0 transparency 0.5; wait 3;
>> volume #0 transparency 0.55; wait 3;
>> volume #0 transparency 0.6; wait 3;
>> volume #0 transparency 0.65; wait 3;
>> volume #0 transparency 0.7; wait 3;
>> volume #0 transparency 0.75; wait 3;
>> volume #0 transparency 0.8; wait 3;
>> volume #0 transparency 0.85; wait 3;
>> volume #0 transparency 0.9; wait 3;
>> volume #0 transparency 0.95; wait 3;
>> volume #0 transparency 1.0; wait 3;
>>
>>
>> #movie finished
>> movie stop;
>> movie encode bitrate 12000 mformat avi output
>> /Users/jean-paularmache/Desktop/firstmovie.avi
>>
>>
>>
>> Ok, what happens is that Chimera generates endless amount of images.
>> Really, without cease. Now, if I do "movie stop;" from the command
>> line, it generates the avi file. However, the whole avi file consists
>> of one frame movie (meaning that even though it has the right  
>> amount of
>> frames, all are just one frame).
>> What is more surprising is that with other scripts this transparency
>> works. It is just right here that it doesn't want to cooperate.  
>> Could you
>> think of any reasons it might be behaving like that?
>>
>>
>> Best regards,
>>
>> Jean-Paul Armache




More information about the Chimera-users mailing list