Extended Edition 0.1.9-query
Sequence tools, explained.
Copy and paste, preserve the destination groove, Undo, save and inspect patterns over USB.
What is new in 0.1.9-query?
Full-pattern and individual-lane copy/paste are joined by read-only pattern inspection. The menu offers25 scopes: ALL PARTS,11 rows for each drum kit,303 A and 303 B. BREAK is included in ALL PARTS; there is no BREAK-only scope.
How do I copy a whole pattern or just one part?
Stop playback. Open GLO → COPY/PASTE SEQUENCES, the top item above CLOCK OUT. Use SELECT to move between COPY FROM, PASTE INTO, COPY SCOPE and PASTE KEEP ACC/SW; ALGORITHM changes values. Select ALL PARTS, a drum row, or 303 A/B. Press SEL on PASTE KEEP ACC/SW, inspect source/destination/scope, then SEL confirms; HOME cancels. The chosen destination scope is replaced, not merged.
What stays unchanged at the destination?
Both shared drum-kit accent rows and pattern swing stay unchanged. Other lanes, sounds, strips, channel assignments and song references are retained for a single-part copy. Bass note accents, slides and ties belong to the bass sequence and do copy. A drum-only paste keeps shared legacy kit timing; in independent-lane mode, the selected lane’s timing copies.
How do I Undo or Redo the paste?
Leave the copy submenu and Global with HOME. With playback stopped, hold HOME and tap REC to Undo; hold HOME and tap PLAY to Redo. One paste is one transaction. Undo history does not survive restart. Check your pattern before saving; normal autosave remains independent.
How do I set a distinct accent and swing for testing?
In a drum SEQ view, hold ENV and tap a white step key to toggle that kit’s shared AC step. On HOME overview, KNOB2 adjusts the selected909 pattern’s swing, used across parts. Give the destination different markers before copying and confirm they survive the paste and Undo.
Does the copy survive saving and restarting?
The copied musical data is project data. A bounded physical909 full-copy test retained drum hits, shared accent step 2 and 60% swing after SAVE and a normal power cycle. This does not establish every instrument’s physical restart coverage. Back up first and verify your chosen workflow.
Can the computer inspect unsaved patterns without saving them?
Yes. This release adds command 49 to read current RAM. It does not call project save/flush, change patterns, edit notes, or alter Undo. CRCs and scan stamps reject corrupt, incomplete or changing scans. Reading requires playback stopped and keys/buttons released. Existing autosave can still operate independently; the query neither triggers nor postpones it.
How do I use the query and comparison tool?
Install Python 3 plus mido and python-rtmidi for USB reads. From the extracted bundle:
python tools/fm1_pattern_read.py read --patterns 5 7 --output before.json # Perform the panel copy or Undo, then release controls. python tools/fm1_pattern_read.py read --patterns 5 7 --output after.json python tools/fm1_pattern_read.py compare before.json after.json
Use a new output filename each time. Compare uses local files only and excludes scan stamps and dirty state from musical equality; it separately reports project fingerprint changes. It covers the requested patterns, not all device settings. Read failure never falls back to export/save.
What can the read-only query see?
All 32 pattern slots,25 instrument lanes, notes/gates/ties/slides/bass accents, shared kit accents and swing, lengths/rates, bass direction/transpose/generator settings, BREAK metadata and pattern-owned motion/probability. Legacy, independent and expanded formats are supported. It is not a raw-memory peek or a full device backup.
Why not use project backup to inspect an unsaved edit?
The stopped project-export path can flush and save dirty edits. Use command 49 for read-only inspection. Continue using ordinary backups for recovery, with sample WAVs separately; backups omit samples, calibration and the reusable default bank.
What was tested on the physical device?
One FM1:909 full/kick/snare copy and Undo visually; destination AC step 2/swing 60 through copy/Undo and saved restart.303 A-only P5→P7 and 808KICK P1→P7 copies passed complete lane readback, source/other-lane isolation and Undo comparisons; the original project fingerprints returned after Undo. The808 test had empty accent rows and 50% swing, so distinct808 groove markers were not independently tested. All 25 scopes have local automated coverage, not all 25 hardware acceptance.
Can I turn off the internal303 and keep sending its MIDI?
Not yet. An independent internal-synthesis bypass is planned. Ordinary part mute suppresses outgoing sequence notes too. The planned control will preserve external note lifecycle while stopping selected internal synthesis.
Can the TRS socket send MIDI to a TD-3?
Current firmware sends MIDI over USB; its TRS jack receives. No selectable original-jack OUT feature is included. A laptop or compatible USB MIDI host can route FM1 output to aDIN/TRS MIDI output interface. The proposed Raspberry Pi router is a development target, not part of this firmware download.
Are weighted blocks, evolving probabilities or externalLFO controls included?
No. Existing per-step probability and motion remain available. Weighted block selection, slowly evolving block weights, named external devices and receiver-specific CC/LFO mapping are planned work.
Does this update the browser emulator or add native sample upload?
No emulator assets are changed by this release. The existing emulator and Slice Profiles tool retain their separate published state. There is no new native sample upload, USB recording or raw REX decoding in this package.
What about autosave and performance?
The separate note/tail-aware autosave fix is not included. Use existing AUTOSAVE OFF and deliberate manual saving where appropriate for external performance. No CPU savings from an internal-sound bypass are claimed because that control is not implemented. Heavy-load, broad receiver timing and long-soak acceptance remain open.
Where are the source, credits and rollback files?
Corresponding source, component notices and GPL licensing accompany the release. The complete bundle includes the previous public 0.1.6-beta1 firmware/source as a rollback option, not factory firmware. Keep a matching pre-update project backup; downgrade/restore is not physically qualified. Read installation and rollback before updating.