Viper｜1.2.2 update with bugfixes and new skin

[adamszabo]

Just put the wav folder in Viper/Waveforms so it will look like this: "Viper/Waveforms/Daniel Craighead - Trance Access Vol.1" and it should find it. Maybe i should include some instructions in the bank

[xanthos]

Just a shot in the dark but perhaps this is a problem with FLS (fiber local storage)? Running out of FLS slots should not lead to crashes but who knows. You can download a checking tool that shows the number of available FLS slots here:
http://planetnine.jp/wp/2018/03/25/fls-checker/

The corresponding thread in the Steinberg forums is:
https://www.steinberg.net/forums/viewtopic.php?t=134715

Some more info in FLS can be found here:
https://www.steinberg.net/forums/viewtopic.php?t=123768

With the following steps you can find out:

1. How many FLS slots are available in you DAW.
2. How many FLS slots Viper acquires.
3. How many slots are left in the big project.

Follow these steps:

• Start a fresh session.
• Load an instance of the FLS checker and check how many slots you have available. This is the maximum number of slots your DAW makes available.
• Load an instance of Viper.
• Update the slot count in FLS checker. The difference between the initial number of slots and the current one is the number of slots that Viper allocates.
• Load the big fat project that already uses many VSTs.
• Load the FLS checker and check how many slots are still available.

If the number of available slots in the big project is smaller than the number of slots that Viper acquires then that's likely the problem.

Sadly it has nothing to do with FLS, ... Viper takes 2 FLS slots.. so thats fine.

The error must be somewhere else, never got an issue with plugins on my system so far ... but Viper is now not usable because it will crash when there are already some vsts loaded....
Windows 10 Pro 1709 64bit, nothing fancy...

[adamszabo]

I just got an email from another user who has a similar issue with Cubase 9.5, he said that there is sometimes an issue with Cubase that if you start the application there will be two Cubases running in the background, and if you remove one of them with the task manager the project will not crash anymore with Viper. Could you perhaps check if thats the case for you as well?

[nix808]

I have Cubase 9.5 too Adam,
if that helps.
nix from FS
What happens here is I have the Cubase process not closing on exit with my FS plugs.
It closes itself 30min to couple hours later

[Armagibbon]

Hey fam been havin that prob in cubase for some time with other plugs. Hangs on exit or leaves a process runnin got some kinda shitty thread cleanup prob... go to start cubase again and half the plugs crash it. Some d16 and izotope and others. Only fix that works is killin it all from task manager. Could be a prob just with cubase imo.

[chk071]

Just a shot in the dark but perhaps this is a problem with FLS (fiber local storage)? Running out of FLS slots should not lead to crashes but who knows. You can download a checking tool that shows the number of available FLS slots here:
http://planetnine.jp/wp/2018/03/25/fls-checker/

The corresponding thread in the Steinberg forums is:
https://www.steinberg.net/forums/viewtopic.php?t=134715

Some more info in FLS can be found here:
https://www.steinberg.net/forums/viewtopic.php?t=123768

With the following steps you can find out:

1. How many FLS slots are available in you DAW.
2. How many FLS slots Viper acquires.
3. How many slots are left in the big project.

Follow these steps:

• Start a fresh session.
• Load an instance of the FLS checker and check how many slots you have available. This is the maximum number of slots your DAW makes available.
• Load an instance of Viper.
• Update the slot count in FLS checker. The difference between the initial number of slots and the current one is the number of slots that Viper allocates.
• Load the big fat project that already uses many VSTs.
• Load the FLS checker and check how many slots are still available.

If the number of available slots in the big project is smaller than the number of slots that Viper acquires then that's likely the problem.

That's super helpful, in general. Thanks for that. Should be stickied here, IMO.

[Armagibbon]

Never heard of fls b4 now... looks like alot of plugs like to leak slots. Open a plug... takes a buncha slots. Close it... gives back that much -1. Not so many plugs respect that resource and give back 1 to 1. Seems like the leaks gotta be managed by restartin the project. Good to know...

[xanthos]

well did some other tests here and it has nothing to do with FLS.
it also has nothing to do with Cubase.
As the same behaviour is with Ableton 10 or Studio One 4.
Just put enough vst instruments/plugins... (in my case its not too much.. all in all around 15 different plugins)
and after that Viper does make some issues.

[ATN69]

@adamtrance. When the dust around Viper settle and everything is back to normal I would hope you consider to port JP6K to 64-bit as well. I have both Viper and JP6K and I use them both frequently. JP6K is my choice for certain plucks, pads, etc, because the super saw is still very nice and the UI is quick and simple. I have moved over to 64-bit only but JP6K still work fine in FL Studio 20 with IL bridge. I have Studio One 4 as well.

Cheers!

[tuzemec]

Love it. Wonderful filters. Amazing presets.
Purchase in 3... 2... 1...

[BlackWinny]

I put that question as Synthedit developer : Adam, do you have an idea of the public release of the 64-bit edition of the FlowStone development environment?

Within the next 3 months?
Within the next 6 months?
Within the next 12 months?


Evaluating the advancement of their work, what is your opinion?

Thanks !
Jacques

[Pyrotek45]

I would love to see an update for jp6k on the filters and the envelopes. maybe add more filters or add more envelope types. that would be amazing.

[adamszabo]

@adamtrance. When the dust around Viper settle and everything is back to normal I would hope you consider to port JP6K to 64-bit as well.

Yes I plan to do that, but only after the summer. I am extremely exhausted I need to take some rest. I also need to find this damn crashing bug, so I cant rest just yet

I put that question as Synthedit developer : Adam, do you have an idea of the public release of the 64-bit edition of the FlowStone development environment?

I have asked them as well, but I didnt get a concrete answer I hope that its officially out this year though.

[BlackWinny]

@adamtrance. When the dust around Viper settle and everything is back to normal I would hope you consider to port JP6K to 64-bit as well.

Yes I plan to do that, but only after the summer. I am extremely exhausted I need to take some rest. I also need to find this damn crashing bug, so I cant rest just yet

I put that question as Synthedit developer : Adam, do you have an idea of the public release of the 64-bit edition of the FlowStone development environment?

I have asked them as well, but I didnt get a concrete answer I hope that its officially out this year though.

Let's hope... and cross our fingers.


Hey, friend ! Even with a product which is payware... don't fall in a burnout ! It is capital to work with the head quiet after a rest of a few days rather than burning the candle by both sides! You have everything to win (and your customers too !) by having a minimal time of rest, because it is extremely hard to recover from a burnout! And the efficiency after such a severe health issue is hugely decreased during months and months!

Even with users pushing you to always work without any rest, you MUST take the time to have a rest for at least a few days (a full week or so) in order to maintain your physical and mental health to continue peacefully your path !

[adamszabo]

I will do that thanks for the encouraging words!