Thank you very much for your reply and for your work on the firmware. In fact, this is the version I am planning to use.
I would like to know if you have any information regarding the behavior of pattern modulation via CV. If the track controlling the patterns is on a clock division of 16, will the pattern change correctly at the start of each new pattern? Also, is the pattern switching instantaneous when triggered via CV?
-- mycose
Well, I don't think this behaves like a queued pattern change that always waits for the next pattern start. From what I understand, the pattern changes when the CV value changes and the routing is processed. So if your control track changes value every 16 steps, the pattern should change around that moment, but I wouldn't want to promise perfect "change exactly at the next pattern boundary" behavior. At the moment I don't have time to test this specific setup, so I'd treat it as supported in principle, but not guaranteed as a tight synced pattern-switching feature. I'd suggest moving this discussion to the Modwiggler forum, where maybe you can find other people interested in this specific behavior and ready to test it: https://www.modwiggler.com/forum/viewtopic.php?p=4507886#p4507886
;)
Hello, I would like to know if it is possible to modulate the number of the pattern in playback with the CV of a track. For example on each step have a pattern number and read the steps randomly. I guess yes by reading the manual, but someone has already tested it or could test it for me? Thanks in advance.
ps: I don't have a performer yet, but I'm seriously considering equipping myself with one
-- mycose
Hello,
speaking for my firmware: yes, this should be possible.
You can use a track's internal CV output as a routing source and route it to the Pattern parameter of another track. So one track could generate stepped/random CV values, and those values could select patterns on another track.
I haven't tested this exact patch recently, so I don't want to overpromise the details, but conceptually this is supported. You may need to adjust Min/Max and the CV range to get clean pattern selection...
WARNING: This is a beta release. Firmware v0.4.5 remains the current stable version. The module displays firmware version 0.4.6; the beta status is carried by the release tag. Important project compatibility warning: The beta can open projects saved by previous versions, but saving upgrades them to the new Version41 project format. Firmware v0.4.5 and earlier cannot reopen those upgraded files.
Please back up the SD card or keep a separate copy of every original project before opening and saving it with this beta.
What I’ve done in this version:
Editing and live-performance workflow beta: MIDI input filters, safer Copy / Paste / Duplicate, faster track navigation, temporary Fill division control, Routing Divisor fixes, and corrected Stochastic / Arp scale handling.
• MIDI Input Filters: projects can now independently filter MIDI Notes, CC, Program Change, Pitch Bend and Aftertouch. Clock and Transport are unaffected. Disabling Notes blocks new Note On messages while still accepting Note Off, avoiding stuck notes. • Copy / Paste / Duplicate: selected-step operations are now more consistent across Note, Curve, Stochastic, Logic and Arp. Paste requires an explicit destination. Duplicate preserves selection gaps, moves the selection to the copied block, extends Last Step when needed and reports when there is no room. • Faster track editing: double-clicking T1–T8 opens the selected track’s Steps editor directly where those buttons are not already reserved by the active page. • Temporary Fill Divisor: while holding a per-track or global Fill control, the module encoder can temporarily change playback division. Releasing Fill restores the saved divisor. The workflow is available from both the module and Launchpad. • Routing Divisor Min / Max: Divisor routing now moves only through valid musical divisions. CV and MIDI modulation are quantized to the same list, with stabilization near boundaries to prevent unwanted switching between adjacent values. • Stochastic / Arp scale reload: fixed Stochastic note-pool drift after saving and reloading projects that use non-chromatic scales. Legacy pitch slots are now interpreted consistently through the selected scale, and the related Arp path follows the same scale-aware behavior. • Documentation and release package: Changelog, Readme, Website, Features, Test Drive, Build Guide, Manual and Printable PDF were updated. The release includes the firmware, checksum and dedicated upgrade smoke tests from both v0.4.4 and v0.4.5.
The complete real-hardware smoke test is still pending, so feedback from beta testers is especially useful.
Also, from earlier versions:
• Generators ecosystem: Random, Euclidean, Acid and Chaos were developed into a coherent performance system with shared preview/apply safety across the module and Launchpad. Acid includes Layer, Phrase and Eucl Phrase. Chaos includes Vandalize, Wreck and Entropy. Wreck was hardened with fixed-size backup storage while preserving A/B, Cancel and Apply. • 16-step Edit Mode: experimental direct editing for Note tracks using external 16-knob + 16-pad controllers. Knobs edit notes, pads toggle gates and longer sequences can be navigated in 16-step banks. Tested on Launch Control XL mk1/mk2; BeatStep Pro is code-supported and template-based, but needs broader hardware validation. • Launchpad, sequencing and Routing workflow: expanded Generators Mode, Init actions, Undo/Redo and safer generator commit/cancel behavior. Sequencing additions include bank-aware editing, tie-chain note editing, Curve Gate Offset / Gate Length, per-track Gate/Trigger output, improved clock/reset handling, scale-safe Arp/Stochastic transpose and Voltage Mode fixes. Routing was hardened by distinguishing continuous, discrete and trigger-like targets and rejecting incompatible target/track combinations more reliably. • Reliability, memory, UI and documentation: SRAM pressure and runtime overhead were reduced through conservative cleanup. Load / Save / Save As, Project LOAD browsing, SD-card boot, Wreck and several crash-prone UI paths were hardened. Generator naming, context labels and Launchpad mappings were made more consistent. The project gained a more practical searchable manual, printable black-and-white PDF, updated cheatsheet and simulators, synchronized website and README, and a clearer feature archive.
A demo / walkthrough video based on the earlier v0.4.2 is available here:
As always, the goal is to make PER|FORMER more playable in live contexts while keeping it open to less predictable workflows. A solid machine for performance, but also a crazy one for experimentation. If you believe free software has value, accept that the work of the people who develop it has value too. Free as in freedom does not mean free labor. If this project is useful to you, consider supporting the work behind it: https://vinxscorza.github.io/performer/donate/
If you notice bugs or weird behavior, feel free to report them through GitHub, email or here.
Feedback is very useful, especially while v0.4.6 is in beta.
A DEMO / WALKTHROUGH VIDEO is now available at the following link:
What I’ve done in this version
• Aligned the Variation semantics, which now behave as a per-step keep/replace control against the original material in both Generators
• Reworked Generators footer/context layouts for a more uniform workflow across all Generators
• In Chaos, clamped Note and Note Range generation to a -24..+24 semitone window
• Made all Generators enter on the original version: the first generated Sequence now requires an explicit reroll action
• In 16-step Editing Mode, updated playhead feedback with dedicated state
• Fixed Voltage Mode behavior on Arp and Stochastic tracks (to be tested)
Also, in earlier versions
• Full evolution of the Generators ecosystem
(Random, Euclidean, Acid, Chaos: Vandalize / Wreck / Entropy)
→ now more coherent, with unified preview/apply safety and a shared playable workflow across the machine and Launchpad
• Added an experimental 16-step Edit Mode on Note Tracks (tested on LCXL, to be tested on BSP)
→ step editing via external controllers with 16 knobs + 16 pads
→ knobs = Note for the visible 16 steps
→ pads = Gate on/off
→ navigation across longer sequences in 16-step sections
• Improved Launchpad integration, with Generators Mode, Inits, and Undo/Redo
• Unified preview/apply workflow with safer destructive operations (1-level Undo/Redo)
• Unified Init behavior (Layer / Steps / Seq), selection-aware with consistent fallback logic
• Refinements in step selection (shift behavior, selection-or-all logic)
• Improvements in timing, clock/reset handling, and edge-safe sync
• Curve track extended with Gate Offset and Gate Length
• Improved handling of scales and operational limits
• Reduced memory footprint and improved runtime efficiency
• Simulators aligned with actual firmware behavior
• Expanded documentation, with a new manual featuring improved search + full Launchpad cheatsheet
• Overall ecosystem cleanup (site, docs, simulator, references)
And many other small improvements that add up, including a near-complete refactor of the Launchpad code
The goal is to make the PER|FORMER more playable in a live context, while keeping it open to less predictable workflows.
A solid machine for performance, but also a crazy one for experimentation.
I’m kinda losing my mind over this fork.
If you find it useful, consider donating https://vinxscorza.github.io/performer/donate/
If you notice any bugs or weird behavior, feel free to report it via GitHub, email, here, or wherever you like.
This fork has been moving fast — and since it’s just me, feedback really helps.
A DEMO / WALKTHROUGH VIDEO is now available at the following link:
What I’ve done in this version
• Aligned the Variation semantics, which now behave as a per-step keep/replace control against the original material in both Generators
• Reworked Generators footer/context layouts for a more uniform workflow across all Generators
• In Chaos, clamped Note and Note Range generation to a -24..+24 semitone window
• Made all Generators enter on the original version: the first generated Sequence now requires an explicit reroll action
• In 16-step Editing Mode, updated playhead feedback with dedicated state
• Fixed Voltage Mode behavior on Arp and Stochastic tracks (to be tested)
Also, in earlier versions
• Full evolution of the Generators ecosystem
(Random, Euclidean, Acid, Chaos: Vandalize / Wreck / Entropy)
→ now more coherent, with unified preview/apply safety and a shared playable workflow across the machine and Launchpad
• Added an experimental 16-step Edit Mode on Note Tracks (tested on LCXL, to be tested on BSP)
→ step editing via external controllers with 16 knobs + 16 pads
→ knobs = Note for the visible 16 steps
→ pads = Gate on/off
→ navigation across longer sequences in 16-step sections
• Improved Launchpad integration, with Generators Mode, Inits, and Undo/Redo
• Unified preview/apply workflow with safer destructive operations (1-level Undo/Redo)
• Unified Init behavior (Layer / Steps / Seq), selection-aware with consistent fallback logic
• Refinements in step selection (shift behavior, selection-or-all logic)
• Improvements in timing, clock/reset handling, and edge-safe sync
• Curve track extended with Gate Offset and Gate Length
• Improved handling of scales and operational limits
• Reduced memory footprint and improved runtime efficiency
• Simulators aligned with actual firmware behavior
• Expanded documentation, with a new manual featuring improved search + full Launchpad cheatsheet
• Overall ecosystem cleanup (site, docs, simulator, references)
And many other small improvements that add up, including a near-complete refactor of the Launchpad code
The goal is to make the PER|FORMER more playable in a live context, while keeping it open to less predictable workflows.
A solid machine for performance, but also a crazy one for experimentation.
I’m kinda losing my mind over this fork.
If you find it useful, consider donating https://vinxscorza.github.io/performer/donate/
If you notice any bugs or weird behavior, feel free to report it via GitHub, email, here, or wherever you like.
This fork has been moving fast — and since it’s just me, feedback really helps.
