Stochas (legacy)

Awesome plug in. Intuitive interface, very easily understandable and modifiable. It's not the London Symphony Orchestra but it's not supposed to be. It's supposed to be a way to generate quasi random events and it does a great job at it.

Amazing Plugin, Worked 100% in Reaper and Ableton. I love how it makes it so easy to create unexpected changes. So much fun to use. So good on drums.

Followed the online tutorial for setting up Stochas in FL Studio and still could not get Stochas to work. Looked to the comments section in order to seek some help or see if anyone else was having similar issues, and the comments were disabled. Disappointing to say the least.

I would give this closer to a 10 if it weren't for the fact that it doesn't work properly in Ableton.

It's remarkable, given the popularity of Ableton, that this company released Stochas without getting to the bottom of the issue.

On their support forum they say "they're looking into it" but that reply was May 2017 and it's now early July.

One of the selling points of Stochas are its 4 layers that can work in parallel to enrichen your sound/melodies etc.

To do this layer 1-4 are routed to MIDI channel 1-4.

On a You tube demo a bloke using Kontakt does this. However Ableton users can't use this functionality. There were 2 other people like me who had written on the Audio vitamin website about this.

The plug in does nearly everything I want for my experimental installation type soundscapes, and I have a workaround for this issue where I just have 4 instances of Stochas each routing to a separate synth/device.

However at $50 this shouldn't have been necessary and the really nice functionality they created for working across layers is lost using my workaround. The functionality is that the notes of other layers are 'shadowed' as you work in parallel layers. It makes it easy to make/see the possible polyrhythmic patters.

So in conclusion. A potentially 'awesome' tool is handicapped. I will come back here and give it a 10 if they fix this issue in an update. But after 2 months since they were "looking into it", I am not convinced that's going to happen.