DSP Robotics Support

Hi,
Just saw how popular this arp is so decided to add in to it some more features like full octave rang size piano roll with 8 bars, gate for instant note length editing and time signature. You're invited to use and customize.

Cheers

Looks good and seems to work fine for me.

One point I note is the blue position marker didn’t move for me, or did I miss something?

Yeah, forgot to connect the position wire. Fixed the original post

kortezzzz wrote:Yeah, forgot to connect the position wire. Fixed the original post

Thank you! Very nice now

By the way, Spogg, dunno if you saw my message on the slack, but be aware of adding your "zero midi vel = midi off" module in any of your 64bit exports since it prevents both audio bouncing and midi to audio exporting. Myco said we should actually avoid of sticking any green midi primitives between midi and midi2poly for proper DAW behavior. It doesn't happens with 3.06 but only since alfa production, so we'll have to find a Ruby solution for that (and so with the green keyboard split, if you ever used it).

Yes I did see it thanks and I was puzzled as to why it should be a problem. In my view it should be fixed and I don’t know why it’s become an issue.

It’s not needed for the regular midi prims (they handle midi running status fine), only when someone uses an on-screen keyboard as you say, which I never do myself. What happens then (I’ve seen it on Johan’s synths) is the on-screen keys show as pressed but they don’t release.

Well, Myco suggested investigating it by testing every single release made by him since 3.08. I don't have the latest released betas of FS3 and I can not test them but I'm sure something went wrong before FS4 production started because my most earliest 64bit exports failed as well.

Any green midi between midi and midi2poly caused bouncing \ export failure here. With the virtual keyboard and without it. I had 4 green midi modules seeded in my midi chain at all of my synths: "Vel=0 -> midi off", midi limiter module, fixed midi module and physical keyboard splitter. Each one of them caused the problem. I've replaced 3 of them with Ruby patches and now everything works, but couldn't find a Ruby solution for the "vel=0 -> midi off" yet.

Nice !, thanks !

kortezzzz wrote:Ruby solution for the "vel=0 -> midi off"

I'm away from my FS machine at the moment, but this Ruby code pasted into a blank RubyEdit (with just a MIDI input and output) should do it...

Code: Select all

if @in.is_a?(Midi)
  if @in.status == 144 && @in.data2.zero?
    @in.status = 128
  end
  output @in
end

Thank you very much, Trog Hope Spogg can now test it with his gear and confirm. By the way, I've abandoned the Ruby solution for "output midi with fixed velocity" and "limit velocity to a fixed threshold value". I'm using poly velocity solutions instead due to intensive CPU usage. Maybe my code is just that horrible... so, Trog, if you got any idea for small & elegant code for that, it would be lovely to hear from you