›

Bug report v0.20 (and other things)

macMOEmacMOE
edited June 2013 in General
Nice update again julian. The new transient modes sound really good and are pretty intuitiv to use.

I found some bugs (not sure if they are new):

1. someties when i press buttons, the led lights up but the step remains as it was.

2. when i rapidly change the max steps in euklid mode, the active step "escapes" the selected area.

3. i can't change the lfo destination with the encoder in detailed view (after pressing the encoder). the 4th pot still works fine.

And one thing i think is weird is that after pressing the encoder to change a value, only the paramter name is displayed in detail but not the value name (not sure if my terminology is correct). It doesn't make a difference when the value is a number. But for names that is not convenient.
 For example: there are different "frq"s in the lfo destination and allthough i know which is which, it would be way easier if the name was displayed completely.

Other than that, this machine is awesome. I am currently using one track to trigger the ambika's sequencer and the fact that you can manually set a note-off (velocity "0") and give that step a probability is, in my opinion, way better than having an adjustable gate length. 
And i don't think it should have extended sequencing options. After all this is a drum synth/sequencer and it's beauty lies in the simplicity of the user interface.

Comments

  • julianjulian
    1. in which mode? are you trying to set/remove steps?
    2. known problem, but not on the list. added. (can also happen when varying track length in mixer page)
    3. i will look into this. added to the list.

    regarding the mod target list.
    I have a big make over planned for those. they are a little bit inconsistent, too.
    but for now there are more important bugs I think.

    thanks for reporting the bugs.

    I'm really glad you like the machine!!! :D
  • macMOEmacMOE
    edited June 2013
    yes, i was talking about setting/removing steps in voice edit mode.
    It doesn't happen often, but if it could be avoided, it should.

    No hurry for the detailed view. It is perfectly usable as it is right now.
  • julianjulian
    so you set a step, the led luights up, but the step is not playing?
    very strange, because the sequencer (mainboard) not the AVR is in control of the steps.
    The fronpanel tells the mainboard that a button was pressed, the mainboard adds/removes the step, and sends the changed pattern information back to the LEDs.

    I'll see what I can do ;)
  • macMOEmacMOE
    edited June 2013
    I can't recreate it at the moment but it could be me, pushing the button in a strange way so it triggers twice. That would explain the "blinking". I have to say that i don't use button caps at the moment and that may add to the problem.

    So don't think about it, it is probably me failing at pressing a button correctly. ^^
Sign In or Register to comment.