Sequentix - User contributions [en-gb]

Main Page

2017-07-24T23:03:59Z

Sequentix:

'''Cirklon Wiki'''

*[https://www.sequentix.com/cirklon-downloads/ Sequentix downloads]: get pdf manual

*Some key combinations and explanations => [[commands]]

*P3 Pattern aux event reference => [[aux events]]

*How to perform various operations => [[How To|how to]]

*How to update the OS => [[notes on updating the OS|OS update]]

*Revision history => [[revision history]]

*Links => [[links]]

*Youtube videos => [[Videos]]

MediaWiki:Sidebar

2012-12-04T23:35:03Z

Sequentix:

Main Page

2012-12-04T23:34:24Z

Sequentix:

'''Cirklon Wiki'''

*[http://www.sequentix.com/sq_download.htm Sequentix downloads]: get pdf manual

*Some key combinations and explanations => [[commands]]

*P3 Pattern aux event reference => [[aux events]]

*How to perform various operations => [[How To|how to]]

*How to update the OS => [[notes on updating the OS|OS update]]

*Revision history => [[revision history]]

*Links => [[links]]

*Youtube videos => [[Videos]]

Main Page

2012-12-04T23:34:03Z

Sequentix:

'''Cirklon Wiki'''

*[http://www.sequentix.com/sq_download.htm Sequentix]: get pdf manual

*Some key combinations and explanations => [[commands]]

*P3 Pattern aux event reference => [[aux events]]

*How to perform various operations => [[How To|how to]]

*How to update the OS => [[notes on updating the OS|OS update]]

*Revision history => [[revision history]]

*Links => [[links]]

*Youtube videos => [[Videos]]

Main Page

2012-12-04T23:33:42Z

Sequentix:

'''Cirklon Wiki'''

*[[http://www.sequentix.com/sq_download.htm Sequentix]]: get pdf manual

*Some key combinations and explanations => [[commands]]

*P3 Pattern aux event reference => [[aux events]]

*How to perform various operations => [[How To|how to]]

*How to update the OS => [[notes on updating the OS|OS update]]

*Revision history => [[revision history]]

*Links => [[links]]

*Youtube videos => [[Videos]]

MediaWiki:Sidebar

2012-12-04T21:25:31Z

Revision history

2012-12-04T21:23:47Z

Sequentix: Created page with "== Build 079b - experimental == * Down-counting length value for the current scene position in the scene list. * Bugfix: In individual song save, edit copies of CK patterns we..."

== Build 079b - experimental ==
* Down-counting length value for the current scene position in the scene list.
* Bugfix: In individual song save, edit copies of CK patterns were not being included.
* minor fixes

== Build 079a - experimental ==
* JSON file format: save and load individual songs, all songs, and all instrument definitions in JSON format text files.

== Build 076a ==
* bugfix: loss of knob assignments for the knob mask events after pattern edits

== Build 076a ==
* new 'mute hold' option: hold the current track mute state across scene selections.
** In play pages press SHIFT+SCENE. Multiple presses of SHIFT + SCENE to step through the options.
** 3 options: OFF, Next and LOCK.
*** OFF: stored mutes will be recalled with scenes as normal.
*** Next: current mute status will be held for the next scene selection only, after which mute hold will reset to OFF.
*** LOCK: stored mutes will never be recalled with scenes.

* pattern SAVE menus in P3 and CK drum edit revised
** save options are now shown above the encoders under the screen, rather than being selected from a scrolling list (less key presses needed now).
** P3: no prompt to confirm the pattern name anymore for a normal 'save'. If you don't want to use the auto name, change it in edit mode before you save.
** undo features clearer. There are two levels of undo that may be available - you can undo changes to any pattern made since you entered edit mode, and you can recall the saved version of a pattern once it has been saved with a scene. These options only appear above the encoders when they are available.
** New Lose+Exit option, which will return the pattern to the state it was in when you entered edit mode, and return you to play mode.
*** new user config option "force save menu after edit": force to decide whether to save or lose the edits to a pattern when you come out of edit mode.

* P3 pattern: SHIFT + turn BAR for rotating (as already in drum edit)

* Another addition, still work in progress:'JSON test' option on the Card/Sysex menu.
** This option will write two files to SD-card called INSTS.TXT and SONG.TXT. These contain a dump of the instrument definitions and current song (excluding scene data, still TBI) in JSON format. I'll be using this format for individual song load and save, as it allows readily available code libraries to be used for writing external editor/librarian tools with the minimum of effort. Specifications, as they say, are subject to change without notice, but it'll give you an idea how I'm thinking of representing the internal data.

* Fixes
** communication between the main CPU and the CVIO board
** timing of aux event processing relative to the start of each step in P3 patterns has been fixed - events are no longer processed in advance of the step, unless a negative delay value has been set.
** changes to the knob grab and knob mask aux events. The knob grab events now take a value for the knob to use to over-ride pattern values of "1", "2", "A" or "B". Knobs 1 and 2 refer to the track control values knob1 and knob2 which can be assigned to each track. Thus the knob grab events can either be controlled individually using the track values page, or you may have multiple patterns simultaneoulsy pulling values from knobs A or B. The knob mask events also now link to the same four choices - when any of these events are assigned to an aux, an extra field will prompt for the knob selection.

== Test build - 075e ==
* CVIO fix

== Test build - 075d ==

* negative delay for set delay aux event

== Test build - 075c ==
* CV offset function

* negative delay for P3 patterns

* prepeat events: similar to the rep*2, rep*3 and rep*4 events - the note on a step is triggered multiple times, with a shorter gate length. The difference is the repeats are closer together (this was found to be more musical), and the first repeat starts in advance of the step (hence, 'prepeat'), such that the last note falls exactly on the step.

* Test build: Now there is a problem with this build as it stands. In order to be able to play steps in advance, the sequencer code needs to process the next step sooner than before. At the moment, the next step is prepared to fire as soon as the note on the current step has played. It's at this point that any aux events are handled. Then a wait period starts until the note is to be played. The problem with this is that if you have a track muted, and you un-mute it just in time for a step to play, you have already past the point in time where the aux events would have been handled, so they will be missed for the first step after un-muting. Another problem is that the 'MIDI send' group of events will send their messages a bit too early. I'm working on a way round these limitations, but it is proving more complicated than it looked at first.

== Build 074f ==

* Changed
** p3 pattern length value edits made finer - long values can be edited in single ticks
** coarse steps (with encoder held) reduced to 12 ticks per click

* Fixed
** ck pattern: auto-length adjust when changing grid timebase improved
** ck pattern: slope edit behaviour when empty step is used cleaned up
** p3 pattern: repeat events behaviour fixed
** p3 pattern: p3 random masking probabilities fixed
** p3 pattern: delete + gang leaves all steps un-ganged, drops out of gang mode
** force-to-scale moving to nearest active note in either direction, instead of downward bias

== Build 074e==
* Added
** ck pattern now has bar length in steps (last step) value. In drum grid edit, hold LAST and press step key to set length of 1 bar. Total length of a pattern = (last step) * (bar length) * (grid timebase). When changing grid timebase, bar length will be auto-adjusted to keep the same overall pattern length where possible. Some changes of timebase may require manual adjustment of bar length.
** SWING previously applied a time delay to every second step in a ck pattern via real-time quantisation (quant% track value). After introduction of grid timebase, swing has been altered to give a 16th note shuffle effect, even on patterns with a finer timebase setting. e.g. 32nd note flams will play with 16th note shuffle
** Bar follow enabled in event list edit (press BAR to toggle)
** Added a clear of recently-sent MIDI state to ensure all pgms and CCs are re-sent for a new SONG, even if the same value had been sent during the previous song - to ensure multiple control CCs take effect as expected

* Fixed
** better checks for memory full error when allocating space for pattern backups, etc.
** delete of saved track values in mixer view, using DELETE + <press track encoder>
** clear assignment of knobs to track values which are manually removed from an instrument
** drum edit, knob A numeric value for new note velocities is moved up to avoid clash with bar 16 indicator
** validation of clipboard contents before paste into ck pattern
** full reset of USB transmit state if interface is re-initialised. added buffer over-flow detection for USB transmit buffers - LED below step 16 flashes red

== Build 073b==
*Fixed occasional encoder skipping
*Fixed error in vscale calibration calculation

== Build 073==
*If you are updating from a build before 073:
**You MUST DO A DATA BACKUP BEFORE, AND A RESTORE AFTER the update process
**Memory should be initialised when prompted at first re-boot
**The firmware for the CVIO CPU will be updated (If you have CVIO installed, first time it boots it will show the firmware update progress. Press SHIFT once that is complete, and CVIO should operate normally.)

*P3 Edit - SCULPT: 4 modes: Sculpt ABS, Sculpt REL, Random ABS, Random REL. To change the SCULPT mode, press ENTER while SCULPT is active, and select the mode from the pick-list.
**Sculpt ABS - the current position of knob A replaces the step values
**Sculpt REL - the current position of knob A is added to the step values (value is bi-polar)
**Random ABS - step values are randomly assigned a value in the range set by knobs A & B
**Random REL - a random offset in the range set by knobs A & B is added to the step values

* CK drum edit: grid timebase setting added, adjusted with VALUE encoder
* CK drum edit: Access to LENG: in row view, turning ROW steps through velo and leng

* Tempo adjust on SONG/SCENE pages: SHIFT + <value> adjusts rate of tempo change

* New Track Control Values: note%, velo%, octave, knob1 & knob2
**note% - scales notes from 0 to 255% of their value
**noteC - this sets the centre point of note% scaling, i.e. at 0%, all notes = noteC value
**velo% - scales velocities from 0 to 255% of their value
**veloC - sets the centre point of velo% scaling, i.e. at 0%, all velocities = veloC value
**octave - track level transpose by +/- 4 octaves
**knob1 & knob2 - for use by P3 knob mask aux events. Knob mask events are now usable with the values taken from these track control values. Knob1 is used by the first knob mask event assigned to an aux. Knob2 is used by any further knob mask events. Starting points for knob mask positions can be saved at the Scene or Song level, as with other track control values.

* CVIO transfer DMA enabled, for reduced latency & CPU load. CVIO config adds pitchbend option for ctrl# (one step before CC #0). When bend is selected, Ctrl amount becomes Bend amount, maximum = 12 semitones. Bend will almost certainly do weird stuff to Hz/v synths - I haven't got one set up at the moment to test how it should work. Gate ports now have independent settings. They can be linked to any CV output number for gate use, or set to output a tempo clock division. Analogue input mode is not yet linked to an incoming MIDI stream, so is not available yet. This is TBI soon, just haven't worked out the precise implementation details.

* MIDI ports can be set to soft-thru all channels in parallel to another port. This includes routing of USB inputs to serial & CVIO outputs, though this is not heavily tested yet. Let me know if you see any weirdness.

* SD-card Save/Load: filenames are now sorted alphabetically, and cached for faster scrolling. Limited to 512 files in the root folder. Sub-folder access and access to internal flash TBI.

== Build 070==
* improved CC recording
** CC track values follow any value sent from a pattern, or passed through MIDI.
** A or B movements recorded in CK pattern record (if the CC record filter is on).

== Build 069g==
* fixed hanging notes on soft-thru.
* improved record filter UI for CK record mode
** asterisk indicates that the event type *will* be recorded.

== Build 069e==
* new scene selection view
** in scene selection list, hold SHIFT and press SCENE
** VALUE encoder + step encoders scroll/select scenes
** 'm' => (manual); number => scene reps count; 'S' => set; 'E' loop end; 'L' single scene loop
** encoder LED colors: red => mapped scene; green => in loop; amber => current scene (also '>' before name)
** hold an encoder to select one scene, then press and release a later encoder, you will select the first scene to play next, and also set the scene loop to start and end on the selected scenes. (roughly the same as part chain selection on P3). Having selected a loop, it won't normally advance while you're on the SCENE page. So, from the new view, you can toggle SONG mode by pressing the SONG key. This will make your loop advance automatically (if reps are not set to manual).
* ck pattern event-list editor improved
** single step period. The step keys are used to select the step view position within the current bar. The BAR encoder moves through the bars as before. The step key LEDs light to show which step periods have events on them. The ROW encoder scrolls through the events on the step. If you scroll before the first, or after the last, the view will move to the adjacent step. Each event is shown with the step number it is on, and a bi-polar offset value (-24 to +23) that shows where the event start time is relative to the current step.

== Build 068==
* new user config menu; from play mode, press MENU, select 'more>', then 'user config'
** "no auto pattern on edit" = no P3 pattern created when you try to edit an un-assigned track
** "name patterns after track" = track number or name included in auto-generated pattern names, e.g. "Trk1 P 1", "Trk15 C 3"
** "no pattern after delete" = after pattern delete, 'no pattern' is assigned
** "show MIDI note numbers" = notes shown as numbers instead of names
** "aux edit sets flag" = in P3 edit mode, changing an aux value always turns on flag for that step
** "ignore MIDI STOP if master" = incoming MIDI STOP will be ignored unless slaved to external clock
** "48ppqn DIN SYNC" = Sync at double the Roland standard, older Korg format machines use 48 instead of 24 ppqn

* text input mode has scrollable cursor (turn VALUE) and insert/overwrite (toggle with INSERT key)
* text input visual aid shows lower/uppercase depending on SHIFT held or locked status
* pattern save-as shows current name for edit; attempting to save-as the same name will auto-increment name
* scene save-as shows current name for edit; attempting to save-as the same name will auto-increment name
* duplicate instrument names no longer sneak past unchecked
* track value knob assignments stored at song level per track
* track value knob edits require pass-through of manually entered value before knob becomes live
* track value page position remembered for each track
* track value display names shown for aux assignments in P3 edit
* edit mode row selection, bar position, bar follow, etc. remembered for each track (reset on scene/pattern change)
* MIDI soft-thru will pass sysex messages up to 15 data bytes in length
* hanging held notes on change of edit-track soft-thru fixed
* basic copy & paste in drum grid edit; hold COPY and press BAR to copy the current bar to the clipboard move to another bar, the press INSERT to paste the copied events into the new bar. apply quantise if you need to delete any doubled events, until I progress this further and include that in the paste code
* MIDI clock output has two resync modes (set in MIDI config, mclk send = [off | norm | tempo | rsyn1 | rsyn2 ])
**resync1 - SHIFT + RUN stops and restarts clock at next gbar loop
**resync2 - SHIFT + RUN stops immediately; further SHIFT + RUN restarts at next gbar loop.
**both resync modes send start only on next gbar loop after pressing RUN
* songs will return to workscene on re-selection if they were last in workscene

== Build 066 ==
* Some bugfixes for P3 patterns using events to change the last step position.
* No Xpose and No FTS instrument settings are fixed for P3 patterns.
* Holding TRACK in pattern edit, pressing another track encoder and releasing TRACK kicks you back into edit mode via the track page. It takes effect when TRACK is released, so you can look through a few tracks before you find the right one.
* In drum edit, SHIFT + ROW toggles the encoders between velocity and length.
* [http://thaumat.org/cirklon_wiki_test/index.php?title=Commands#slope_edit Slope edits] in the drum grid.

== Build 065d ==

== Build 065b ==
* added LAST + BAR encoder to edit bar length in P3 edit
* added INSERT filter in P3 edit. Insert filter is shown on the top line of display when insert is pending. Use VALUE encoder to select what will be pasted.

* changed behaviour for stop/start re-sync. SHIFT + run previously triggered a rapid stop/start on the next gbar loop. Now the first press of SHIFT + run will stop slaved devices. Another press will arm them for restart on next gbar loop (mungo-sync style)

* fixed auto-generation of duplicate pattern names
* fixed missing DELETE LED in drum edit with record active
* fixed DIN sync minimum times between state changes

== Build 064 ==
* fixes a couple of reported bugs, such as the USB soft-thru and DIN sync tempo, and some oddities in drum edit.
* adds the same save/save as/undo menu to the ck pattern edit modes as in the P3 edit mode, accessed with the SAVE key.
* new option on the main drum edit menu to 'purge muted notes'. This operation permanently deletes any notes from the pattern than you have turned off (muted) using the step keys. The grid is also refreshed, so any rows for notes that no longer appear in the pattern will be removed, unless they were manually added or fixed in theinstrument def.

== Build 063d ==
* fix a bug where the first note in a manually entered ck pattern was not showing up on the drum grid.
* fixes a couple of subtle ck pattern playback issues.
* addition of a bar on the far right of the drum grid. This shows the current position of knob A. When you turn on a note on a step without an existing velocity value, the knob A value is used.

Notes on updating the OS

2012-12-04T21:23:20Z

Sequentix: Created page with "== update by SD card == There is a video tutorial for firmware update by SD card here: http://www.youtube.com/watch?v=Wko-ZiAAlWc * rename downloaded sysex file to 'CIRKOS.SY..."

== update by SD card ==
There is a video tutorial for firmware update by SD card here:
http://www.youtube.com/watch?v=Wko-ZiAAlWc

* rename downloaded sysex file to 'CIRKOS.SYX', copy to SD cards root folder
* hold SHIFT and step key 1 on boot
* choose MMC-Card

The file must be named CIRKOS.SYX, in the root folder of the card. That is
hard-coded to keep the size of the update code to a minimum.

== data loss ==
When updating the OS, you should ''always make a backup of your song data''.
In most cases, the data will survive the update process, but sometimes changes to the internal data format may require the data to be reloaded.

After an OS update, you may see the warning message:

'''WARNING: bbram state inconsistent''' 
'''press <SHIFT>'''

The most common reason for this message to appear is because new configuration values have been added to the battery-backed memory area. 
The warning message will be followed by a prompt to '''Wipe ALL Data''' 
You do not normally need to wipe and restore your data after an OS update. 
Just press 'cancel' and continue as normal. 
However, under some circumstances (eg. major changes in the internal memory structures) it may be required to delete to old data: just wipe it out and reload the data from backup you`ve done before (see full dump memory backup below). 
If there is any problem with the data, there is a further check of the data that should detect it.

== bootloader protection ==
There is no way you can disable your unit with a firmware update.
The bootloader is a totally separate program, sitting in the first 32k of
the program space.
It will only write to the 480k of main code space.
If the content of the main code fails a checksum, it will not start it
running.
So even interrupting the update part way through, or somehow managing to
write random nonsense will not prevent you re-writing a correct image.

==full dump memory backup==
From SONG MODE, press Menu then,
if you have an SD-card, hold SHIFT while you press "card SAVE", and the
whole contents of memory will be written to a file called FULLDUMP.SYX

==memory wipe out==
To wipe the memory, keep the SONG key held as you power on, then press the
encoders 6 & 8 together to confirm when the wipe memory page appears.
Then restore from your normal backup.

How To

2012-12-04T21:22:58Z

Sequentix: Created page with "== How to Enable MIDI Clock output == Out of the box Cirklon is not set to generate MIDI Clocks. To activate this on specific ports: With '''Song''', '''Scene''' or '''Trac..."

== How to Enable MIDI Clock output ==

Out of the box Cirklon is not set to generate MIDI Clocks. To activate this on specific ports:

With '''Song''', '''Scene''' or '''Track''' active (press one of those buttons first if in '''Pattern''' mode)

Press '''MENU'''

Select the '''More>''' option by pressing encoder 11 (it is labelled in the screen above the encoder)

Scroll to Midi Config in the pop-up menu using the '''Value''' encoder and press it to enter the configuration screen.

Enable clock (and other settings) using the encoders below the screen.

== Port numbering ==
Colin says: The CV port is MIDI port number 6, but since it doesn't have any serial MIDI
output as such, it doesn't have a slot in the array of MIDI output buffers.
References to the USB port needs the port number adjusted by 1.
I've forgotten to do that somewhere...
It would be simplest just to re-number the CV port as number 12, and have
the USB ports as (internal numbers) 6 to 11.

== PSU problems ==
Symptoms: Display flickering, no power (?)

Colin says: I noticed the same problem with a PSU in the last batch shipped.
I isolated it the PSU connector by testing with other PSUs, and Cirklons.
Then I gave it a spray with contact cleaner, and it worked perfectly
afterwards.
Some contamination on the internal surface of the power connector must have
been causing a poor contact.
They are moulded parts, so I guess it may be release agent.
I've been watching out for it since, but yours was shipped before I noticed
this.
Can you give it a clean with something suitable (isopropyl alcohol or
electronic contact cleaner)

==set up CV Tracks for multiple CV`s==
Colin says:

From an initialised machine...

In play mode (SONG, SCENE or TRACK pages), press MENU, then "more>", then
scroll and select "CVIO config".

In CVIO config, the VALUE encoder selects the output to configure.
Each output has at least a mode and channel value.
Set output 1 to mode = "note" usign encoder 6.
Leave its channel at 1, and leave the other default settings.

Turn VALUE to see output 2.
Set its mode to "velo". Leave the other default settings.

Turn VALUE to see output 3.
Set its mode to "ctrl".
One the line below the mode setting, the default of ctrl# = 1 will be shown.
Leave as is for output 3.

Turn to output 4.
Set its mode to "ctrl".
Then turn encoder 5 to move to the lower line, and use encoder 6 to set the
ctrl# = 4

Turn to output 5.
Set its mode to "ctrl".
Then turn encoder 5 to move to the lower line, and use encoder 6 to set the
ctrl# = 6

Turn to output 56.
Set its mode to "ctrl".
Then turn encoder 5 to move to the lower line, and use encoder 6 to set the
ctrl# = 10

Now CV output 1 will output the pitch CV, output 2 will be velocity, and
outputs 3, 4, 5 and 6 will be CCs 1, 4, 6 and 10.
These CCs are default assignments in a P3 pattern.
All these outputs should have the default channel value = 1.

Press MENU to exit from CVIO config.
Go to a track.
Create an instrument and set it to output on port CV, channel 1.
Then create a P3 pattern on that track.

Enter some note, velocity and aux values.
Play the pattern.
On steps with notes set, CV outputs 1 and 2 will output the note and
velocity values.
On steps with one or more auxes enabled, the values for auxes A, B, C and D
will appear on CV outputs 3, 4, 5 and 6 respectively.

==Q&A: transpose a pattern==
from the beta-mailinglist:
Question:
Okay I have a 16 beat pattern. What I would like to do is have it play 4 times then transpose up a half step (semitone)for 4 cycles, and repeat.

Answer: (Colin)

Starting with a single bar P3 pattern in edit:

- go to bar edit (press BAR)

There should be one column of xpose, reps and gbar for the one bar of the
pattern.
Only one red LED should be lit under the step keys, to show the 1 bar length.

- hold COPY and press step 2

Your first bar is copied to the second bar, and the bar length of the pattern set to 2

- turn step endoder 2 up 1

That should increase the Xpose value for bar 2 to +1

- turn ROW to edit Reps

- turn both encoder 1 and encoder 2 up to 4, to set 4 reps on each bar

==Track Values / Program Changes==

colin says:

From the TRACK page, press TRACK once more to access the track values.

The track values are user-defined for each instrument, depending on what the
instrument can respond to.

For an instrument which has no values configured, the page should show a
message telling you to press the INSERT key to add one.

There are 6 positions for values on each row of the track values page,
aligned with the 6 encoders under the display.

To add a new value, or change and existing one, press the encoder to select
the position you want it to appear in, then press INSERT.

A menu appears which lets you choose from MIDI CCs or track control values.
Program change is under track controls.

If you have filled all 6 slots, you can add futher values on other rows.

The ROW encoder is used to access other rows, but normally only rows with
values (or the first row) are shown.

To access a new blank row, hold SHIFT and turn ROW one step clockwise.

Use INSERT to add a value on this new blank row, and you'll see that you can
now freely move between the rows.

Once you have added the program change value, you can turn the encoder below
it to send the values.

Then, while you are on the track values page, if you press the SAVE key, you
will see options to store the current value at the SCENE or SONG level.

Select your option, then you should see that the value is labelled [SONG] or
[SCENE].

If you adjust the value again, the label will change to [EDIT].

This indicates that a stored value is present for the scene, but is not the
current value.

On important point is that when you store a value to the scene, it is
written to the scene edit buffer.

you must then save the scene if you want to make the value permanent.

==Setup CC`s on Aux Tracks==

colin says:

Got to the aux row.

Press, hold and turn the ROW encoder.

Up pops a scrolling picklist of all CCs.

From there, press, hold and turn ROW again, and you get the list of aux
groups.

==Save and Undo Structure==

colin says (from the mailing list):

When you first create a pattern it is "unsaved".
Each time you go into pattern edit, an undo copy of the pattern is made, so
you can undo changes made since you entered pattern edit.
Until the pattern is saved, that is as much undo as you have.

In pattern edit, if you press SAVE, then save the pattern, the status of the
pattern changes to "saved".
A saved pattern will not be permanently changed unless you manually save
changes.

When you enter pattern edit for a saved pattern, an edit copy is made. Any
edits now apply to the edit copy.
The first time you edit a saved pattern, you will see the option to "recall
saved version".
That will restore your pattern as it was when you saved it.

As you work on an edit copy of a saved pattern, an undo copy is still made
each time you enter edit mode, so you can "undo recent edits" as before.

If a pattern is assigned to a track when you save a scene, the pattern is
automatically saved, and also marked as being in use by that scene.
The "in use" count for a pattern shows how many scenes a pattern is used in.
When you save a scene after having edited some of the patterns used (thereby
creating edit copies), you are prompted to decide whether to save the
changes to the original pattern, or save the modified pattern as new.

The principle is, if you create a pattern, and you get it to a point you
think is worth keeping, save it.
Then it will be safe.
Or if you have saved the pattern as part of a scene, that's done for you.

If you save patterns in a scene, then edit them further, and save them to a
new scene, you must decide whether the changes you have made should apply to
any previous use of the patterns in previous scenes (save changes), or if
the changed pattern is developing from the previous scene (save as new).

==expanding lenght of CK patterns==
from the mailing list

Q: I know it is possible to have CK patterned longer than 1 bar by setting REPS before creating the pattern.

Is there a way of adding/removing bars after this?

A: press REC and then MENU. turn stepencoder below "bar length" right under the display (display encoder 6). you see this option in the rec menu, when pressing rec

==Aux Track Tips, User experiences and suggestions==
from the mailing list

===from Geoff:===

The P3 manual makes a great job of explaining common techniques and uses of auxes but I thought a few more real world examples would do well. Note none of these are particularly special or new and I’m still getting to grips with interesting methods for creating patterns – so please do contribute. Some ideas are knicked from the manual or other peoples suggestions (namely Colin and Paul) so please don’t think I’m trying to get credit for these J

Patterns where notes and velocities rows have differing length rows

I find myself using this technique a lot (hence desire to have multiphasic patterns!) but this creates for some great sounding subtly different patterns. Use track 1 for your notes, and track 2 for your velocities. Set track 2 to an uneven number of steps. In an aux row of track 1 assign all steps (if you want) to grab velocity from track 2. I find works best when track 2 is set to a faster time base than track 1 and where track 2 has quite varying velocity values!

Patterns that speed up and slow down

Use an aux row of a track to affect the timebase (under pattern settings I think). As soon as you change how long each step takes it means the pattern won’t run directly in sync (similar to changing the pattern length to an uneven number) but I find this is great to get funky rhythms and basslines. Use in combination with an accumulator mask change how often the modulation occurs.

Patterns with repeats for percussion

I find works best with hats, claves and rimshots. Use an aux row of a track to set repeats on some steps and then use an accumulator mask to change how often these repeats happen. Can also work great for snare rolls and fills.

Use of note gate mask and velocity / tie modulation for acid lines

Use aux rows to hide and unhide notes (based on either randomisation or accumulator masks) and to modulate when tie / velocity changes happen (with velocity affecting whether accent is turned on in 303 style synths and tie affecting whether slides occur in monophonic/legato synths).

===from Paul:===

One of my fave tricks is using P3 patterns for percussion - things such
as hand drums, djembes, talking drums etc. Great when they're responsive
to velocity in more ways than mere volume. I typically use event masking
so that the patterns are always different, but in pre-determined ways.
Some examples that come to mind:

Aux A Random Mask Aux B
Aux B Repeat Note based on length
Aux C Randomise velocity
Aux D Random Mask Gate

Aux A Random Mask Aux B
Aux B Set Note (set alternate notes to be played from time to time)
Aux C Random Mask Aux D
Aux D Repeat Note *3

Aux A Random Mask Aux B
Aux B Grab All Track n (replace the step with the contents of track n)
Aux C Accumulate Velocity
Aux D Randomise Note

Remember that setting up the auxes is one thing, you mask on a per step
basis, set repeats on a per step basis and you can copy the bar to a
second bar and have different steps masked, different probabilities of
masking too. Accumulators let you build patterns, often producing
similar-sounding results compared to using rows of different lengths on
other machines. The Aux D accumulator lets you accumulate anything - try
it on last step, direction, MIDI CCs etc. :)

==step manually through P3 Patterns==
from Colin

You can trigger the individual notes in a P3 pattern while stopped - hold
the step encoder, then press the step key below.

==calibrate VCO`s==
from Colin

At the moment, the method I use to calibrate a VCO is to hold a reference
note on another synth, then play two notes an octave apart on the synth
being calibrated.
For the lower note, I adjust the synth so it's in tune, then play the higher
note, and adjust Vscale until it's in tune.
Then repeat, until the error is tuned out.
The next update to the CVIO menu will automate this process, so you'll just
need to tune for a low note, then tune for a high note, and the Vscale value
can be calculated from the two adjustments.

==shift Steps in P3==

in p3 pattern mode press menu - first step - press the step which shall be the first one in your pattern.

==change note length in ck patterns==
from colin

Length is there, but a bit hidden.

In drum grid edit, if you press ROW you'll switch between the grid view and
the bar view of the current row values.

The bars default to velocity, but if you press SHIFT + ROW they'll switch to
lengths.

In the alternative event-list edit for CK patterns (hold SHIFT while
pressing PATTERN), you always see the length.

==debug pages==
(from colin, 0.68d)

There is already a debug option to view an event list pattern in its raw
form, which will give you an event count and block usage for a pattern.
The event data itself may not mean much, it's all in hex.
Select a track with a ck pattern assigned.
From play mode, do SHIFT + INSERT, then choose option 9, 'Evlist view'.
Press SHIFT to scroll each page of event list, or hold FILL/X to scroll
without stopping.
At the end of the list you'll get a count of blocks used.

==memory optimizations==
(from colin, 0.68d)

Something to try if you have high memory usage...
Go to the debug page, using SHIFT + INSERT from play mode.
Press the DELETE key.
This will call a routine to remove any undo copies for edited patterns.
Check your memory usage.

Backup copies of P3 patterns were being cleared out on exit from edit mode,
but this wasn't happening for CK patterns.
The recent build fixes this, though there was some clear-up happening
elsewhere, so it may not make a huge difference.

==bar copy==
colin says

Hold COPY and press BAR.

A popup should say "Copied BAR".

Then move to another bar and press INSERT.

A popup should say, "Clip inserted", and the events from the copied bar
should appear.

==label MidiCCs==
If you set up a track value for a CC for an instrument and give it a label, then that label appears instead of the CC number (in aux menu)

==How can i increase the patternlenght to 4 or 16 Bars ?==
colin says

===In P3 edit:===

- press the BAR encoder to switch to bar edit

- hold the LAST key

- press the step key for the desired length

New empty bars are added up to the length.
Instead of the LAST key, you can hold the COPY key and select a new length.
New bars added will be copies of the current bar.

===In ck edit:===

- hold LAST

- turn the BAR encoder to adjust the length

==How can i change the CC# on the aux tracks to other numbers ?==
colin says

With the aux row selected, press, hold and turn the ROW encoder.
That pops up a list of CCs to select.
Use ROW to scroll and press again to select a new CC.
You can press MENU here to cancel and return to the previous setting.
A second press/hold/turn of ROW while on the CC select list will take you to
the aux group select list.

==How can I reorder track values ?==
That can be done by INSERTing the same value in a new location - it will be moved from its previous location, with any stored values intact.

==How to set a default length for newly created patterns ?==
The number of bars defaults to the current scene length. Try making your scene 4 reps and you should see new patterns 4 bars. [tkx to softroom]

== Change instrument-track assignment in different scenes ==
* Track to Instrument relations can refer to a scene or to a song. It depends if the SONG or the SCENE key is lit when assigning instruments to tracks.
* Colin: When you have brought up the instrument select list on the track page, normally the SONG key will flash, to show you're making a song-level instrument assignment. If you press the SCENE key, it will flash instead, and the new instrument selection will be at the scene level. A [SCENE] label will appear just below the instrument name to show this. Remember to save the scene to store it permanently. If you select the same instrument for a scene as is set for the song, the scene level setting is removed.

Aux events

2012-12-04T21:22:29Z

Sequentix: Created page with "'''Aux events - main menu ''' In essence, an auxiliary event is like a controller message that is sent internally within Cirklon. Each event can modify some internal setting ..."

'''Aux events - main menu '''

In essence, an auxiliary event is like a controller message that is sent internally within Cirklon.
Each event can modify some internal setting or value within the Cirklon’s sequence playback engine:

• They can alter the current values for each playing pattern – note, velocity, length, delay, aux and status values.

• They can change pattern values like timebase, direction and last step.

• They can change global values, such as the current tempo, track mutes, or part selection.

• They can also access normally “hidden” values that affect patterns in unusual ways.

Video by Paul Nagle: http://www.youtube.com/watch?v=vfkhs3GGNjYi

To access the aux event menu, from the Pattern edit screen, select an AUX row (A, B, C or D) and push+turn ROW twice.

=MIDI CC=
=Accumulator=
==offset note abs==
Offsets the note on the step to which a value is applied by n*semitones ("n" being the user input value).

Positive n yields higher notes.

Negative n yields lower notes.

==offset note rel==
Offsets the note on the step to which a value is applied and to the notes of subsequent steps in the pattern by n*semitones ("n" being the user input value).
The offset applied is relative to the previous offset value, meaning it is added.

Example 1: if a step has a note offset value of -12, the pattern will be 1 octave lower on each pass (assuming all other steps have a note offset value of 0).
Example 2: if step 1 has a note offset value of n, and the last step in the pattern has a note offset value of -n, each step in the pattern will be played n semitones higher.

Positive n yields higher notes.

Negative n yields lower notes.

==offset velo abs==
==offset velo rel==
==offset aux D abs==
==offset aux D rel==
==note acc defeat==
==velo acc defeat==
==auxD acc defeat==
==set note acc lim==
==set velo acc lim==
==set auxD acc lim==
==add dAcc to leng==
==add dAcc to dlay==
=Accumulator Mask=
==Mask gate,dAc>=n==
==Mask gate,n>dAcc==
==Mask tie,dAcc>=n==
==Mask tie,n>dAcc==
==Mask xB,dAcc>=n==
==Mask xB,n>dAcc==
==Mask xC,dAcc>=n==
==Mask xC,n>dAcc==
==Mute trk,dAcc>=nMask tie==
=Aux Note Events=

(from P3 Manual) The '''Aux note''' event group is different to the others since the events do not change any values.
Each aux that is assigned to an aux note event can play one extra note on each pattern step, in addition
to the main note value.

If you assign all four auxes to aux notes, your pattern will be 5 note polyphonic .

There are four events in the Aux note group:

• aux note abs
• aux note rel
• aux note abs xF
• aux note rel xF

In these events, “'''abs'''” means '''absolute''', and “'''rel'''” means '''relative'''. For the '''absolute''' events, you to enter the extra note as a normal '''note name'''.
The '''relative''' events take a '''number''' value that is an '''offset''' from the main pattern note.

The “'''xF'''” versions of the events send the extra notes without applying any Force-To-Scale settings.
'''Note that no aux notes play unless the step gate is on''' .

For example, let’s say you want to send a C major 7 chord on step 1 of a pattern using four notes:

• set the note value on step 1 to C5
• assign aux A to the event “aux note abs”
• assign aux B to the event “aux note abs ”
• assign aux C to the event “aux note abs ”
• set the aux A value on step 1 to E5
• set the aux B value on step 1 to G5
• set the aux C value on step 1 to B5

When the pattern step plays, the four note chord C5, E5, G5, B5 will be sent.
All notes share the same '''velocity''' value.

Let’s do the same thing, using the “'''aux note rel'''” event:

• set the note value on step 1 to C5
• assign aux A to the event “aux note rel”
• assign aux B to the event “aux note rel”
• assign aux C to the event “aux note rel”
• set the aux A value on step 1 to 4
• set the aux B value on step 1 to 7
• set the aux C value on step 1 to 11

In the case of '''relative''' events, the note sent by each aux is the main note shifted by the aux value. In this example, with a main note of C5:

• C5 + 4 semitones = E5
• C5 + 7 semitones = G5
• C5 + 11 semitones = B5

...and you have the same notes as you set for the “aux note abs” event.
The difference with the '''relative''' events is that you can now '''transpose''' all the notes in the chord just by changing the main note value on the step.

'''Chord Memory'''

It is possible to use the aux note rel events to recreate the chord memory function found on early
polyphonic synthesizers.

This means you can set up the aux values in advance to create a given chord shape on every step of a pattern.

Then you can set the root note of your chord using the normal note value, and activate the gate.

'''Polyphonic Real-time Record'''

As mentioned in the chapter on real-time record, and worth repeating here, if you have configured some of the auxes in a pattern with any of the aux note events, you can record polyphonic patterns directly from an attached keyboard.

The lowest note played in any step will be written to the main note value, and up to 4 more notes will be written into the auxes.

==aux note abs==

==aux note rel==
==aux note abs xF==
==aux note rel xF==

=Global Control=
==mute trk n==
==un-mute trk n==
==set tempo==
==set scene xpos==
=Inter Track=
==grab==
==swap==
==push==
==xpose by trk n==
==xpose by trk n+B==
=Knob Grab Events=

(from P3 Manual) These events take the current value from any play mode knob, and use it to over-write the pattern values.

The knobs for these events are not automatically assigned – the aux value is used to specify exactly which knob should be assigned.

==knob n to velo==

replace velocity value with current value of knob n

==knob n to leng==

replace length value with current value of knob n

==knob n to auxC==

replace aux C value with current value of knob n
==knob n to auxD==

replace aux D value with current value of knob n

=Knob Mask Events=
==Mask gate,Kn>n==
==Mask gate,Kn~n==
==Mask gate,Kn<n==
==Mask tie,Kn>n==
==Mask tie,Kn~n==
==Mask tie,Kn<n==
==Mask auxB,Kn>n==
==Mask auxB,Kn~n==
==Mask auxB,Kn<n==
==Mask auxC,Kn>n==
==Mask auxC,Kn~n==
==Mask auxC,Kn<n==
==Mask auxD,Kn>n==
==Mask auxD,Kn~n==
==Mask auxD,Kn<n==
==Mask nAcc,Kn>n==
==Mask nAcc,Kn~n==
==Mask nAcc,Kn<n==
==Mask vAcc,Kn>n==
==Mask vAcc,Kn~n==
==Mask vAcc,Kn<n==
==Mask dAcc,Kn>n==
==Mask dAcc,Kn~n==
==Mask dAcc,Kn<n==

=MIDI Send=
==NRPN==
==send MIDI a/t==
==send MIDI pbend==
==send MIDI pgm==
==send MIDI clock==
sends Start, Stop or Continue message

=Pattern Control=
==set lstep abs==
==set lstep rel==
==set norm tbase==
==set trplt tbase==
==set drctn==
=Randomize=
==Rndmz note==
==Rndmz velocity==
==Rndmz length==
==Rndmz delay==
==Rndmz aux B==
==Rndmz aux C==
==Rndmz aux D==
==Rnd mask gate==
==Rnd mask tie==
==Rnd mask aux B==
==Rnd mask aux C==
==Rnd mask aux D==
=Redirect Aux=

(from P3 Manual) The “Redirect Aux” event group allow you to temporarily re-assign aux B, C or D to a different MIDI controller or aux event.

There is no such event for aux A as the auxes are processed in order - you must re-direct one aux from an earlier one. Since A is the first aux, it could not be re-directed.

==aux B = cc #n==

temporarily re-assign aux B to a MIDI controller

range: 0 -127

==aux B = event==

temporarily re-assign aux B to an aux event

range: aux events

==aux C = cc #n==

temporarily re-assign aux C to a MIDI controller

range: 0 -127

==aux C = event==

temporarily re-assign aux C to an aux event

range: aux events

==aux D = cc #n==

temporarily re-assign aux D to a MIDI controller

range: 0 -127

==aux D = event==

temporarily re-assign aux D to an aux event

range: aux events

==auxes to trk n==

This event re-directs all following auxes so that they apply to the specified '''target track''' instead of the '''current track'''.

This allows you to cascade more than four aux events to one track, or send more than the maximum four MIDI CCs.

=Repeat=
(from P3 Manual)
The “Repeat” event group used to create repeats of notes within the same step.
They are useful where you may want the occasional double speed note without having to use a faster tbase setting, or for those 'Berlin School' grace note effects.

The first repeat note events all divide the step into equal parts for the main note and the repeat notes. So, a '''rep*2''' will divide the step in two equal parts, and each note will play for a proportion of their half of the step based on the l'''ength''' value for that step. '''rep*3''' will divide the step in three equal parts, and '''rep*4''' into four.

The value range for all these events is +/- 63.
The note and velocity offsets are added to the note or velocity value on each repeat.

So if the primary note is a C, and you set '''rep*4, note + n''' on a step with a value of 1, the four notes played would be C, C#, D, D#. These four notes would each be a quarter of the length of the normal note length for the pattern.

If you want to have both a velocity and note offset on your repeat notes on the same step, you can combine these events on more than one aux.

The next repeat event is a bit different - it doesn't equally divide the step among the repeat notes.
It simply repeats the note after the '''length''' setting for the step has elapsed.
If the length is set too long, you may get no repeats.
If it is set very short, you can get very rapid streams of notes.
Since this event takes a value for the number of repeats, another couple of events are provided to configure note and velocity offsets if required.

==rep*2, note + n==

repeat the note twice, with a note offset added to the repeat

==rep*2, velo + n==

repeat the note twice, with a velocity offset added to the repeat

==rep*3, note + n==

repeat the note 3 times, with a note offset added to each repeat

==rep*3, velo + n==

repeat the note 3 times, with a velocity offset added to each repeat

==rep*4, note + n==

repeat the note 4 times, with a note offset added to each repeat

==rep*4, velo + n==

repeat the note 4 times, with a velocity offset added to each repeat

==prep*2, note + n==
Difference to the rep events: repeats are closer together (this was found to be more musical), and the first repeat starts in advance of the step (hence, 'prepeat'), such that the last note falls exactly on the step.

==prep*2, velo + n==

==prep*3, note + n==

==prep*3, velo + n==

==prep*4, note + n==

==prep*4, velo + n==

==rep*n, by length==

sets note to repeat n times, with length of note controlling repeat time

==set rep*n note+==

set repeat note offset for rep*n

range: +/- 63

==set rep*n velo+==

set repeat velocity offset for rep*n

range: +/- 63

==rep*n tbase==
[Colin] "rep*n tbase" works in conjunction with other rep events.
Each of the rep events sets a repeat period in ticks.
They are preset for the rep*2/3/4 events, and set equal to the gate length
for the "rep*n by length" event.
If you apply a "rep*n by length" on a step, you can use "rep*n tbase" to set
the repeat period as a tbase value.
So "rep*n by length" = 10, and "rep*n tbase" = 16 would make the note repeat
10 times at tbase 16.
etc.

I find this a fun set of auxes for a polysynth:
* rep*n by length
* rep*n tbase
* set rep*n note+
* set rep*n velo+

FTS comes in handy.

=Set Step Value Events=

(from P3 Manual) The '''Set Step Value''' event group mainly has events to set a pattern value on the step to a new value.

This may not seem like much use but it is very useful in combination with one of the mask events. For example, you might use it to randomly switch a step between two specified notes, or by using the aux D accumulator and a mask event, you can perform pattern 'morphs', where the notes of the pattern gradually switch from the normal note values to those set in a 'set note' aux.

The events of this type are:

==set note==
==set velocity==
==set length==
==set delay==
==xpose by n==

adds a set value to the note value

==add n to xC==

adds a set value to the aux C value

==add n to xD==

adds a set value to the aux D value

==set midi chan==

...this allows you to re-assign a single step to any MIDI channel of your choice.

Great fun when used with another event to randomize the MIDI channel value!

Commands

2012-12-04T21:22:07Z

Sequentix: Created page with "== General == * The aim of this section is to have a reference about functions that can only be accessed by 'complex gestures' thus being harder to remember. Functions that ar..."

== General ==
* The aim of this section is to have a reference about functions that can only be accessed by 'complex gestures' thus being harder to remember. Functions that are available by stepping through the MENU pages are not included even if they may be hard to find.

=== Encoder Gestures ===
* Some words about gestures. All Cirklon except the A/B knobs have an additional push function (1-16, ROW, BAR or VALUE)
** So, sometimes you have to turn or to push an encoder. Sometimes you have to push and turn the same encoder.
** That special gesture counts for the aux selection lists for instance.

== SONG ==
=== [DELETE+SONG] delete ===
confirm with encoder6+encoder7

=== [SHIFT+SONG] create new===

=== [SHIFT+VALUE] bpm fine / coarse adjust ===
0.1, 1, or 10 bpm steps

== SCENE ==

=== [DELETE+SCENE] delete ===
confirm with encoder6+encoder7

=== [SHIFT+SCENE] mute hold ===
Multiple presses of SHIFT + SCENE to step through the options: OFF (recalled as normal), Next (for next scene selection only, afterwards OFF) and LOCK (never recall)

=== create new ===

=== [SHIFT+RETURN] edit scales ===
*in scale select list, hold SHIFT while selecting the scale.
That brings up the edit page.
*The step keys select notes of the chromatic scale.
*The note name is displayed as you add or remove it from the scale. The root note is always present.
*You can edit the preset scale, though the changes will not be saved.

== TRACK ==

=== [DELETE+TRACK] delete ===
confirm with encoder6+encoder7

=== create new ===

=== [ROW] overview ===
*A press of the ROW encoder toggles between the zoomed-in view of all data for a single track, and the wide view of a single value for 16 tracks..

=== [SHIFT+TRACK] track mixer ===
==== [BAR] select tracks 1-16/17-32 ====
==== [ROW] toggle volume/pan ====

=== [SHIFT+VALUE] access pattern pool ===
* or SHIFT+encoder N
*assigning a pattern to a track you can normally just choose from patterns already assigned to that track. hold SHIFT while pressing VALUE and there is the complete list of all patterns.

=== [SHIFT+ENTER] change instrument settings ===
*in instrument select list
*change port, channel, FTS, Xpose settings for a defined instrument.

=== [TRACK, TRACK, encoder6-11 + INSERT] track values ===
available track values: CC or tbar (resolution), quant%, length%, pgm (program change).

=== [SHIFT+encoder6-11, knob A/B] knob control ===
*Colin: This isn't fully implemented yet - it doesn't apply to all of the values,
but does work with an CC value and the length ratio (leng%).

=== [TRACK+ROW] switch tracks ===
switch tracks without loosing pattern view

alternatively: TRACK+encoder1-16

=== [DELETE+encoder1-16] delete of saved track values ===
delete saved track values in mixer view

==== realtime quantization ====
Colin: track values view - you get to this by pressing TRACK again when you
are on the TRACK page.The track values appear as a row of up to 6 numeric or rotary indicators on the
display.You add them by pressing an encoder below the screen to select an empty slot,
then press INSERT.The track value page which appears lets you pick a MIDI CC or 'track control',or empty to remove a value.
Choose 'track control', then 'quant%'.
Once added, set the quant% control to 100%.
Your ck pattern will now be quantised in real-time to 16th notes.

== PATTERN ==

=== [DELETE] delete ===
For an individual pattern, go to the pattern select list, then press DELETE.
Then press ENTER to confirm pattern deletion.
If you delete a pattern that's an edited version of a saved pattern, the saved
version will re-appear.

=== [SAVE] create new ===
*'save as new'
*pattern creation and assignment are available in track mode

=== [TRACK+encoder] change TRACK ===
*Stay in edit mode on track change.
*Holding TRACK in pattern edit, pressing another track encoder and releasing TRACK kicks you back into edit mode via the track page. It takes effect when TRACK is released, so you can look through a few tracks before you find the right one.

=== ck pattern ===

==== [SHIFT+PATTERN] list view ====
* in SONG, SCENE or TRACK mode

==== [LAST+BAR] set pattern length ====

==== [SHIFT+BAR] shift steps left/right ====

===== [SHIFT+NEXT] shift steps right =====
alternatively

==== [COPY+BAR] copy current page to the paste buffer ====

==== [INSERT+BAR] insert the paste buffer to current page ====
Note: duplicate events may be created if the current page already contains events

==== [BAR] toggle bar follow ====

==== [SHIFT + ROW] edit step length ====
*toggles the encoders between velocity and length

==== [encoderN1 + encoderN2] slope edit ====
*draws a curve between selected steps
*if encoderN2 is pushed values change in steps of 10
===== set all steps to the same value =====
Colin: I find slope edit is the fastest way. Set the first encoder to the desired value, then hold it in without turning, and turn the last encoder to the desired value. All steps will then be on a 'flat slope' of the same value.

=== p3 pattern ===
==== [ROW 2x] aux event selection ====
* hold ROW, turn ROW to access aux event selection for the selected aux event. hold and turn ROW again to access the aux event selection list.
*in step edit view or aux encoder view
*push and turn ROW to enter the currently assigned aux event list (CC by default). push and turn ROW a second time to access the aux event type selection list

==== [GANG+keyN1+keyN2] select multiple steps ====
* Multiple of key interval is selected for GANG.
* For example: press key 1 and 3: all odd steps are selected.

==== [SHIFT+GANG] inverse GANG selection ====

==== [BAR] bar edit ====

==== [SHIFT+BAR] shift steps left/right ====

==== [SHIFT+keyN1, SHIFT+keyN2] bar loop ====
*in bar edit

==== [LAST+BAR] pattern length ====
*in bar edit: LAST+key N; COPY/DELETE+key N

==== [BAR] toggle bar follow ====
push BAR to toggle bar follow on/off

==== [SHIFT+RECORD] arpeg record ====

==== [SHIFT+SCULPT, SCULT+knobA/b] sculpt ====
* draw curves in realtime (knob A)
* (knob B)
*Colin: SCULPT needs to be activated by holding SHIFT and pressing the SCULPT key. One the LED is lit, hold the SCULPT key and tweak knob A while the pattern plays. The current row values will be captured from the knob position. Knobs A and B are also assignable to track values in play mode.

==== [encoder1-16+step1-16] audition step ====
Auditions a step. Hold the step encoder, then press the step key below. Browse samples for instance.

==== [SHIFT+VALUE] tbase/direction for the current bar only ====
Usually he tbase resolution (or direction) affects all bars. If the tbase (or direction) selection list is opened with SHIFT enabled, the setting is applied to the current bar only.

==== [DELETE+GANG] un-gang ====
leaves all steps un-ganged, drops out of gang mode

== Misc==

=== [SHIFT x2] arm SHIFT ===

=== [MENU] abort operation ===

=== [SHIFT+PLAY] resync slaves ===
*first SHIFT+PLAY stops slaved devices instantly
*second SHIFT+PLAY restarts slaved devices on next gbar loop start

=== [SHIFT+STOP] toggle safe stop ===

=== [SONG] reset ===
*on boot
*confirm with encoders6+8

=== [SHIFT+step1] OS update ===
*on boot

=== [SHIFT+INSERT] debug mode ===

=== [MENU, SHIFT+encoder7] display OS version ===
*exit with ROW

=== [MENU, SHIFT+encoder8] enable DIN SYNC, DRUM TRIGGER ===
.. (deprecated?)

=== [MENU, Card/Sysex SHIFT+card SAVE] dump to SD card===
The entire contents of memory will be written to a file called FULLDUMP.SYX

Main Page

2012-12-04T21:21:47Z

Sequentix:

'''Cirklon Wiki'''

*[[Sequentix docs|Sequentix]]: get pdf manual

*Some key combinations and explanations => [[commands]]

*P3 Pattern aux event reference => [[aux events]]

*How to perform various operations => [[How To|how to]]

*How to update the OS => [[notes on updating the OS|OS update]]

*Revision history => [[revision history]]

*Links => [[links]]

*Youtube videos => [[Videos]]