Block
From Livid Wiki
Contents |
Introduction
Thank you for purchasing the block control surface from Livid Instruments. Block features assignable LED backlighting, custom designed rubber buttons, and high quality sliders and knobs, and is hand-crafted in our Austin, TX shop.
What’s in the box
Livid Block
USB Cable
Features
64 button clip bank
2 Faders
8 Rotary knobs
6 Function knobs
1 BPM/Tap button
Controls and Connections
While any of the controls on the Block can be used for a wide range of functionality, here are some basic
terms and uses for the controls.
- Programmable Clip Bank – The Clip Bank sends out data for activating files, triggering loops, sequences, or files. The programmable buttons on the Clip Bank can be assigned to MIDI notes or Continuous Controllers (CCs).
- Programmable Sliders – These programmable vertical sliders can be used to adjust effects, mapped to pitch and volume, or used to manipulate data. The sliders can be programmed to send CC or Pitch Bend messages.
- Programmable Knobs – These programmable knobs can be used to adjust effects, EQ settings, and control playback. The knobs can be programmed to send CC or Pitch Bend messages.
- Programmable Function Buttons – These programmable buttons can be used to activate various functions within the software such as: switching between channels or banks, selecting tracks, or used to cue, play, pause, and rewind your media. The buttons can be assigned to MIDI notes, program changes, or CCs.
- Programmable Tap Button – This programmable button is designed for tapping the BPM. This button can be assigned to MIDI notes, program changes, or CC’s.
Connecting
The Block is class-complaint and does not require drivers when using the USB connectivity.
- Connect the USB cable from the computer to the USB port on the Block.
- When the logo on the Block is illuminated, the device is powered.
For MIDI Connectivity
Using a standard MIDI cable, connect the Block MIDI in and out to the MIDI in and out of your sound-card or other MIDI interface. The Block must be plugged into a USB host and have MIDI software running (even if it's something basic like MIDI Monitor (http://www.snoize.com) or MIDI OX (http://www.midiox.com) running. This is a by-product of USB-powered class-compliant devices with no external power source. However, once you have the Block connected to a computer and some simple MIDI application running, you can send the Ohm's MIDI out the MIDI output jack.
Troubleshooting
Make sure your USB cable is properly connected. If you are using a USB hub, try connecting the Block USB cable directly to your computer. The lights should come on once the Block is connected.
If you are using a Macintosh Computer running OSX, make sure you have Block selected as your device in the Audio MIDI setup. To access Audio MIDI go to Applications>Utilities>Audio MIDI Setup.
Check to make sure your software is configured to use the Block. Open your application’s preferences to verify that the software is configured to receive the MIDI messages from the Block controller.
Windows XP will show the port names as “USB Audio Device” and “USB Audio Device[2]”, though the “New Hardware Found” popup will show the device as “Block”.
Windows 7 will show your controller as Block and will automatically recognize the device.
If you are still having problems, confirm that you are receiving MIDI data using MidiMonitor (for OS X) at http://www.snoize.com/MIDIMonitor/ or MIDIOX (for Windows) http://www.midiox.com.
Editor
See Block Editor
Support
For questions or support please visit our forums at http://community.lividinstruments.com/forum Here you will find answers to many of your questions and ask new ones. We will do our best to answer most of of your questions within 24 hours.
Appendix
Block Sysex
SYSTEM EXCLUSIVE COMMAND BYTES
The System Exclusive message includes the official MIDI Manufacturer ID for Livid, a Product number, and the Command number. A "wild card" Product number allows the same commands to be shared across multiple Livid products. These messages can be almost any number of bytes from 7 to (183) bytes.
Note: In this specification, all numbers are hexadecimal unless parenthesized or otherwise noted, in which case they are decimal.
F0 00 01 61 02 NN ... F7
The Product number is 03for the Block, and the Command numbers, NN, are described below.
COMMAND SUMMARY
00 : individual button map (not supported) *
01 : individual control map (not supported) *
02 : Save User Settings
03 : read presets (ignored) *
04 : Set all LED indicators
05 : Recall User Settings
06 : Factory Reset
07 : Request, multiple subtypes:
07.04 : Request all LED indicators
07.06 : Request Control Surface Snapshot
07.08 : Request MIDI Settings (Local Control, etc.)
07.09 : Request Single MIDI Input mapping
07.0A : Request Analog mapping
07.0B : Request Button mapping
07.0C : Request MIDI Basic Channel
07.0D : Request MIDI Output Merge setting
07.0F : Request crossfader Flip setting
08 : MIDI Settings Response
09 : Map Single LED Indicator
0A : Map Analog Inputs
0B : Map Buttons
0C : Set MIDI Basic Channel
0D : Set MIDI Output Merge
0E : Erase entire MIDI Input Map
0F : Set crossfader Flip
7E : NAK Negative Acknowledge
7F : ACK Positive Acknowledge
Commands 0, 1, and 3 are Ohm "classic" System Exclusive commands. Even though the MIDI Manufacturer ID is different, and the command structure is different as well, these skipped command numbers pay tribute to what came before.
COMMAND DETAILS
02 : Save User Settings
F0 00 01 61 03 02 F7,
All User Settings which can be remembered will be stored in Flash and automatically restored whenever the Block is powered up.
The Block responds with ACK when finished processing this command.
04 : Set all LED indicators
F0 00 01 61 03 04 LL HH LL HH LL HH LL HH LL HH F7
All (64) LED grid indicators can be set on or off with this command. There are (10) bytes, or 5 pairs of LL HH. Values must be 7F or less. The first LL HH pair represents column 1, with each subsequent LL HH pair representing the next column. Within each pair, LL represents the first 7 rows, and HH represents the remaining 6 rows. There are (14) bits total for rows, but bit (11) is unavailable and reserved for future use. A 0 bit turns the LED off, a 1 bit turns it on.
The LED columns and rows do not conveniently match up with the physical layout of the Button columns and rows. Using codes as C.R to specify column and row, the LED codes are as follows (all codes are decimal in this table, and all columns and rows are numbered starting at 1 - the first line is the first Button column from first to last row, etc.):
64 grid:
1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8,
2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8,
3.1, 3.2, 3.4, 3.4, 3.5, 3.6, 3.7, 3.8,
4.1, 4.2, 4.4, 4.4, 4.5, 4.6, 4.7, 4.8,
5.1, 5.2, 5.4, 5.4, 5.5, 5.6, 5.7, 5.8,
1.9, 1.10, 1.12, 1.13, 1.14, 4.9, 4.10, 4.12,
2.9, 2.10, 2.12, 2.13, 2.14, 5.9, 5.10, 5.12,
3.9, 3.10, 3.12, 3.13, 3.14, 4.13, 4.14, 5.13
The Block responds with ACK when finished processing this command.
05 : Recall User Settings
F0 00 01 61 03 05 F7
Recall User Settings from storage, just like what happens on power up.
The Block responds with ACK if the User Settings are valid, or NAK when no setting have been saved or the memory is unreadable.
06 : Factory Reset
F0 00 01 61 03 06 F7
This will erase the User Settings so that the Block is factory fresh.
The Block responds with ACK when finished processing this command.
07 : Request
F0 00 01 61 03 07 RR .. F7
This command allows several types of information to be requested. Each request type, RR, will be detailed below. Some request messages require additional information bytes to specific which particular item is being requested.
The Block responds with the specified data.
07.04 : Request all LED indicators
F0 00 01 61 03 07 04 F7
Request state of all LED indicators. The Block will respond with Command 04, and the bits are interpreted identically.
07.06 : Request Control Surface Snapshot
F0 00 01 61 03 07 06 F7
Request values for all Analog inputs. The Block will re-scan every analog input and report the value with the usual MIDI Channel Message, even if it has not changed.
07.08 : Request MIDI state (Channel Mode, etc)
F0 00 01 61 03 07 08 F7
Request state of settings that are controlled by MIDI messages, such as Local Control, Omni, Mono/Poly Mode. The Block will respond with Response Command 08.
07.09 : Request Single MIDI Input mapping
F0 00 01 61 03 07 09 LL HH F7
Request the current mapping of incoming MIDI messages. LL HH is the 8-bit map code defined under Command 09 below. Both values must not exceed 7F. LL holds the lower 7 bits, HH holds the most significant bit. Values of HH greater than 1 are reserved. The Block will respond with Command 09, which repeats LL and HH followed by the LED code as CR.
07.0A : Request Analog mapping
F0 00 01 61 03 07 0A F7
Request MIDI map for all Analog inputs. The block will respond with Command 0A, and the bits are arranged identically.
07.0B : Request Button mapping
F0 00 01 61 03 07 0B F7
Request MIDI map for all Buttons. The block will respond with Command 0B, and the bits are formatted identically.
07.0C : Request MIDI Basic Channel
F0 00 01 61 03 07 0C F7
Request MIDI Basic Channel. The block will respond with Command 0C.
07.0D : Request MIDI Output Merge setting
F0 00 01 61 03 07 0D F7
Request MIDI Output Merge setting. The Block will respond with Command 0D.
08 : MIDI Settings Response
F0 00 01 61 03 08 XX F7
Individual MIDI settings, such as the Channel Mode flags, are combined into the data of this message, XX. Bit 1 is Omni Mode Off/On. Bit 3 is Local Control Off/On. All other bits, including 0 and 2, are Reserved. They may reflect other settings, but they may change in future releases. Note that this is a response command only, and it will be ignored if received by the Block. Use the official MIDI messages to change these settings.
09 : Map Single LED Indicator
F0 00 01 61 03 09 LL HH CR F7
This command updates the MIDI Input map for a single entry. If HH is 00, then LL specifies the Note number. If HH is 01, then LL specifies the Control number, but only valid control numbers are accepted from 00 to 78. Values of HH above 1 are reserved. CR is the LED indicator Column and Row (see Command 04 for details), or 7F to clear the mapping for the specified entry.
The Block responds with a Single MIDI Input mapping for the specified message.
0A : Map Analog Inputs
F0 00 01 61 03 0A (10)*[LL HH] F7
This command updates the MIDI map for all (10) Analog inputs. If HH is 00, then LL specifies the 7-bit Control number, but only valid control numbers 00 to 78 are accepted. If HH is 01, then LL selects between 14-bit Control numbers and Pitch Bend. In the latter case, LL between 60 and 6F specifies a Pitch Bend message on Channel (1) through (16), respectively. Otherwise, LL selects a 14-bit Control number, of which the only valid control numbers are 00 to 1F. All other values for LL, 20 through 5F and 70 through 7F are reserved for future use. Values of HH above 1 are similarly reserved.
There are (10) sets of LL HH value pairs in this message, each corresponding to the index of an Analog input. These indices do not conveniently match up with the physical layout. The index codes are arranged as follows (all indices are decimal in this table, and start with 0):
upper knobs:
3, 2, 1, 0, 5, 4, 6, 7
two faders, from left to right:
9, 8
The Block responds with ACK when finished processing this command.
0B : Map Buttons
F0 00 01 61 03 0B (72)*[LL HH] F7
This command updates the MIDI map for all (71) Buttons. If HH is 00, then LL specifies the Note number. If HH is 01, then LL specifies the Control number, but only valid control numbers are accepted from 00 to 78. Larger values of LL and HH are reserved, with 7A (start), 7B (continue), and 7C (stop) used for MMC.
There are (72) sets of LL HH value pairs in this message, each corresponding to the index of a Button. These indices do not conveniently match up with the physical layout, and there is one missing code near the end which is reserved. The index codes are arranged as follows (all indices are decimal in this table, and start with 0):
grid buttons are:
0, 8, 16, 24, 32, 40, 48, 56
1, 9, 17, 25, 33, 41, 49, 57
2, 10, 18, 26, 34, 42, 50, 58
3, 11, 19, 27, 35, 43, 51, 59
4, 12, 20, 28, 36, 44, 52, 60
5, 13, 21, 29, 37, 45, 53, 61
6, 14, 22, 30, 38, 46, 54, 62
7, 15, 23, 31, 39, 47, 55, 63
BPM:
64
function 1-6:
69, 70,
66, 67,
71,
68
The Block responds with ACK when finished processing this command.
0C : Set MIDI Basic Channel
F0 00 01 61 03 0C NN F7
This command sets the MIDI Basic Channel to NN, where 00 through 0F are valid and the rest are reserved. During operation, incoming Channel messages are ignored if Omni Mode is Off and the Channel does not match. If Omni Mode in On, then the incoming Channel is not checked, and all messages are interpreted. For outgoing MIDI messages, the Basic Channel is always used unless an Analog input is mapped to Pitch Bend, in which case the Channel number is specified by the mapping entry.
The Block responds with ACK when finished processing this command.
0D : Set MIDI Output Merge
F0 00 01 61 03 0D NN F7
This command allows the Control Surface to merge its messages onto the MIDI output jack, in addition to USB. NN can be 00 (off) or 01 (on). Other values are reserved.
The Block responds with ACK when finished processing this command.
0E : Erase entire MIDI Input Map
F0 00 01 61 03 0E F7
This command erases all MIDI Input message mappings. These affect the remote control of LED indicators, so no remote control will be available immediately after the map is erased. Because there are as many as (256) possible MIDI Input messages that can be mapped to an LED, and because multiple assignments to the same LED can cause conflicts, it is best to start the LED indicator mapping process by first erasing all entries before filling in the desired mappings, no more than (64), preferably.
The Block responds with ACK when finished processing this command.
7E : NAK Negative Acknowledge
F0 00 01 61 03 7E F7
This is intended as a way for the Block to indicate a problem with the previous message. Unfortunately, when messages are sent too fast, it becomes impossible for the Block to reply with anything reliably, even NAK. The best approach is to wait for ACK (see below) after sending each message, rather than depend on NAK to indicate an error. The one exception is Recall User Settings, where the Block will reply with NAK if the contents of User memory are empty or otherwise corrupted.
7F : ACK Positive Acknowledge
F0 00 01 61 03 7F F7
ACK means the previous message was handled correctly. Some messages (e.g. Map Single LED Indicator) simply reply with a specific command instead of ACK, when more context is needed than a simple acknowledgment.
MAPPING SUMMARY
Analog to CC; 121 control numbers; 7-bit value
Analog to CC; 32 control numbers; 14-bit value
Analog to Pitch Bend; 16 channels; 14-bit value
Button to Note; 128 note numbers; 1-bit value
Button to CC; 121 control numbers; 1-bit value
Button to MMC; 3 types; no value
LED from Note; 128 note numbers; 1-bit value
LED from CC; 121 control numbers; 1-bit value
MIDI IMPLEMENTATION
The following standard MIDI messages are implemented.
System Real Time:
MIDI System Reset
Channel Mode Messages:
Reset All Controllers
Local Control (connects buttons to corresponding LED indicators)
Poly On / Mono On (both set Omni Off)
Omni On/Off
All Notes Off (turns off all LED indicators)
Controller Numbers:
1F : logo, 14-bit (10-bit effective) dimmer
FRONT PANEL CONTROL
The following key combinations allow front panel control of certain settings.
F1+BPM Local Control on (LED indicators controlled by buttons and external)
F3+BPM Local Control off (LED indicators under external control only)
F5+BPM Omni on (messages received on all channels)
F6+BPM Omni off (messages received on Basic Channel only)
Note: the following are defeated since there are no MIDI output ports.
F2+BPM MIDI out merge on (Control Surface sends to USB & MIDI out, default)
F4+BPM MIDI out merge off (Control Surface sends on USB only)
LED Control Column/Row Codes
Assigning Buttons MIDI Values with SySex
Controls Naming Convention
Warranty
Block WARRANTY AND RETURN POLICY
Damage
Your Instrument should be inspected immediately upon receiving it. If there are any damages they should be reported immediately. All of our instruments are fully tested just prior to leaving our plant. Return Policy
All sales of Livid Instruments hardware are given a fifteen (15) day return policy. A controller may be returned within fifteen (15) days of purchase. We will refund the purchase price of the product, less shipping, immediately upon receipt of the returned item in as good of shape as it was shipped in. Any damage will be the responsibility of the customer. We will do our best to determine if damage happened during shipping and will help the customer by allowing carrier inspection of any damaged items. Software cannot be returned. Any open software packaging is not returnable or available for any refund.
Warranty
Livid Instruments warrants that this product is free of defects in materials and workmanship under normal conditions for one year from the purchase date, so long as the product is: owned by the original purchaser; the original purchaser has proof of purchase from Livid Instruments or an authorized dealer. Warranty does not include repairs needed due to misuse or abuse.
In the event that Livid Instruments receives written notice of defects in materials or workmanship from such an original purchaser, Livid Instruments will either replace the product, repair the product, or refund 21
the purchase price at its option. In the event any repair is required, shipment to and from Livid Instruments and a nominal handling charge shall be born by the purchaser. In the event that repair is required, a Return Authorization (RMA) number must be obtained from Livid Instruments. After the RMA number is obtained, the unit should be shipped back to Livid Instruments in a protective package with a description of the problem and the Return Authorization (RMA) clearly written on the package.
In the event that Livid Instruments determines that the product requires repair because of user misuse or regular wear, it will assess a fair repair or replacement fee. The customer will have the option to pay this fee and have the unit repaired and returned, or not pay this fee and have the unit returned un-repaired.
THE REMEDY FOR BREACH OF THIS LIMITED WARRANTY SHALL NOT INCLUDE ANY OTHER DAMAGES. LIVID INSTRUMENTS WILL NOT BE LIABLE FOR CONSEQUENTIAL, SPECIAL, INDIRECT, OR SIMILAR DAMAGES OR CLAIMS INCLUDING LOSS OF PROFIT OR ANY OTHER COMMERCIAL DAMAGE, EVEN IF ITS AGENTS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IN NO EVENT WILL LIVID INSTRUMENTS' LIABILITY FOR ANY DAMAGES TO THE PURCHASER OR ANY OTHER PERSON EXCEED THE PRICE PAID FOR THE PRODUCT, REGARDLESS OF ANY FORM OF THE CLAIM. LIVID INSTRUMENTS SPECIFICALLY DISCLAIMS ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED. SPECIFICALLY, LIVID INSTRUMENTS MAKES NO WARRANTY THAT THE PRODUCT IS FIT FOR ANY PARTICULAR PURPOSE.
This warranty shall be construed, interpreted, and governed by the laws of the state of New Jersey. If any provision of this warranty is found void, invalid or unenforceable, it will not affect the validity of the balance of the warranty, which shall remain valid and enforceable according to its terms. In the event any remedy hereunder is determined to have failed of its essential purpose, all limitations of liability and exclusion of damages set forth herein shall remain in full force and effect.
Livid Instruments, Viditar Inc.
The Block is handcrafted and assembled in The United States of America.
