Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#56 polysix: monomode code bug when sequencing

admin
closed-duplicate
Nick Copeland
5
2010-04-18
2009-10-01
Andrew C
No

The polysix in -mono -hnp mode seems to mess up it's monophonic code assignment when sequencing from rosegarden (I haven't experienced it while playing live).

Occasionally (and I don't know how to cause this bug), the polysix will appear to be totally silent, even when reciving note on events, from both sequencer and keyboard.

Holding one key and then pressing one higher than it ('cos i'm using the -hnp option), causes the polysix to play notes AND drop back to the first key played, as if the note had originally sounded, which it didn't.. Releasing the key results in a note off, but pressing either the same key or another key, no sound comes out of the polysix...

Andrew Coughlan.

PS. I'm using Rosegarden as my midi sequencer

Discussion

  • Nick Copeland
    Nick Copeland
    2009-10-05

    You might want to try this with the option -mididbg2. The output might not be too clear however it should let you see what note on/off events occur. What can happen with HNP is that the sequencer plays a high note and when you stop the sequencer it does not stop the note (or I lose it, or perhaps it just sends an AllNotesOff').

    This high note then blocks all other low notes from sounding. That is just conjecture, the debug may shed more light on the issue and I can perhaps have a look through my AllNotesOff code to see what it does with monophonic note logic - to be honest I don't think it does anything, and arguably it should clear out the monophonic notes table too.

    Regards, nick.

     
  • Nick Copeland
    Nick Copeland
    2009-10-05

    • labels: --> Bristol Engine
    • milestone: --> admin
    • assigned_to: nobody --> ncopeland
    • summary: mono polysix code bug when sequencing --> polysix: monomode code bug when sequencing
     
  • Andrew C
    Andrew C
    2010-04-18

    • status: open --> closed-duplicate
     
  • Andrew C
    Andrew C
    2010-04-18

    I think this is a duplicate entry on an already opened bug report.

    I should've closed it sooner...

    Andrew.