When can we stop making 32-bit plugins?

[Teksonik]

Just out of curiousity, how do you handle old projects that you created before you moved to 64-bit only? This is basically the only snag I came across. Any good tips?

Since I had my new studio computer built I've only installed 64 bit plugins and DAWs (whenever possible, some plugins force you to install the 32 bit version as well. They get deleted right after install). So there are no projects that use 32 bit plugins.

For really old projects I still have my old studio computer which was Win XP 32 bit but I haven't fired it up (other than to play Modern Warfare) in quite some time. So the transition to 64 bit for me was abrupt and well considered which is probably why it was so painless. I've never looked back......

You could just install 32 bit versions of your DAWs and plugins on your 64 bit system if you want to keep working on old projects.

[Teksonik]

nothings the matter, tinkerbell. just enjoying your constant stream of the usual BS.

That's nice but no one is enjoying your incessant anti-bloat campaign. So why don't you just go outside and get some fresh air. Adults are talking here......

[ATN69]

Just out of curiousity, how do you handle old projects that you created before you moved to 64-bit only? This is basically the only snag I came across. Any good tips?

Since I had my new studio computer built I've only installed 64 bit plugins and DAWs (whenever possible, some plugins force you to install the 32 bit version as well. They get deleted right after install). So there are no projects that use 32 bit plugins.

For really old projects I still have my old studio computer which was Win XP 32 bit but I haven't fired it up (other than to play Modern Warfare) in quite some time. So the transition to 64 bit for me was abrupt and well considered which is probably why it was so painless. I've never looked back......

You could just install 32 bit versions of your DAWs and plugins on your 64 bit system if you want to keep working on old projects.

I have 2 computers now. One older laptop with 32-bit + 64-bit and a brand new computer with only 64-bit. I guess I better try to keep the old system running then. My main DAW is FL Studio and the IL-bridge is very moody. Bridging is to be avoided at any cost, all though I find some old 32-bit plugs are running just fine in bridged mode. My JP6K plug is unfortunately 32-bit only but it is a one of a kind synth and thankfully it run well in bridged mode.

[Teksonik]

Ok we better stop. We'll end up getting the thread locked.

So at this point 65% have voted "Yes I've completely moved on to 64 bit". I don't know if that's the result the OP expected but there you have it. Run the same Poll next year and I bet it's closer to 80%.

[Teksonik]

My main DAW is FL Studio and the IL-bridge is very moody. Bridging is to be avoided at any cost, all though I find some old 32-bit plugs are running just fine in bridged mode. My JP6K plug is unfortunately 32-bit only but it is a one of a kind synth and thankfully it run well in bridged mode.

So doesn't the 32 bit version of FL.exe install with the 64 bit version ? Could you just run the 32 version with your 32 bit plugins ?

You've hit on the main advantage of bit matching. No Bit Bridge.

[ATN69]

My main DAW is FL Studio and the IL-bridge is very moody. Bridging is to be avoided at any cost, all though I find some old 32-bit plugs are running just fine in bridged mode. My JP6K plug is unfortunately 32-bit only but it is a one of a kind synth and thankfully it run well in bridged mode.

So doesn't the 32 bit version of FL.exe install with the 64 bit version ? Could you just run the 32 version with your 32 bit plugins ?

You've hit on the main advantage of bit matching. No Bit Bridge.

FL Studio install as both 32-bit and 64-bit but once you open the 64-bit version and work with that, you will of course be in 64-bit, meaning that all 32-bit plugins used in a project will open up in bridged mode. It's the other way around if you open 32-bit FL Studio for work and then load up a 64-bit only plug.

As it is now I have a lot of plugs that I bought. Some of them like Avenger is 64-bit only, while JP6K is 32-bit only. I have the same situation for some FX plugs and some other synth. I guess this is how it is in a generation change. But lately I only use 64-bit for all new projects. The only exception is JP6K but that run just fine in the IL-bridge.

[Aloysius]

64bit only. I dont use freeware. I can afford quality synths.

Soundtoys LittlePlate is free right now. Are you seriously not going to use it out of ''pride''.

[AnX]

64bit only. I dont use freeware. I can afford quality synths.

Soundtoys LittlePlate is free right now. Are you seriously not going to use it out of ''pride''.

Not pride, ilok.

[Aloysius]

You don't need one. You can activate to your computer.

[AnX]

Still need an ilok account.

[Aloysius]

Oh yeah, they're free, I get it. Can't use freeware.

[A_SN]

You might want to drop 32 bit since it is just more code to support, even if it is just handled by the compiler. There can still be bugs that only show up in one and not the other, and it is a lot more compatibility testing too, especially if you do Mac/Win. You still should verify everything works before pushing out a build to your customers, even if it is unlikely something is different. So basically it costs more to support 32 bit still.

Very true, mostly if you deal with lots of memory, which can actually start being a problem even around 1 GB as memory fragmentation means that you might not find a range for a large allocation, as people familiar with Photosounder and its out of memory errors know.

Worth it for who ? One percent more sales for the developer ?

Well it's not just the money, I don't want my inbox to fill up with people asking for the 32-bit version back just like I'd get people asking for AAX or Linux builds (haven't gotten either of those in a long time though). So when 32-bit become less relevant than AAX or Linux I'll drop it.

oh yeah more RAM to load bigger samples to make projects fat and bloated. no thanks man
i'll stick to 5-10mb physical modeled and VA synths and 1mb EnergyEXT2 that loads in a split second.

I actually kind of agree with that, but then I get emails about how processing one hour of sound as a big picture makes my program crash, so sometimes it's needed. Sometimes I feel like the newest Photoshop loads in as much time on my PC as Photoshop 5 loaded on my old 75 MHz Mac, why??

So at this point 65% have voted "Yes I've completely moved on to 64 bit". I don't know if that's the result the OP expected but there you have it. Run the same Poll next year and I bet it's closer to 80%.

That's what I wanted to find out. 80% isn't enough for me to drop it, but at this rate maybe around the year 2020 will be about the right time.

[AnX]

I get it.

Seems you dont.

[Daimonicon]

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.

And with some dev´s plugins you still must install 32-bit too. Really annoying I noticed it 6 months ago when I purchased a new pc.

[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.

And with some dev´s plugins you still must install 32-bit too. Really annoying I noticed it 6 months ago when I purchased a new pc.

Some devs (Soundtoys, I'm looking at you) even install the AAX versions as well!