DSP Robotics Support

Hello!

Based on advice from others I installed 3.06 but I got a crash every time when I tried to drag in a Wave Player module. I returned to 3.08 and it was fine with this module.
Then I renamed the Flowstone program folder (not the App data one) and re-installed 3.06. The rogue Wave Player was gone (a “good” one was still there) and 3.06 seems to work fine now. I must assume that this module was left over from 3.08 and the installer for 3.06 didn’t remove it.

As far as I can tell all my toolbox is still intact and as it was before (this is in the Appdata folder).

The edit environment now seems more responsive somehow, on my large schematic, plus I gather from tulamide that Ruby runs “better” in 3.06, so I’m happy so far.

If I do get any issues that I think may be version-related I'll post in this topic.

Cheers

Spogg

Thanks Spogg,

My partner did it as well, and yes, 3.0.6 version is far more stable with my big project, even though one of the most important ruby blocks that tulamide made for me doesn't work with 3.0.6

kortezzzz wrote:... even though one of the most important ruby blocks that tulamide made for me doesn't work with 3.0.6

That is literally impossible, since I work with 3.0.6

So, there's only two possibilities: You messed things up, or I messed things up. Please pm me with a link to a schematic, that contains my non-working Ruby code, demonstrating the issue. I will have a look at it.

Thanks for the answer, tulamide

The schemating is attached to the post. After re-loading it, the Ruby module won't work for me.

The basic idea behind the the ruby module is to output "1" every time a matched midi key is pressed. For instance, if key C is pressed, the Ruby module will output "1" from it's first output. If key #C is pressed, it will output "1" from it's second output and so on.

kortezzzz wrote:Thanks for the answer, tulamide

The schemating is attached to the post. After re-loading it, the Ruby module won't work for me.

The basic idea behind the the ruby module is to output "1" every time a matched midi key is pressed. For instance, if key C is pressed, the Ruby module will output "1" from it's first output. If key #C is pressed, it will output "1" from it's second output and so on.

I see the issue. Needs a workaround. When you open the schematic, for whatever reason, two midi triggers are sent with a note off event. That messes up the array counter that I implemented assuming that we won't receive midi when nothing is played

I'll upload as soon as the workaround is ready.

THANKS

Just a one more question: how can the midi triggers mess with the array? or it's something related to Ruby midi stuff only? It's never happened to me before.

kortezzzz wrote:THANKS

Just a one more question: how can the midi triggers mess with the array? or it's something related to Ruby midi stuff only? It's never happened to me before.

No, it is not related to Ruby Midi. It is an error of the incoming midi stream. It sends midi note offs without prior midi note ons. That's a violation of the midi protocol => a bug.

I could track down the issue to that keyboard module. It produces those note offs. The issue is buried somewhere in the "GUI notes" structure. I tried my best to fix it, but wasn't successful. You should contact the author of that module. He makes a couple of odd things, like sending a midi note off for every incoming midi message, whose second data byte is 0 (regardless of status byte) .

Anyway, maybe Spogg should split our parts from his thread into a new one, as it has nothing to do with going from 3.0.8.1 to 3.0.6

tulamide wrote:The issue is buried somewhere in the "GUI notes" structure. I tried my best to fix it, but wasn't successful. You should contact the author of that module. He makes a couple of odd things, like sending a midi note off for every incoming midi message, whose second data byte is 0 (regardless of status byte) .

[/quote]

Thanks for your efforts, tula. I went back to my old trusted green solution, although its a lot more clumsy, but seem like I can never get everything all the time. Only some of the things, some of time, and I'm still happy with it, as long as things keep working somehow

kortezzzz wrote:

tulamide wrote:The issue is buried somewhere in the "GUI notes" structure. I tried my best to fix it, but wasn't successful. You should contact the author of that module. He makes a couple of odd things, like sending a midi note off for every incoming midi message, whose second data byte is 0 (regardless of status byte) .

Thanks for your efforts, tula. I went back to my old trusted green solution, although its a lot more clumsy, but seem like I can never get everything all the time. Only some of the things, some of time, and I'm still happy with it, as long as things keep working somehow

That's totally fine.

But, while my module works flawlessly, the keyboard module produces bugs and propagates them through your schematic. Yet, you prefer to keep that buggy module and instead let go off a perfectly fine one. That's really strange. It's not that there wouldn't be lots of keyboard modules (for example, Nubeat made a Ruby based one). So why not using another one? Or trying to solve the issue in that keyboard module?

My module works fine as long as the provided midi data sticks to the midi protocol.

tulamide wrote:Anyway, maybe Spogg should split our parts from his thread into a new one, as it has nothing to do with going from 3.0.8.1 to 3.0.6

Yeah I thought about this but it would be tricky to split it without losing some context.

I did it successfully once before but the last time I tried the whole lot got lost. This board can be a bit unpredictable at times. Or maybe I did some bad clicking

Cheers

Spogg