Viper｜1.2.2 update with bugfixes and new skin

[Dip200]

On another note: Does anyone have the wavetables of the Virus TI WITHOUT Interpolation recorded ? Afterall Viper should handle the interpolation.

[VELLTONE MUSIC]

Trance spirit in vst body = Viper :):)

[Syngularity]

Update w/o cpu spikes?

[Dip200]

I know that's it's hard to implement the grain and formant oscillators but what about the Wavetable PWM oscillator ? Any chance that we will see it implemented at some point ?

[plrdmus]

Honestly, the only thing this synth need compared to similar alternatives is growing an userbase.
Also fixing the cpu spike bug, but let's leave that to DSPRobotics

[Echoes in the Attic]

I'd love to use this more but the cpu spikes are keeping me from loading it more. How's progress on that coming, after the recent discovery that the small delay of a wrapper fixes it?

[adamszabo]

There is an update very soon which fixes crashes and lowers the cpu spike and improves performance. I showed the wrapper delay thing to the dev but he mentioned it not easy to do so we have to live with that for now

[monophonK]

There is an update very soon which fixes crashes and lowers the cpu spike and improves performance. I showed the wrapper delay thing to the dev but he mentioned it not easy to do so we have to live with that for now

Update with an new Sale?

[Vortifex]

Edited

[Dip200]

... growing an userbase. ...

A few small steps could be done that may help:

- Lock this topic and start a new thread once 1.06 is out. This thread is potentially turning off people. To much nonsense about 32 bit, pricing and what it means to use an integrated development environment.
- Emphasize that the audio engine is written in assembly and ruby (iirc) on the webpage
- Create a sexier looking GUI. (OK this is not a small step)

[plrdmus]

... growing an userbase. ...

A few small steps could be done that may help:

- Lock this topic and start a new thread once 1.06 is out. This thread is potentially turning off people. To much nonsense about 32 bit, pricing and what it means to use an integrated development environment.
- Emphasize that the audio engine is written in assembly and ruby (iirc) on the webpage
- Create a sexier looking GUI. (OK this is not a small step)

Yes, to make it perfect it would need:

-Better skin. It's not bad, but looks matters and the first impression means a lot. Mentioning FS makes it seem amateur-ish even if it's not.
-More soundbanks. I've read some comments about importing Virus banks too. That would be amazing.

[Echoes in the Attic]

I think the GUI looks great. I don't see what should be improved about it. Wouldn't mind multi-touch. But really just want these cpu spikes dealt with.

[plrdmus]

I think the GUI looks great. I don't see what should be improved about it. Wouldn't mind multi-touch. But really just want these cpu spikes dealt with.

I don't think it's bad, although a slightly different GUI could attract more users.
Maybe adding different color schemes (with different backgrounds) but not much else

[izonin]

... growing an userbase. ...

A few small steps could be done that may help:

- Lock this topic and start a new thread once 1.06 is out. This thread is potentially turning off people. To much nonsense about 32 bit, pricing and what it means to use an integrated development environment.
- Emphasize that the audio engine is written in assembly and ruby (iirc) on the webpage
- Create a sexier looking GUI. (OK this is not a small step)

Ruby is not the best choice for realtime audio, as it uses garbage collection (those CPU spikes).

Also I agree about the GUI. Hire a pro designer, it will pay off.

I must say I love how the synth sounds. The only area that needs some further tweaking is the filter response. It's not 100% accurate.

[adamszabo]

Ruby is not the best choice for realtime audio, as it uses garbage collection (those CPU spikes).

Also I agree about the GUI. Hire a pro designer, it will pay off.

I must say I love how the synth sounds. The only area that needs some further tweaking is the filter response. It's not 100% accurate.

Ok, time to make a few things clear:

I am 100% fully aware that I need more content for Viper. There will be lots of soundbanks coming in the future after the new site is done.
There are plans to have user skins so everyone can make whatever GUI they wish.

Only the audio engine is in assembler, Ruby is only used for GUI and non audio calculations, it has nothing to do with the CPU spikes (except the ruby midi handling)