DSP Robotics Support

In relation to the request made on the Facebook group, I'm asking the question here as well.

How can I split MIDI channels to control a voice algorithm per channel.

I've tried intercepting a splitter and event:

and the scheme here:
DSP Robotics Support Forum: Process MIDI data?

Both seem to do nothing to effect the output downstream.

I've also been messaging Nix who says it has to be ruby coded, which is doable. Any suggestions for Ruby online campuses?

My goal is a MIDI guitar synth, which has each string as a channel. The big barrier here is the pitch bend per string. Most synths and samplers (with a single timbre) only have one pitch bender and dumps all the pitch bends across the played notes; which makes for a wrong and unrealistic performance.

I started a project in SynthEdit to realize this dream but 64bit doesn't allow for channels and recording pitch bend data internally to a parameter is not possible at this time; in fact, recording a single pitch bend's data internally is not possible at this time, as far as I can determine:
SynthEdit@Groups.io: #bug Using "Bender" from The "Assign Controller" Menu Crashes Builds
SynthEdit@Groups.io: #Bug #MIDI 64bit Plug-ins Are Only Receiving MIDI Channel 1
SynthEdit@Groups.io: How Can I Record Pitch Bend Data?

The only work around I have is to bring in 6 "MIDI Outs" (FL Studio) and link each pitch bend channel to each pitch bender, but then the notes are spread across multiple Channels/Piano rolls.

This is also only a workaround for FL Studio, I prefer to conceptualize compositions in Tracktion's Waveform, as it has the ability to change the root, key, and mode for the whole composition on the fly.

I also use Cubase but that's mostly for vocal processing.

I've attached a very simple schematic that has the selector intercepting a splitter and event, with a single oscillator downstream. This is as far as I made it after watching a few youtube videos and poking around the manual.

I know, I have to read the manual!

Thanks for any consideration.

Hi,
didn't understood what is your most final goal. You'd like to stream the midi channels to some outsider channel in the DAW to power other vsti or you just wanna keep the stream internal to power your own synth?

And which version of Flowstone you used for this example? It doesn't get opened with 3.0.6 version.

The basic outline of the algorithm is:
6 channel selectors/splitters splitting 6 of the channels of incoming MIDI data to a separate oscillator with pitch bend data as a automate able parameter.

Alpha 2782

I'm focusing on the bare basics here, and tell things that you probably know. But I want us to talk about the same things, so let's find the common ground.

1) Every Flowstone plugin has a midi input.
2) Which channel this midi in stream represents, is determined by the DAW.
3) You can create a plugin that provides 6 midi inputs (actually any number, but here for the 6 strings), but the DAW must be able to handle multiple inputs per plugin
4) Which channel is used per input is determined by the DAW.

What you will never have is one midi input that carries 6 different midi channels in parallel. In serial progression it would be possible, but that defeats the purpose here.

Figured out an algorithm, thanks.

JWP wrote:Figured out an algorithm, thanks.

I can’t add anything to what tulamide said, but I would really like to see what you come up with.

Cheers

Spogg

Thanks for the interest Spogg. I got a long way to go.

I managed to do a midi separation by input channels with Flowstone version 3.0.6, however I have another scheme with the same structure in the same version and it is not working, I attach the first scheme that works:

I tested it with SpringBeatsvMIDI to virtually communicate Flowstone with Fl Studio and thus test the channels

That's interesting!

Way cleaner than what I have, I haven't tested yours yet.

I've been spending most of my time in SynthEdit after hitting a wall in Flowstone. Currently -in Synthedit- I'm looking at anti-aliasing distortion techniques. All the distortion type modules by default have aliasing, and I'm just now finding out. I imagine the same techniques applied to Flowstone will yield the same result.
The main idea is to not oversample and keep latency off the table, but it looks like it's the only way, then again Flowstone has Ruby and Assembler.

I've been fiddling with phase cancellation but it's not happening and I'm done!

Interesting to see one of my threads float back up, I'll have to start scaling that wall again.

Thanks.

@JWP I have worked with synthedith for many years, it was my first development software, and there I learned many things too, that I have been able to apply methodically in FS as well,

JWP wrote:Currently in Synthedit, I am looking for anti-aliasing distortion techniques. All the default distortion type modules are aliased, and now I'm figuring it out.

for antialising on both SE and FS, you can try a low or medium pass filter or a Smooth (De-Zip) and experiment somewhere in the chain,

I imagine the same techniques applied to Flowstone will produce the same result.

the truth, each program has its virtues, and sometimes what is learned in one, can be applied in another, the schematic methods can serve to enrich and simplify the logical way of elaborating them,
just to think that it took me 3 years to understand and learn FS to start developing serious projects in it, you can see that everything is possible,
I love how graphic it is and that makes things much easier for me, and also saves me a lot of time, and that is important,
has the support of the members, so we help each other overcome those walls