When can we stop making 32-bit plugins?

[A_SN]

How many of you would be bothered if developers stopped making 32-bit versions of their plugins? Are people still using 32-bit hosts, and if so, for how many more years? I'm guessing that if a lack of 32-bit plugins may or may not be a problem now it might be much more acceptable in a few years, obviously at some point everybody will have moved on, I'd like to know when!

The downsides for developers aren't huge, but making more builds is tedious, having to make 32-bit versions makes us think twice about using certain things (like 64-bit integers for instance, and I think some things are not available, like OpenCL maybe?), which is why I want to figure out when it will be okay for me to stop caring about 32-bit versions.

I probably wouldn't do that, but what if let's say I released a new version of SplineEQ and there's just no 32-bit version anymore?

[SirkusPi]

I think the only real answer is "it's OK to stop making 32-bit plugins as a developer when the market is small enough it's not worth your time." I mean, I don't think there's any kind of "moral" obligation to continue supporting technology that's not sufficiently profitable -- we're talking plugins here, not food.

Me, I haven't bought a 32-bit plugin in probably 4-5 years. When enough people are like me that sales aren't compensating you for the hassle, then stop.

[A_SN]

But that's the question! When will the market be small enough? I have no idea if my users still use the 32-bit build or not.

[ZeePok]

 
My opnion is: as long as OS-makers release 32-bit versions of that OS there will be people who want to use it and they will need 32-bit plugins.

I never had the desire to go 64-bit. Just too much hassle for me!

So I will be using 32-bit software until my computer (or I) give up the ghost!

[Googly Smythe]

But that's the question! When will the market be small enough? I have no idea if my users still use the 32-bit build or not.

Can you not separate the one installer into several (32-bit, 64-bit...) and see how many of each is downloaded? A lot of devs seem to do this these days.

[No_Use]

 
I never had the desire to go 64-bit. Just too much hassle for me!

So I will be using 32-bit software until my computer (or I) give up the ghost!

Same here.
edit: Voted too.

[A_SN]

But that's the question! When will the market be small enough? I have no idea if my users still use the 32-bit build or not.

Can you not separate the one installer into several (32-bit, 64-bit...) and see how many of each is downloaded? A lot of devs seem to do this these days.

That's an idea, yeah. I put it all in the same ZIP file though, Mac, Windows, VST, AU, 32 bit, 64 bit, so at the moment I have no data. But it would be great if other developers had such data, even better if we could know the evolution throughout the years!

ZeePok: Wait, you still use a 32-bit OS?? Why? There's a very good reason for using 32-bit hosts which is using old plugins, but I can't think of any for using a 32-bit OS (except not being bothered to upgrade... in a very long time!)! You're stuck with 2 GB of RAM max for instance! You know you can very well use a 32-bit DAW on a 64-bit OS right? I'm guessing your computer must be pretty old too, not that there's anything wrong with that if you're happy with how it works of course.

[Aloysius]

I use 32 bit and wouldn't mind if developers stopped producing 64 bit plug-ins.

[Pyrotek45]

32bit for me all the way, im not switching until everything has caught up to 64. not to mention there are some great old vst's i use that are only 32.

[shidostrife]

 
My opnion is: as long as OS-makers release 32-bit versions of that OS there will be people who want to use it and they will need 32-bit plugins.

I never had the desire to go 64-bit. Just too much hassle for me!

So I will be using 32-bit software until my computer (or I) give up the ghost!

Any specific reasons? What's the hassle?

To OP: I've been using 64-bit OS and hosts forever, but only completely ditched 32-bit plugins after cubase 9, as it doesn't have built-in bridge.

[ATN69]

Just bought a new computer and decided to only install 64-bit in those cases I could choose. There are a few 32-bit plugs I still use but luckily enough they been working fine with the IL-bridge.

[thecontrolcentre]

I still find it useful to have both, but I think its likely that devs are going to move to 64bit only. Live 10, for example, will only support 64bit OS's ... I keep a few 32bit plugins around for use in Sound Forge, which still doesn't support 64bit plugins. Everything else on my system is 64 bit.

[melomood]

Wait....there's 64bit now?

[ATN69]

Wait....there's 64bit now?

Not really. You just install the 32-bit version 2 times and that's it.

[aciddose]

But it would be great if other developers had such data, even better if we could know the evolution throughout the years!

Since I've provided 64-bit versions (~2008) 32-bit has never been above 50%. The past two days 32-bit has made up 37% of downloads but to get real numbers you would need to track installations using a server ping.

For example in your installer you can insert a download of a bitmap for a logo and include the version number in the request. By tracking distinct IP addresses accessing the resource you can get a rough estimate of actual installations.

I do not collect this data but I would guess 32-bit installations make up a far smaller percentage. 90% of 32-bit downloads are accompanied by 64-bit downloads with the clicks/requests approximately 2 seconds apart: 64-bit first followed by 32-bit. Most curious is the fact that left-to-right the 32-bit download link appears first.

The really difficult thing is that it is impossible to discern bots/scripts/etc from actual users without using a ping in the installer. I'd recommend you place this on the post-install page to ensure the product has already been installed before the ping occurs (otherwise you'd technically be measuring how many times the installer is run, not actual installations.)

Such an action requires a start-page with an EULA that disclaims liability and grants permission to transmit the request. Most people will click through such an EULA anyway, so it's a simple cure for the potential legal issues of collecting such statistics. You can see these "pings" present in a huge number of product installers and even applications once you know where to look for them. My systems for example use a white-list for network connectivity due to such things.

I wouldn't recommend attempting to collect statistics from applications/plug-ins directly but this is also extremely common.