# Automatically Refreshing Pipeline from Filter Plugin Paraview-v5.8.1

**URL:** https://discourse.paraview.org/t/automatically-refreshing-pipeline-from-filter-plugin-paraview-v5-8-1/7504
**Category:** ParaView Support
**Created:** [June 28, 2021, 7:23pm UTC](https://discourse.paraview.org/t/automatically-refreshing-pipeline-from-filter-plugin-paraview-v5-8-1/7504 "2021-06-28T19:23:13Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Joachim\_P](https://discourse.paraview.org/user_avatar/discourse.paraview.org/joachim_p/32/9596_2.png) [@Joachim\_P](https://discourse.paraview.org/u/Joachim_P)
#### Post date: [July 14, 2021, 10:04am UTC](https://discourse.paraview.org/t/automatically-refreshing-pipeline-from-filter-plugin-paraview-v5-8-1/7504/3 "2021-07-14T10:04:34Z")

</div>

Hi,

You may consider to take a look at this answer:

> [@Live point cloud visualization plugin](https://discourse.paraview.org/t/live-point-cloud-visualization-plugin/1795/2):
>
> Hi, In the code of [VeloView](https://github.com/Kitware/VeloView) (which basically is a bundled ParaView+LidarPlugin), the timesteps of ParaView is changed by the main code, not the Lidar Plugin. We advice you to start from VeloView code, which is much closer to your goal. If you really want to start from scratch within ParaView, you need to increment this requested timestep yourself. Newest version of VeloView (unreleased) uses the same mechanism as ParaView “LiveSource” plugin (available in 5.6+), where the plugin tells ParaVi…

HTH.

---

_[View the full topic](https://discourse.paraview.org/t/automatically-refreshing-pipeline-from-filter-plugin-paraview-v5-8-1/7504)._
