Known issues & bugs

Home Discussions Delta [MB] Known issues & bugs

Tagged: , , , ,

This topic contains 6 replies, has 2 voices, and was last updated by  moshang 3 years, 4 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #1730

    moshang
    Keymaster

    We’ll add bugs to the list as they’re identified, and remove them as they’re squashed.

    The bugs below were addressed in Delta v.115.

    • The first step doesn’t sound and a MIDI note is not sent for the first step when stopping playback and restarting./ Similar to the issue identified in the Alpha firmware and already addressed in the RED’s firmware.
    • Occasionally spurious notes are sent in the MIDI stream when using slides on a step.
    • MIDI clock Stop command is not sent when stopping the sequencer.
    #1732

    moshang
    Keymaster

    Christian Schenk wrote via email:
    Hi!

    Spent many hours for solving Midi-Slide. During this process I did find 2 issues which I hereby document with a screenshot from
    MidiOX: (I used your original delta-version 112 – un-changed)

    Delta MIDI bug

    Just for simplicity my sequence consists just of 2 notes: C2 and D3. (step 1 and step 2)

    issue 1)
    when starting the sequence the first note (C2) is not sent to MIDI out channel – it´s first played from the second sequence-loop on.
    So the sequence starts with D3.

    issue 2)
    it should send C2 Note On, C2 Note Off, D3 Note On, D3 Note Off, C2 Note On, C2 Note Off, D3 Note On, D3 Note Off and so on…
    instead it´s sending additional MIDI-Note On or Offs: G#1, C#-1 and/or skipping Note Offs (see screenshot)

    While issue 1) is just an annoyance issue 2) is a major problem!!
    (is also the reason why I could not solve the Midi-Slide-problem)

    I do think you should have a look in your code, especially your toggles (on, slide, etc.) – I spent now too many hours, I give up L

    As you remember I do want to use your Groovesizer only as a MIDI-sequencer (I do not need the synth-part). Right now unfortunately it is useless for me.

    #1733

    moshang
    Keymaster

    Hey Christian,

    Issue 1) This has also been identified for the Alpha firmware and is fixed in the RED’s firmware.

    Issue 2) Thanks for catching this – it has not been identified before, but I’ve manage to replicate it this side. No, Delta, bad dog! The good news is that this behavior does not occur on the RED, so I’ve already accidentally fixed it there. The RED’s sequencer is based on that of the Delta, so hopefully it won’t take long to implement a fix for the Delta.

    I intended to look at the Delta’s firmware next (and the Alpha’s too as far as programming space allows) to bring feature parity with that of the RED. The Delta can definitely do with the RED’s scales, and variety of play options. I’ll also bring across improved transpose via MIDI.

    Keep the faith, Christian – unfortunately, I’m a single developer with a day-job and a two-year old, so I don’t always get to things as quickly as I’d like to. Fixes are forthcoming.

    PS. As I mentioned before via email, I don’t see a way to implement slides via MIDI. You need to be able to set the bend range for each slide before you send the pitch bend CC data, and though I know it’s possible on some instruments, I don’t know of a universal way to do so.

    #1865

    moshang
    Keymaster

    Received from Christian Schenk via email:
    Hi!

    Spent the evening on testing new Delta-version 115 – here is my feedback:
    (tested only the MIDI-out-side of the sequencer which was connected to Volca Keys; external MIDI-Clock/Start/Stop was provided by MidiPal); measurements were done with MidiOX

    1) generell:
    Right now when you power on the groovesizer the (empty) sequence starts to run. I would recommend to change this (seqRunning = false).
    It should only start to run either if it receives an external START (or without external clock when F1 is pressed)
    I measured internal Midi-clock, it seems a little bit unstable.

    2) EDIT-Mode:
    Stop/Start/Rewind (F1) does not work when receiving external clock
    Clear All Selected (ShiftL+F1) does not work when receiving external clock
    Step Tie Page (F3): you can activate steps but nothing happens when receiving external clock
    Clear All (Shift L & Shift R): does not work when receiving external clock;
    without external clock it does not clear Accents, Play Mode, MIDIcc-Automation, Nudge, etc.

    3) Pot-Shift-Mode:
    Pot2 (Accent Page): has no influence at all on Midi-velocity – there is a “low” and a “high” velocity value, both remain the same whatever you do with Pot2
    Pot5 (Note duration): has no influence when receiving external Midi-clock
    Random patterns: suggestion: it should also randomly generate Accent-steps
    Random patterns: does not randomly generate Ties-steps when receiving external Midi-clock
    Random patterns: it always starts the sequence when leaving Preference page – in my opinion it should keep the seqRunning-status that it had when entering the Preference Page
    Tempo Nudge Slower: when receiving external Midi-clock it “forgets” the nudge whenever I stop and restart external clock

    4) Preference Page:
    general: on entering the Preference Page it stops a running sequence – in my opinion seqRunning-status should remain unchanged; the same should be when leaving the Preference Page (see above)
    SyncOut (F1): does not work when receiving external clock – IMPORTANT: it should not send out its own clock/Start/Stop but let through external clock/Start/Stop
    Automation: once an Automation is recorded it is sent even when the sequencer is not running; additionally it cannot be deleted with ClearAll() (only toggled on/off)

    Overall:
    – nice new features
    – Major problems with external Midi-Clock/Start/Stop (groovesizer as a slave)
    – REMARK: I just tested what is important to me – I suppose there might me additional problems in combination with external MIDI-clock

    #1909

    moshang
    Keymaster

    Hey Christian,

    I’ve just released v.120 of the Delta firmware. It addresses a number of your concerns. Details are here.

    Specifically in response to what you wrote:
    1) generell:
    Right now when you power on the groovesizer the (empty) sequence starts to run. I would recommend to change this (seqRunning = false).
    It should only start to run either if it receives an external START (or without external clock when F1 is pressed)

    I like it this way ;^) I think it’s friendlier to beginners – the machine is ready to start making music as soon as it’s switched on. The compromise is that when you switch on the Delta whilst already sending MIDI clock to it, it will wait for you to press play/start (F1) before the sequencer starts running.
    I measured internal Midi-clock, it seems a little bit unstable.
    I’m afraid you’re right – the jittery clock is down to three factors that I can see:
    1) my lack of skills as a programmer – seriously, I’m a beginner, so I hope to get better at this.
    2) my sequencer is based on measuring elapsed time, instead of running on an interrupt. It means a process can take too long to complete and cause notes to be late. I’ve incorporated checks and balances, but there are limits to what you can achieve with this implementation
    3) given the same firmware, the MIDIpal can be inherently more stable, because it runs on a 20MHz clock as opposed to a 16MHz clock. The downside for me is that using a faster clock on the Groovesizers would break compatibility with the Arduino IDE – compatibility with the IDE is important for me to make the Groovesizers as beginner friendly as possible.
    I think it’s important to remember that we’re talking about machines here, so even my jittery clock will keep better time than any mere human ;^)
    2) EDIT-Mode:
    Stop/Start/Rewind (F1) does not work when receiving external clock

    Fixed
    Clear All Selected (ShiftL+F1) does not work when receiving external clock
    Can’t reproduce, works fine here.
    Step Tie Page (F3): you can activate steps but nothing happens when receiving external clock
    Can’t reproduce, works fine here.
    Clear All (Shift L & Shift R): does not work when receiving external clock;
    Fixed
    without external clock it does not clear Accents, Play Mode, MIDIcc-Automation, Nudge, etc.
    Fixed, with the exception of nudge.

    3) Pot-Shift-Mode:
    Pot2 (Accent Page): has no influence at all on Midi-velocity – there is a “low” and a “high” velocity value, both remain the same whatever you do with Pot2

    Fixed
    Pot5 (Note duration): has no influence when receiving external Midi-clock
    Fixed
    Random patterns: suggestion: it should also randomly generate Accent-steps
    Done
    Random patterns: does not randomly generate Ties-steps when receiving external Midi-clock
    Can’t reproduce
    Random patterns: it always starts the sequence when leaving Preference page – in my opinion it should keep the seqRunning-status that it had when entering the Preference Page
    I’ve stuck with this behavior for now.
    Tempo Nudge Slower: when receiving external Midi-clock it “forgets” the nudge whenever I stop and restart external clock
    This behavior stays the same for now. Incidentally, there’s no variable to keep track of a nudge value. To stay in sync, the Delta counts incoming clock ticks. Nudging the Delta faster simply adds one tick to the current count, and nudging it backwards subtracts one from the count.

    4) Preference Page:
    general: on entering the Preference Page it stops a running sequence – in my opinion seqRunning-status should remain unchanged; the same should be when leaving the Preference Page (see above)

    I kinda agree with you – this is the behavior on the RED. But my button and mode checks on the Delta is quite convoluted and I couldn’t unravel it easily myself. It’ll have to wait for another day. In the meantime, it’s not a show-stopper – I can’t think of any options you definitely need to change whilst the sequencer is running.
    SyncOut (F1): does not work when receiving external clock – IMPORTANT: it should not send out its own clock/Start/Stop but let through external clock/Start/Stop
    This is by design – the Delta shouldn’t send its own clock messages whilst a slave, but echo the incoming clock on the output – it does so, unless you turn off MIDI Thru. In other words, control this option with Thru On (F4) and not Sync Out (F1).
    Automation: once an Automation is recorded it is sent even when the sequencer is not running;
    Couldn’t reproduce – on the other hand I found that automation wasn’t being sent whilst slaved to MIDI clock. This has been fixed.
    additionally it cannot be deleted with ClearAll() (only toggled on/off)

    Fixed

    Thanks for your input!

    • This reply was modified 3 years, 4 months ago by  moshang.
    #1912

    ChrisS
    Participant

    Hi!
    Did a (quick) check:

    3) Pot-Shift-Mode:
    Pot2 at Max means no (! = no note) velocity – it´s a cool feature but caused some confusion at the beginning

    Accent-step random: there are too many Accent steps created – could you pls change this to get a similar random-distribution as for example with ties?

    Ties-step random: if P1 is at Maximum then NO ties are created randomly. Once you (just slightly) lower P1 suddenly there are ties randomly created.

    MIDI-clock/start/stop OUT (groovesizer as slave; external clock/start/stop via MidiIN, Midi-Keyboard via MidiIN):
    I use my external Midi-Keyboard in two ways:
    a) to put in notes for the step-sequencer (sequencer is NOT running – F1=stop) – in that case I want to hear the notes pressed (F4 thruOn=true)
    b) to transpose a running note-sequence – in that case I do not want to hear the keyboard notes pressed (F4 thruOn = false) BUT I do want to have Midi-clock/start/stop getting thru (from external source) to MidiOUT. Pls make a difference between “channel-related” Midi-Messages (note on/off etc. – “F4″=toggle true/false) and “System Common” Midi-Messages (clock, start, stop, etc. – “F1″=toggle true/false)

    regards,

    Christian

    #1915

    moshang
    Keymaster

    Hey Christian,

    I’ve uploaded v.122 to take care of these issues.

    3) Pot-Shift-Mode:
    Pot2 at Max means no (! = no note) velocity – it´s a cool feature but caused some confusion at the beginning

    Yeah the accent is fixed at velocity 127, so really when you bring up the velocity knob, it lowers the velocity of non-accented steps.

    Accent-step random: there are too many Accent steps created – could you pls change this to get a similar random-distribution as for example with ties?

    Fixed.

    Ties-step random: if P1 is at Maximum then NO ties are created randomly. Once you (just slightly) lower P1 suddenly there are ties randomly created.

    Fixed.

    MIDI-clock/start/stop OUT (groovesizer as slave; external clock/start/stop via MidiIN, Midi-Keyboard via MidiIN):
    I use my external Midi-Keyboard in two ways:
    a) to put in notes for the step-sequencer (sequencer is NOT running – F1=stop) – in that case I want to hear the notes pressed (F4 thruOn=true)
    b) to transpose a running note-sequence – in that case I do not want to hear the keyboard notes pressed (F4 thruOn = false) BUT I do want to have Midi-clock/start/stop getting thru (from external source) to MidiOUT. Pls make a difference between “channel-related” Midi-Messages (note on/off etc. – “F4″=toggle true/false) and “System Common” Midi-Messages (clock, start, stop, etc. – “F1″=toggle true/false)

    OK. On the Preferences Page, F4 now toggles between 3 possible values for ThruOn. 0 = off, 1 = Full (everything is echoed), 2 = Partial (all note-related messages are blocked) Really the partial option is the DifferentChannel option in the MIDI library. It’s supposed to allow through all messages not on the input channel, but since our input channel is set to Omni, it block messages on all channels, but not clock, stop, start etc. Press and hold F4 to see whether you’ve selected option 1 or 2 (works better if Notify is off – F6).

    • This reply was modified 3 years, 4 months ago by  moshang.
Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.