# DigitalSignalProcessing plugin limited to vtkMultiBlockDataSet inputs

**URL:** https://discourse.paraview.org/t/digitalsignalprocessing-plugin-limited-to-vtkmultiblockdataset-inputs/17682
**Category:** Development
**Created:** [August 13, 2026, 9:57pm UTC](https://discourse.paraview.org/t/digitalsignalprocessing-plugin-limited-to-vtkmultiblockdataset-inputs/17682 "2026-08-13T21:57:40Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 13, 2026, 9:57pm UTC](https://discourse.paraview.org/t/digitalsignalprocessing-plugin-limited-to-vtkmultiblockdataset-inputs/17682/1 "2026-08-13T21:57:41Z")

</div>

I am working on steps 1 and 2 outlined in the post [Deprecating MultiBlock datasets - #50 by spyridon97](https://discourse.paraview.org/t/deprecating-multiblock-datasets/4950/50)

There were only two filters in ParaView proper that did not accept `vtkPartitionedDataSetCollections` as input: **BlockIds** and **IntersectFragments**. I have changes to those filters to address that.

Now the only remaining filters that don’t accept `vtkPartitionedDataSetCollections` are in the DigitalSignalProcessing plugin:

- **ProjectSpectrumMagnitude**
- **SoundQuantitiesCalculator**
- **MergeReduceTables**
- **MeanPowerSpectralDensity**

Is there a reason that `vtkPartitionedDataSetCollections` _shouldn’t_ be supported by these filters?

@Lucas_Givord @Louis_Gombert @mwestphal

---

<div class="post-metadata">

### Author: ![Lucas\_Givord](https://discourse.paraview.org/user_avatar/discourse.paraview.org/lucas_givord/32/6851_2.png) [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [August 14, 2026, 7:16am UTC](https://discourse.paraview.org/t/digitalsignalprocessing-plugin-limited-to-vtkmultiblockdataset-inputs/17682/2 "2026-08-14T07:16:59Z")

</div>

> [@cory.quammen](#):
>
> lters in ParaView proper that did not accept `vtkPartitionedDataSetCollections` as input: **BlockIds** and **IntersectFragments**. I have changes to those filters to address that.
> 
> Now the only remaining filters t

There is no real reason, I suppose we avoid PDC because at that time, this data type was too recent when we made it initially.

TBH supporting PDC for these filters would be very nice

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 14, 2026, 1:42pm UTC](https://discourse.paraview.org/t/digitalsignalprocessing-plugin-limited-to-vtkmultiblockdataset-inputs/17682/3 "2026-08-14T13:42:33Z")

</div>

Okay, I took a stab at it over at [https://gitlab.kitware.com/paraview/paraview/-/merge\_requests/7910](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/7910) - it wasn’t too much work.