Viper｜1.2.2 update with bugfixes and new skin

[adamszabo]

Those are good ideas thanks! I think it would also help if people would review Viper on the kvr rating system, so it goes up in rank and more people discover it. So please, review Viper here on kvr, it would be extremely appreciated!

[surreal]

Would do it if I had it!

[Stefken]

Viper has a lot going for it. It certainly deserves a broader audience. When I render a track with viper I'm always amazed at how good it sounds (compared to other synths).
The arp functionality is great as well. And it has a good emulation of that Virus sound at a fraction of the price of hardware.
It would benefit from more sound sets though.

I think it is a good product but imo it suffers from the way it is communicated.
Releasing it first as 32 bit was a mistake imo. Also pointing out repeatedly: I don't have time for this now, I don't know how to do this may be very honest on your part but does not induce confidence. Maybe you should refrain from doing so and just communicate broad deadlines for new features/development.

If it is feasible you could try to bring somebody else on board to help with the coding (that would also free up time for you to make some sound sets).

Just trying to help here.

[tristan-]

Viper has a lot going for it. It certainly deserves a broader audience. When I render a track with viper I'm always amazed at how good it sounds (compared to other synths).
The arp functionality is great as well. And it has a good emulation of that Virus sound at a fraction of the price of hardware.
It would benefit from more sound sets though.

I think it is a good product but imo it suffers from the way it is communicated.
Releasing it first as 32 bit was a mistake imo. Also pointing out repeatedly: I don't have time for this now, I don't know how to do this may be very honest on your part but does not induce confidence. Maybe you should refrain from doing so and just communicate broad deadlines for new features/development.

If it is feasible you could try to bring somebody else on board to help with the coding (that would also free up time for you to make some sound sets).

Just trying to help here.

Ditto. I think the same about the "32 bit fiasco". What else? I'm not sure if an entire synth development cycle has to be completely and openly communicated. Think about Dune, Serum, Sylenth1, all the others. They're just out there, and that's good enough. There are probably people who think that this synth is the same as the bluearp project, or Charlatan, or whatever freebie is being developed in a community effort.

I'd like to see this synth featured in Future Music, Computer Music. I'd like to see it reviewed in YouTube by users like PlugInGuru etc. How do you do it? that's a question. but the quality is there.

[adamszabo]

Yes I the 32 bit issue might have tainted the synth a bit, but I hope that when I make soundsets for it, it will be quickly forgotten. On the other hand, I like to communicate with customers and people who are interested in Viper, I hate when a developer is totally silent and no one knows whats going on. I feel it is important to let everyone know that Viper is actively being improved, and many features and sounds are coming so its a good investment. I also agree that I need to improve my marketing strategy as well

@Surreal: well, there is a free demo version you can try and evaluate the sound and features to write a review

[fluffy_little_something]

I see it is made with FlowStone. Has FlowStone overtaken SynthEdit?

How big is the GUI in pixels?

Do I need Serum to survive Viper?

[anoise]

There are probably people who think that this synth is the same as the bluearp project, or Charlatan, or whatever freebie is being developed in a community effort.

This is the reply I got on this forum when I recommended Viper: "the sound quality is nowhere near the Virus. The price is pretty high for a synth that was created with a sandbox without own development."

Maybe "Everything is custom written from the ground up" should be added and highlighted also on the website, not just here, so people see it's not just another subpar flowstone synth.

So, 32 bit only on release; "made" in Flowstone = gives a subpar quality perception; no mac version; and market saturation are maybe detrimental for more success.

[tristan-]

There are probably people who think that this synth is the same as the bluearp project, or Charlatan, or whatever freebie is being developed in a community effort.

This is the reply I got on this forum when I recommended Viper: "the sound quality is nowhere near the Virus. The price is pretty high for a synth that was created with a sandbox without own development."

Maybe "Everything is custom written from the ground up" should be added and highlighted also on the website, not just here, so people see it's not just another subpar flowstone synth.

So, 32 bit only on release; "made" in Flowstone = gives a subpar quality perception; no mac version; and market saturation are maybe detrimental for more success.

Absolutely. Ditch the "made in Flowstone" and the "no MAC version" for starters. I couldn't give a d*** once the finished product sounds and plays great.

[fluffy_little_something]

Why was FlowStone used at all when the synth was hand-coded anyway, so to speak?

[adamszabo]

Because in FlowStone, everything is there to create whatever you want right from the start. And instead of figuring out how to compile shit with the Steinberg SDK and I can spend more time improving the synth.

[fluffy_little_something]

I see. I think that is also how Lennard did Sylenth1 initially, using SE as a mere framework for his own code. But he abandoned SE sooner or later, and I assume it helped his product's reputation.

[Stefken]

There are probably people who think that this synth is the same as the bluearp project, or Charlatan, or whatever freebie is being developed in a community effort.

This is the reply I got on this forum when I recommended Viper: "the sound quality is nowhere near the Virus. The price is pretty high for a synth that was created with a sandbox without own development."

Maybe "Everything is custom written from the ground up" should be added and highlighted also on the website, not just here, so people see it's not just another subpar flowstone synth.

So, 32 bit only on release; "made" in Flowstone = gives a subpar quality perception; no mac version; and market saturation are maybe detrimental for more success.

Absolutely. Ditch the "made in Flowstone" and the "no MAC version" for starters. I couldn't give a d*** once the finished product sounds and plays great.

+1

You talked about better marketing?
Ditch it. Put 64 bit in front; then 32 bit.
Perception is reality.

[eyezermusic]

I think one reason why Viper hasn't yet reached any larger attention is because most people follow the herd and what's cool. If the famous producers uses Sylenth1, Spire, Serum etc, then everyone else will follow. Then imo, Viper has a sound characteristic that don't fit with modern EDM. It could perhaps just be me but I think Viper sounds very 2000'ish, which is why it's my favorite VST plugin. This however pretty much means it's not a synth for everyone (or the masses rather since they tend to have a shit taste). Some guy in this thread complained about too many Hardstyle videos on Youtube with Viper. That kind of proves my statement since Viper is a fantastic synth for Hardstyle music, especially if you like the 2008-2009 kind of Hardstyle. If Viper has a future (which I hope), then it will not surprise me if Hardstyle ends up being one of the most popular genres people will use Viper for.

[adamszabo]

Also dont forget that Viper is only 10 months old, while any other popular synth has been out for many years now to get around

[eyezermusic]

That's true. Time will tell and hopefully for the positive.