Now I'd like to also exploit the opportunity to drop the 32-bit plugin support. Many other devs already did that, I think it's time for Melda too. So this is just a notice, just in case many of you would start screaming like "nononono... we want to stay in 20ths century" haha
16.00 - removing the 32-bit plugin support
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Hey folks, so, V16 won't be big, it will be mainly about some further optimizations, but I want to make it a major update, since it won't be "forwards compatible" - meaning that it will use a different storage system (so way faster loading/saving of everything), which the old versions won't be able to read. So once you save your project, you won't be able to load it with older versions. This is quite normal, but I want to highlight that anyways.
Now I'd like to also exploit the opportunity to drop the 32-bit plugin support. Many other devs already did that, I think it's time for Melda too. So this is just a notice, just in case many of you would start screaming like "nononono... we want to stay in 20ths century" haha
Now I'd like to also exploit the opportunity to drop the 32-bit plugin support. Many other devs already did that, I think it's time for Melda too. So this is just a notice, just in case many of you would start screaming like "nononono... we want to stay in 20ths century" haha
-
- KVRian
- 502 posts since 14 Aug, 2012
I preemptively voice my support for dropping 32-bit. Not that having it available hurts me personally; but I understand it's a pain for you as a developer to maintain, and I expect there will likely be people complaining, so I just want to be on record as saying I believe your decision as to where to (and where not to) focus your development time is completely fair and rational. And I wish you good luck dealing with the likely blowback! 
-
- KVRian
- 811 posts since 2 Aug, 2013
Hope to see cpu optimizations for smart interpolation if possible.
- KVRist
- 377 posts since 31 Jan, 2014 from Denmark
Yes, drop 32-bit. More dev time for other things. 
I can't lie to you about your chances, but... you have my sympathies.
-
- KVRAF
- 2513 posts since 24 Jul, 2017
+1
No more ancient hardware here any more.
- KVRian
- 1094 posts since 23 Sep, 2006
Yep, would love to see 32bit gone, every install I install them into a folder and then delete them... it's a minor pain. I guess as long as you keep the oldest version with 32bit support accessible in the website somewhere then it's not a problem as it's super old tech and it'll be rare for people to want to use them.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- Topic Starter
- 14339 posts since 15 Mar, 2008 from Czech republic
You misunderstood, backwards compatibility is a must! I was talking about forward compatibility (if it is even defined), meaning that old versions can read (at least partially) settings created by newer versions.vanerio wrote: Tue Mar 08, 2022 5:55 pm Nice!
Considering that it is an irreversible change, maybe it is convenient to match some parameters between MSF and some plugins (like the vibrato rate or depth)![]()
-
- KVRist
- 59 posts since 30 Dec, 2018
I'm in support of dropping 32bit - focus on the future!
Great to hear that more optimization is inbound!
And, as alluded to by vanerio, I'm also in support of fixing some legacy items kept a certain way only for backwards compatibility - perhaps by incorporating functionality to convert pre-v16 settings/presets to post-v16 settings/presets and thus technically maintaining backwards compatibility?
And, as alluded to by vanerio, I'm also in support of fixing some legacy items kept a certain way only for backwards compatibility - perhaps by incorporating functionality to convert pre-v16 settings/presets to post-v16 settings/presets and thus technically maintaining backwards compatibility?
-
- KVRian
- 502 posts since 14 Aug, 2012
I'm (happily) amazed at all the responses coming out in support of dropping 32 bit. Where are all the naysayers I was expecting? Have we finally turned the corner and gotten to the point where everyone can acknowledge that yes, technology does indeed march forward, and sometimes older technologies get left behind? If so, then I welcome this new era of understanding!
-
- KVRAF
- 10374 posts since 2 Sep, 2003 from Surrey, UK
Naysayer here 
I have a 32-bit DAW that I sometimes use. What would be handy is to have v15.xx 32-bit plug-ins and v16.xx 64-bit plug-ins. Or will the common App Data files be a problem?
I have a 32-bit DAW that I sometimes use. What would be handy is to have v15.xx 32-bit plug-ins and v16.xx 64-bit plug-ins. Or will the common App Data files be a problem?
-
- KVRAF
- 2052 posts since 13 May, 2004 from Germany
I think it is a good idea to abandon the 32 bit plugins.
But IF the 15.xx are included in 32 bit installing them is an absolute no go. I don't even want to unselect them during every install.
But IF the 15.xx are included in 32 bit installing them is an absolute no go. I don't even want to unselect them during every install.
-
- KVRian
- 836 posts since 1 Sep, 2007
I still use a few 32bit versions as well... I would still like to be able to use them (have no need for them to be further developt)...DarkStar wrote: Wed Mar 09, 2022 12:01 pm Naysayer here
I have a 32-bit DAW that I sometimes use. What would be handy is to have v15.xx 32-bit plug-ins and v16.xx 64-bit plug-ins. Or will the common App Data files be a problem?
however, I understand dropping them.
-
- KVRAF
- 2052 posts since 13 May, 2004 from Germany
Well, you just can continue to use the 15 version....
