64 vs 32 bit FIGHT FIGHT FIGHT!!!

[braj]

I'm only posting this to give the discussion in the Korg thread somewhere to go. So, do you have an opinion on 32 bit support in 2018? Post it here.

[ATS]

I'm only posting this to give the discussion in the Korg thread somewhere to go. So, do you have an opinion on 32 bit support in 2018? Post it here.

yeah who cares, it's defeated tech

[chk071]

IMO, everything which had to be said has already been said in the Korg Legacy Collection thread.

[braj]

IMO, everything which had to be said has already been said in the Korg Legacy Collection thread.

I agree, but people keep saying it, over and over, even when asked politely by Hink to stop, so obviously there's a 'market' for it.

[chk071]

I think the only reason why Hink intervened is because it was a bit on the limit in terms of personal stuff. Which i agree it was. But, frankly, the 32-bit crew is so religious over their point, while displaying such a small portion of the market, that it makes no sense to rationally argue with such people.

[foosnark]

There is no good replacement for ET-301, Night Flight, and some others. I'll stay with 32. There is nothing "religious" about it.

[braj]

There is no good replacement for ET-301, Night Flight, and some others. I'll stay with 32. There is nothing "religious" about it.

I happily am using both, 64 bit host with a few 32 bit plugins bridged.

[ATS]

I use only 64 bit myself. I moved on.

[chk071]

There is no good replacement for ET-301, Night Flight, and some others. I'll stay with 32. There is nothing "religious" about it.

Well, maybe i should have explained my point a bit better. What i meant with the "religious 32-bit crew" is the peeps advocating that it is still THAT important in 2018 to release plugins as 64-bit AND 32-bit. And they argue on and on, as if their life depended on it, while it's so obvious that the market shifts more and more towards 64-bit applications and plugins, and, for some of the biggest players in the DAW business, it doesn't even make sense to support 32-bit anymore.

BTW, if you use 32-bit, and there are 64-bit only plugins, you can bridge those as well, with jBridge. Or with Reaper 32-bit. It's really interesting that this is being brought up, whenever there's a 32-bit only plugin released, but, i never heard it, when people are crying their hearts out about developers releasing 64-bit only plugins.

[Teksonik]

One can assume that developers who are no longer supporting 32 bit have their reasons. They've done the market research and decided 32 bit support is not worth the effort. I don't think we're in a position to second guess their decision.

[chk071]

Exactly. Never got these kind of discussions.

[ontol]

I just load 32 bit plugs twice, sounds just as good and only half the calories.

[Orbit-50]

For those that use older 32-bit plug-ins, I get it, there's nothing wrong with their love for those plugins, but in the year 2018 I really don't see why developers still include both 64-bit and 32-bit versions. I'm sick and tired of directing the installers to send the 32-bit version to the trash.

[foosnark]

Eh. I was a bit annoyed when NI's Christmas gift was 64-bit only. I didn't make a fuss over it because I don't care that much.

Last time I tried to use jBridge it didn't work at all, so I haven't tried again.

[braj]

I used Jbridge when I used Live and Studio One. It worked for me. I don't know if it would work for every plugin out there though, but the bitbridge in Reaper has never failed me.