DSP Robotics Support

nix wrote:I can confirm the bug

Thx a lot Nix!

deraudrl wrote: I (sort of) see the "bug"

deraudrl wrote:I'm not sure it counts as a "bug"

Thx, it IS a bug... Doesn't matter where the signal comes from..; it's in the interpretation of the signal that the bug is... Midi to poly obviously... as Nix says he doesn't have this problem with the midi code he uses...
And I have the same thing when using my NanoKey controller...
Thx for your time guys... appreciated!
If more people could confirm that... I'll link the Slack thread I made to this one...

tektoog wrote:Thx, it IS a bug... Doesn't matter where the signal comes from..; it's in the interpretation of the signal that the bug is... Midi to poly obviously...

Huh?!? You jumped to that conclusion with remarkably little (dare I say zero?) evidence.

If it were in MIDI to poly, it would show up in any MIDI input, including MIDI events coming from sequencers, algorithmic note generators, and even external DAWs.

Maybe... but I wouldn't say 0... Me, you, Nix spotted the bug...
So what would it be then?
It doesn't come from the controller as the PC keyboard and Midi controllers behave the same... buggy...
I've tried many controllers as well... Main one being a NordLead2 (which is rock solid with midi controls, and it has almost all of them on front panel )
Same thing with NanoKey, and MAudio O2... that's already 4 controllers that have the same behavior.
I could almost draw a conclusion from that... and then You and Nix confirmed...
That's why it would be nice if more people confirm that also

deraudrl wrote: it would show up in any MIDI input, including MIDI events coming from sequencers, algorithmic note generators, and even external DAWs.

I don't think so... there's a difference by reading data and interpreting external inputted data... it doesn't go thru the same pipe...
When you say sequencer, you mean DAW or internal Step sequencer or Arpeggio?
Because I said in a previous post that the example synth arpeggiator just gets stuck and produces no sound at all when hitting 3 keys at once, and it's because it is linked to the Midi2Poly...
Last thing to test really, is reading the chord in a DAW... Which I haven't really tried, cause I got stuck by the other problems I had (DS error, failing exports) before reaching this point But it might work well just reading the data... need to be tested...
I will do that later, after sleep...
Take care

it is a problem with the 'midi in' component

'midi mono' sees 2 notes when 3 are pressed

there may not be a problem with the MIDI to poly conversion

nix wrote:it is a problem with the 'midi in' component

'midi mono' sees 2 notes when 3 are pressed

yep, you're right good find!

thanks, glad the component to diagnose was there/easily found to help us

nix wrote:it is a problem with the 'midi in' component

With any input or just PC keyboard?

I tried with my max 6 poly Squier Rockband Strat,
and I couldn't find any isuue with 6 poly, or several 3-4 note chords
I did seem to be getting some sort of buffer underrun, even with a high buffer

I can't say 100% that the problem is existant with my M-Audio Audiophile 5 pin DIN into FS,
or not. It seems usable, the buffer thing was no good to play though, but I don't ever run my Squier into FS until now

For me,
It does it with my M-Audio O2 controller either plugged in Midi or USB
It does it with my M-Audio Uno USB2Midi interface
It does it with my Korg NanoKey controller (USB)
It does it with my Clavia NordLead2 synth plugged (with 5 pin midi) thru my TC electronic konnekt 8 soundcard
I won't make a video for each of these...
It's a bug and need to be looked at by the Dev(s)