October 21, 2013 at 12:56 pm #766
Undoubtedly some gremlins have made their way into the release code. We’ll add items to the list as they come up, and remove them as they get smitten.
February 20, 2014 at 4:51 am #1627
MIDI sync out is unreliable at higher BPMs. [V100] The Alpha firmware doesn’t send out the 24ppq required for MIDI sync beyond a certain tempo – it seems to become unstable after about 130bpm… This one is a biggy!FIXED with the caviat that MIDI sync doesn’t work in conjuction with sending automation out via MIDI. The latter is already an option on the preferences page. It would probably be a good idea to make sync out an option too, and to make the two options mutually exclusive. [EDIT] The options are now mutually exclusive on the preferences page. Tap tempo is a little broken. [V100]Seems fine after all, but it would be useful to have a nudge tempo feature – ie. make the sequencer run faster or slower in small increments. [EDIT] Nudge tempo is now implemented, also when slaved to midi (Piano Phase!)
- When the pattern plays in reverse, step 1 doesn’t sound. [V100] This one seems to be intermittent and as such harder to pin down.
- Sometimes on first saving a pattern, the note duration gets reset to default. Man, I thought I got this one already! As a work-around readjust the duration, and resave the pattern.
- The first step doesn’t sound when stopping playback and restarting. Just fixed this for the RED: on restarting the sequencer after a stop, set currentTime = 0 so we trigger the “first time” code section in the sequencer. Whilst receiving clock, add the following to HandleStart:
- sixteenthStartTime = millis();
- seqMidiStep = true;
just build the alpha last night, it rules.
i’m having trouble with a couple things:
1) the pattern chaining and true step – i can’t get those buttons to light up when i press them in the trigger mode.
2) in edit mode, when i press f1 to trigger the sequencer, it always skips the first step
any insight on either or those? thanks!!!February 20, 2014 at 11:03 pm #1633
1) Yikes, this is a case of me stuffing up the documentation (it’s fixed now) – in short:
- Return To Head = Shift L & F5
- Next Pattern = Shift L & F6
- True Step = F6
2) Confirmed as a bug. I remember just fixing this recently for the RED. I’ll see to it very soon.February 21, 2014 at 2:40 am #1635
thanks so much for the response. i got the return to head / next pattern functions to work. true step is working too, but a bit differently than i expected.
in trigger mode, when i press f6, nothing happens with the led.
if i hold the random note / repeat note function in trigger mode, then let go, it will always keep going with the place in the pattern where the last random note existed. then i press f6, it will jump to what appears to be the true step.
is there a way to have true step be a toggle that is either activated or not, and when the random step / repeat step functions are released it automatically jumps to the true step?
thanks moshang!!!February 21, 2014 at 10:19 am #1636
But if True Step is latching and on, the LED for F6 will be lit. Currently that LED is used to indicate Next Pattern. Would it help to change the default behavior of Step Repeat and Random Step to always jump to the true step when released, but keep the True Step button momentary?February 22, 2014 at 4:49 am #1637
i think that would be awesome. imo i’d want the true step to be the default… curious what others think too thoughMarch 12, 2014 at 3:37 am #1875
wondering what you and others think of this..
when i build a pattern, if i start tweaking the notes, it’s much easier to do this with shift r pressed and using f5-f6 to get solid note increments rather than using the 6th pot on normal edit mode.
because of this, and often needing to restart the pattern, i sometimes accidentally hit f1 while still in shift r mode (forgetting to get out that mode because the workflow is so quick), thus losing all my work and getting the random pattern generator.
it’s happened to me a bunch of times now. totally user error, but the layout sort of sets it up for disaster. what are your potential solution ideas?
i sort of feel like the random *chromatic* pattern generator is a bit useless, or at least definitely not as useful as the other 3 options of generators. what about making the random chromatic shift r + f1 is the shift r mode instead of just f1?
curious your thoughts. ever happen to you?March 13, 2014 at 1:14 am #1887
Yup, it’s happened to me too. I agree that it’s too easy to overwrite something you’ve been working on with a random pattern. Your solution sounds like a quick and easy fix.
By the way, I implemented a change on the Delta inspired by your comments about the Pattern Mode – releasing the Step Repeat and Random Step now jumps to the true step. Also, instead of just reversing the playback, F1 now steps through a bunch of Play Modes (forward, reverse, pendulum, random interval, drunk and random). On returning to “forward”, the step also jumps to the true step.
Question is how much I’ll be able to implement in the remaining bytes of programming space for the Alpha.
You must be logged in to reply to this topic.