If you have been using ParaView for a while, you have no doubt encountered at least one of these dialogs:
While both configure how images were saved out from ParaView, they unfortunately offer different set of options. Notably, when saving animation dialog doesn’t have options to save a single view (it always saves all views in the app), or change the color palette. Furthermore, the Python API for both of these operations is inconsistent and lacking features. For example, despite having means to change the color palette in the UI, the Python API to SaveScreenshot has no mechanism to do that. Also, one could not simply request an image of specific resolution using the Python API, but instead as a magnification factor of the current view size — which was a major inconvenience, in my opinion.
Changes slated to be available in the next release of ParaView (version 5.4) address these issues. Here are the new versions of these two dialogs:
It is fairly obvious that both have similar options with a few more animation specific parameters in the Save Animation Options dialog. Some of the other salient features of this change are as follows:
Separator Options: when saving multiple views in the active tab (or layout), you can specify a separator width and color directly from this dialog. In the previous versions, these options were configured from the Settings dialog. They have been removed from Settings, and now available when saving images/movies.
Transparent Background: when saving PNGs, this option allows you to save out images with transparent background. This option, like separator options, has moved from Settings dialog, making it more obvious and available when you need it.
Python API: Besides the UI, the Python API too has got a face lift. As always, the easiest way to learn the new Python API is to use Python Tracing capabilities in the UI. Choose options in the dialog as you like, and the trace will generate the script to do the same in Python. These include simple.SaveScreenshot and simple.SaveAnimation functions. simple.WriteImage and simple.WriteAnimation while still supported are now deprecated and it’s strongly suggested that you update your Python code to use the new methods. Likewise, old arguments to simple.SaveScreenshot which include magnification are also supported, but cannot be used together with the new options. See the ParaView Python API docs for details.
C++ API: These changes have some impact on the C++ API for custom applications. Please check the major API changes page for details and feel free to use the mailing list if you have any issues with porting old code.
10 comments to Improvements for saving screenshots and animations in ParaView
Moving the ‘transparent background’ checkbox to the save screen/animation dialog boxes will be greatly welcome. I need to toggle this option frequently and am always either forgetting that it’s set/unset, or I’m spending a lot of time hunting and pecking for it in settings.
I hear ya! I too have been burnt by it in the past.
I am using Paraview 5.4.1 on Mac OS X, and I can not see the ‘Save Animation with advanced options window’. This is a big problem as I can not make the movies produce a frame rate that is reasonable. I only can specify the resolution and Colouring.
Did you try clicking on the “gear” icon next to the “Search” bar to see advanced properties? See https://blog.kitware.com/effectively-using-the-properties-panel-in-paraview/
Thank you that explains a whole lot. I was unaware of the new changes in the UI (my fault for not reading the release notes). that said I am still not happy with the documentation/ tutorials on animations, as there are large behaviours that seem like they should be easy but seem much harder in the new version.
Josh, feel free to offer any specific ideas on what needs to documented better or what UX can be improved. We’ll surely be glad to update, if that seems reasonable.
tell me where to send it and I will get on it next week. (friday afternoon here). I have been trying to build an animation were I perform multiple orbits toggling objects on and off to show different features. Problem being adding extra orbits is a non-trivial task, as I need to build the orbit from the ground up. I feel that there should be a clone option for camera path, but I do not see this in the user guide/ tutorials or even just an easy poke in the properties.
I’d recommend the paraview users mailing list (https://www.paraview.org/mailing-lists/) as that’s a good place to discuss suggestions. If you have specific fixes/bugs, for example, reporting an the issue tracker (https://gitlab.kitware.com/paraview/paraview/issues) would be best. thanks.
thanks will do
While exporting plots or contours, there is lot of irrelevant white space, how to get rid of this redundant and get compact plots with only relevant data, just like in tecplot one can manipulate how much area should the plot cover from left, right, bottom and top side.