Tascam Digital Mixing Console TM-D4000 Owners Manual

							9 - Machine Control—Notes on individual devices
9–7
2Press the EDIT key.
The location memory source (timecode or 
MTC, or ABS) is shown, along with the value 
of the location memory.
9.3.6 Manual location
It is also possible to enter a location point manually, 
(from a cue list, for instance) and locate straight to it.
1Press the MANUAL LOCATE key so that the 
indicator lights.
2Use the number keys to enter a number in 
hh:mm:ss (and optionally frames) format.
3When the ENT or ENTER key is pressed, the 
controlled device will start to locate to the 
location point just entered.
This location point can be stored by pressing the 
MEMO key so that the indicator flashes, followed by 
the 
MANUAL LOCATE key.
To locate to this point again after storing the location 
point, press the 
MANUAL LOCATE key, followed by 
the 
ENT or ENTER key.
Note that the pre-roll time (9.2.4, “Locate Preroll”) 
does not apply here.
9.3.7 Repeat play
Location memories 8 and 9 (accessed with the 8 and 
9 keys) are used as the start and end points of a repeat 
loop that can be played by pressing the 
REPEAT 8-9 
key 
[40].
While the controlled device is in repeat mode, the 
REPEAT indicator is lit. The indicator flashes when the location of the controlled device is outside the 
repeat points.
If point 8 follows point 9, or if the distance between 
the two points is very short, the behavior of the 
repeat playback depends on the device which is 
being controlled.
9.3.8 Auto punch operations
For DTRS units, the three “punch” keys: RHSL , IN/
OUT
 and CLEAR [36] are used in the same way as 
the corresponding keys on the DTRS unit.
Consult the documentation for the DTRS unit for 
details of how to perform punch operations.
When punch operations are taking place, the punch-
in and punch-out points may be viewed and edited in 
location memories 4 and 5 respectively. When the 
CLEAR key is pressed to finish punch operations, the 
original location memories (if any) are restored.
9.3.9 ALL INPUT and AUTO MON
The ALL INPUT and AUTO MON keys send the 
appropriate commands to all devices in the list that 
have the REC function enabled. When the function is 
active, the key’s indicator will light.
If the controller does not support the function, the 
indicator will not light.
If a number of controllers have had the REC function 
selected, some of which do accept this command, 
and some which do not, the indicator will not light in 
the majority of cases.
DTRS and ADAT devices can accept this command, 
as can MMC devices. Some devices controlled using 
the P2 protocol can accept these commands, but 
some cannot, depending on the manufacturer’s 
implementation of the protocol.
9.4 Notes on individual devices
These following notes apply to the external control 
screens, etc. for some of the specific devices that may 
be controlled by the TM-D4000.
9.4.1 MIDI timecode generator
The timecode generator incorporated into the TM-
D4000, which outputs MIDI Timecode (MTC) from  
						

							9 - Machine Control—Notes on individual devices
9–8 
the MIDI OUT port, is controlled using the 
Automation Setup screen.
1Move the cursor to the SYNC SOURCE 
panel, and select the timecode type 
(
30fps, 25fps, etc.),
2Select the INT (internal generator) option.
3While this screen is displayed, and the cursor 
is pointing to this bottom section of the 
screen, the PODs can be used to set the start 
time of the internal generator.
Alternatively, the numeric keypad can be 
used for direct entry of the time value, if the 
memory location functions are not being 
used (and taking over the use of the numeric 
keypad).
9.4.2 DTRS devices
Depending on the functionality of the DTRS unit 
(DA-88, DA-38 or DA-98), different options, such as 
track delay, dither setting, etc. are available, allowing 
these menu operations to be carried out easily from 
the TM-D4000. Consult the documentation of your 
DTRS unit for full details of these operations.
It is essential that only one unit is connected directly 
using the 
REMOTE OUT connection from the TM-
D4000 and this should be is ID 1 (0 in the case of 
DA-88). It is suggested that the other units in the 
chain are numbered in order following this (but this 
is not essential). Remember that all chains of DTRS 
units should be terminated.
If the DTRS units are to be word clock slaves of the 
TM-D4000, the dedicated word clock input of the 
DTRS unit connected directly to the TM-D4000 
should be connected to the word clock sync output 
(
[76]) of the TM-D4000, and the clock source set to 
WORD. Subsequent units in the chain will receive 
their word clock information directly through the REMOTE connections, and do not require dedicated 
word clock connections.
9.4.3 8mm DTRS
This setting allows the control of a DTRS unit 
through the RS-422 connection, using the P2 proto-
col. This may be useful in certain setups where the 
P2 protocol is being used extensively.
9.4.4 ADAT devices
The SYNC OUT connector on the IF-LP4000 is used 
for controlling ADAT recorders (as selected from the 
list of available units). No matter how many ADATs 
are connected, only one SYNC connection should be 
made from the TM-D4000 to the ADAT chain.
In addition to control information, this also provides 
a word clock to the ADAT recorder. This is particu-
larly useful when using the TM-D4000 with ADAT 
models which do not have a dedicated word clock 
input. 
It may take a little experimentation before the best 
way of providing a word clock to the system is dis-
covered. ADAT models LX20 and XT20 have a 
“LOCK” indicator which can help determine the 
most stable configuration. 
However, we suggest that ADAT recorders are not 
used as clock masters.
In addition, the SYNC word source should be used 
when more than one ADAT recorder is connected 
(the “lightpipe” clock can cause noise in some chains 
of ADATs).
Some models of ADAT recorder (e.g. the LX20 and 
XT20 models) will echo the status of their REC 
FUNCTION keys on the TM-D4000’s 
REC indica-
tors. However, other models will not echo the status 
of their REC FUNCTION keys on the TM-D4000. 
In addition, other ADAT settings, such as all input, 
auto monitor, input source, etc. cannot be read by the 
TM-D4000.
Also note that it is not possible to add ADAT units 
while the TM-D4000 is powered on (it is never a 
good idea to connect and disconnect equipment 
which is powered on in any case). When adding or 
removing ADAT units from a chain, we suggest that 
the ADATs are turned on first, in order to establish 
their IDs, before turning on the TM-D4000 (and then 
the monitoring system).
9.4.5 MIDI Controllers and MIDI Faders
These are covered in the section on MIDI, but basi-
cally, these two settings (MIDI Controllers and MIDI  
						

							9 - Machine Control—Notes on individual devices
9–9
Faders) allow the PODs and MASTER layer faders 
respectively to send MIDI Control Change messages 
to MIDI devices connected to the TM-D4000.
9.4.6 JLC BB3
The J. L. Cooper BB3 transport controller can be 
connected to the MIDI IN of the TM-D4000 and 
used to duplicate the transport keys of the console 
(i.e. pressing the keys of the BB3 will control the 
external unit currently selected for transport control 
in the Machine Control List). As well as MMC com-
mands, the BB3 also transmits MIDI Note On and 
Note Off information for notes 21 through 25 on 
channel 16 (fixed).
To avoid confusion, therefore, the TM-D4000 will 
not map these notes on channel 16 to the transport 
keys, unless the BB3 is added to the list of external 
devices from the Supported Devices list.
9.4.7 MMC devices
There are two MMC control methods: the first being 
a closed-loop (
MMC closed) where the con-trolled device is sending information back from itself 
using the MIDI connections, providing an informa-
tion feedback cycle. Connections should be made 
from the 
MIDI OUT of the TM-D4000 to the MIDI 
IN of the controlled unit, and from the MIDI OUT 
of the controlled unit to the 
MIDI IN of the TM-
D4000, allowing two-way communication.
The second is an open system (
MMC open), 
which is closer to a “command and forget” system. 
No feedback is provided from the controlled device, 
and the connection is a one-way connection; from the 
MIDI OUT of the TM-D4000 to the MIDI IN of the 
controlled unit.
9.4.8 Cascade slave
This allows control of a slave cascade unit’s transport 
keys from a master cascade unit. For details of this 
facility, see 11, “Cascade”.
Any unit which is connected for transport control to a 
cascade slave will then behave as if the slave’s own 
transport keys have been pressed to control it. 
						

							 
 
 
10–1
 
10 - MIDI
 
The TM-D4000 is capable of acting as a MIDI con-
troller as well as responding to Program Change 
commands. Each Program Change command corre-
sponds to a snapshot which is recalled.
MIDI Timecode (MTC) can be used as the timecode 
base, and displayed on the time counter.
Library data may be stored to a MIDI bulk ling 
device using MIDI System Exclusive, and recalled. 
This includes EQ data, effect and dynamics proces-
sor data, as well as snapshot library entries. These 
procedures are described in 8.1.6,  “MIDI dumping 
and loading of snapshot library entries ” and 8.2.5, 
“Naming a library entry ”. See these sections for 
details of this facility.
Other parameters may also be stored and recalled by 
means of MIDI System Exclusive dump commands, 
and these are explained below.
The TM-D4000 controls can be used to send MIDI 
Control Change commands through the MIDI OUT, 
as described here, using one of two methods: the 
MIDI Controller and the MIDI Fader  “external 
devices ”, selected from the Machine Control List.
All MIDI connections to and from the TM-D4000 
are made in the standard way, using standard MIDI 
connectors: the 
 
MIDI IN
 
 accepts MIDI data, the 
 
MIDI 
THRU
 
 echoes these commands, and the 
 
MIDI OUT
 
 
outputs those MIDI commands that originate from 
the TM-D4000 (there is a soft  “through ” described 
below).
 
10.1MIDI settings
 
The following settings affect the operation of the 
TM-D4000 with regard to MIDI:
 
Basic Channel : 
 
This sets the channel on which 
the TM-D4000 receives Program Change messages, 
etc. Use the 
 
JOG
 
 dial or the number keypad, fol-
lowed by the 
 
ENTER
 
 key, to enter the MIDI channel 
from 1 to 16.
 
OMNI Receive : 
 
The setting made above can be 
overridden, so that the TM-D4000 will respond to 
MIDI messages received on any channel (see the 
note below regarding the JLC BB3).
In addition to this setting, the Omni Off (B
 
n
 
 7C) and 
Omni On (B
 
n
 
 7D) where 
 
n
 
 is the basic MIDI chan-
nel) messages are also recognized and interpreted by 
the TM-D4000.
 
RESET : 
 
If a MIDI Reset messages is received by 
the TM-D4000, there are three options: the TM-
D4000 will 
 
Ignore
 
 this message (it will be dis-
carded, and not used), the 
 
Prompt User
 
 set-
ting will produce a popup message when a Reset 
message is received, allowing the choice of whether 
the console should be reset or not, and Honor will 
always reset the console when a 
 
Reset
 
 message 
is received.
 
Output Active Sensing : 
 
enables or disables 
the reception of System Real Time Active Sensing 
messages (FEh) by the TM-D4000. If Active Sensing 
is enabled, and the data stream is interrupted, a 
popup panel appears on the display to inform you of 
the fact.
 
Output MTC when slaved : 
 
When this is 
turned on, the TM-D4000 will output MIDI Time-
code from the 
 
MIDI OUT
 
, echoing the current time-
code source (as selected in the 
 
OPTION
 
 screen). 
If the internal generator is running (as selected by the 
Machine Control screens), MTC is always output, 
regardless of the setting made here.
 
Merge In 
 
®  
 
Out : 
 
This allows the 
 
MIDI OUT
 
 to 
echo the data received at the 
 
MIDI IN
 
, merged with 
the data originated by the TM-D4000. Regardless of 
this setting, the 
 
MIDI THRU
 
 will only re-transmit the 
data received at the 
 
MIDI IN
 
.
Received MTC (including full frame MTC mes-
sages) is not merged into the 
 
MIDI OUT
 
.
 
NOTE
 
When a valid dump header is received, merg-
ing of MIDI data is turned off until the next 
power-up. The TM-D4000 supports the MIDI 
FILE DUMP, as specied in the MIDI 1.0 
specications, and because of the handshak- 
						

							 
10 - MIDI—MIDI data dumps
 
10 –2 
 
ing between the units, data merging is turned 
 
off here. 
 
10.2MIDI data dumps
 
As well as the library entries, as described in the 
Library section, it is also possible to save and restore 
the following parameters:
•Program Change Tables (see 10.3,  “Program 
Change commands ” below)
•Setup Data (the preferences settings, etc.)
•All data (including library settings, etc.)
The automation communication speed should be set 
to 
 
MIDI
 
 (use the 
 
AUTOMATION SET UP
 
 key —
shifted 
 
DIGITAL I/O
 
 to edit the automation setup 
screen) for MIDI bulk transmission and reception. If 
it is not set when the MIDI bulk dump screen is 
started, a popup message appears to remind you.
The method for saving and restoring this data is the 
same as for library entries.
 
1
 
Use the cursor and 
 
ENTER
 
 keys to select the 
checkboxes corresponding to the data set to 
be backed up or restored.
 
2
 
To dump the data, make any preparations on 
the receiving device so that the bulk dump 
data can be received successfully.
 
3
 
Move the cursor to the 
 
BULK DUMP
 
 but-
ton, and press 
 
ENTER
 
 to start the bulk dump. 
 
10.2.1Receiving bulk data
 
1
 
Start the bulk transmission on the MIDI data 
ling device.
 
2
 
The bulk data is automatically received by 
the TM-D4000.
 
10.2.2Transferring data between two TM-
D4000 units
 
1
 
Connect the two units so that the 
 
MIDI OUT
 
 
of each unit one is connected to the 
 
MIDI IN
 
 of 
the other.
 
2
 
The automation communication speed of the 
receiving unit should be set to 
 
MIDI
 
 (use 
the 
 
AUTOMATION SET UP
 
 key — shifted 
 
DIGITAL I/O
 
 to edit the automation setup 
screen).
         
NOTE
 
It is strongly advised that the TM-D4000 con-
trols are not moved during a dump process, 
either in or out), as this may affect the suc-
cessful trasnmission of data. Also note that 
after a dump transmission, if the faders have 
accidentally been moved during the transmis-
sion, they will return to their original (pre-
dump) position as soon as the dump is 
 
ended.
 
10.3Program Change commands
 
The TM-D4000 can hold four different tables of Pro-
gram Changes, only one of which may be active at a 
time.
These tables are  “mappings ” of Program Change 
numbers to snapshot numbers, meaning that a partic-
ular Program Change number is used to change to a 
particular snapshot memory setting. Because the Pro-
gram Change number does not necessarily corre-
spond to the snapshot number, it is possible for the 
TM-D4000 to share a MIDI channel with another 
MIDI device which is also to change programs 
together with the TM-D4000 (e.g. a MIDI-controlled 
external effect unit).
    
These Program Change messages can be sent at the 
beginning of a sequence, or part of the way through, 
to synchronize the settings with the input material. 
Alternatively, a MIDI controller can be used to trans-
mit the Program Change messages  “off-line ”.
3Start the bulk transmission on the first
TM-D4000.
4The bulk data is automatically received by 
the second TM-D4000. 
						

							 
10 - MIDI—MIDI controllers 
 10–3 
WARNING 
A change of snapshot may cause sudden 
changes in level which, if you are not pre-
pared for them, may result in damage to mon-
itoring equipment. Be aware of these possible 
level changes when making snapshot  
changes. 
10.3.1Setting the Program Change tables 
1 
Use the  
MIDI/MC SETUP 
 screen. The  
PROG. CHANGE TABLE 
 section is 
at the bottom left: 
2 
Move the cursor to select one of the four 
banks, and press  
ENTER 
. 
3 
Use the JOG dial to scroll through the 128 
Program Change numbers ( 
000 
 through  
127 
). 
4 
When the Program Change number to be 
edited is highlighted, use the numeric keypad 
to enter the value of the snapshot to be asso-
ciated with the highlighted Program Change 
number (snapshot numbers less than 10 
should be prefixed by a zero). 
5 
Use the JOG dial and numeric keypad until 
you havce entered all the Program Change 
number/snapshot assignments you want to 
use into the current bank. 
6 
Use the cursor keys to select another bank, if 
necessary. 
10.4 MIDI controllers 
One of the remote “devices” which may be set up in 
the  
MIDI/MC 
  
MACHINE CTRL  
screen (see 9.1, “Selecting devices for control”) is the  
MIDI Controllers 
 “device”.
This allows the PODs of the TM-D4000 to be used as 
a bank of continuous controllers, sending Control 
Change messages to an external MIDI device.
The “ID” set in the  
MACHINE CTRL
 screen 
corresponds to the MIDI channel of the device to be 
controlled.
The names of the controllers correspond to the stan-
dard MIDI controller names. Some of these controls 
are off/off controls, although the POD continuous 
controls are used to make these settings.
The Program Change POD (left POD, second row) is 
not, of course, a Control Change message. Instead, 
turning the knob changes the value of the Program 
Change number. If the left switch of this POD is used 
to turn the button 
ON, the Program Change message 
is sent as the knob is turned. If the the button is 
turned 
OFF, the Program Change message corre-
sponding to the current position of the knob will only 
sent when the button is turned 
ON.
The official MIDI specification defines the names of 
these controllers as follows:
Controller nameNumber 
(decimal)Number 
(hex)
MODULATION101
BREATH202
FOOT404
EXPRESSION11 0B
CH. VOL707
BALANCE808
PAN10 0A
EFF CTRL 112 0C
EFF CTRL 213 0D
SUSTAIN64 40
SOFT67 43
GPC116 10 
						

							10 - MIDI—MIDI Faders
10–4 
10.5 MIDI Faders
Another “device” which may be selected for external 
control from the 
Machine Ctrl screen is 
the 
MIDI Faders “device”.
Here, the “Device ID” is a two-digit hexadecimal 
number, corresponding to a Controller, as defined by 
the MIDI Specification.
When the external control screen for the MIDI Fad-
ers “device” is displayed, as in the example above, 
each of the channel faders in the Master fader layer is 
then used to set the Controller value.
Note that the TM-D4000 is constantly monitoring the 
controller status of the controllers on all 16 channels, 
so that when the Master faders are selected as the 
controls for a particular MIDI Controller, they will 
move to match the current values in the MIDI setup.
The fader numbers (1 through 16) correspond to the 
16 MIDI channels. In the example above, since the 
“ID” of the “device” has been set to 07, i.e. Channel 
Volume, the sixteen channel faders in the master 
layer are used as volume controls. Of course, any 
continuous controller may be selected as the “device 
ID”, allowing the TM-D4000 to be used as a conve-
nient general-purpose controller for a MIDI setup.
The TM-D4000 recognizes and interprets the Reset 
All Controllers message (Bn 79, where n is the basic 
MIDI channel).The parameters of the internal Control Change map 
are reset to:
This message only has any real meaning when the 
MIDI Faders are being used.
10.6 Sequenced mixing
It is not possible to use a MIDI sequencer to auto-
mate the TM-D4000, other than by sending Program 
Change messages to change snapshots. Use the TAS-
CAM Automation Software for realtime control of 
the TM-D4000.
10.7 MIDI System Exclusive data 
formats
Some of the System Exclusive formats data formats 
used by the TM-D4000 are as follows. However, 
there are many other System Exclusive messages 
sent and received by the TM-D4000. If you wish to 
know the details of these messages, please contact 
your TASCAM Service Center. The more common 
messages are listed below:
10.7.1Device Inquiry
When the following inquiry is received,
the TM-D4000 responds with:
GPC217 11
GPC318 12
GPC419 13
PORTO TIME505
PORTO CTRL84 54
NON REG (MSB)99 63
REG (MSB)101 65
Controller nameNumber 
(decimal)Number 
(hex)
Channel volume 100
Balance 64
Pan 64
Expression 127
All others 0
Value 
(hexadeximal)Meaning
F0h Status byte
7E
device ID  01h–7Fh (7Fh = broadcast)
06
01
F7h EOX
Value 
(hexadeximal)Meaning
F0h Status byte
7E Inquiry
device ID  00h–7Eh (7F = broadcast)
06
02
4E
07 
						

							10 - MIDI—Updating the system software
 10–5
10.7.2Master Volume
The TM-D4000 responds to the following Master 
Volume System Exclusive command.
10.7.3Other System Exclusive messages
As well as the System Exclusive messages described 
above, the TM-D4000 uses the following:
• Device Inquiry messages are sent by the TM-
D4000 when the auto detect operation (described 
in 9.1.2, “Auto-detection of devices”) is taking 
place, to discover what devices are connected using 
MIDI. Any devices which are capable of control by 
the TM-D4000 are added to the list.
• When MTC is selected as the timecode source, the 
TM-D4000 will receive and display MTC Full 
Frame messages.
• MTC Full Frame messages may be transmitted by 
the TM-D4000.
• When the TM-D4000 is emulating a CS-10 con-
troller, it will respond to System Exclusive mes-
sages for this J. L. Cooper product. Consult the CS-
10 documentation for details of these messages.
• When the TM-D4000 is acting as a controller for 
some of the devices in the controlled devices list, 
the messages sent out may be System Exclusive 
messages which are not mentioned explicitly 
above.
• Again, when acting as a controller for some of the 
devices in the list, the TM-D4000 may output 
MIDI messages such as aftertouch, Program Change, etc. which are not listed here, and are used 
specifically for the control of those devices.
10.8 Updating the system software
The system software of the TM-D4000 can be 
upgraded without the need for special equipment or 
personnel.
As upgrades are released (your TASCAM distributor 
will inform you of their availability), you can add 
new features to the TM-D4000, including the ability 
to control other devices using the Machine Control 
screens of the TM-D4000.
Only transfer files for system update which have 
been prepared by TASCAM using the method 
described here.
10.8.1Viewing the current version 
number
To view the version number of the software currently 
installed on the TM-D4000:
1Press the OPTION key until the SETUP 
screen is shown.
2Press the DIRECT key (to the right of and 
below the display screen):
10.8.2Equipment needed
To upgrade your TM-D4000, you will need the fol-
lowing:
• A MIDI cable.
• A program on your computer that allows you to 
play MIDI files, together with a MIDI interface.
10.8.3Connections
There is only one connection you need to make.
01
00
02
p1 panel firmware version (1st byte)
p2 panel firmware version (2nd byte)
m1 main firmware version (1st byte)
m2 main firmware version (2nd byte)
F7h EOX
Value 
(hexadeximal)Meaning
F0h Status byte
7E
device ID  00h–7Eh (7F = broadcast)
04
01
xx Volume, between 00 and 127)
F7
Value 
(hexadeximal)Meaning 
						

							10 - MIDI—MIDI Implementation Chart
10 –6 
1)Connect the MIDI OUT of your MIDI 
interface or sequencer to the MIDI IN of the 
TM-D4000.
10.8.4Preparing to upgrade
Upgrading the system software will not lose any 
data, so there is no need to take any special precau-
tions when upgrading.
1)If you have been running the TM-D4000 
automation software and you intend to use the 
computer which runs the automation 
software to perform the upgrade, quit the 
automation software.
Macintosh and MacOS users should enable 
the MIDI interface system Extension if it has 
been disabled, and restart the computer if 
necessary.
2)Open the le containing the upgrade le with 
your MIDI sequencer.
If you are using a dedicated MIDI sequencer, 
you should transfer the le to the sequencer 
from your computer using an appropriately-
formatted oppy disk.
10.8.5Upgrading
1)Start playing the MIDI le (as if it was a 
sequence le).
The MIDI data will start to be transferred to 
the TM-D4000. 
2)The display of the TM-D4000 will change to 
show the number of received data blocks.
3)When the data has been transferred, the TM-
D4000 will update its ROM memory and reset 
itself.
WARNING
Do not turn off the power or interrupt the TM-
D4000 ’s updating process while the following 
message is displayed on the TM-D4000 dis-
play screen:
Updating ROMs, please wait
This message will appear as a blinking mes-
sage for between 20 and 40 seconds after 
“playback ” has nished.
10.8.6Notes on the upgrade process
The update process will take some time. The main 
portion of the system software will take about 15 
minutes to transfer, the panel software will take 
about 13 minutes, and the remote modules portion of 
the system software will take about ve minutes.
If the transfer is interrupted part of the way through 
(for instance, the power is cut to the TM-D4000), 
when the TM-D4000 is next turned on, a message 
will appear on the display screen, asking you to make 
the transfer again.
As noted, you should not interrupt the update process 
after the transfer of data has ended, and the TM-
D4000 is updating its ROM memory.
10.8.7A note on using sequencer 
programs
If the computer mouse is moved while the upgrade is 
under way, there may be problems with the update 
process. Some computer software is particularly sus-
ceptible to input from the keyboard or mouse while 
“heavy-duty ” background processes, such as bulk 
transfer of MIDI data, are going on
These difculties may include the corruption of the 
system software, making it impossible to re-start the 
TM-D4000 and necessitating a change to the ash 
ROMs by service personnel.
For this reason, once you have started the  “playback ” 
of the upgrade software to the TM-D4000, we 
strongly recommend that you should not touch the 
computer or any peripherals until the uploading pro-
cess is complete, as shown on the TM-D4000 
display. 
						

							 
  
11–1 
11 - Cascade 
The TM-D4000 can be linked in a cascade with to up 
to three other similar units, providing up to 128 mono 
channels of input, together with eight stereo inputs.
The stereo outputs of all cascaded console are 
summed. The eight output busses and the first four 
Aux sends may also be summed, turning the chain of 
TM-D4000 units into a modular, flexible recording 
console. Note that Aux sends 5 and 6 are excluded 
from the cascade, and hence can be used locally, with 
the built-in effect processor of each cascaded unit—
this provides more flexibility in effect processing.
In the cascade, one unit is designated as the master 
unit. All aux sends and busses that are being summed 
are passed through to this master unit and are output 
from the appropriate connectors on the master.
In addition, a summed output buss is always echoed 
locally at the outputs of all consoles contributing to 
the summed buss (this allows more than three MDM 
units to be controlled by a cascade of TM-D4000s).
Individual busses and aux sends may be excluded 
from the cascade summing, so that they are local to 
the unit.
In addition to the signal summing described above, 
the cascade function also links the following func-
tions of the cascaded units:
• soloing, for both IPS and PFL (5.4, “SOLO”)
• snapshot store and recall (8.1, “Snapshot memo-
ries”)
• option settings (3.3, “Option setup”)
• automation setup (automation documentation)
• automation mode (automation documentation) 
11.1 Cascade connections 
As always, connections should be made with the 
power to the units turned off.  
WARNING  
Only use the special TASCAM-supplied 
cables (PW-4000CS) to make cascade con-
nections. Although computer cables may 
appear similar, and may even be wired identi-
cally, the cables themselves have different 
electrical characteristics, and damage may be 
caused to the units if the wrong cables are 
used.If the use of cables other than these TASCAM 
cables causes or results in damage, the war- 
ranty is voided. 
Slave units are numbered from 1 through 3. This 
numbering is carried out as carried out below.
A cascade of TM-D4000 units is a “daisy-chain”; the 
master unit should be at one end of the chain, with its  
CASCADE OUT  
connector  
[78] 
 connected to the  
CASCADE IN 
 of slave 1, whose  
CASCADE OUT 
 
connects to the  
CASCADE IN 
 of slave 2, etc. 
No termination is necessary, but all units in a cascade 
connection must be turned on and selected as being 
part of the cascade, even if they are not being used as 
part of the chain. It is not possible to have a “dead” 
unit in a chain or to have a unit in the physical cas-
cade chain which does not have the cascade function 
selected. 
1 
If your units have not yet been configured for 
use in a cascade, turn on and configure the 
units that will be slaves first, and then turn 
on and configure the unit that will act as the 
cascade master. 
2 
On the first slave unit (connected to the mas-
ter unit) use the  
DIGITAL I/O 
CASCADE 
 screen to select the  
SLAVE 
1 
 ID for this unit. 
3 
Move the cursor to the  
CASCADE ON/
OFF 
 button at the top of the screen, and 
turn the cascade on for this unit: 
4 
Repeat this procedure for all the other slaves 
in the chain, assigning the appropriate ID to 
each slave. 
5 
Finally, set the master unit’s ID to MASTER, 
and turn the cascade ON.