14
edits
→patternblade
| (6 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
I wanted to have a stepsequencer with a tangible interface and with pattern-mode transpose abilities. As I haven’t found any of these in hardware or in software on the net, I decided to make one myself. | I wanted to have a stepsequencer with a tangible interface and with pattern-mode transpose abilities. As I haven’t found any of these in hardware or in software on the net, I decided to make one myself. | ||
There are some | There are some already existing sequencers which have their own pros and cons. Let’s take a look at some of them. | ||
== Comparision of stepsequencers == | == Comparision of stepsequencers == | ||
| Line 47: | Line 46: | ||
=== Oberkorn SL16 / oberkorn-sliders | === Oberkorn SL16 / oberkorn-sliders === | ||
type: | type: | ||
1x16 step, 2bus cv (+midi) sequencer | 1x16 step, 2bus cv (+midi) sequencer | ||
| Line 62: | Line 61: | ||
rather simple (and a bit too pricey for that) | rather simple (and a bit too pricey for that) | ||
no transpose function | no transpose function | ||
=== Quasimidi Polymorph === | === Quasimidi Polymorph === | ||
| Line 117: | Line 115: | ||
== What does a sequencer need and what not? == | == What does a sequencer need and what not? == | ||
=== Cycle length === | |||
A good sequencer consists at least of one line with 16 steps. There are obscurities like the MFB Step64 which has 64 steps, but in general, 16 are enough. | A good sequencer consists at least of one line with 16 steps. There are obscurities like the MFB Step64 which has 64 steps, but in general, 16 are enough. | ||
Tracks | === Tracks === | ||
I surely would like to have more than one track, 5 or 6 would be nice. But one is also enough for a start. | I surely would like to have more than one track, 5 or 6 would be nice. But one is also enough for a start. | ||
Directions | === Directions === | ||
Usually, I only use the forward direction. Backward and random are nice, but I never found myself using that. | Usually, I only use the forward direction. Backward and random are nice, but I never found myself using that. | ||
Cycle-length | === Cycle-length === | ||
This is an important feature since not every music can be pushed into a 16 scheme. Also, it can be really convenient to just let a sequencer play the first half, while you’re still adjusting the second half to your needs. But it is not nessecary to let the sequence start from somwhere else but 1. | This is an important feature since not every music can be pushed into a 16 scheme. Also, it can be really convenient to just let a sequencer play the first half, while you’re still adjusting the second half to your needs. But it is not nessecary to let the sequence start from somwhere else but 1. | ||
Syncing abilities | === Syncing abilities === | ||
Would be great but I do not have enough knowledge to realize this. If the sequencer is big enough it’s not neccesary to link it to another one. | Would be great but I do not have enough knowledge to realize this. If the sequencer is big enough it’s not neccesary to link it to another one. | ||
== Arpeggiator (transpose on midi input) == | == Arpeggiator (transpose on midi input) == | ||
| Line 184: | Line 181: | ||
All the ingredients are together, the building may begin. | All the ingredients are together, the building may begin. | ||
= The PD Patch = | = The PD Patch = | ||
== Implementing the UC33e== | == Implementing the UC33e== | ||
This was annoying as I had to do this several times. I mapped the controls to 1...8 in each row and every row had another midi channel. The UC-33e forgot its settings a few times, until I replaced the CMOS battery. | This was annoying as I had to do this several times. I mapped the controls to 1...8 in each row and every row had another midi channel. The UC-33e forgot its settings a few times, until I replaced the CMOS battery. | ||
All the in and output happens in midiio. | |||
=== Forwarding and distributing the control messages === | === Forwarding and distributing the control messages === | ||
| Line 207: | Line 205: | ||
Of course that doesn't make up for a complete sequencer. So I implemented a start and stop button, connected to the complexcounter. If that patch stops counting, the whole sequencer stops playing. A note off will be sent anyway. | Of course that doesn't make up for a complete sequencer. So I implemented a start and stop button, connected to the complexcounter. If that patch stops counting, the whole sequencer stops playing. A note off will be sent anyway. | ||
=== Paracontrol panel === | === Paracontrol panel === | ||
| Line 215: | Line 214: | ||
=== patternblade === | === patternblade === | ||
This contains the mechanism for my programmable arpeggiator. It works exactly as described above ( | This contains the mechanism for my programmable arpeggiator. It works exactly as described above (Arpeggiator). If the cycle length is set to 1, the main sequence will just repeat as usual. | ||
=== midiio === | === midiio === | ||
A diagnosis tool, intended to show all incoming CC. | A diagnosis tool, intended to show all incoming CC. | ||
Furthermore, | Furthermore, the Fader F9 controls the note volume (velocity) globally. | ||
= Working with the sequencer = | = Working with the sequencer = | ||
| Line 246: | Line 244: | ||
= Appendix = | = Appendix = | ||
The complete patch including subpatches can be downloaded [http://www.lauserundleiter.de/stepsequencer.zip here.] This has been built on PD for Windows, v. 0.42.5. You need the Vanilla library and a UC-33e midi controller or anything comparable. | |||
Thanks to Schneiders Laden in Berlin, where I had the opportunity to test the Oberkorn and Manikin Schrittmacher and to Mr. Schneider himself who helped with explanations. | |||