Skip to content

Releases

tabby-v1.2.1

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 21 Nov 03:58

A message goes away at once when you press anything, and PLAY / STOP stays readable while it is up. A muted internal sound no longer loads the sound engine. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v1.2.1: a message goes when you press anything

  • Firmware package build ID: 9e858b3b5fa9f1b1 (first 16 hex digits). App image 488676 bytes (measured), margin 30781 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 52). From tabby-v1.2 (fef558ab16e275b4): +128 bytes. At least
    15360 bytes stay free for fixes. Free RAM 143180 bytes.
  • Installing over tabby-v04.2 to tabby-v1.2 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20. A song with EVENT LEAD set plays on older firmware, without the lead.
  • Released through the candidate flow, with the per-page timing check and the comparison of the device's own
    screen pixels, as candidate 3. Candidate 1 was held back: the pixel comparison again found a row of the page
    before left on HOME (fixed, below). Candidate 2 has that fixed, was installed and tested, and made the device's
    screen pictures; its first run stopped because this computer could not load the candidate's page for a moment
    (the device was never at fault), and was run again. Candidate 3 is the same firmware with those pictures in the
    manual, tested in full, and promoted. docs/BUILD.md 66.5 and 66.6.

What changed

  • Any press takes a message away at once: a button, a pad, a key of the keyboard, a knob. Untouched it stays
    about a second and a half, as before. (Buttons and knobs did this already; pads and keys did not.)
  • PLAY / STOP / REC stays readable while a message is up: the word stands at the left end of the message, in
    its own colour on black. The first line of a message therefore holds 9 characters and the others 13; thirteen
    messages were reworded to fit in three lines (FADER 1-4 / MOVE TO MATCH, PARA + K1 / MOVES A SCENE, > AGAIN /
    DELETES THE CLIP ...). Help and the guide quote the new words.
  • A band of the page before no longer stays on the screen. Seen again in the device's own pixels, on HOME
    after a page change while a song plays: the fix in tabby-v1.2 was not enough. The painter is called just before
    a note is due, so a band that takes long to paint (a title row) found a note due every time, while the short
    bands of the level meters went through. Each band now has its own limit: after a quarter of a second it is
    painted whatever is due.
  • An internal sound that cannot be heard is not played. A track muted on the mixer (blue, INT), or silenced
    by another track's solo, no longer starts its song notes on the SMK-37's sound engine. Until now the engine
    rendered such a track in full and threw the result away. A song whose parts go to outside gear only now costs
    the engine nothing. Unmuted, the track sounds from its next note. MIDI out is not touched by any of this.

Why CPU! is on for the whole Wrong Room song (your question)

  • Which parts trip it: track 1 (the DX7 piano), track 3 (the PSG) and track 8 (the 808 kit) together. Take any
    one of the three away and the guard does not act once in 16 seconds; take away track 2, 4, 5, 6 or 7 and it
    still acts once a second.
  • What it acts on: not a shortage. A block of sound took 0.6 to 1.0 ms to make, of the 2.9 ms it may take;
    the largest ever seen is 1.29 ms. The guard, which is inside the SDK's sound library (not ours to change), acts
    when a block comes in somewhere between 1.16 and 1.29 ms, under half of what is allowed.
  • What it changes: it lowers the number of voices the engine may sound at once from 62 to 59. No audio block
    was late or lost (0 underruns, 0 DMA overruns, 0 overloads in every run), and nothing changes on MIDI out (every
    soak: all notes on both cables, on time). The Wrong Room song plays eight parts of one note each, so three
    voices fewer of 62 take nothing from it. NOT MEASURED: the audio itself, voice by voice.
  • Was it counting load that is not real? In your project as it is: no. The three parts that trip it are parts
    whose internal sound is on. But a muted sound was counted in full: with every internal sound muted on the mixer
    the guard acted exactly as often and a block took as long. That is the cause fixed above; the release run now
    measures it (step guard).

Validation

Candidate 3 (builds/tabby-v1.2.1-rc3/) on the device, unattended, before the promotion. The test computer was kept
awake while it measured. "Own" is the device's own figure: the latest a timed event left after its due time. The DIN
figure is the band without each line's first note at SEQ PLAY, which stands behind MIDI Start and Song Position on
the cable and is given beside it.

  • The device's pixels: 46 of 46 pictures identical to the simulator's, 24 at rest and 22 while the song played;
    among them a message with PLAY or STOP at its left end, and the page half a second after a key: no message.
  • The CPU guard, Wrong Room song: as it is 0.00 actions a second, a block of sound 0.63 ms of 2.90, 62 voices
    (tabby-v1.2: 1.06 a second, 0.86 ms, 59 voices). Every internal sound muted: 0.00 a second, 0.10 ms.
One line, 960 notes DIN ms first note USB ms own ms
Overview (three runs) 1.71, 1.67, 1.67 +1.12, +1.36, +1.41 1.71, 1.71, 1.68 1.55, 1.51, 1.44
CLIPS 1.65 1.66 1.51
SCENES 1.71 1.81 1.47
SYNC / MIDI 1.63 1.64 1.46
ACTIONS 1.67 1.64 3.50
Mixer 1.63 1.69 1.49
  • One line stays under 2 ms on every page. Eight lines: 2.57 to 2.88 ms on DIN, about 1.9 on USB. On ACTIONS the
    device's own figure is 3 to 4 ms as in every version (reported, not judged).
  • Soak with EVENT LEAD OFF, 40 minutes, 19 segments on six pages, none bad: every scene entry sent its events; USB
    band 1.30 to 2.33 ms; on the one DIN cable 14.70 to 15.13 ms, as before.
  • Soak with EVENT LEAD 1/16, 40 minutes, 19 segments, none bad: DIN band 1.57 to 1.84 ms, USB 1.31 to 1.64 ms.
  • CLIP SETTING 40 of 40, take edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip
    chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16, recording 25 of 25, STEP page 18 of 18, CLIPS page 40
    of 40 twice, the timing song 960 of 960 notes (worst 1.16 ms).
  • Full backup, restore of that backup, verify: PASS (41 items). The panel was left as it was found; no command went
    unanswered; the only thing a test left was the CLIPS page after the screen tour (put back).
  • Still not looked at by a person: the glass itself (test T97 of the guide).

tabby-v1.2

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 20 Nov 10:59

Messages moved to the top of the screen, so they never cover the pads' cells. The firmware can now give back the pixels it sent to its screen; the release test compares them with the simulator's on every page, and the manual's pictures are the device's own. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v1.2: messages at the top; the screen proven on the device

  • Firmware package build ID: fef558ab16e275b4 (first 16 hex digits). App image 488548 bytes (measured), margin 30909 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 51). From tabby-v1.1 (f0bd5047ca742907): +1824 bytes. At least
    15360 bytes stay free for fixes. Free RAM 143244 bytes (192 fewer).
  • Installing over tabby-v04.2 to tabby-v1.1 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20. A song with EVENT LEAD set plays on older firmware, without the lead.
  • Released through the candidate flow, as candidate 7. Candidate 1 was held back: its screen copy asked the device
    for one block of 57600 bytes and the device's heap refused. Candidate 2 (a smaller copy) was held back: one line
    measured 2.01 and 2.03 ms on two of eight pages, and its screen copy showed why the device never finished a
    picture while a song played (below). Candidate 3 (no more repaint on every step) was held back: the pages were still
    repainted on every eighth note, now exactly on the notes, and one line measured 2.3 to 2.5 ms on CLIPS and
    SCENES. Candidate 4 has the fix for that and for the standing CPU GUARD box, was installed and tested and made
    the device's screen pictures. Candidate 5 (candidate 4's firmware, those pictures in the manual) was held back:
    its own pixel comparison found leftover pieces of the page before on HOME, and eight lines on SCENES measured
    3.9 ms once. Candidate 6 has both fixed and passed everything but one soak segment, in which the
    song stayed in a scene: a fault of the song player at SEQ PLAY that is as old as song mode (below). Candidate 7
    has it fixed, was tested in full, and is the one promoted. Its manual pictures are the ones taken on candidate
    4's build; its own release run compared its own pixels again. docs/BUILD.md 65.1 to 65.7.

What changed

  • A message is an amber box across the top, over the top line (in tabby-v1.1 it was across the bottom and
    covered the lower pad row and part of the queue line of tracks 5 to 8). One line covers the top line; two or
    three lines also cover the title row and the row under it. It stays about a second and a half, as before. The
    KNOB BANK list stays at the bottom and is readable under a shortcut's message.
  • CLIPS and SCENES are no longer painted again on every 16th note while a song plays. Found by the screen
    copy: the page's own "did anything change" test included the step counter, so the whole page (15 bands) was
    repainted eight times a second, more than the painter manages beside the MIDI sends (84 bands a second): a
    picture was never finished, and every note had a band in its way. It has been so since these pages exist. Now a
    page is repainted when something it shows changes (the scene, a launch, a queue); the bar count repaints only its
    own digits; on STEP only the rows of the step cells follow the running step. The pads' blink phase, which
    repainted the page on every eighth note without anything on the screen blinking, is out of that test too.
  • A song could start wrong at SEQ PLAY: fixed. Rarely (once in the roughly 300 starts of this release's test
    runs; never seen before, though the code was the same), the song played scene 1, then scene 2, then scene 2 for
    ever, and sent its notes on the device's MIDI channels instead of the song's. The control task looked at "is it
    playing?" and then at "is a start pending?"; when the audio interrupt took the start between those two looks,
    it saw neither, took the song for ended and let go of it while it played on. The two looks are in the safe order
    now, and a test puts the interrupt at that very place. If this ever happened to you on stage it looked like a
    song stuck in its second scene with some parts on the wrong synth; stopping and starting cured it.
  • A band left over from the page before is painted within a few passes. Found by the pixel comparison on
    candidate 5: 2.4 seconds after PATCH from CLIPS to HOME, while a song played, the project name's row still showed
    pieces of CLIPS. On HOME the level meters ask for their bands on every frame and were served first every time.
    Every second band now goes in plain rotation.
  • A page is not composed when a note is due before the composing would end (as for a band): SCENES is composed
    again at each new scene, the moment its first notes are due.
  • CPU GUARD - VOICES ADAPTED is no longer a message box. Seen in the device's own pictures: with eight parts on
    the internal sounds the guard takes voices back about once a second, and its message stood over the page for the
    whole song (every Wrong Room soak since tabby-v1.0 counted 125 of them in 125 seconds; nobody was looking at the
    screen). It is CPU! in amber in the top line while it happens. AUDIO OVERLOAD and MIDI FULL stay message boxes.
  • The wait before a due MIDI note counts the band's own last painting time, not only that of the band before it
    (large text makes bands differ more: 0.6 to 2.5 ms).
  • Kept as they were, by your answers: MASTER MUTED small in the top line (K8=0); no pattern cells and no knob strip
    on HOME.
  • The screen copy (remote command 29 {19}; it only reads). The LCD cannot be read back: one data line, driven by
    the SoC only. So the firmware can keep a copy of every rectangle of pixels it hands to the LCD, freeze it when the
    picture is whole, and send it over USB. It takes 29 KB of memory, in fifteen small blocks, only while a test has
    switched it on.
  • The comparison (a step of every release run from now on): one tour of every page of docs/CONTROL-MAP.md
    section 20, 22 pictures at rest and 22 while the song plays, run on the device with remote panel keys and in the
    simulator with the same song at the same place in the song; every pixel compared. Left out, and named in the
    result: the level meters and MIDI-in marks on HOME (they follow the audio), FREE / RECL on ACTIONS and the stored
    project name on PRESETS and SAVE PROJECT (the device holds your data, the simulator starts empty).
  • The timing figures: this computer measures when a note arrives; the device also counts, by its own clock, how
    long after its due time each note left. From this release the release run reads both, and one line must be
    under 2 ms by both. The test computer is kept awake while it measures: idle, its own timestamps wander by 0.1 to
    0.3 ms (docs/BUILD.md 65.4).
  • The manual's pictures are the device's, taken by that test, in place of simulator renders. Two are still the
    simulator's and say so: SAVE PROJECT and STOP TO SAVE need the > button, which the device does not let a remote
    command press.
  • What this does not prove: the last step from the LCD's input to the glass (colours, contrast, viewing angle, a
    dead pixel), and the start screen (gone before a command can ask). Test T97 of the guide is that look, by you.

Validation

Candidate 7 (builds/tabby-v1.2-rc7/) on the device, unattended, before the promotion. Times at the test computer
were taken with its cores kept awake; "own" is the device's own figure: the latest a timed event left after its
due time.

  • The device's pixels: 44 of 44 pictures identical to the simulator's, 22 at rest and 22 while the song played.
    Left out, by name: the level meters and MIDI-in marks on HOME, FREE / RECL on ACTIONS, the stored project name on
    PRESETS, the last played note's name on STEP, and the unsaved-project mark and CPU! in the top line where the two
    differ. Not taken on the device: SAVE PROJECT and STOP TO SAVE (the > button).
One line, 960 notes DIN ms USB ms own ms
Overview (three runs) 1.66, 1.75, 1.85 1.62, 1.60, 1.62 1.49, 1.51, 1.48
CLIPS 1.75 1.60 1.49
SCENES 1.68 1.68 1.44
SYNC / MIDI 1.79 1.59 1.44
ACTIONS 1.74 1.64 2.96
Mixer 1.79 1.62 1.45
Eight lines, worst line DIN ms USB ms own ms
Overview 3.04 2.35 2.21
CLIPS 2.27 2.17 2.19
SCENES 2.36 2.24 2.12
  • One line stays under 2 ms on every page, at the test computer and by the device's own figure (tabby-v1.1, own:
    CLIPS 1.66, SCENES 1.87, mixer 1.49). On ACTIONS the device's own figure is about 3 ms as in every version (the
    page reads the song storage; the line's notes arrive within 1.74 ms); it is reported, not judged.
  • Soak with EVENT LEAD OFF, the Wrong Room song looping, 40 minutes, 19 segments on six pages, none bad: every
    scene entry sent its events; USB band 1.73 to 2.19 ms; on the one DIN cable 14.88 to 15.79 ms, as before.
  • Soak with EVENT LEAD 1/16, 40 minutes, 19 segments, none bad: DIN band 1.91 to 2.33 ms, USB 1.75 to 1.98 ms.
  • CLIP SETTING 40 of 40, take edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip
    chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16, recording 25 of 25, STEP page 18 of 18, CLIPS page 40
    of 40 twice, the timing song 960 of 960 notes (worst 1.16 ms).
  • Full backup, restore of that backup, verify: PASS (41 items). The panel was left as it ...
Read more

tabby-v1.1

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 19 Nov 21:16

A screen you can read at arm's length on a dark stage: nothing smaller than 10 x 14 pixels a character, stage information larger still, fewer things on a page. No new function; songs, projects and timing as on tabby-v1.0.2. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v1.1: the readable screen

  • Firmware package build ID: f0bd5047ca742907 (first 16 hex digits). App image 486724 bytes (measured), margin 32733 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 50). From tabby-v1.0.2 (9b00a12fd0346a65): 4032 bytes smaller
    (shorter texts; the font is the same one, drawn larger, so it costs nothing). At least 15360 bytes stay free for
    fixes. Free RAM 143436 bytes (1024 more).
  • Installing over tabby-v04.2 to tabby-v1.0.2 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20. A song with EVENT LEAD set plays on older firmware, without the lead.
  • Released through the candidate flow: published as builds/tabby-v1.1-rcN/, installed and tested on the device
    (every device test, the timing runs on eight page and song combinations, both soaks, full backup, restore, verify)
    before it reached the main page.

What changed: the screen, and only the screen

Up to tabby-v1.0.2 almost all text was the 5x7 font at scale 1 (5 x 7 pixels a character, about 3 point). Now:

  • Nothing is smaller than scale 2 (10 x 14 pixels, 20 characters on a line).
  • Scale 3 (15 x 21 pixels, 13 on a line) for what you need while playing: the tempo, PLAY / STOP / REC, the
    selected track, the song and the scene, what comes next, queued launches, and every message and warning.
  • The font is still the 5x7 one, enlarged: its strokes are 2 and 3 pixels thick, which reads better in the dark
    than a finer 8x16 font with 1-pixel strokes would, and it costs no flash. No lowercase.
  • The layouts are in docs/CONTROL-MAP.md section 20, page by page; the manual has a picture of every page, made
    from the simulator (the firmware's own screen code).
Page What it shows now
Top line (every page) 120 PLAY T1, large: tempo; PLAY, STOP, PAUS, REC (red), ARMD, CNT4 (count-in), LOST; the selected track in its colour. Small: ARP; K8=0 while the master volume is at zero; in amber *SNG / *PRJ / *S+P for what waits for a save. It follows the song (before, it said STOP while a song played). Gone: the pattern step counter, LIVE.
Messages An amber box across the bottom, black letters at scale 3, one to three lines; a question on ACTIONS stays until answered. The messages you meet while playing were shortened to two lines (TO SCENES AT CYCLE, EMPTY PAD / REC OR PARA, TRACK MUTED / SOUND + MIDI, RESERVED FOR SEQ PLAY ...).
KNOB BANK held The shortcut list at scale 2 on a grey box; a shortcut's message as the amber box over it.
HOME Eight rows: the track number at scale 3 (filled box: selected), K / P where the keys and the pads play, the sound, MUTE / INT / SOLO / LIVE / OFF, the level and a meter. Gone: the pattern step cells, the knob strip (K1 moves the row's level, K4 the tempo in the top line), the pad pressure figure, the standing explanations (the row shows the state).
CLIPS S01 SCENE 002 at scale 3. A cell per track in two rows of four: the clip it plays at scale 3 (white from the scene, green launched, -- silent; amber / blue when muted) and under it at scale 3 what is queued (>05, >ST, >SC), where a chain leads (+05, +ST), or MUT / INT. The 16 pads of the bank in two rows of eight like the pads, with the clip numbers. Gone: SELECTED / STEPS / BLK, the help lines.
SCENES SONG 01, SCENE 001/002 and what comes next (NEXT 002, TO 002 queued, AT 003 reserved, LOOPING, LAST SCENE; errors in amber) at scale 3. The pass and bar, the scene's clip per track, the 16 scenes of the pad bank in two rows of eight, and K1 to K4 as TIME / THEN / HOLD / JUMP. Gone: block numbers, the LEN line, EVENTS, the help lines.
STEP STEP CLIP 02 at scale 3; the bar's 16 steps in two rows of eight with their note counts; the step's notes by name on one line; the chosen note's NOTE / VEL / STRT / LEN over K1 to K4 (before: a six-line table at scale 1).
CLIP SETTING Eight lines a page at scale 2, four pages instead of three (1/4 and 2/4 the clip, 3/4 and 4/4 the song). Shorter: PLAY QUANT, CLICK CH, K1 CC to K4 CC; values 016, 016 ST, 03 EMPTY / 03 USED, REC ONLY, MIDI, FWD+REV, 1/8=032.
SYNC / MIDI, MIDI TRACK, PARA, FX, ARP One line per knob: K1 to K4 with the full name at scale 2 and the value at scale 3 (before: a strip of four small boxes and a list of what the knobs do).
MIX Mute and solo in two rows of eight like the pads, eight level bars, K1 to K4.
ACTIONS, SOURCE, PRESETS, SAVE PROJECT, start screen Scale 2 lists; names, slot numbers, results and errors at scale 3. ACTIONS shows FREE 317K RECL 0K and USER 471040 READY.
  • The workbench's simulator draws the same pages (it runs the same code), and its click areas moved with them.
  • Timing: the drawing is sliced as before (bands of 16 rows, a band waits for a due MIDI event). Measured below.

Validation

Candidate 1 (builds/tabby-v1.1-rc1/) on the device, unattended, before the promotion. Every time below was taken
against a clock the test computer does not correct.

One-line song, 960 notes, worst line DIN ms USB ms
Overview (three runs) 1.85, 1.70, 1.74 1.72, 1.84, 1.76
CLIPS 1.80 1.74
SCENES 1.78 1.61
SYNC / MIDI 1.81 1.69
ACTIONS 1.76 1.67
Mixer 1.75 1.61
Eight-line song, worst line DIN ms USB ms
Overview 2.38 2.43
CLIPS 2.35 2.45
SCENES 2.71 2.66
  • One line stays under 2 ms on every page (tabby-v1.0.2, overview: DIN 1.74 to 1.94, USB 1.70 to 1.78). Eight
    lines are where they were (2.2 to 3.1 ms from tabby-v04.4 to tabby-v1.0).
  • Soak with EVENT LEAD OFF, the Wrong Room song looping, 40 minutes, 19 segments on six pages, none bad: every
    scene entry sent its events; USB band 1.68 to 1.96 ms; on the one DIN cable 14.83 to 15.65 ms, the first notes
    after the loop point behind the events, as on tabby-v1.0.1 and tabby-v1.0.2.
  • Soak with EVENT LEAD 1/16, 40 minutes, 19 segments, none bad: DIN band 1.83 to 2.78 ms, USB 1.66 to 2.52 ms;
    left out of the band as before, the very first note at SEQ PLAY (14.39 ms on DIN).
  • CLIP SETTING 40 of 40, take edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip
    chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16, recording 25 of 25, STEP page 18 of 18, CLIPS page 40
    of 40 twice, the timing song 960 of 960 notes (worst 1.19 ms on DIN, 1.08 ms on USB).
  • Full backup, restore of that backup, verify: PASS (41 items). The panel was left as it was found (mutes, focus,
    ARP switches, CLOCK, A2: read after every test).
  • Not tested by a person: how the screen reads from arm's length in the dark. The device tests read the firmware's
    state over the remote commands, not the pixels; the pixels were checked in the simulator, which runs the same
    screen code (28 pages, pictures in the manual). Test T97 of the guide is the check on the unit.

tabby-v1.0.2

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 19 Nov 11:52

EVENT LEAD: a song setting that sends a scene's program changes before its downbeat. It is OFF unless you turn it on, and with OFF every song plays exactly as on tabby-v1.0.1. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v1.0.2: EVENT LEAD

  • Firmware package build ID: 9b00a12fd0346a65 (first 16 hex digits). App image 490756 bytes (measured), margin 28701 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 49). From tabby-v1.0.1 (b3ecdffbabe49bf0): +288 bytes. At least
    15360 bytes stay free for fixes. Free RAM 142412 bytes (unchanged).
  • Installing over tabby-v04.2 to tabby-v1.0.1 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20. A song with EVENT LEAD set plays on older firmware, without the lead.
  • Released through the candidate flow: published as builds/tabby-v1.0.2-rcN/, installed and tested on the device
    (every device test, both soaks, full backup, restore, verify) before it reached the main page.

What is new: one setting

  • EVENT LEAD on CLIP SETTING (FX on CLIPS; page 3/3, the last line): OFF, 1/32, 1/16, 1/8 or 1/4.
  • A scene can send program changes, a bank select and controllers when it is entered. With EVENT LEAD they go out
    that long before the scene's downbeat. On one DIN cable those messages used to pass ahead of the scene's first
    notes and made them late (about 0.8 ms a message: 14 ms behind 17 messages). With a lead they have left the cable
    before the downbeat and the first notes are on time.
  • It is OFF in every song until you set it. With OFF the SMK-37 sends exactly what tabby-v1.0.1 sends: in the
    simulator, every byte of six passes of the Wrong Room song, clock included, in the same audio block.
  • What a lead costs. The synth changes its sound that much before the downbeat, so the tail of the previous
    scene's last notes is heard on the new sound. Use the shortest lead that is enough, and leave it OFF where the
    change must not be heard early.
  • A device's waiting time from the rig profile (the H90's 255 ms, for example) is kept and counts from when its
    own program change goes out; the lead comes in front of it.
  • No lead at SEQ PLAY: the first scene's messages go out with the start (use SEND SETUP before). A scene recalled
    later than the lead before its bar sends its messages at once. A change of the setting is heard from the scene
    after the next. It is saved with the song.
  • Nothing else is new.

Validation

Candidate 2 (builds/tabby-v1.0.2-rc2/) on the device, unattended, before the promotion. Every time below was taken
against a clock the test computer does not correct.

  • Soak with EVENT LEAD OFF, the Wrong Room song looping, 40 minutes, 19 segments on six pages, none bad: every
    scene entry sent its events (136 program changes and 48 controllers in every segment); USB band 1.64 to 2.75 ms;
    on the one DIN cable 14.8 to 17.0 ms, the first notes after the loop point behind the events, as on tabby-v1.0.1.
  • Soak with EVENT LEAD 1/16, 80 minutes, 38 segments, none bad: every scene entry sent all its events, and on
    the DIN cable they had ended 112 to 126 ms before the scene's first note (124 to 128 ms on USB). The first notes
    are on time on DIN: band 1.82 to 2.42 ms
    (USB 1.66 to 2.07 ms). Left out of that band, and still late on a
    shared cable: the very first note at SEQ PLAY (14.4 ms), where there is no lead.
  • In the simulator: with EVENT LEAD OFF every byte of six passes of the song, the clock included, in the same audio
    block as tabby-v1.0.1 sends it (SHA-256 f2651bb6dbf247c6...); with 1/16 every entry's events 43 blocks (a 16th)
    before its first note and every note in the block it was in; with a 255 ms device gap inside the stream, the next
    message 255 ms after that program change and the last one still a 16th before the note.
  • CLIP SETTING 40 of 40 (with the EVENT LEAD line: OFF, two clicks 1/16, no further than 1/4, back to OFF), take
    edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip chains 11 of 11, scene chain
    13 of 13, scene edit 16 of 16, recording 25 of 25, STEP page 18 of 18, CLIPS page 40 of 40 twice, the timing song
    960 of 960 notes (worst 1.19 ms).
  • One line, 960 notes, three runs: DIN 1.83, 1.74, 1.94 ms; USB 1.74, 1.70, 1.78 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice. The panel was left as it was found (mutes,
    focus, ARP switches, CLOCK, A2: read after every test).

Candidate 1 was the same firmware build and passed both soaks too. It was not promoted because one check of the
CLIP SETTING test counted no controller message after a knob click, once; the test passed 40 of 40 twice afterwards
and in candidate 2. The likely cause was the test tool mixing two clocks (docs/BUILD.md 63.2); that is not proven.

tabby-v1.0.1

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 19 Nov 02:57

A fix for songs of two scenes that loop: each scene's program changes are now sent every time the scene is entered. Use this instead of tabby-v1.0 (Full backup first; storage does not move).

Classic Tabby tabby-v1.0.1: scene events in a two-scene loop

  • Firmware package build ID: b3ecdffbabe49bf0 (first 16 hex digits). App image 490468 bytes (measured, unchanged), margin 28989 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 48). At least 15360 bytes stay free for fixes. Free RAM 142412 bytes.
  • Installing over tabby-v04.2 to tabby-v1.0 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20.
  • Released through the candidate flow: published as builds/tabby-v1.0.1-rcN/, installed and tested on the device
    (every device test, the soak, full backup, restore, verify) before it reached the main page.

The fix

  • What was wrong. A scene can carry row events: program changes, a bank select, controllers for your synths and
    pedals. They are sent when the scene is entered. In a song of two scenes that loops (scene 1, scene 2, scene 1,
    ...) they were sent on the first pass and after that only now and then: in the two-hour test of tabby-v1.0 between
    half and all of them arrived, depending on the page on the screen. A synth could stay on the other scene's sound.
    The notes were never affected.
  • Who was affected. Songs that go round two scenes. Three or more scenes in a row were not, and neither was a
    scene that repeats. tabby-v04.23 shows the same; older versions have the same code.
  • Now every entry sends its events. Nothing else changed from tabby-v1.0.

How it was missed

The two-hour soak of tabby-v1.0 recorded the missing program changes; my check of the soak only compared the two
MIDI ports with each other, and both lacked the same messages, so it passed and tabby-v1.0 was released. I found it
when I read the numbers for the release notes. The soak now requires the events of every scene entry.

The limit of tabby-v1.0's notes still holds

On one DIN cable a scene's program changes pass ahead of its first notes (about 0.8 ms each).

Validation

Candidate 1 (builds/tabby-v1.0.1-rc1/) on the device, unattended, before the promotion; it passed at the first attempt.
Every time below was taken against a clock the test computer does not correct.

  • The two-hour soak, the Wrong Room song looping, 120 minutes in 57 segments on six pages. Every scene entry
    sent its events:
    17 messages for scene 1 and 6 for scene 2, sixteen entries in every segment, on USB and on the DIN
    cable; 136 program changes and 48 controllers in each of the 57 segments (tabby-v1.0: 68 to 136). Every note-on
    and note-off arrived, no stuck note, no underrun. On USB each line's band was 1.70 to 2.45 ms, the largest single
    error 1.75 ms. On the one DIN cable 14.8 to 16.2 ms, in the first notes after the loop point (behind the events).
  • Take edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip chains 11 of 11, scene
    chain 13 of 13, scene edit 16 of 16, CLIP SETTING 38 of 38, recording 25 of 25, STEP page 18 of 18, CLIPS page 40
    of 40 twice, the timing song 960 of 960 notes on DIN and USB (worst 1.12 ms).
  • One line, 960 notes, three runs: DIN 1.87, 1.81, 1.77 ms; USB 1.90, 1.78, 1.98 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.
  • In the simulator, six passes of the song: 17 and 6 event messages at every entry (before the fix: 17 6 0 0 0 6 0 0 0 6 0 0).
  • Not checked by a machine: the screen fix of tabby-v1.0 (the KNOB BANK list) has been seen in the simulator only.

tabby-v1.0

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 19 Nov 00:25

Use tabby-v1.0.1. Found after this release: in a song of two scenes that loops, this build skips most of the scenes' program changes after the first pass (tabby-v04.23 does too; older builds have the same code). The notes are not affected. tabby-v1.0.1 fixes it.

The release for the stage: no new function, a full regression with a two-hour soak, one screen fix, and a one-page stage checklist. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v1.0

  • Firmware package build ID: 3b6cde4c259dd43a (first 16 hex digits). App image 490468 bytes (measured), margin 28989 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 47). From tabby-v04.23 (c7b2ff04e81b3226): +32 bytes. At least
    15360 bytes stay free for fixes. Free RAM 142412 bytes (unchanged).
  • Installing over tabby-v04.2 to tabby-v04.23 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20.
  • Released through the candidate flow: published as builds/tabby-v1.0-rcN/, installed and tested on the device
    (every device test, the soak, full backup, restore, verify) before it reached the main page.
  • The name has no leading zero any more: tabby-v1.0 follows tabby-v04.23.

What changed

  • No new function. Everything is as in tabby-v04.23.
  • One fix on the screen. KNOB BANK with a pad selects or mutes a track and says so (TRACK SELECTED, TRACK MUTED:
    SOUND AND MIDI, TRACK UNMUTED). That message was written on a line the KNOB BANK list covers while the button is
    down, so it was never seen. It is now the first line of that list for a second.
  • The stage checklist: one page, docs/STAGE-CHECKLIST.md in the source and section 9 of the manual: before the
    show day (never install firmware on a show day), power-up order, what to check on the screen, what to do when a
    synth does not respond, what to do when the timing feels off.
  • The pad rows are confirmed on a unit: pads 1 to 8 are the upper row.

A limit you should know

On one DIN cable (the TRS jack with an adapter) a scene's program changes and controllers pass ahead of its first
notes, about 0.8 ms each. With the Wrong Room test song (17 such messages at its loop point) the first notes after
the loop came 14 ms late on the cable, while on USB every note was within 2.2 ms. With the H4MIDI on USB each synth's
cable carries only its own messages. This is not new and not changed; the manual's known limits say it too.

Validation

Candidate 1 (builds/tabby-v1.0-rc1/) on the device, unattended, before the promotion; it passed at the first attempt.
Every time below was taken against a clock the test computer does not correct.

  • The two-hour soak: the Wrong Room song (8 parts, 16 program changes, a bank select and 5 controllers in its two
    scenes, looping) for 121 minutes in 57 segments on six pages. No bad segment: every note-on, note-off, program
    change and controller arrived, the same on USB and on the DIN cable; no stuck note, no underrun. On USB each
    line's band was 1.65 to 2.76 ms and the largest single error 2.13 ms. Correction: "every ... program change
    and controller arrived" was wrong. The check compared the two ports with each other; both lacked the same
    messages. Between 68 and 136 of 136 program changes arrived in a segment (docs/BUILD.md 62). On the one DIN cable the band was 14.8 to
    15.8 ms, all of it in the first notes after the loop point (the limit described above).
  • The one-hour soak (on tabby-v04.23, the same code but for the screen fix): 70 minutes, 33 segments, one line
    and eight lines in turn on six pages, A2 on: one line 1.60 to 1.93 ms on DIN and 1.62 to 1.87 ms on USB; eight
    lines 2.26 to 3.14 ms on DIN and 2.15 to 2.67 ms on USB; no bad segment.
  • Take edit 26 of 26, note repeat and step loop 20 of 20, program and knobs 10 of 10, clip chains 11 of 11, scene
    chain 13 of 13, scene edit 16 of 16, CLIP SETTING 38 of 38, recording 25 of 25, STEP page 18 of 18, CLIPS page 40
    of 40 twice, the timing song 960 of 960 notes on DIN and USB (worst 1.12 ms).
  • One line, 960 notes, three runs: DIN 1.78, 1.70, 1.64 ms; USB 1.75, 1.78, 1.67 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.
  • Not checked by a machine: the screen fix was seen in the simulator's picture; nobody has looked at it on a unit yet.

tabby-v04.23

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 18 Nov 19:57

The step loop: on CLIPS, hold NOTE REPEAT and pad 9, 10, 11 or 12, and everything that plays repeats its last 1, 2, 4 or 8 steps until you let go. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v04.23: the step loop

  • Firmware package build ID: c7b2ff04e81b3226 (first 16 hex digits). App image 490436 bytes (measured), margin 29021 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 46). From tabby-v04.22 (1726ba6b317b1bb5): +640 bytes. At least
    15360 bytes stay free for fixes, so 13661 bytes can still go to features. Free RAM 142412 bytes (-288).
  • Installing over tabby-v04.2 to tabby-v04.22 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20.
  • Released through the candidate flow: published as builds/tabby-v04.23-rcN/, installed and tested on the device
    (every device test, full backup, restore, verify) before it reached the main page.

What is new

  • The step loop. While the song plays, on the CLIPS page, hold NOTE REPEAT: pads 9 to 12 light amber. Hold one of
    them: every track that plays repeats its last 1, 2, 4 or 8 steps (16th notes), over and over: STEP LOOP: LAST 4
    STEPS. Let the pad go and the song goes on where it would have been, in time with the master cycle.
  • Launched clips and tracks that follow the scenes are looped alike. Clips, chains and scenes change underneath as
    they would have; you hear the result when you let go.
  • While NOTE REPEAT is down no pad launches a clip.
  • Not while the song is stopped and not during a take. Stopping the song ends a loop.
  • It takes the steps just played, not steps you choose, and it loops all tracks, not one (on the MC-707 the pads are
    the steps; here they are the clips).

Validation

Candidate 2 (builds/tabby-v04.23-rc2/) on the device, unattended, before the promotion:

  • Note repeat and step loop 20 of 20. Heard on the MIDI out: with pad 10 held the last two steps repeat, the note
    every 250.0 ms (249.9 expected); with pad 12 the last eight, the bass note every 999.4 ms (999.7 expected) and the
    other bass note not at all; after the pad is let go the notes are back on the song's beats (within 1.5 ms); a pad
    pressed while NOTE REPEAT is down launches nothing. A one-step loop cannot be aimed by remote and was only
    checked to loop one step (the simulator checks its notes: every 16th).
  • One line, 960 notes, three runs: DIN 1.90, 1.76, 1.71 ms; USB 1.78, 1.79, 1.73 ms: the change in the audio thread
    costs nothing that shows. The timing song: 960 of 960 notes, worst 1.22 ms.
  • Take edit 26 of 26, program and knobs 10 of 10, clip chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16,
    CLIP SETTING 38 of 38, recording 25 of 25, STEP page 18 of 18, CLIPS page 40 of 40 twice.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.

Candidate 1 was the same firmware build. It was not promoted: one new check of mine could not be aimed by remote,
and three timing checks read up to 9.9 ms in that run, equally on DIN and USB. The same build read 1.2 ms in three
later runs of that test; the likeliest cause is the test computer's clock being corrected during the run, which I
could not prove (docs/BUILD.md 59.1 and 59.2).

tabby-v04.22

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 18 Nov 18:43

NOTE REPEAT now does what is printed on it: hold it and a held key or pad repeats. The keys / pads switch moved to KNOB BANK + NOTE REPEAT. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v04.22: NOTE REPEAT repeats notes

  • Firmware package build ID: 1726ba6b317b1bb5 (first 16 hex digits). App image 489796 bytes (measured), margin 29661 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 45). From tabby-v04.21 (0bb7c4fb25bc175a): +608 bytes. At least
    15360 bytes stay free for fixes, so 14301 bytes can still go to features. Free RAM 142700 bytes (unchanged).
  • Installing over tabby-v04.2 to tabby-v04.21 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20.
  • Released through the candidate flow: published as builds/tabby-v04.22-rcN/, installed and tested on the device
    (every device test, full backup, restore, verify) before it reached the main page.

What changed: one gesture moved

  • The keys / pads focus switch is now KNOB BANK + NOTE REPEAT. Before, it was NOTE REPEAT alone. The KNOB BANK
    list on the screen has always shown it as NOTE REPEAT KEY-PAD.

What is new

  • Note repeat. Hold NOTE REPEAT and hold a key (or a pad, on a page where the pads play notes): the note repeats
    at the track's ARP rate for as long as you hold both. The screen says NOTE REPEAT 1/16 - HOLD A KEY OR PAD and the
    NOTE REPEAT lamp is lit. Turn K1 while you hold NOTE REPEAT for the rate: 1/4, 1/8, 1/16, 1/32. It works on every
    page and does not change the page.
  • What it is, and its limits. Note repeat is the track's arpeggiator switched on while the button is down. One
    held note repeats. Several held notes take turns in the ARP's DIRECTION (a chord is arpeggiated, not repeated as a
    chord), and with RANGE above 1 OCT a note also climbs octaves. GATE and SWING of the ARP page apply. A key that is
    already down when you press NOTE REPEAT is cut off: press NOTE REPEAT first. A take records the key you hold as one
    note, not the repeats. The project shows as changed afterwards, because the ARP switch belongs to the project. A
    track whose ARP is on already is left alone.

Validation

Candidate 1 (builds/tabby-v04.22-rc1/) on the device, unattended, before the promotion; it passed at the first attempt:

  • Note repeat 11 of 11. Heard on the MIDI out: a held key 18 times in 2.2 s, 124.8 ms apart at 1/16; one click of
    K1 faster, 62.7 ms apart (1/32). No interval was more than 3.0 ms from the middle one: the arpeggiator starts its
    notes on audio blocks of 2.9 ms, so the repeats are even to one block, not to the 2 ms of the song's notes.
    NOTE REPEAT let go: nothing repeats and the ARP switch is off again. KNOB BANK + NOTE REPEAT: keys to pads and back.
  • Take edit 26 of 26, program and knobs 10 of 10, clip chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16,
    CLIP SETTING 38 of 38, recording 25 of 25, STEP page 18 of 18, CLIPS page 40 of 40 twice, the timing song 960 of
    960 notes on DIN and USB.
  • One line, 960 notes, three runs: DIN 1.71, 1.73, 1.79 ms; USB 1.60, 1.68, 1.70 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.

tabby-v04.21

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 18 Nov 18:05

Three things on the panel: FX with a key clears notes during a take, KNOB BANK with OCTAVE- or OCTAVE+ shifts a clip by a step, and NEW SONG in ACTIONS starts an empty song. Reinstall to get them (Full backup first; storage does not move).

Classic Tabby tabby-v04.21: clear notes in a take, shift a clip, a new song on the panel

  • Firmware package build ID: 0bb7c4fb25bc175a (first 16 hex digits). App image 489188 bytes (measured), margin 30269 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 44). From tabby-v04.20 (693c8946957ae272): +1600 bytes. At least
    15360 bytes stay free for fixes, so 14909 bytes can still go to features. Free RAM 142700 bytes (-64).
  • Installing over tabby-v04.2 to tabby-v04.20 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20. Nothing in this release adds to that list: a shifted clip and a song made with NEW SONG are read by
    tabby-v04.10 and later.
  • Released through the candidate flow: published as builds/tabby-v04.21-rcN/, installed and tested on the device
    (every device test, full backup, restore, verify) before it reached the main page.

What is new

  • Clear notes during a take. While a take runs, hold FX and hold a key: each note of that key is taken out of
    the clip as the clip passes it. One pass of the clip clears them all; a shorter hold clears only what was passed.
    The key sounds but is not recorded; several keys can be held. During a take FX does nothing else (pressed alone it
    says HOLD FX + A KEY: CLEARS ITS NOTES). The cleared notes come back with the undo of the take.
  • Shift a clip. On the STEP page, KNOB BANK + OCTAVE+ moves every note, controller and step probability of the
    clip one step later, KNOB BANK + OCTAVE- one step earlier. What leaves one end of the clip comes in at the other.
    A run of shifts is one undo level. Without KNOB BANK the two buttons change the bar, as before.
  • NEW SONG in ACTIONS (SEQ + PARA). On SCENES, with the song stopped, turn K5 to a slot that says NO SONG; open
    ACTIONS, choose NEW SONG, press the > button twice. The song is named NEW SONG, uses the loaded project and its
    tempo, and has one empty scene. CLIPS opens: hold an empty pad and press SEQ REC or PARA for the first clip. A
    slot that holds a song is never replaced. The song's name is changed in the workbench.
  • ACTIONS has nine entries now (NEW SONG before A2 FAST MIDI) and shows them a little closer together.
  • Stickers (docs/STICKERS.md v0.4, in the source): no type below 6 point; they now cover the strip of key functions
    printed above the keys, on purpose, because none of those functions works in Classic Tabby. The pad rows are
    written down as an assumption: upper row = pads 1 to 8.

Validation

Candidate 2 (builds/tabby-v04.21-rc2/) on the device, unattended, before the promotion:

  • Take edit 26 of 26: the clip shifted later, earlier and round its end; FX + the key cleared the clip's four notes
    in one pass (2 left after 0.9 s) and recorded nothing; NEW SONG refused on a slot that holds a song, made in an
    empty slot, a first clip recorded into it, saved, read again, and the song deleted again.
  • Program and knobs 10 of 10, clip chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16, CLIP SETTING 38 of 38,
    recording 25 of 25, STEP page 18 of 18, CLIPS page 40 of 40 twice, the timing song 960 of 960 notes on DIN and USB.
  • One line, 960 notes, three runs: DIN 1.91, 1.72, 1.81 ms; USB 1.59, 1.67, 1.74 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.

Candidate 1 was the same firmware build. It was not promoted because one check group of the new device test failed:
the test pressed the wrong key (it assumed the keys' octave). The corrected test passed on candidate 1 as installed,
and candidate 2 passed every step (docs/BUILD.md 57.4).

tabby-v04.20

Choose a tag to compare

@SeattleUser0 SeattleUser0 released this 18 Nov 08:39

DIRECTION for each clip on CLIP SETTING: forwards, backwards, or forwards then backwards. Reinstall to get it (Full backup first; storage does not move).

Classic Tabby tabby-v04.20: direction for each clip

  • Firmware package build ID: 693c8946957ae272 (first 16 hex digits). App image 487588 bytes (measured), margin 31869 bytes
    below the 519457-byte limit (docs/FLASH-BUDGET.md 43). From tabby-v04.19 (60dd42e69b99e957): +1184 bytes. At least
    15360 bytes stay free for fixes, so 16509 bytes can still go to features. Free RAM 142764 bytes (-256).
  • Installing over tabby-v04.2 to tabby-v04.19 keeps storage as it is. Take a Full backup first anyway.
  • Going back to older firmware: songs saved on tabby-v04.10 or later cannot be read by older firmware. Go back to
    an older build only with a Full backup made before tabby-v04.10: install the older build, then restore that backup.
    A clip is refused (its track is silent) by firmware that does not know one of its settings: TRANSPOSE before
    tabby-v04.15, SHUFFLE and PLAY QUANTIZE before tabby-v04.17, STEP SIZE before tabby-v04.19, DIRECTION before
    tabby-v04.20.
  • Released through the candidate flow: published as builds/tabby-v04.20-rcN/, installed and tested on the device
    (every device test, full backup, restore, verify) before it reached the main page.

What is new

  • DIRECTION on CLIP SETTING (FX on CLIPS, page 2/3, after STEP SIZE): FORWARD, REVERSE or FWD THEN REV.
    REVERSE plays the clip's steps from the last to the first; each note keeps its place inside its step and its
    length. FWD THEN REV plays the clip forwards and then backwards, twice as long; if that would be more than 128
    steps or 512 events the line shows LONG and the clip plays forwards.
  • The clip itself is not changed. The STEP page shows the clip's own steps: the running light walks backwards, and
    a take is recorded at the step that sounds.
  • The MC-707's random direction is not built.
  • CLIP SETTING has 24 lines.

Validation

Candidate 1 (builds/tabby-v04.20-rc1/) on the device, unattended, before the promotion; it passed at the first attempt:

  • CLIP SETTING 38 of 38. Measured on MIDI out with a two-note test clip: in REVERSE the time from the first note to
    the second is 913.7 ms (914.1 calculated; 164.0 forwards); STEP SIZE 1/8 327.6 ms, SHUFFLE 50 PERCENT 207.0 ms,
    PLAY QUANTIZE 1/16 126.0 ms as before.
  • Program and knobs 10 of 10, clip chains 11 of 11, scene chain 13 of 13, scene edit 16 of 16, recording 25 of 25,
    STEP page 18 of 18, CLIPS page 40 of 40 twice, the timing song 960 of 960 notes on DIN and USB.
  • One line, 960 notes, three runs: DIN 1.68, 1.79, 1.85 ms; USB 1.68, 1.75, 1.82 ms.
  • Full backup, restore of that backup, verify: PASS (41 items), twice.