Viper｜1.2.2 update with bugfixes and new skin

[Halonmusic]

G-Sonique afaik uses custom code inside SE world. Shame they don't do the final piece with fully c++ or similar..

I thought G-Sonique used SM/FS?

They do.

That's what i though.

They use a plugin wrapper with a built-in bit bridge (developed by the guy behind jBridge), in which they place their plugins.

Didnt know that. Thanks.

[xbitz]

any news ?

[adamszabo]

Yes Im hard at work on making the youtube video and finalizing all the sounds. I didnt have any time to work on it on the summer unfortunately so I need a little more time, but its very very close

[Cyforce]

... but its very very close

Good to here that news

[v1o]

Another widespread misconception is the belief that there is this big difference between SE and C++. (As if SE plugins were made of some mysterious material that just kinda exists but nobody really knows what it is.) Not surprisingly i say, because there simply is no such thing. As far as i was able to see, practically all of the SE stock modules ARE written in C++ and the same goes for the vast majority of 3rd party modules too. (Ive seen a few modules by one single developer (Christian Budde if i remember correctly) which were written in Delphi but thats it.) So the idea that there should be this big huge difference in quality if only the plugin was converted from 'SE' (you know, the mystery stuff) to C++ is just crazy because in like 99% of the cases the code already is C++ and in the rest of the cases it would probably be Delphi, which of course doesnt sound any different either.


Anyway. Just thought id mention it.

Just because SE is written in C++ doesn't mean that there isn't anyone overhead in using it. There is no one size fits all. Writing your own bespoke code is faster usually if you know what you are doing.

[LeVzi]

Regarding G-Sonique , from their website :

4. Is it true that your instruments are created using the SM program from Outsim Ltd.?
Yes but actually we do not use the inner modules only. The final product is a combination of SM modules and our own algorithms written using code
module in C++ Alike and Assembler language. This means there's no way to create our products by SM program with using its standard modules only.
Thankful to the SM we are able to use programming environment where we are able to hear the results of our codes and virtual circuits in realtime to catch
the best sound. SM environment is very similar to the analog domain, where we began with sound processing and many of our plugins have a very similar
inner structure as a real analog circuits.

[Nside]

Any update Adam, looking forward to hearing some new bits

[adamszabo]

Yes, as mentioned above I am working very hard on the sound demos and youtube video. I really want to impress everyone so it takes a bit of time to make it just the way I want it, but its very near to be complete.

[Elektronisch]

Cant wait to demo this because my Virus Ti is driving me nuts

[commodore]

Yes, as mentioned above I am working very hard on the sound demos and youtube video. I really want to impress everyone so it takes a bit of time to make it just the way I want it, but its very near to be complete.

Thanks, I can't wait to try it. I remember this being talked about since last year, and very eager to hear more of it in action. Sorry if this was asked already, but will there be a demo or trial we can download?

[adamszabo]

Sorry if this was asked already, but will there be a demo or trial we can download?

No problem, yes there will be a demo of course, with the manual uploaded on the site too so everyone can check it out before deciding if its something for them or not.

[Halonmusic]

A bit off topic buy do you have any plans on adding new features to J8p in the future adam?

[adamszabo]

A bit off topic buy do you have any plans on adding new features to J8p in the future adam?

You mean JP6K? Yes Ive had some thoughts about that. JP6K was meant to be a tiny project, but if I were to do any new features or updates it would eventually grown into a much bigger synth and the interface and whole design is not suited for that. So I thought I would do a new version JP7K or called something else, and start from scratch. I learned a lot when creating Viper, and I could code much more efficiently now, so if I were to make JP7K I would want to model the whole jp8000, the other waveforms, proper envelopes and filters, chorus and effects, everything. But this is a project for the distant future haha. I also have to see if Viper will become successful or not, because if I wont get any support for my hard work, then there is no point in making the new JP7K.

[chk071]

Awesome.

[Halonmusic]

A bit off topic buy do you have any plans on adding new features to J8p in the future adam?

You mean JP6K? Yes Ive had some thoughts about that. JP6K was meant to be a tiny project, but if I were to do any new features or updates it would eventually grown into a much bigger synth and the interface and whole design is not suited for that. So I thought I would do a new version JP7K or called something else, and start from scratch. I learned a lot when creating Viper, and I could code much more efficiently now, so if I were to make JP7K I would want to model the whole jp8000, the other waveforms, proper envelopes and filters, chorus and effects, everything. But this is a project for the distant future haha. I also have to see if Viper will become successful or not, because if I wont get any support for my hard work, then there is no point in making the new JP7K.

Right, JP6K was what i meant. So you've thought about it, cool. Hope Viper gets a lot of love. Will Deffo demo it when its released, maybe even buy it.