Vista Digital Mixing System
Date printed: 20.08.09 SW V4.1 Software V4.1 13
A.5.2 Restricting Shared I/O
Per default, all sources and targets attached to a Vista system can be seen
and used by other systems that are part of the I/O Sharing network. Access
to these I/Os may be restricted; they can then be used on the local Vista
system only, but are not available to other systems within the network.
This is done with a text file containing a list of fixed labels of the I/Os that
should be visible to others; the file must be named SharedPatches.iosharing
and saved in the folder of the VMC configuration which it is valid for, such
as D950SystemDB\Config1.
SharedPatches.iosharing Example: ...
I 17 B 1 Ch17
I 18 B 1 Ch18
I 19 B 1 Ch19
I 20 B 1 Ch20
I 21 B 1 Ch21
I 22 B 1 Ch22
I 23 B 1 Ch23
I 24 B 1 Ch24
...
Notes: The I/O configured as tie lines must also be added in this file.
If no file with this name is found in a configuration folder, all I/Os of this
Vista system will be available for networked access.
A.5.3 Configuration Changes
Every VMC configuration change in a Vista console has an effect on the
other consoles using this Vista’s I/O at the same time. This means that an
I/O can disappear and then reappear in a different constellation.
When using a file named CommonSharedPatches.iosharing located in the
D950SystemDB folder, a number of sources and targets can be defined as
I/O that must not change. This is useful for inputs or outputs that remain
the same throughout all VMC configurations on the Vista. It contains a list
of the fixed labels of the desired I/O.
CommonSharedPatches.iosharing Example:
...
I 65 B 1 Ch65
I 66 B 1 Ch66
I 67 B 1 Ch67
I 68 B 1 Ch68
I 69 B 1 Ch69
I 70 B 1 Ch70
I 71 B 1 Ch71
I 72 B 1 Ch72
...
This file needs to be created manually. If no file with this name is found in
a configuration folder, all I/O will be reinitialized by a configuration
change.
To Next Page
Loading...
