Hex - Revision history

Okyeron: /* Overview */

2012-12-06T08:13:03Z

‎Overview

Okyeron: /* Overview */

2012-12-06T08:12:46Z

‎Overview

Okyeron at 08:11, 6 December 2012

2012-12-06T08:11:17Z

Amounra: /* Known Issues and Bugs */

2012-11-09T22:49:05Z

‎Known Issues and Bugs

Amounra at 22:46, 9 November 2012

2012-11-09T22:46:32Z

Amounra: /* The Encoders */

2012-11-03T06:16:57Z

‎The Encoders

Amounra: /* poly record */

2012-11-03T06:14:56Z

‎poly record

Amounra: /* The Encoders */

2012-11-03T06:12:02Z

‎The Encoders

Amounra: /* Overview */

2012-11-03T06:07:58Z

‎Overview

Amounra: /* The User Interface */

2012-11-03T06:05:43Z

‎The User Interface

← Older revision		Revision as of 08:13, 6 December 2012
Line 10:		Line 10:

	'''Video Demos'''		'''Video Demos'''
		+
	[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics]		[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics]

@@ Line 9: / Line 9: @@
 Hex is currently built for the CNTRL:R, but it's functionality can be accessed from any controller by using Live's MIDI Mapping capabilities.  It will include support for other grid-based controllers that are compatible with Monomodular with future releases.  The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.
-[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics Video Demo]
+'''Video Demos'''
 [http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics]
 =The User Interface=

← Older revision		Revision as of 08:11, 6 December 2012
Line 8:		Line 8:

	Hex is currently built for the CNTRL:R, but it's functionality can be accessed from any controller by using Live's MIDI Mapping capabilities. It will include support for other grid-based controllers that are compatible with Monomodular with future releases. The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.		Hex is currently built for the CNTRL:R, but it's functionality can be accessed from any controller by using Live's MIDI Mapping capabilities. It will include support for other grid-based controllers that are compatible with Monomodular with future releases. The idea here is to eventually replace the functionality of Stepp:r, Polygome, TR256, and Binary with a single patch that is accessible from multiple controllers at once, while improving the speed, efficiency, and capabilities of the originals.
		+
		+	[http://www.youtube.com/watch?v=BkyNa4tz1y4 Hex Basics Video Demo]
		+
		+	[http://www.youtube.com/watch?v=V6TOLEEDQfU Hex Details Video Demo]
		+

	=The User Interface=		=The User Interface=

@@ Line 267: / Line 267: @@
 Read and Write (via pattrstorage) are currently broken.  I'm looking into this.
-Freewheel is currently not functioning correctly.  This was working in the prototypes (as it works in "binary", as well), but due to some last minute bugs that cropped up I had to disable some of its functionality in order to promote better timing of the rest of the patch.  It will be back shortly.
+Freewheel is currently not functioning correctly.  This was working in the prototypes (as it works in "binary", as well), but due to some last minute bugs that cropped up I had to disable some of this mode's functionality in order to promote better timing for the rest of the patch.  It will be back to normal in an update, hopefully soon.
 Automation rec/play currently only supports the mutes and single preset changes.  This will probably see more additions later if it proves to be truly useful.
 =Technology=

← Older revision		Revision as of 22:46, 9 November 2012
Line 262:		Line 262:

	If "Global" is active, any randomization or initialization changes will affect all global presets (that means every single preset in every single sequence). Be carefull....it takes a little while.		If "Global" is active, any randomization or initialization changes will affect all global presets (that means every single preset in every single sequence). Be carefull....it takes a little while.
		+
		+	=Known Issues and Bugs=
		+
		+	Read and Write (via pattrstorage) are currently broken. I'm looking into this.
		+
		+	Freewheel is currently not functioning correctly. This was working in the prototypes (as it works in "binary", as well), but due to some last minute bugs that cropped up I had to disable some of its functionality in order to promote better timing of the rest of the patch. It will be back shortly.
		+
		+	Automation rec/play currently only supports the mutes and single preset changes. This will probably see more additions later if it proves to be truly useful.
		+

	=Technology=		=Technology=

@@ Line 127: / Line 127: @@
 When you open hex for the first time, it should be in its default mode, or "Plug" mode.  This means that its output is sent to the m4l plugins output.  You can either place a DrumRack after it or send the tracks output to another track containing a DrumRack that you want hex to play.  If hex does not automatically detect the DrumRack you wish it's encoders to control, it will look something like this:
-[[File:hex_detect_instrument]]
+[[File:Hex_detect_instrument.png]]
 Don't worry, all  is not lost.  Just press the button that says "Detect Instrument".  A little window will be floated on your screen, that looks like this:
-[[File:hex_detect_float]]
+[[File:Hex_detect_float.png]]
 Select the DrumRack you wish to control (the "Blue Hand" should appear on it, and it should be hilighted), and then press the button in the float.  The CNTRL:R's encoder rings should immediately update to reflect the currently selected part's parameters.
@@ Line 137: / Line 137: @@
 Your GUI should look something like this:
-[[File:hex_encoders]]
+[[File:Hex_encoders.png]]
 If you're not happy with the parameters that hex uses, just group the instrument and assign the macros to the parameters that you wish to control.  Hex will happily lock to them instead.
 When you're ready to go further and explore some new madness, turn the "Channel" encoder to something besides "Plug".  In addition to the plugin's output, hex can transmit your part to one of sixteen MIDI channels.  Hex stores a different device for each MIDI channel.  In this way, you can quickly assign a single note sequence that is outputting to your DrumRack to an instrument in a completely different place in your set, and it will start playing whatever multi-note pattern you've recorded in that track.
 There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You'll need to create an IAC loop passthrough by doing the following:
@@ Line 157: / Line 161: @@
 Once you have assigned an instrument to one of hex's individual channels, the display should look like this:
-[[File:hex_encoders2]]
+[[File:Hex_encoders2.png]]
 Notice that there are some differences.  Hex only controls 4 parameters of the target instrument (on the top 4 encoders).  On the second row of encoders, PolyOffset and Mode have replaced the "Plug"s parameter assignments.

@@ Line 111: / Line 111: @@
 ===poly record===
-[[File:hex_polyrec.png]]
+[[File:Hex_polyrec.png]]
 Poly record mode allows the user to record a sequence of notes via the keys top keys.  The notes will only be played back at their recorded pitch if the selected voice is set to a channel other than "Plug".  Unfortunately, this limits use of this feature to OSX only....however, I have a solution for Windows user's coming soon ;)

@@ Line 143: / Line 143: @@
 When you're ready to go further and explore some new madness, turn the "Channel" encoder to something besides "Plug".  In addition to the plugin's output, hex can transmit your part to one of sixteen MIDI channels.  Hex stores a different device for each MIDI channel.  In this way, you can quickly assign a single note sequence that is outputting to your DrumRack to an instrument in a completely different place in your set, and it will start playing whatever multi-note pattern you've recorded in that track.
-There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You'll need to do the following:
+There are a few caveats here.  As mentioned earlier, this only currently works on OSX.  You'll need to create an IAC loop passthrough by doing the following:
 .  Create an IAC Bus in OSX"s "Audio MIDI Setup".
 .  Open hex's Settings and assign that IAC Bus as the "Poly Output Port".
 .  Assign the instrument you want to control to Hex in the same manner you did with the DrumRack.  You'll need to do this once for each of the sixteen channels, but the settings will be stored with your project unless you delete the controlled instrument at some point.
 Once you have assigned an instrument to one of hex's individual channels, the display should look like this:

@@ Line 3: / Line 3: @@
 [[File:Hex pic a.png]]
-Hex contains sixteen sequences, or parts, that can be edited and manipulated in real time in various ways from the controller.  When linked to a properly configured DrumRack, the controller's encoders control parameters belonging to each of it's chains.  Each of the sequences contains sixteen different presets, which can be chosen and stored directly from the controller.  Loop begin and end points can also be set using the controller.  All of the sequences speed settings can be set changed independently in either quantized or unquantized amounts.  Sequence timing can be synchronized between different parts in an easy fashion.  Different behavior definitions can be made for each step of each sequence directly from the controller.  Part-mute and preset changes can be recorded directly into the currently playing MIDI clip on the same track that the mod is present, even while playing back previously recorded automation data in the same clip.
+Hex contains sixteen sequences, or parts, that can be edited and manipulated in real time in various ways from the controller.  When linked to a properly configured DrumRack, the controller's encoders control parameters belonging to each of it's chains.  When in PolyMode, the part can be transmitted directly to an instrument and send a pitched sequence.  Each of the sequences contains sixteen different presets, which can be chosen and stored directly from the controller.  Loop begin and end points can also be set using the controller.  All of the sequences speed settings can be set changed independently in either quantized or unquantized amounts.  Sequence timing can be synchronized between different parts in an easy fashion.  Different behavior definitions can be made for each step of each sequence directly from the controller.  Part-mute and preset changes can be recorded directly into the currently playing MIDI clip on the same track that the mod is present, even while playing back previously recorded automation data in the same clip.
 Hex combines most of the ergonomics of the Livid Stepp:r with the versatility and speed of the "binary" mod I wrote for the Code last year.  It is still a work in progress, and some features are still being fleshed out (among which are polyphonic step mode, solo mode, and trigger mode).  While borrowing heavily from both of its predecessors, it yet promises a lot of unrealized potential under the hood.  A great deal of the underpinnings of "binary" have yet to be implemented.

@@ Line 120: / Line 120: @@
 Poly play mode allows the user to play back the current sequence immediatedly, ala Polygome.  Each of the top keys represent a base note, and pressing it will start the sequence playing independent of the current time position, with its root based on the note pressed, and locked to the current mode setting.  It's also important to recognize that the Poly Offset parameter is useful here, since otherwise the sequence base note will be C-2.
 ==Other Controls==
@@ Line 137: / Line 181: @@
 In order to play back this data, just play the clip and make sure that PLAY is turned on in the UI.  You can have both PLAY and REC enabled at the same time in order to overdub new changes (however, this will not currently erase older data).
-Hex uses note-based automation.  It's important to understand a little about this:  any note event arriving at the mod's input can be interpreted as automation data.  Hex reserves note numbers above 113 for use with automation.  As long as "Play" is not enabled, nothing dire will happen.  However, be sure not to send unintentional notes to Hex when it's in play mode, or some wacky things will probably happen.  Any notes below its automation range will just be passed through to Hex's output.
+Hex uses note-based automation.  It's important to understand a little about this:  any note event arriving at the mod's input can be interpreted as automation data.  Hex reserves note numbers above 113 for use with automation.  As long as "Play" is not enabled, nothing dire will happen.  However, be sure not to send unintentional notes to Hex when it's in play mode, or some wacky things will probably happen.  Any notes below its automation range will just be passed through to hex's output.
 ===Behaviors===