PizMIDI plugins binaries for Mac

#1

It seems to have become very difficult to find built versions of the popular ‘Insert Piz Here’ plugins. The author’s website seems to have been down for several years and it’s very hard to find compiled binaries and if you do, it’s unclear whether they are a safe source.

The source is available on GitHub (https://github.com/jpauwels/pizmidi) but unless you’re a software developer, these are no use to you. Even if you are, as they stand, it’s a headache to build them because of bizarre ancient and somewhat strange configuration settings.

So we’ve taken the liberty of building binaries from these source files and are making them available on our website solely for the convenience of our users. We’ve only tried a couple of them very briefly and we have no idea if they all work.

Just to be clear, these plugins are provided with absolutely NO WARRANTY, NO GUARANTEES, NO NOTHING. If you download them and/or use them, you 100% indemnify us against any and all losses and/or expenses arising from any problems with them.

We’re not supporting them or planning to fix any bugs.

Use them completely at your own risk. Do not call us for any help. If they work for you, great. If they don’t, sorry about that!

You can download an archive of the plugins for OS X below.

Download Insert Piz Here for OS X

One of our users (thanks, @themaartian) already had the Windows 64-bit version of these plugins so they’re now available as well. Same license rules apply.

Download Insert Piz Here for 64-bit Windows

3 Likes
#2

I have the 2017-06-19 64-bit builds for Windows if you’d like them.

pizmidi x64 2017-06-19.zip (3.8 MB)

#3

Cool - that saves us some work

Thanks

#4

Here’s a 2018 version for Mac OS. All the ones I have attempted to use have worked fine. I regularly use them in my racks.pizmidi.dmg.zip (2.4 MB)

#5

Hmm, those VSTs are about 3 times as big as the ones that I compiled yesterday. Where did you get them? I wonder if they are debug versions (and if so then most likely slower code)?

#6

I also have the MacOS build with plugins 3 times as big as your ons. Don’t know where I got them from… as you said… very difficult and it took a while :slight_smile: (and in some bundles exactly the plugins I needed were missing)

Thanks for the work David!

That calms me down a bit… some years ago I spent some time trying to build them in Visual Studio but couldn’t make it work so I gave it up after some hours :slight_smile:

#7

@dhj They were recommended to me by another user of the previous VST host program I was using before GP. As I recall, they came from the creator’s web site or an approved download site (I am very cautious and NEVER download anything from mystery sites). I have used them for at least a year and a half and never had any issues. But then, I am not a programmer.

The zip file I uploaded is smaller than the one themaartian uploaded - were the actual VSTs larger than those?

#8

The ones I posted were built directly from the source code. It makes no sense that yours would be three times as big unless they were built in debug mode and so contain a lot extra information useful for developers. However, it also likely means the code isn’t able to run as fast as it could.

I don’t know this but the chances are that the ones I built will be more efficient at runtime.

As an analogy, Gig Performer is somewhere around 45-50 Mb but the debug version which we use internally is about 80Mb and is also a few percent less efficient.