On 16/02/07, Prabhu Ramachandran <[EMAIL PROTECTED]> wrote: > >>>>> "Angus" == Angus McMorland <[EMAIL PROTECTED]> writes: > > Angus> Now I have new problem with mayavi (which I'm running from > Angus> a recent svn). Whenever I try to save snapshots from the > Angus> render window I get out garbage files like the one > Angus> attached. The pattern of the lines is affected by the > Angus> actual image, i.e. rotation does change the output garbage, > Angus> but re-capturing the same image does not. > > Wow, never seen that kind of output!
In my meanderings through parameter space I've also been able to generate snapshot images where the bottom-most band of the image is rendered/saved correctly,but the rest of the image is full of repetitions of the top-most good line from the lower band. > Angus> Screen rendering is still fine, so I've been able to take > Angus> screen captures without problem, and that's fine for > Angus> stills. However, now I'd like to render a reasonable number > Angus> of movie frames, and built-in snapshot capabilities would > Angus> be appreciated. > > How exactly are you making these snapshots? Those outputs were produced by clicking on the "Save" button in the GUI. After your other email in this thread, I tried using mv.engine.current_scene.scene.save(filename), which I hadn't known about until then. Using that method to save images did _not_ seem to suffer the same problem, and so I've been using that since. Interestingly, I cannot peruse the scene object members using ipython's browsing features, as in: s = mv.engine.current_scene s.scene.<tab> current_scene and even children of s.scene, as in s.scene.camera, work as expected by printing a list of the available items belonging to that object. Any ideas why that behaviour occurs? > Angus> A couple of other data points that may help: 1) the problem > Angus> exists with all image formats, i.e. specifying snapshot.jpg > Angus> also gives similar garbage); 2) tvtk.tools.mlab does not > Angus> have this problem - i.e. its snapshot facility works okay; > > That seems absurd, since tvtk.tools.mlab and anything else uses the > same code for the Scene window! > > Angus> 3) in my attempts to generate test cases I did get it to > Angus> save 1 (out of about 12) correct snapshots, but couldn't > Angus> replicate that. > > Can you clarify what exactly you did to get this behavior? How did > you generate the snapshot, what platform, what version of VTK? I've also, after playing around a bit more, discovered another solution to the problem which is to reduce the 'anti-aliasing frames' property of the tvtk scene object to zero or one frame, from the default eight. I'm running debian testing with vtk 5.0.2-4, on both an i686 and an amd64 and got similar behaviour on both. Thanks again, Angus. -- AJC McMorland, PhD Student Physiology, University of Auckland ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ MayaVi-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mayavi-users
