That's a great question, and you've hit on the key to a proper FX chain! You are totally right—if you're filtering the dry signal, it means your filter is in the wrong place.
To fix it, you need to make sure your Low-Cut/High-Cut filters are only placed inside the 'Wet' signal chain (the one that holds the reverb module). If you have your setup using a Split container (as discussed earlier), the dry signal should be on one side (no filters), and the reverb + filters should be on the other side.
That should keep your dry signal clean!

Whew, glad you got this sorted out!
That's an awesome update—it's super useful to know that tweaking the Mac display settings made the tools/grid visible. And thanks for confirming that the interface script issue d.healey mentioned was also part of the initial problem.
Definitely helpful for anyone else who hits a weird UI scaling bug!

Ah, I know that feeling! It seems like HISE just gets into a strange state sometimes.
Good call on just remaking the network from scratch. If everything is wired up correctly and works the second time, it usually means there was just a hidden, strange corruption in the original network that was failing the compiler.

That sounds frustrating!
I'm running into the exact same weird behavior with the Macro LFO pausing for a few cycles right after a note-on/note-off. It totally breaks rhythmic effects.
Did you ever find a fix for this, or did it resolve itself in a newer HISE build? Super annoying! Let me know if you figured it out.

Totally agree that the stock table is really showing its age! The clunky right-click curve control and that annoying single-pixel movement resolution are definitely the biggest pain points.
I think the suggestion to introduce a "Flex Table"—just like the Flex Envelope—is the perfect path forward. It keeps the workflow consistent and, most importantly, avoids breaking backward compatibility for existing projects, which would be a nightmare.

A curve node system would make this component feel instantly modern. Great ideas everyone!

Hey! You're on the right track with copying the XML data, but there's one small, crucial step you're missing!
When you duplicate the network and paste the XML into the new file, you have to open the new .xml file in a text editor and change the unique ID/name right at the top of the file.
The HISE compiler uses that unique identifier to distinguish the network. If two files have the exact same ID, HISE gets confused and only loads the first one it finds.

Just change the name/ID string in the duplicated file, save it, and it should pop right up! Hope that helps!