Biamp Tesira Configuration - Revision history

IVSWikiBlue at 21:30, 24 March 2025

2025-03-24T21:30:02Z

← Older revision		Revision as of 21:30, 24 March 2025
Line 1:		Line 1:
	== Note about AVB ==		{{Article - Manual \| content =
			<h1>Note about AVB</h1>
	If we are installing one TesiraForte server, and ONLY one remote expander OR a TCM1-A microphone, (and any number of analog mics and speakers) there is no need for an AVB Extreme switch. If that’s the case, the expander/beamtracking mic will be plugged into the AVB port on the Tesira. Any config with more than a 1:1 ratio of remote devices to Forte servers will require the use of the Extreme switch. It also means we must enable AVB on the Tesira Forte in the device settings.		If we are installing one TesiraForte server, and ONLY one remote expander OR a TCM1-A microphone, (and any number of analog mics and speakers) there is no need for an AVB Extreme switch. If that’s the case, the expander/beamtracking mic will be plugged into the AVB port on the Tesira. Any config with more than a 1:1 ratio of remote devices to Forte servers will require the use of the Extreme switch. It also means we must enable AVB on the Tesira Forte in the device settings.

			{{hr}}

	== Before Arriving On Site ==		== Before Arriving On Site ==
Line 6:		Line 9:

	Build a Biamp Software Configuration for the job. If possible, test it out in-house with the devices being used, before they are shipped to the customer. This will allow us to give it a live test run, as well as assign the software to the hardware macs before we arrive to install.		Build a Biamp Software Configuration for the job. If possible, test it out in-house with the devices being used, before they are shipped to the customer. This will allow us to give it a live test run, as well as assign the software to the hardware macs before we arrive to install.

			{{hr}}

	= Creating a Software Audio Solution =		= Creating a Software Audio Solution =
Line 11:		Line 16:
	== AVB Switch ==		== AVB Switch ==
	The Extreme switch needs a license, and needs to have AVB enabled. If this isn't done before being shipped, we will need to get IVS Support to complete. Either a laptop with a serial port or a serial-to-usb adapter will be required. Plug into the Console port on the Extreme switch to perform this task.		The Extreme switch needs a license, and needs to have AVB enabled. If this isn't done before being shipped, we will need to get IVS Support to complete. Either a laptop with a serial port or a serial-to-usb adapter will be required. Plug into the Console port on the Extreme switch to perform this task.

			{{hr}}

	== On-site Configuration ==		== On-site Configuration ==
Line 16:		Line 23:
	:# '''If it’s a standalone solution with an Extreme switch''': Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.		:# '''If it’s a standalone solution with an Extreme switch''': Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.
	:# '''If we are using an Extreme switch, and they want the Tesira on their network''': The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.		:# '''If we are using an Extreme switch, and they want the Tesira on their network''': The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.

			{{hr}}

	== Software Configuration ==		== Software Configuration ==
Line 31:		Line 40:
	# Navigate back to '''Control''' in the Interface ID. Type in the IP scheme for the Control port.		# Navigate back to '''Control''' in the Interface ID. Type in the IP scheme for the Control port.
	# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under ''Allocated to Unit'', select whichever device number is our desired device. Then change ''Fixed in Unit'' to ''True''. This will keep the input/output block from getting another device assigned to it.		# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under ''Allocated to Unit'', select whichever device number is our desired device. Then change ''Fixed in Unit'' to ''True''. This will keep the input/output block from getting another device assigned to it.

			{{hr}}

	== Sending a Config to the System ==		== Sending a Config to the System ==
Line 45:		Line 56:
	# Remember- if the mics need phantom power, we must activate it on the input block for each channel.		# Remember- if the mics need phantom power, we must activate it on the input block for each channel.
	# The input block is also where the gain is set on the preamp. Depending on what mics we are using, and how far they are physically placed from the subjects in the environment, it's not uncommon to see the preamps at 36-42 dB on the input blocks. With a subject in the main pickup area speaking at an average but strong level, the peak meter should be reaching into the yellow section, but definitely not reaching into the red.		# The input block is also where the gain is set on the preamp. Depending on what mics we are using, and how far they are physically placed from the subjects in the environment, it's not uncommon to see the preamps at 36-42 dB on the input blocks. With a subject in the main pickup area speaking at an average but strong level, the peak meter should be reaching into the yellow section, but definitely not reaching into the red.
			}}

			[[Category:Audio]]

IVSWikiBlue: /* Note about AVB */

2020-04-02T22:03:31Z

Note about AVB

← Older revision		Revision as of 22:03, 2 April 2020
Line 1:		Line 1:
	== Note about AVB ==		== Note about AVB ==
	If we are installing one TesiraForte server, and ONLY one remote expander OR a TCM1-A microphone, (and any number of analog mics and speakers) there is no need for an AVB Extreme switch. If that’s the case, the expander/beamtracking mic will be plugged into the AVB port on the Tesira. Any config with more than a 1:1 ratio of remote devices to Forte servers will require the use of the Extreme switch.		If we are installing one TesiraForte server, and ONLY one remote expander OR a TCM1-A microphone, (and any number of analog mics and speakers) there is no need for an AVB Extreme switch. If that’s the case, the expander/beamtracking mic will be plugged into the AVB port on the Tesira. Any config with more than a 1:1 ratio of remote devices to Forte servers will require the use of the Extreme switch. It also means we must enable AVB on the Tesira Forte in the device settings.

	== Before Arriving On Site ==		== Before Arriving On Site ==

IVSWikiBlue at 16:07, 7 May 2019

2019-05-07T16:07:17Z

IVSWikiBlue: /* Sending a Config to the System */

2019-04-26T16:49:54Z

Sending a Config to the System

← Older revision		Revision as of 16:49, 26 April 2019
Line 33:		Line 33:

	== Sending a Config to the System ==		== Sending a Config to the System ==
	# The Tesira comes with a default config file loaded. Before we send our config to the device, we need to ~~clear this first~~. Go to Device Maintenance, select our TesiraForte, and click Clear Configuration. Now the Forte is "blank", as it were.		# The Tesira comes with a default config file loaded. Before we send our config to the device, the config file will first need to be cleared. Go to '''Device Maintenance''', select our TesiraForte, and click '''Clear Configuration'''. Now the Forte is ''blank'', as it were.
	# Go to System > Compilation > Compile Active Partition to make sure all paths are connected properly.		# Go to System > Compilation > Compile Active Partition, and make sure all paths are connected properly.
	# Go to System > Network > Send Configuration.		# Go to System > Network > Send Configuration.
	# It will ask us to name the config; ~~let’s~~ give it a name that makes sense.		# It will ask us to name the config; give it a name that makes sense.
	# Start System Audio: Yes.		# Start System Audio: '''Yes'''.
	# Start All. Close.		# Start All. Close.

	~~Now we~~ have a working Tesira Configuration and are live!		We now have a working Tesira Configuration and are live!

	# Double click on our peak meters to see whether audio is passing at the input and at the output.		# Double click on our peak meters to see whether audio is passing at the input and at the output.
	# Remember- if the mics need phantom power, we must activate it on the input block for each channel.		# Remember- if the mics need phantom power, we must activate it on the input block for each channel.
	# The input block is also where the gain is set on the preamp. Depending on what mics we are using, and how far they are physically placed from the subjects in the environment, it's not uncommon to see the preamps at 36-42 dB on the input blocks. With a subject in the main pickup area speaking at an average but strong level, the peak meter should be reaching into the yellow section, but definitely not reaching into the red.		# The input block is also where the gain is set on the preamp. Depending on what mics we are using, and how far they are physically placed from the subjects in the environment, it's not uncommon to see the preamps at 36-42 dB on the input blocks. With a subject in the main pickup area speaking at an average but strong level, the peak meter should be reaching into the yellow section, but definitely not reaching into the red.

IVSWikiBlue: /* Software Configuration */

2019-04-26T16:48:28Z

Software Configuration

IVSWikiBlue: /* Software Configuration */

2019-04-26T15:54:06Z

Software Configuration

← Older revision		Revision as of 15:54, 26 April 2019
Line 18:		Line 18:

	== Software Configuration ==		== Software Configuration ==
	# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first~~, either way is fine~~. (If we open Biamp first, select “Audio Partition”, and select “both Tesira server and TesiraFORTE”).		# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first. (If we open Biamp first, select “Audio Partition”, and select “both Tesira server and TesiraFORTE”).
	# If need be, upgrade the firmware. ~~Simply Google “Tesira Forte Firmware”~~ and ~~download~~. Once finished, unpack the zip file so the firmware file is available in the ~~downloads~~ folder. In Tesira, go to Device Maintenance, select the TesiraForte, click Update Firmware, and navigate to the firmware file. '''Updating firmware takes a good hour or more.'''		# If need be, upgrade the firmware. Firmware and software downloads can be found [https://support.biamp.com/Tesira/Software-Firmware here]. Once finished, unpack the zip file so the firmware file is available in the '''Downloads''' folder. In Tesira, go to '''Device Maintenance''', select the TesiraForte, click '''Update Firmware''', and navigate to the firmware file. ''Updating firmware takes a good hour or more.''
	# ~~Still~~ on Device Maintenance, click Remote Devices. Click on each ~~one~~ and update their firmware too. '''(Takes 10+ minutes each).'''		# While still on Device Maintenance, click '''Remote Devices'''. Click on each device and update their firmware too. ''Takes 10+ minutes each.''
	# Head to the Equipment Table (under System~~; or it’s~~ the little table icon, with 3 bullets and 3 lines).		# Head to the Equipment Table under '''System'''. ''It can otherwise be the little table icon, with 3 bullets and 3 lines.''
	# If nothing is listed, ~~we have to add~~ lines for devices. In the fields in the middle of the Equipment Table, select ~~“Forte”~~ and ~~“Forte CI”~~ or ~~“Remote Expander”~~ and ~~“TCM~~-~~1A”~~ or whichever device, then click ADD.		# If nothing is listed, lines for devices will need to be added. In the fields in the middle of the Equipment Table, select '''Forte''' and '''Forte CI''' or '''Remote Expander''', and '''TCM-1A''' or whichever device, and then click '''ADD'''.
	# Click on the Tesira server, make sure our server is selected under Host Name. (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server and it will scroll the serial number briefly.)		# Click on the Tesira server, and make sure our server is selected under '''Host Name'''. (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server and it will scroll the serial number briefly.)
	# Click on the expanders/mics, select one serial number for each device in the Host Name, and select the Tesira server for the Proxy Host Name. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.		# Click on the expanders/mics, select one serial number for each device in the Host Name, and select the Tesira server for the Proxy Host Name. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.
	# Go to Device Maintenance. Then click Remote Devices.		# Go to Device Maintenance. Then click Remote Devices.
Line 30:		Line 30:
	# In the Interface ID field, click onto the Media AVB. Click the “Enabled” box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.		# In the Interface ID field, click onto the Media AVB. Click the “Enabled” box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.
	# Switch back to Control in the Interface ID. Type in the IP scheme for the Control port.		# Switch back to Control in the Interface ID. Type in the IP scheme for the Control port.
	# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under “Allocated to Unit” select whichever device number is our desired device. Then change “Fixed in Unit” to “True”. This will keep the input/output block from getting another device assigned to it.		# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under “Allocated to Unit” select whichever device number is our desired device. Then change “Fixed in Unit” to “True”. This will keep the input/output block from getting another device assigned to it.

	== Sending a Config to the System ==		== Sending a Config to the System ==

IVSWikiBlue: /* On-site Configuration */

2019-04-26T15:26:46Z

On-site Configuration

← Older revision		Revision as of 15:26, 26 April 2019
Line 14:		Line 14:
	== On-site Configuration ==		== On-site Configuration ==
	Physical Installation:		Physical Installation:
	:# If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.		:# '''If it’s a standalone solution with an Extreme switch''': Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.
	:# If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.		:# '''If we are using an Extreme switch, and they want the Tesira on their network''': The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.

	== Software Configuration ==		== Software Configuration ==

IVSWikiBlue: /* On-site Configuration */

2019-04-26T15:26:27Z

On-site Configuration

← Older revision		Revision as of 15:26, 26 April 2019
Line 14:		Line 14:
	== On-site Configuration ==		== On-site Configuration ==
	Physical Installation:		Physical Installation:
	## If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.		:# If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.
	## If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.		:# If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.

	== Software Configuration ==		== Software Configuration ==

IVSWikiBlue: /* On-site Configuration */

2019-04-26T15:26:16Z

On-site Configuration

← Older revision		Revision as of 15:26, 26 April 2019
Line 13:		Line 13:

	== On-site Configuration ==		== On-site Configuration ==
	# Physical Installation:		Physical Installation:
	## If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.		## If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.
	## If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.		## If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.

IVSWikiBlue: /* On-site Configuration */

2019-04-26T15:26:05Z

On-site Configuration

← Older revision		Revision as of 15:26, 26 April 2019
Line 14:		Line 14:
	== On-site Configuration ==		== On-site Configuration ==
	# Physical Installation:		# Physical Installation:
	## (If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.)		## If it’s a standalone solution with an Extreme switch: Plug both Tesira ports into the Extreme switch, all expanders and beamtracking mics, and our laptop for configuration.
	## (If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.		## If we are using an Extreme switch, and they want the Tesira on their network: The Tesira must be able to talk to any expanders or TCM1-A mics, so the Forte server and the Extreme switch need to be plugged into their network. All the remote devices still plug into the Extreme switch, as will the AVB port on the Tesira.

	== Software Configuration ==		== Software Configuration ==

← Older revision		Revision as of 16:07, 7 May 2019
Line 5:		Line 5:
	Determine whether the client wants to access their Tesira from their network, or if it will be a standalone solution. This will change our physical cabling, as well as how we set up the network settings.		Determine whether the client wants to access their Tesira from their network, or if it will be a standalone solution. This will change our physical cabling, as well as how we set up the network settings.

	Build a Biamp Software Configuration for the job. If possible, test it out in-house with the devices before they are shipped to the customer. This will allow us to give it a live test run, as well as assign the software to the hardware macs before we arrive to install.		Build a Biamp Software Configuration for the job. If possible, test it out in-house with the devices being used, before they are shipped to the customer. This will allow us to give it a live test run, as well as assign the software to the hardware macs before we arrive to install.

	= Creating a Software Audio Solution =		= Creating a Software Audio Solution =

	== AVB Switch ==		== AVB Switch ==
	The Extreme switch needs a license and needs to have AVB enabled. If this isn't done before being shipped, we will need to get IVS ~~support~~ to complete. Either a laptop with a serial port or a serial-to-usb adapter will be required. Plug into the Console port on the Extreme switch to perform this task.		The Extreme switch needs a license, and needs to have AVB enabled. If this isn't done before being shipped, we will need to get IVS Support to complete. Either a laptop with a serial port or a serial-to-usb adapter will be required. Plug into the Console port on the Extreme switch to perform this task.

	== On-site Configuration ==		== On-site Configuration ==
Line 19:		Line 19:
	== Software Configuration ==		== Software Configuration ==
	# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first. (If we open Biamp first, select ''Audio Partition'', and select ''both Tesira server and TesiraFORTE'').		# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first. (If we open Biamp first, select ''Audio Partition'', and select ''both Tesira server and TesiraFORTE'').
	# If need be, upgrade the firmware. Firmware and software downloads can be found [https://support.biamp.com/Tesira/Software-Firmware here]. Once finished, unpack the zip file so the firmware file is available in the '''Downloads''' folder. In Tesira, go to '''Device Maintenance''', select the TesiraForte, click '''Update Firmware''', and navigate to the firmware file. ''Updating firmware takes a good hour or more.''		# If need be, upgrade the firmware. Firmware and software downloads can be found [https://support.biamp.com/Tesira/Software-Firmware here]. Once finished, unpack the zip file, so the firmware file is available in the '''Downloads''' folder. In Tesira, go to '''Device Maintenance''', select the TesiraForte, click '''Update Firmware''', and navigate to the firmware file. ''Updating firmware takes a good hour or more.''
	# While still on Device Maintenance, click '''Remote Devices'''. Click on each device and update their firmware too. ''Takes 10+ minutes each.''		# While still on Device Maintenance, click '''Remote Devices'''. Click on each device and update their firmware too. ''Takes 10+ minutes each.''
	# Head to the Equipment Table under '''System'''. ''It can otherwise be the little table icon, with 3 bullets and 3 lines.''		# Head to the Equipment Table under '''System'''. ''It can otherwise be the little table icon, with 3 bullets and 3 lines.''
	# If nothing is listed, lines for devices will need to be added. In the fields in the middle of the Equipment Table, select '''Forte''' and '''Forte CI''' or '''Remote Expander''', and '''TCM-1A''' or whichever device, and then click '''ADD'''.		# If nothing is listed, lines for devices will need to be added. In the fields in the middle of the Equipment Table, select '''Forte''' and '''Forte CI''', or '''Remote Expander''', and '''TCM-1A''' or whichever device, and then click '''ADD'''.
	# Click on the Tesira server, and make sure our server is selected under '''Host Name'''. (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server and it will scroll the serial number briefly.)		# Click on the Tesira server, and make sure our server is selected under '''Host Name''' (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server, and it will scroll the serial number briefly.).
	# Click on the expanders/mics, select one serial number for each device in the '''Host Name''', and select the Tesira server for the '''Proxy Host Name'''. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.		# Click on the expanders/mics, select one serial number for each device in the '''Host Name''', and select the Tesira server for the '''Proxy Host Name'''. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.
	# Go to '''Device Maintenance'''~~. Then click~~ '''Remote Devices'''.		# Go to '''Device Maintenance''', followed by clicking '''Remote Devices'''.
	# If it’s helpful we may want to give each expander a description, such as ''Room 2200, Camera 1 and 2''. (The same is true for the servers. If we have more than one, such as ''Tesira for Sim Room'' or ''Tesira for Observation Rooms'', that will be on the main ''Device Maintenance'' page.) We can also give the remote expander's IP addresses here. The expanders MUST be done first, before changing the IP of the Tesira.		# If it’s helpful, we may want to give each expander a description, such as ''Room 2200, Camera 1 and 2''. (The same is true for the servers. If we have more than one, such as ''Tesira for Sim Room'' or ''Tesira for Observation Rooms'', that will be on the main ''Device Maintenance'' page.) We can also give the remote expander's IP addresses here. The expanders MUST be done first, before changing the IP of the Tesira.
	# Navigate back to the '''Device Maintenance''' page. Click '''Network Settings'''. We’ll need 2 IP addresses for our Tesira; one for Control and one for AVB.		# Navigate back to the '''Device Maintenance''' page. Click '''Network Settings'''. We’ll need 2 IP addresses for our Tesira; one for Control and one for AVB.
	# In the '''Interface ID''' field, click onto the '''Media AVB''', followed by selecting the '''Enabled''' box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.		# In the '''Interface ID''' field, click onto the '''Media AVB''', followed by selecting the '''Enabled''' box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.

← Older revision		Revision as of 16:48, 26 April 2019
Line 18:		Line 18:

	== Software Configuration ==		== Software Configuration ==
	# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first. (If we open Biamp first, select ~~“Audio Partition”~~, and select ~~“both~~ Tesira server and ~~TesiraFORTE”~~).		# Once physically connected, either double click on the config file first (if we did indeed build it ahead of time), or open Biamp software first. (If we open Biamp first, select ''Audio Partition'', and select ''both Tesira server and TesiraFORTE'').
	# If need be, upgrade the firmware. Firmware and software downloads can be found [https://support.biamp.com/Tesira/Software-Firmware here]. Once finished, unpack the zip file so the firmware file is available in the '''Downloads''' folder. In Tesira, go to '''Device Maintenance''', select the TesiraForte, click '''Update Firmware''', and navigate to the firmware file. ''Updating firmware takes a good hour or more.''		# If need be, upgrade the firmware. Firmware and software downloads can be found [https://support.biamp.com/Tesira/Software-Firmware here]. Once finished, unpack the zip file so the firmware file is available in the '''Downloads''' folder. In Tesira, go to '''Device Maintenance''', select the TesiraForte, click '''Update Firmware''', and navigate to the firmware file. ''Updating firmware takes a good hour or more.''
	# While still on Device Maintenance, click '''Remote Devices'''. Click on each device and update their firmware too. ''Takes 10+ minutes each.''		# While still on Device Maintenance, click '''Remote Devices'''. Click on each device and update their firmware too. ''Takes 10+ minutes each.''
Line 24:		Line 24:
	# If nothing is listed, lines for devices will need to be added. In the fields in the middle of the Equipment Table, select '''Forte''' and '''Forte CI''' or '''Remote Expander''', and '''TCM-1A''' or whichever device, and then click '''ADD'''.		# If nothing is listed, lines for devices will need to be added. In the fields in the middle of the Equipment Table, select '''Forte''' and '''Forte CI''' or '''Remote Expander''', and '''TCM-1A''' or whichever device, and then click '''ADD'''.
	# Click on the Tesira server, and make sure our server is selected under '''Host Name'''. (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server and it will scroll the serial number briefly.)		# Click on the Tesira server, and make sure our server is selected under '''Host Name'''. (If we have multiple servers, we can decide where each device is listed. I’d recommend whichever device is physically installed above the other is first in the list, just for our peace of mind. If we need to, press the large button on the front of the Tesira server and it will scroll the serial number briefly.)
	# Click on the expanders/mics, select one serial number for each device in the Host Name, and select the Tesira server for the Proxy Host Name. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.		# Click on the expanders/mics, select one serial number for each device in the '''Host Name''', and select the Tesira server for the '''Proxy Host Name'''. (This will tell them all to receive their instructions from the Tesira). Make note of how the devices are numbered in here.
	# Go to Device Maintenance. Then click Remote Devices.		# Go to '''Device Maintenance'''. Then click '''Remote Devices'''.
	# If it’s helpful we may want to give each expander a description, such as ~~“Room~~ 2200, ~~camera~~ 1 and 2”. (The same is true for the servers~~, if~~ we have more than one, such as ~~“Tesira~~ for Sim ~~Room”~~ or ~~“Tesira~~ for Observation ~~Rooms”~~, ~~but that’s~~ on the main Device Maintenance page.) We can also give the remote ~~expanders~~ IP addresses here. The expanders MUST be done first, before changing the IP of the Tesira.		# If it’s helpful we may want to give each expander a description, such as ''Room 2200, Camera 1 and 2''. (The same is true for the servers. If we have more than one, such as ''Tesira for Sim Room'' or ''Tesira for Observation Rooms'', that will be on the main ''Device Maintenance'' page.) We can also give the remote expander's IP addresses here. The expanders MUST be done first, before changing the IP of the Tesira.
	# ~~Come~~ back to the Device Maintenance page. Click Network Settings. We’ll need 2 IP addresses for our Tesira; one for Control and one for AVB.		# Navigate back to the '''Device Maintenance''' page. Click '''Network Settings'''. We’ll need 2 IP addresses for our Tesira; one for Control and one for AVB.
	# In the Interface ID field, click onto the Media AVB~~. Click~~ the ~~“Enabled”~~ box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.		# In the '''Interface ID''' field, click onto the '''Media AVB''', followed by selecting the '''Enabled''' box (only necessary if we are using remote expanders). Type in the IP scheme for the AVB port.
	# ~~Switch~~ back to Control in the Interface ID. Type in the IP scheme for the Control port.		# Navigate back to '''Control''' in the Interface ID. Type in the IP scheme for the Control port.
	# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under ~~“Allocated~~ to ~~Unit”~~ select whichever device number is our desired device. Then change ~~“Fixed~~ in ~~Unit”~~ to ~~“True”~~. This will keep the input/output block from getting another device assigned to it.		# On our input/output blocks, we’ll notice a number in the upper left-hand corner of each. Make sure they reflect the proper devices (we made note of this info in the Equipment Table). The Properties menu will display information for one block at a time; if the correct device is not assigned, look on the Properties menu; on the DSP Properties tab, under ''Allocated to Unit'', select whichever device number is our desired device. Then change ''Fixed in Unit'' to ''True''. This will keep the input/output block from getting another device assigned to it.

	== Sending a Config to the System ==		== Sending a Config to the System ==