GMU:Dataflow II/Lukas - Revision history

Kine5848: /* patternblade */

2013-09-28T00:14:58Z

patternblade

← Older revision		Revision as of 00:14, 28 September 2013
Line 214:		Line 214:

	=== patternblade ===		=== patternblade ===
	This contains the mechanism for my programmable arpeggiator. It works exactly as described above (~~5 -~~ Arpeggiator). If the cycle length is set to 1, the main sequence will just repeat as usual.		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 ===

Kine5848: /* What does a sequencer need and what not? */

2013-09-28T00:13:37Z

What does a sequencer need and what not?

← Older revision		Revision as of 00:13, 28 September 2013
Line 115:		Line 115:
	== What does a sequencer need and what not? ==		== What does a sequencer need and what not? ==

	~~Step-~~length		=== 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) ==

Kine5848: /* Intention */

2013-09-28T00:09:44Z

Intention

← Older revision		Revision as of 00:09, 28 September 2013
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 ~~hardware synthesizers~~ which have their own pros and cons. Let’s take a look at some of them.		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 ==

Kine5848: /* Appendix */

2013-09-28T00:08:34Z

Appendix

← Older revision		Revision as of 00:08, 28 September 2013
Line 246:		Line 246:

	= 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.

Kine5848: /* The extras */

2013-09-28T00:00:02Z

The extras

← Older revision		Revision as of 00:00, 28 September 2013
Line 207:		Line 207:

	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 220:		Line 221:
	A diagnosis tool, intended to show all incoming CC.		A diagnosis tool, intended to show all incoming CC.

	Furthermore, ~~thhe~~ Fader F9 controls the note volume (velocity) globally.		Furthermore, the Fader F9 controls the note volume (velocity) globally.

	= Working with the sequencer =		= Working with the sequencer =

Kine5848: /* Doepfer Dark Time */

2013-09-27T23:59:16Z

Doepfer Dark Time

← Older revision		Revision as of 23:59, 27 September 2013
Line 47:		Line 47:


	=== 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 62:
	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 ===

Kine5848: /* The PD Patch */

2013-09-27T23:58:58Z

The PD Patch

← Older revision		Revision as of 23:58, 27 September 2013
Line 184:		Line 184:

	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==

	~~-->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.		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 221:		Line 222:

	Furthermore, thhe Fader F9 controls the note volume (velocity) globally.		Furthermore, thhe Fader F9 controls the note volume (velocity) globally.


	= Working with the sequencer =		= Working with the sequencer =

Kine5848: /* Pattern-Stepsequencer */

2013-09-27T23:58:52Z

Pattern-Stepsequencer

← Older revision		Revision as of 23:58, 27 September 2013
Line 1:		Line 1:
	= Pattern-Stepsequencer =		= Pattern-Stepsequencer =

	== Intention ==		== Intention ==

Line 9:		Line 8:


	== ~~Archetypes~~ of stepsequencers ==		== Comparision of stepsequencers ==


	~~'''~~ARP Sequencer (Mod. 1601)~~'''~~		=== ARP Sequencer (Mod. 1601) ===
	type:		type:
	1x16 or 2x8 step analog cv sequencer (no midi)		1x16 or 2x8 step analog cv sequencer (no midi)

Line 32:		Line 30:


			=== Doepfer Dark Time ===
	~~'''~~Doepfer Dark Time~~'''~~		type:
	type: 2x8 or 1x16 step sequencer		2x8 or 1x16 step sequencer
	2bus		2bus
	midi in/out		midi in/out
Line 49:		Line 47:


	~~'''~~Oberkorn SL16 / oberkorn-sliders'''		=== Oberkorn SL16 / oberkorn-sliders'''
	type:		type:
	1x16 step, 2bus cv (+midi) sequencer		1x16 step, 2bus cv (+midi) sequencer
Line 66:		Line 64:


	~~'''~~Quasimidi Polymorph~~'''~~		=== Quasimidi Polymorph ===

	type:		type:
Line 90:		Line 88:


	~~'''~~Manikin Schrittmacher~~'''~~		=== Manikin Schrittmacher ===

	type:		type:
Line 116:		Line 114:

	I had the opportunity to try out all of these in real (except for the ARP Sequencer, which I used as a software version together with the Arp2600V by Arturia). Additionally, I do own a Polymorph myself.		I had the opportunity to try out all of these in real (except for the ARP Sequencer, which I used as a software version together with the Arp2600V by Arturia). Additionally, I do own a Polymorph myself.




	== What does a sequencer need and what not? ==		== What does a sequencer need and what not? ==
Line 189:		Line 184:

	All the ingredients are together, the building may begin.		All the ingredients are together, the building may begin.


	= The PD Patch =		= The PD Patch =

Kine5848: /* Pattern-Stepsequencer */

2013-09-27T23:56:33Z

Pattern-Stepsequencer

← Older revision		Revision as of 23:56, 27 September 2013
Line 1:		Line 1:
	== Pattern-Stepsequencer ==		= Pattern-Stepsequencer =


	~~----~~

	== Intention ==		== Intention ==

Kine5848: /* The heart of the sequencer */ --appendix

2013-09-27T23:55:51Z

The heart of the sequencer: --appendix

← Older revision		Revision as of 23:55, 27 September 2013
Line 206:		Line 206:

	== The heart of the sequencer ==		== The heart of the sequencer ==

			The central subpatch is switchblade, containing the main mechanism to save the note values and forward each of them to the midimaker. This is triggered individually by the ticker (so there is only one note played simultaneously), which is generated by the complexcounter.
			That complex subpatch counts from 1 to 16, it detemines which of the 16 steps is being played and for how long.
			The midimaker simply generates a midi note (with on and off message), the length is determined by the bpmtomsec. The length is calculated in a way, that the notes do not overlap but are as long as possible.

			To put it in a nutshell, the whole patch generates MIDI on and off messages with controllable speed and pitch.

			== The extras ==

			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 ===
			The paracontrol panel allows the user to control the tempo, the cycle length and the note scaling of the main sequencer and the bottom offset and cycle length of the transpose section. These are mapped to the upper row of the UC-33e in the same order as displayed in PD.

			=== bottomoffset and rangeselect ===
			As it is difficult to get the right note when you have 127 values on a small knob, I implemented a stretching feature. It reduces the range of selectable notes and takes the range to the desired level (otherwise one would be only able to trigger subaural bass notes with this). bottomoffset and rangeselect neatly display the amount of octaves from the bottom, the lowest key and how many octaves wide the stretching should be. As I know from experience, a range from 1-4 octaves is more than enough.

			=== patternblade ===
			This contains the mechanism for my programmable arpeggiator. It works exactly as described above (5 - Arpeggiator). If the cycle length is set to 1, the main sequence will just repeat as usual.

			=== midiio ===
			A diagnosis tool, intended to show all incoming CC.

			Furthermore, thhe Fader F9 controls the note volume (velocity) globally.


			= Working with the sequencer =

			It works as desired, but by now only within the computer, using its own wavetable MIDI synthesizer.


			== Issues ==
			* MIDI communication to other devices doesn't work. During opening, PD moans that "MIDI input is dangerous in Windows". It also means that I cannot plug in the PC's midi output to any of my synths, for whatever reason. The forums did not give me an answer for this.
			* Due to these circumstances, I wasn't able to test the transpose-on-note-in feature. It has been removed from the patch.
			* The current note cannot be seen, but I don't really need this.
			* Programming the steps is a bit fiddly due to the small knobs. That may be solved by using different pot heads.
			* During startup, multiple zero division errors pop up. This is caused by the autoscale object, because most of the values need to be stretched to an area starting with zero and as soon as this value is entered into there, an error notification appears. Interestingly, this has no effect on performance or program stability, so I suggest to ignore it.



			= What else to implement next? =
			* Another blade showing the note value of each step and the current output and the option to mute each step individually. I tried this, but for unknown reasons, PD always crashed, so I decided to stay with the version I had before.
			* Getting (several) another UC-33e and make more tracks (but thanks to the MIDI issues of PD, this will be quite likely impossible)


			-----


			= Appendix =