Unfortunately, this plugin just doesn't work... Few people before me had the same issue.
"Cannot read property (filter name) of undefined". I also tried map notes - nothing.
Tested on versions 1.2, 1.5.1 and 1.6.1.
Any thoughts?
Just to tackle the part of this I know I can answer first: this plugin can't always work properly with RPGMaker MV versions below 1.5. There's a note in the original post about it. If you don't need to use an older version for a specific reason, I'd stick with 1.6.2. (I'm pretty sure 1.6.1 works just as well with plugins, as I've never seen a break in compatibility between these two versions, but I haven't seen everything and I think it's generally a good idea to work with the latest version of any software if you can.)
Anyway, I had trouble getting this plugin to work in the beginning. It was awhile ago so I can't remember what problem I had, specifically, but I think it was similar to yours and I remember most of what I did to figure it out. First, let's get into what's happening. The plug-in is looking for a filter with the name you specified but it's undefined. That could mean one of several things. First, though, I think it'd be good to understand what's going on here so you can troubleshoot more easily.
When an errors tells you that a variable is undefined, it's like the code is doing a roll call for attendance. Rather than just mark the variable absent during roll call, the code reacts more like "f* this, I quit!" With these errors, your goal is to find the truant variable. Your error has some clues in it. We know it's not finding the "filter name" property and can't. It wouldn't be looking for the filter name property if you didn't try to add a filter to some part of your game so we can assume that the entire object is undefined. (If you're not familiar with the terms, an object is just a variable that can contain a bunch of variables in one nice little package. Events in RPGMaker are objects. When you set a self switch, for example, you're actually setting a boolean—true or false—property on the instance of an event class—or, in other words, a copy made from the "blueprint" for how events are structured.) If the entire object is undefined and you've defined it, it either means you've defined it and are referencing it incorrectly or something is unsetting/overwriting it. The error you're getting is likely one of these two things but the second can have different sources. I'll go over the likeliest possibilities.
1) Your syntax is wrong and you're using the name of the filter and not the instance name of the filter you created. If this is the case, you have a very easy fix because you just need to change the name you're referencing. If you paste in examples of the ways you've tried to create filters (map notes or otherwise) I'll know right away if this is the problem and can tell you what to fix. It's a little confusing to get the syntax right so don't feel bad if the problem is just as simple as a misplaced word. I screw it up all the time. That might be my dyslexia, though.
2) This plugin isn't working because another plugin is in conflict with it. When you make plugins for RPGMaker MV, you're writing code that alters existing classes and functions in the original code. Ideally that's done by making a copy first because then that copy will contain any changes made by plugins that run before it in the plugin order. When plugins don't do this, it can cause problems. You'll rarely find a plugin that doesn't do this, but if you have any less-common ones installed it's entirely possible that it's completely overwriting the Pixi Filters plugin and that's throwing the error. But it's also possible that you have another plugin that interacts with the same stuff, comes later in your plugin list, and is overwriting the object even if it's following the best practices for creating a plugin (that being the copying thing I just mentioned). In either case, plugin order can make or break any plugins. If you have any other effects plugins—or any sort of visual enhancement, such as overlays—try putting the PixiFilters plugin before and after those plugins to make sure the position isn't the sole issue. If that doesn't get you anywhere, try disabling every other plugin you can and test a very simple filter targeting the entire screen to see if that works. If you can't do that or it doesn't work, try creating a new game with nothing but this plugin active and try the same thing. If that doesn't work, you've probably got issue #1 or something strange and unique. While system compatibility issues are definitely possible, I'm having trouble coming up with any reason they'd cause this type of error.
3) It's also possible that you're trying to use the plugin in a way that causes an error due to a bug in the plugin's code. After fixing the issue similar to yours, I ran into something like this myself. If you scroll back a little in this thread's history you'll see the fix I posted for it. It's a pretty simple adjustment. It fixes an error similar to this, where the plugin fails to apply effects because it's looking for something that doesn't exist in a specific situation (specifically, in my case, map stuff that doesn't exist during a battle). I don't think that's what's happening in your case because your error is much more broad. Nevertheless, it's possible that you have a unique use case that causes a bug in the code. If this is the case, one of the tests in #2 will have worked for you because you'll have tested a generic map with a simple filter applied to the entire screen when on the map. So if that works and you just can't get your unique use case to work, it's possible there's a bug. It's probably not a hard bug to fix, but I'd need to know more about what you're trying to do with the filters to know where to look for that. This is unlikely, but if you're not able to fix things on your own please post your note tags (or whatever else) you're using to create and set filters. That'll tell me the location in the code that's throwing the error. Also, the full text of the error usually includes the line that failed so that's useful as well.

It's not always the correct location, but it's related to the correct location if not.
Okay, I think that's plenty to start with.

Hopefully this helps you get to the bottom of the problem! If not, please share more information. This plugin definitely does work but it's not the easiest to get to work in every situation. If you're diligent, though, you'll get it working and it's absolutely worth it to be able to use the Pixi filters. It took me a couple of hours, but it saved me from having to write this plugin from scratch myself which would've taken sooooo much longer. And you can do some really awesome things if you explore the Pixi filters beyond what's built into this plugin. There's a lot more you can do with very little JavaScript. It's not too difficult even if you don't know how to code.