Viper｜1.2.2 update with bugfixes and new skin

[adamszabo]

Not just the tiny size but also the contrast.

You can drag the corner of the GUI to make it larger

[fdigl]

I was surprised how good the JP6K sounds when I demo'd it. The only reason I didn't buy it is because it's quite limited. Great, great sound though.

I totally agree. I would definitely pay for a JP7K that becomes a more fully featured JP-80x0 emulation.

[goldenanalog]

I could in theory open and read the data thats contained in the virus .mid files, and simply convert the midi values to values that Viper understands, but the problem is legality as we discussed a few pages back. First I will ask Access if they have any problem with that, and then I can dive deeper into this.

It's ALWAYS a good idea to ask first; but in your case: you've already accurately copied their wavetables w/o a peep from them, correct? And furthermore: since their patches transmitted are in .mid format (open standard/non-proprietary format), then you'd be simply "lining up" their patch info to accurately match what their hardware synth does with that info, which (when you think about it) is what an accurate 3rd party TI EDITOR would have to do - exactly the same thing; but with a different purpose.

As long as you're not out-and-out reverse engineering the Virus TI, then you should be fine. imho i think that if Access wanted to create a stink about anything, then they would've already done so when you took their wavetables and made them part of your synth. But look out! Sometimes companies can be genuine bastards about stuff: they won't say anything (like cease and desist) until they have enough on someone to kick-em' in the groin surprise-attack style - especially true if accused offender clearly has valuation worth the up-front legal costs; or poses a perceived threat to their bottom line.

[goldenanalog]

On another note, in theory it would be possible to import Virus patches, my only concern is if are there any legality issues with it? Do I need permission from Access for me to be able to import their patches? I am not knowledgeable in these matters, if someone has any advice please share. Basically I would just be "reading" the patches and it wouldnt modify them in any way. As far as I know, other commercial Vst as alternate midi controllers for the Virus can also open midi patches and can communicate with the Virus and that seems to be fine. I would also be doing the same, except I would just convert the read data to a format that Viper understand so it can open it. However I dont know if Access would be happy that Virus presets could be opened with another product. I guess I could send them an email and ask but if they say no then I wont take any risks. On the other hand if I dont ask, and do it, then they might never notice or care, but I wouldnt want any lawyers knocking at my door later on.

Here's a question: are all the native presets in a Virus TI wholly Access's ip? If Access paid for the patches; or if there was authoring of the presets by 3rd party programmers who might still hold rights to their work - I don't know how all parties would feel about their work being integrated into an independent software having no connection w/Access, Adam.

To put it another way: It's one thing to have Access's Virus TI patches stay wholly in their ecosystem; it's quite another to have them shared in an entirely different ecosystem completely disconnected from the source; and sold as a "feature" (I'm not being judgmental - having a soft that would directly import native VTI patches certainly appeals to me)

[plrdmus]

As long as you're not out-and-out reverse engineering the Virus TI, then you should be fine. imho i think that if Access wanted to create a stink about anything, then they would've already done so when you took their wavetables and made them part of your synth. But look out! Sometimes companies can be genuine bastards about stuff: they won't say anything (like cease and desist) until they have enough on someone to kick-em' in the groin surprise-attack style - especially true if accused offender clearly has valuation worth the up-front legal costs; or poses a perceived threat to their bottom line.

Access/Kemper Audio doesn't even care about Virus at this point. See for example how they dropped support for the plugin since it stopped working on macOS Catalina (which has been out for a year now). Customers are still complaining.
Last time they updated their products it was 2017.

Maybe they're doing way much better with their guitar amplifiers, and they simply... don't care about this anymore.

Here's a question: are all the native presets in a Virus TI wholly Access's ip? If Access paid for the patches; or if there was authoring of the presets by 3rd party programmers who might still hold rights to their work - I don't know how all parties would feel about their work being integrated into an independent software having no connection w/Access, Adam.

To put it another way: It's one thing to have Access's Virus TI patches stay wholly in their ecosystem; it's quite another to have them shared in an entirely different ecosystem completely disconnected from the source; and sold as a "feature" (I'm not being judgmental - having a soft that would directly import native VTI patches certainly appeals to me)

Probably they commissioned some sound designers, so they probably own the rights to it. Doesn't matter, as long as those presets are not included here.
See for example what happened with bigger companies like Sony and Nintendo and see how they can't stop emulation at all.

[nix808]

I am a FlowStone developer also.
I have contacted Marc Shlaile at Kemper about this years ago.
We have permission to use the wavetables
- if we were to use the TI plugin graphics it would be a problem to them imo.
However to use it's sounds- we have express permission

[trusampler]

This is incredible, I have a Virus TI2 and love this synth, not many Va's I like, but to think I'd be able to use these sounds in viper one day is just amazing. This is all too exciting.

[plrdmus]

I am a FlowStone developer also.
I have contacted Marc Shlaile at Kemper about this years ago.
We have permission to use the wavetables
- if we were to use the TI plugin graphics it would be a problem to them imo.
However to use it's sounds- we have express permission

Obvious. You can't use their code or anything that comes directly from them without their permission (which is basically stealing).

Not that their graphics are too fancy anyway, although theirs look more "serious".

[adamszabo]

It's ALWAYS a good idea to ask first; but in your case: you've already accurately copied their wavetables w/o a peep from them, correct?

I asked them about the wavetables and they gave me permission to sample it. You are right about the patches might be copyright to third parties, but lets imagine that Viper has a Virus import feature, I WONT be including any Virus patches with Viper, each user can import whatever they wish, which will be out of my hands.

[zvenx]

Still hoping one day that there will be a mac version.
rsp

[nix808]

Still hoping one day that there will be a mac version.
rsp

we can start a crowdfund

I was talking to the dev, and a really rough estimate is 600k euro for the Mac
-- + now it's even harder as the move to ARM is like- what does that mean entirely

[chk071]

600k? Do you mean for a Flowstone version which outputs Mac AU?

Apart from that, good luck to do a crowdfunder to get 600k... nobody but some indie developers even care about Flowstone.

[recursive one]

Mac guys are severely out of luck.

For what I know, the TI plugin doesn't work with the latest Macs either.

[nix808]

600k? Do you mean for a Flowstone version which outputs Mac AU?

yeah- for the rewrite which would be Mac compatible

the new FS for WIN should be released in March-May next year

yeah- Apple r always breaking things for dev

[vertibration]

FYI, Steinberg isnt offering VST2 SDK for Big Sur at the moment......this presents a bit of a problem.