Would be possible use one cv input to enter note value in step recording? Would be super useful, as not everyone use midi keyboard\controller within modular.
Something like cv output from cv\gate keyboard into cv input 1 for note value, and trigger\gate out from keyboard into cv input 2 to determine when pass to the next step.

On power up of my rack (doepfer psu3), performer fails to start until power cycled. I am at less than 50% rated current for the psu. Lots of other digital modules. On other psus it starts first time. I suspect this is an in-rush current/timing event.

Suggestion: if you are updating the hardware - any chance of a supervisor ic on the rst pin? Or using the firmware supervisor? (But I know nothing about the stm32 built in supervisor other than it exists). Thanks for the consideration....

Would love to have octave&transpose to patterns to be applied at song level so at a stage in the song the key can change.

Steps to reproduce:

1. Create a chromatic user scale with a new name (ex: DORIAN)
2. Save this scale to the SD card on an empty slot
3. Load it back from the SD card on any user scale slot
4. The scale structure will be preserved, but the name is not (always INIT)

Expected result: Both name and structure are preserved
Version: 0.1.13

Would be great if we could make sure the CV output value is available before gates are triggered. I encountered this not to be ensured when programming a certain pattern for BIA.
Current workaround: CV Update Mode = Always and programming the desired CV value in the note slot before (!).

It would be nice to be able to mute/solo tracks from curve tracks.
The interface could look exactly as any other routable parameter where you can pick a track to be affected (via checkbox). On Performer page we also could show that mute/solo is controlled by curve track (similar to the arrow sign)

Document legato and slides.

Display Note and Curve-mode track patterns in different colours on the pattern-select page on the Launchpad.

It would help a lot if the "base note" of each octave was permanently shown in some way on each note "page" on the Launchpad.

Scales do not always contain exactly 8 notes so the first note in an octave often isn’t on the bottom row of pads.

Because of this, it would be useful to have a visual cue on the Launchpad itself of where the base note of each octave lies.

Allow to override global swing in track settings.

I did unnecessary troubleshooting for hours until i checked the sequencer.hex...

hi

any objections to (eventually) adding or pulling 16 bit support into your main repo? i'm not 100% but it looks as if that's all there is to it (minus the OFFSET_0995 switch of course, which obviously is tangential / irrelevant).

would be nice if One could also affect Divisor on the routing page

What's the current behaviour for slides with MIDI output? It doesn't currently seem to have any effect.

Suggested Behaviour Options:

• Overlap incoming note and previous step note. This would work with MIDI synthesisers with a "mono legato" mode or similar.
• Transmit standard MIDI CC for Portamento (CC65), and possibly also CC5 (Portamento Time)

Each method has advantages and disadvantages.

Negatives for Method 1:

• Gate-length of previous step would be ignored.
• Previous triggered note may not be on previous step, so last note may have to be extended over several steps, which might be confusing.

Negatives for Method 2:

• Envelopes on receiving MIDI device will be re-triggered with slid notes, so not possible to emulate classic "acid-style" note-slides.

Maybe there could be an option on the MIDI output page to choose one of the above slide behaviours.

To aid fast note-entry, when using an attached MIDI keyboard to enter notes, automatically increment the active step after entering a note.

I'd envisage starting entering notes in this way by holding a step button, and hitting a key on the keyboard (as it operates currently). After that, though, active step would automatically increment so the next key-press would set the note for the next step, etc.

One of the step buttons could be held in the normal way, to edit the note at that step, and auto-incrementing would continue from that step.

Auto-incrementing would continue until the either the last step pf the pattern had been reached (either the Last Step set on the Sequence page, or step 64), or could wrap around to the beginning of the pattern.

Some form of randomisation of Curve track steps.

The most obvious thing to randomise would be segment type.

Another possibility (maybe in addition to the above), would be some equivalent of the gate probability control for a Note track. In this case, how about a set-able probability to determine if the selected curve plays, or the value at the end of the previously-played segment is held for the duration of the current step?

Allow shifting steps left/right in time. This is a little tricky to implement as we now have to do look ahead when playing back the sequences. This would also allow unquantized live recording.

There seems to be an issue with the front panel. The v-cut line is missing.

Currently a curve is always one step in duration.
It would be useful to allow curves to span multiple steps i.e. Have a duration.
Perhaps holding both the start and the end step simultaneously whilst dialing in the curve could set a duration greater than one?

Hey first of all I want to say you doing great work with the performer. I am enjoying it a lot.
the gate offset is great, but it would be much more useful for me if I could set finer percentage like 3% 6% or so.

I'm finding the encoder glitchy. If turned too fast, it can reverse direction.

I'm using the specified encoder part.

I thought initially it was a hardware issue with my build (I've experienced similar behaviour with other builds, when I've forgotten to solder a capacitor related to the encoder), but a more experienced DIY builder friend noticed the same behaviour with their build.

Currently, the Min and Max values can only be set for steps in Curve mode in 0>63 range from an attached Launchpad, where the true range of these values is 0>255.

This limits the usefulness of Launchpad integration when editing Curve tracks (though segment curve-selection is excellent!).

possible solution:

Remap LP values to 0>255 range, so each pad represents 4 values.

1. There is few drum machines that respond only to midi channel #10.
   Currently it's possible to work only with channes 1-8.
2. There is no sign at the midi monitor page.

I used to own a delptronics triggerman and it has this wonderful function to fill or populate the gates in a sequence. You just turn the knob and it has an algorithm which populates the sequence at the turn of the knob making it more and more complex until it fills it up This would be amazing for live performance without having to go into the generator menu.

Explanation video:
https://youtu.be/vP50CgGeuhk?t=46
(second 46 shows how the complexity knob works)

Add a track option to disable CV output when track is muted. Currently CV is output even if track is muted (only gates are muted).

I´m having an issue when setting a scale (even user scales) and then changing the root note. For example if i choose "minor" scale and then choose D it will make make the note in my oscilator go to D# and then if i choose D# as my root note the oscilator will output G. It will quantize to wrong scale notes when changing the root note.

When soloing a track the currently active mutes are not remembered. This means than when unsoloing the the same track, all tracks are now unmuted. It might make sense to switch to a solo mode when soloing the first track, and restore the mutes when solo mode is left.

Currently, Reset Measure is ignored if Play Mode is set to Aligned, which is the default setting.

It's currently not possible to tell if a pattern on the Pattern-select page is empty or not.
Suggest lighting non-empty patterns in a dimmed colour, leaving empty patterns unlit.

Add the option to output the analog clock with swing. This would allow to output the same swing to external sequencers that is also used internally.

To support a wider range of encoders, it would be helpful to have support for reversing the encoder direction in a global setting.

Banks for pattern would be nice.
16 pattern per project seem a little less.

Routing a MIDI CC to Run Mode seems to have no effect.

maybe use SHIFT to jump between MIDI/USB

Most references simply say "Launchpad" without specifying that Launchpad (NOVLPD01 / 0x000e) will not work. Should specify "Launchpad Mini" or others as compatibility is confirmed.

Add support for Akai APC Mini pad controller.

Things to consider:

Extra non-illuminated button could be used instead of Launchpad button 8.

Round buttons under and to right of 64-pad matrix are single-colour (red/green). Maybe buttons down side could light constantly to indicate selected track, flash to indicate gate activity of non-selected tracks.

9x sliders. Maybe 9th slider could be used as value slider, and other sliders could be assignable on Routing page.

Option in MIDI Output page to have Note and Octave from different tracks, or have one track as transpose source for notes from another track.

Lately I'm thinking about more kind of retriggers. As for now we can set it to 1,2,3 or 4 retriggers for step. Would be cool\useful to add more retriggers per step or different distribution of retriggers...sort of burst generation!
Also actually 3 and 4 retriggers seems to be unequally distributed along the step, is this right?

Some kind of ability to capture step-playback order of randomised, or random-walked steps of sequence, either to a new pattern, or to some kind of 'variation snapshot', to be stored with the current pattern.

A basic tempo-synced arpeggiator option would be really nice for the MIDI>CV track mode.

How about implementing MIDI Bank-Select and Program-Change for MIDI outputs?

I guess the module would sent out the messages when first playing a Project.

To make it even more useful, bank and program-change messages could be set on a per-pattern basis, so patches could be changed on MIDI devices when changing patterns on the Performer.

There's a growing number of eurorack modules that can store states and respond to preset recall via the 'select bus' spec. Malekko modules can, some WMD, some Make Noise, Expert Sleepers Distings and Mungo modules

This is really just a MIDI CC to indicate save or recall, followed by a midi program change message to indicate the slot.

Here is a short video of a Teletype implementation im working on
https://www.youtube.com/watch?v=45sEcgE0N6Q

Here is a video from Make Noise
https://www.youtube.com/watch?v=W5mx6kuHgQU

These MIDI messages need to make there way onto the CV bus pin. Obviously that would mean a huge redesign, however in the mean time expert sleepers make a cheap DIY module that has MIDI input jack onto the bus.

I think the feature to send select bus control would be great to implement onto the Performer! Required MIDI messages are:

MIDI instruction on Project load:
CC 16 Val 64 (Load)
PRG change [Performer Project Number]

MIDI instruction on Project save:
CC 16 Val 127 (Save)
PRG change [Performer Project Number]

Those few lines enable save and recall of many modules states synced with the performer projects!

Hi Simon,
Have you considered adding a build/port of the simulator for VCVRack? there are already many sequencers available there but people love skeuomorphic interfaces and i think per|former would be a hugely popular module there.
Cheers,
southpole

Implement trigger conditions similar to elektron sequencer.

How about a new Dual track mode, that could use both CV and Gate outputs as drum triggers?

It would have two Gate layers, on for the Gate output, the other would use the CV output of the gate/CV pair as gate/trigger.

Been thinking about how a chords mode could work. I cant decide if it is a sensible idea or not.