Hello,
I bought the new Producer version recently and am loving the option to easily build tracks with my patterns.
I was wondering if there's a feature planned so that you can set step conditions for each VA Beast sequencer step. i think this would be really useful in both Studio and Producer versions
thanks for all the hard work!
drew
Step Conditions for VA Beast
Step Conditions for VA Beast
https://soundcloud.com/fevered-shiva
Re: Step Conditions for VA Beast
drewinnit wrote:I bought the new Producer version recently and am loving the option to easily build tracks with my patterns.
I was wondering if there's a feature planned so that you can set step conditions for each VA Beast sequencer step. i think this would be really useful in both Studio and Producer versions
Thanks a lot for buying G-Stomper Producer in early access state. That's really appreciated.
So far, it's not planned to have step conditions in the VA-Beast sequencers.
The reason is its polyphony, which makes it much more complicated to handle conditional steps.
How to handle the conditions for example? Per Step or Step and Voice? And that's just the first of a lot of unanswered questions.
If it comes to "probability", how should chords be held together. Should you, the user, handle chords by PRE conditions, or should chords generally be held together (this would mean the conditions would be per step).
Nevertheless, it's not impossible. Maybe at some point in the future, as I see the benefit of having it there as well.
Thanks for the push;)
Re: Step Conditions for VA Beast
thanks for your reply here, and sorry I didn't write again sooner.
I can definitely see that it's a more complex issue than the monophonic step conditions for the Sampler.
I think a condition per step would be ideal. so not accounting for polyphony, just any sequencer info on that step is played when the step conditon is triggered.
this would open up a lot of creativity and sequence variety which the Sampler currently provides, but is lacking from the Beast
not a high priority feature but would be nice to have
I can definitely see that it's a more complex issue than the monophonic step conditions for the Sampler.
I think a condition per step would be ideal. so not accounting for polyphony, just any sequencer info on that step is played when the step conditon is triggered.
this would open up a lot of creativity and sequence variety which the Sampler currently provides, but is lacking from the Beast
not a high priority feature but would be nice to have
https://soundcloud.com/fevered-shiva
Re: Step Conditions for VA Beast
drewinnit wrote:I think a condition per step would be ideal. so not accounting for polyphony, just any sequencer info on that step is played when the step conditon is triggered.
this would open up a lot of creativity and sequence variety which the Sampler currently provides, but is lacking from the Beast
not a high priority feature but would be nice to have
I agree that a per step handling would be suitable.
I'll keep that feature request in mind as a possible upgrade.
Thanks again, drewinit.
Re: Step Conditions for VA Beast
Hi there, first off, thanks for creating your app lineup, they are really great. I've been working with 'Rhythm' for a bit and learning it. I'm about to pull the trigger on purchasing Studio and Producer.
I had this very same question about setting up Step Cond on Beast. I would very much like to see this feature added in.
I ssee some of the complexity, per your response several years ago. I would be happy with setting a Step Cond for whatever array of note(s) that appear. Whether it's a chord or a single note, the whole thing gets modified per the Step Cond setting.
I'm sure it's a much more complex issue than that, but it's a feature that would add a lot to Beast, imo.
Thanks again and 'bump' to this thread!
I had this very same question about setting up Step Cond on Beast. I would very much like to see this feature added in.
I ssee some of the complexity, per your response several years ago. I would be happy with setting a Step Cond for whatever array of note(s) that appear. Whether it's a chord or a single note, the whole thing gets modified per the Step Cond setting.
I'm sure it's a much more complex issue than that, but it's a feature that would add a lot to Beast, imo.
Thanks again and 'bump' to this thread!
Re: Step Conditions for VA Beast
jc2023 wrote:Hi there, first off, thanks for creating your app lineup, they are really great. I've been working with 'Rhythm' for a bit and learning it. I'm about to pull the trigger on purchasing Studio and Producer.
I had this very same question about setting up Step Cond on Beast. I would very much like to see this feature added in.
I ssee some of the complexity, per your response several years ago. I would be happy with setting a Step Cond for whatever array of note(s) that appear. Whether it's a chord or a single note, the whole thing gets modified per the Step Cond setting.
I'm sure it's a much more complex issue than that, but it's a feature that would add a lot to Beast, imo.
Thanks again and 'bump' to this thread!
Thanks a lot for the kind words, jc2023.
Unfortunately, I have no capacity at the moment to implement a change of that dimension. It's a major change in the core of the polyphonic sequencer, which might have critical side effects. If I once get back into full time app development, I can think about it. But for now, it's impossible, sorry.
-
Horrorflies
- Posts: 4
- Joined: Fri Sep 26, 2025 4:25 am
Re: Step Conditions for VA Beast
Hi planet-h, thanks for the clear explanation. I understand the polyphony is what makes step conditions in VA Beast much harder to implement, especially deciding whether conditions should apply per step or per voice, and how chords should behave under probability or PRE logic.
For my use, a simple per-step approach would already be very valuable: whatever notes exist on that step, whether a single note or a chord, would all follow the same condition together. That seems like the most musical and practical behavior from a user side, even if it is less granular than per-voice control.
I realize it is a core-engine change and not a small request, but I still want to add support for this as a future upgrade if development time ever allows. It would add a lot of creative variation to VA Beast and help bring it closer to the flexibility that step conditions already provide elsewhere in G-Stomper.
Thanks again for keeping it in mind.
For my use, a simple per-step approach would already be very valuable: whatever notes exist on that step, whether a single note or a chord, would all follow the same condition together. That seems like the most musical and practical behavior from a user side, even if it is less granular than per-voice control.
I realize it is a core-engine change and not a small request, but I still want to add support for this as a future upgrade if development time ever allows. It would add a lot of creative variation to VA Beast and help bring it closer to the flexibility that step conditions already provide elsewhere in G-Stomper.
Thanks again for keeping it in mind.
Re: Step Conditions for VA Beast
Horrorflies wrote:Hi planet-h, thanks for the clear explanation. I understand the polyphony is what makes step conditions in VA Beast much harder to implement, especially deciding whether conditions should apply per step or per voice, and how chords should behave under probability or PRE logic.
For my use, a simple per-step approach would already be very valuable: whatever notes exist on that step, whether a single note or a chord, would all follow the same condition together. That seems like the most musical and practical behavior from a user side, even if it is less granular than per-voice control.
I realize it is a core-engine change and not a small request, but I still want to add support for this as a future upgrade if development time ever allows. It would add a lot of creative variation to VA Beast and help bring it closer to the flexibility that step conditions already provide elsewhere in G-Stomper.
Thanks again for keeping it in mind.
Thanks for your message, Horrorflies.
And welcome to the forum.
Thanks for bringing this back in mind. I've made a note on the list of next features to consider.
Cannot guarantee anything yet. But I'll definitely look into it to see what's possible.
-
Horrorflies
- Posts: 4
- Joined: Fri Sep 26, 2025 4:25 am
Re: Step Conditions for VA Beast
planet-h wrote:Horrorflies wrote:Hi planet-h, thanks for the clear explanation. I understand the polyphony is what makes step conditions in VA Beast much harder to implement, especially deciding whether conditions should apply per step or per voice, and how chords should behave under probability or PRE logic.
For my use, a simple per-step approach would already be very valuable: whatever notes exist on that step, whether a single note or a chord, would all follow the same condition together. That seems like the most musical and practical behavior from a user side, even if it is less granular than per-voice control.
I realize it is a core-engine change and not a small request, but I still want to add support for this as a future upgrade if development time ever allows. It would add a lot of creative variation to VA Beast and help bring it closer to the flexibility that step conditions already provide elsewhere in G-Stomper.
Thanks again for keeping it in mind.
Thanks for your message, Horrorflies.
And welcome to the forum.
Thanks for bringing this back in mind. I've made a note on the list of next features to consider.
Cannot guarantee anything yet. But I'll definitely look into it to see what's possible.
I really appreciate what youve done with this app and having step control would really give me the full ensemble to play and record live. My goal is to be able to play and control with my gear only, emulating a dawless setup so I dont have to operate the screen. This is the missing piece of my project. Ive already removed analog from my setup and are operating a tab s9+ and dell latitude with traktor pro 3 using a owc thunderbolt 4 hub and scrcpy no video with lossless audio with practicaly no latency. Im really pushing the limits on android to promote it over apple and other cash grab corporations that are in the subscription high. I have bypassed a lot of roadblocks in the past year to get this far and give big corporations the middle finger for locking down midi devices and ripoff new generations through their proprietary bs. thanks again and will be looking forward for any new features you guys come up with. You are true heroes in my book.
Who is online
Users browsing this forum: No registered users and 141 guests
