GMU:Dataflow II/Lukas: Difference between revisions

Line 164:

'''What methods do I have available to make a step sequencer?'''

~~1.)~~ Soldering one together, using an arduino and a lot of potentiometers. Ok, I may do this in another project as this will take a lot of work.

# Soldering one together, using an arduino and a lot of potentiometers. Ok, I may do this in another project as this will take a lot of work.

~~2.)~~ Cascading several Doepfer Dark Time. This would work, but even for a 2 set of them I would need to pay 900€+ which I don't have.

# Cascading several Doepfer Dark Time. This would work, but even for a 2 set of them I would need to pay 900€+ which I don't have.

~~3.)~~ Disassembling the Polymorph's OS and modify the sequencer to my needs. Too bad I can't handle this. Not to mention that I still have to make up for a different interface.

# Disassembling the Polymorph's OS and modify the sequencer to my needs. Too bad I can't handle this. Not to mention that I still have to make up for a different interface.

~~4.)~~ Using a midi controller and make a software based sequencer with a tangible interface.

# Using a midi controller and make a software based sequencer with a tangible interface.

4.) seems to be the best since I have an UC-33e midi controller floating around for ages. Together with Pure Data, this will make up for a tangible sequencer according to my wishes.

== The UC-33e controller ==

This box features 24 knobs, 9 sliders and 16 programmable buttons. This is a limitation to what I planned, since I originally wanted to have 4x16 steps. It wouls be possible to have 4x8 steps, but then there wouldn't be any dials left for controlling the other parameters.

So what would be possible with one controller?

* 3x8 steps, 9 controls

* 2x8 steps, 9 controls

* 1x16 steps, 17 controls

The last option sounded interesting, but there were a bit too many controls. I decided to use these for the pattern mode.

So, there we have:

C17...C25 as Step 1-16

F1...F8 as Pattern transpose 1-8

C26...C33 and the buttons for controlling issues

All the ingredients are together, the building may begin.

= The PD Patch =

== Implementing the UC33e==

-->midiio

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.

=== Forwarding and distributing the control messages ===

The input for the step sliders will be forwarded to the pushbar subpatch, which stretches the input in push to a definable range (coming in from paracontrol) and then it will be displayed on a set of 16 and 8 sliders on the main display.

== The heart of the sequencer ==

@@ Line 164: / Line 164: @@
 '''What methods do I have available to make a step sequencer?'''
-.) Soldering one together, using an arduino and a lot of potentiometers. Ok, I may do this in another project as this will take a lot of work.
+# Soldering one together, using an arduino and a lot of potentiometers. Ok, I may do this in another project as this will take a lot of work.
-.) Cascading several Doepfer Dark Time. This would work, but even for a 2 set of them I would need to pay 900€+ which I don't have.
+# Cascading several Doepfer Dark Time. This would work, but even for a 2 set of them I would need to pay 900€+ which I don't have.
-.) Disassembling the Polymorph's OS and modify the sequencer to my needs. Too bad I can't handle this. Not to mention that I still have to make up for a different interface.
+# Disassembling the Polymorph's OS and modify the sequencer to my needs. Too bad I can't handle this. Not to mention that I still have to make up for a different interface.
-.) Using a midi controller and make a software based sequencer with a tangible interface.
+# Using a midi controller and make a software based sequencer with a tangible interface.
+.) seems to be the best since I have an UC-33e midi controller floating around for ages. Together with Pure Data, this will make up for a tangible sequencer according to my wishes.
+== The UC-33e controller ==
+This box features 24 knobs, 9 sliders and 16 programmable buttons. This is a limitation to what I planned, since I originally wanted to have 4x16 steps. It wouls be possible to have 4x8 steps, but then there wouldn't be any dials left for controlling the other parameters.
+So what would be possible with one controller?
+* 3x8 steps, 9 controls
+* 2x8 steps, 9 controls
+* 1x16 steps, 17 controls
+The last option sounded interesting, but there were a bit too many controls. I decided to use these for the pattern mode.
+So, there we have:
+C17...C25 as Step 1-16
+F1...F8 as Pattern transpose 1-8
+C26...C33 and the buttons for controlling issues
+All the ingredients are together, the building may begin.
+= The PD Patch =
+== Implementing the UC33e==
+-->midiio
+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.
+=== Forwarding and distributing the control messages ===
+The input for the step sliders will be forwarded to the pushbar subpatch, which stretches the input in push to a definable range (coming in from paracontrol) and then it will be displayed on a set of 16 and 8 sliders on the main display.
+== The heart of the sequencer ==