Viper｜1.2.2 update with bugfixes and new skin

[MyCo]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

[wagtunes]

I'm not going to buy Viper in the HOPES that MAYBE JBridge works with it as there are no refunds with VST purchases.

Why you don't try out it with the demo of Viper?

Because I do not enjoy demoing VSTs that emit noise every 60 seconds. I have found with 32 bit apps and Cubase, it takes a good hour of straight use before I can be sure that the app won't crash my system. Sometimes it happens sooner, but in most cases, between 30 minutes and 60 minutes I'll get the "VST Connection Lost" message and have to reboot my DAW. I choose not to have to put up with an hour of demo noise for a 32 bit app that costs 89 euro (over $100) US when there are plenty of 64 bit apps available that I don't have to wrestle with.

I hope this is a sufficient enough answer for you.

Maybe Adam can modify the interval of the noise. Would be good for sure.

Anyway, it's your decision but thinking pragmatical i would set it just on loop and looking after a hour if it's still running.

Well, it's a pretty substandard way of demoing a synth. I don't get to work with the controls, hear what it sounds like, see if I even enjoy the workflow.

And again, at over $100 US currency, there are plenty of 64 bit options that I don't really need to concern myself with the app for the time being. I'm patient enough to wait for a 64 bit release. And if it doesn't happen, well, it's not like I don't already have over 100 VSTs.

I'll survive.

In all honesty, I feel badly for the dev. I think his sales are going to suffer a lot. And, as somebody else pointed out, it's a catch 22. With weak sales figures, there's really no incentive to make a 64 bit version. At least I know I wouldn't. And yet, the weak sales figures will be a direct result of not having a 64 bit version.

It's kind of ironic when you look at it like that.

But like I said, I'm patient and I'll survive without it.

[wagtunes]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

I think you're making an assumption here based on absolutely no empirical data. I own over 100 VSTs. In fact, as a sound designer, I buy every new VST that comes out if it's 64 bit if for no other reason than to create and sell a library. And you really don't know how many people love the sound of this synth and aren't buying it solely because it's 32 bit. Especially since 60% of the people on Windows 7 are using 64 bit and 85% to 90% of the people using Windows 8 are using 64 bit. Yes, I looked up the data earlier.

So the truth is, you really don't know what percentage of users are staying away from this software only because it's 32 bit. It could be a lot more than you realize.

Unless you have some data to back up your statement.

[Stefken]

If there was a good solution

Like Bitwig or Reaper which runs the plugin (flawlessly) in a separate processing and if the app crashes, the DAW continues to work?

Right, Ableton is about 600 euros. I'm gonna buy and learn a new DAW because of one synth?

Not gonna happen...

[Halonmusic]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

This.

[MyCo]

Especially since 60% of the people on Windows 7 are using 64 bit and 85% to 90% of the people using Windows 8 are using 64 bit. Yes, I looked up the data earlier.

You are not even close. Just because the OS is 64bit doesn't mean the DAW has to be 64bit. And then you can overlap that with the DAWs in use. And even then it is the subset of 64Bit only DAWs with users not wanting to use a bridge... this is not more than 1% of all VST users.

[swatwork]

If i were project manager I would either hire another programmer or send the programmer to 'school' to learn a more suitable framework. Or let him do pair programming with a programmer that knows that framework so he can learn it at the workplace.

No disrespect intended, but this is breathtakingly clueless. Are you sure you're not a project manager?

I suggest you start at the beginning of this thread and work your way through it, Adam has discussed his reasons for choosing Flowstone several times.

@Adam: fantastic job by the way. I've dabbled with SM/FL quite a bit over the years and what you've managed to achieve is hugely impressive.

[wagtunes]

Especially since 60% of the people on Windows 7 are using 64 bit and 85% to 90% of the people using Windows 8 are using 64 bit. Yes, I looked up the data earlier.

You are not even close. Just because the OS is 64bit doesn't mean the DAW has to be 64bit. And then you can overlap that with the DAWs in use. And even then it is the subset of 64Bit only DAWs with users not wanting to use a bridge... this is not more than 1% of all VST users.

That's true. But we've already had a number of DAWs go to 64 bit only. Based on current trends, by 2023, there isn't going to be any 32 bit left to speak of. Now granted, by 2023 this plugin will hopefully be in 64 bit form. But like I said, I have plenty of patience. I can wait.

That sales are going to be lost because of 32 bit only isn't even disputable. What neither of us knows, again unless you have definitive numbers, is what percentage of sales will be lost.

I don't think either one of us knows the answer to that question. And to say it's just 1% is pulling a number out of a hat without anything to back that up other than your opinion.

Again, unless you have data that you can show me.

[Stefken]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

Closing arguments

Then as a developer you are depriving yourself of a large market segment if you won't bother with the 64 bit segment. Not smart.

Also make 64 bit your primary release. Not an afterthought. This is a volatile market. When you finished porting, your competition might have taken over the spotlight.

[MyCo]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

Closing arguments

Then as a developer you are depriving yourself of a large market segment if you won't bother with the 64 bit segment. Not smart.

You should read it once again. I don't say 64bit is worthless, I specificly say: Caring about those who complain isn't worth it!

[chk071]

Caring about those who complain isn't worth it!

You're right. The decision to serve the biggest market should have been made in the first place.

Again, i do understand the reasons why this hasn't been done in this case. I don't quite get the reasoning behind developing a 64-bit version, "when this will be a success" though. It won't be as big as a success as if it had been 64-bit in the first place for sure.

[MyCo]

If i were project manager I would either hire another programmer or send the programmer to 'school' to learn a more suitable framework. Or let him do pair programming with a programmer that knows that framework so he can learn it at the workplace.

No disrespect intended, but this is breathtakingly clueless. Are you sure you're not a project manager

hehehe... I thought the same.

[wagtunes]

I wonder how many of those "won't buy it because 32bit" complainer actually buy it when the 64bit version gets released... like 1%? As a developer I don't want these guys as customers either, the trouble wouldn't be worth it, tbh.

Closing arguments

Then as a developer you are depriving yourself of a large market segment if you won't bother with the 64 bit segment. Not smart.

You should read it once again. I don't say 64bit is worthless, I specificly say: Caring about those who complain isn't worth it!

Again, you're making the huge assumption that the 64 bit market is minuscule. Now maybe Adam doesn't care. Maybe he has a full time job, makes plenty of money doing that, and is just doing this as a hobby and for fun and thus is only doing what he can do without making himself crazy. In that case, then there is no question that 32 bit only is the way to go because it gives him the least amount of grief as far as customer support, especially since he will undoubtedly have fewer of them to contend with.

But from a pure numbers standpoint, he will absolutely lose sales.

There is no disputing that.

[Stefken]

You should read it once again. I don't say 64bit is worthless, I specificly say: Caring about those who complain isn't worth it!

The complains are often made by the same small percentage so i get what you mean.

But i'm not complaining.I just won't buy it as I have plenty of synths to go round.

I hope a lot of people decide differently because as a synth it is really well made.

[MyCo]

Again, you're making the huge assumption that the 64 bit market is minuscule

No I didn't! Again: I said those who complain here in this forum and say they won't buy it are very small part. And even when a 64bit version would be available I don't want to have to do support work for those who complain beforehand in a public forum. They cause just too much trouble!