Quote:
Originally Posted by MalcolmG
Has anyone tried spanning a TrackNavigator across two surfaces?
I have two BCF2000's setup and recognised under CSI. I can set either up like this and have the 8 faders mapped correctly:
Code:
Zone Home
IncludedZones
Channel|1-8
IncludedZonesEnd
ZoneEnd
Zone Channel|1-8
TrackNavigator
Fader| TrackVolume
ZoneEnd
However, if I then try to add the following to the zone file for the right hand one:
Code:
Zone Home
IncludedZones
Channel|9-16
IncludedZonesEnd
ZoneEnd
Zone Channel|9-16
TrackNavigator
Fader| TrackVolume
ZoneEnd
It doesn't work as I'd hoped. The faders for tracks 9-16 never get mapped, even when I have >8 tracks.
Currently I have my CSI.INI like this, so the two BCFs are sharing a mst but have their own zone files.
Code:
MidiInMonitor On
MidiOutMonitor On
VSTMonitor On
OSCInMonitor Off
OSCOutMonitor Off
Page HomePage FollowMCP NoSynchPages UseScrollLink UseTrackColoring 75 255 166
MidiSurface AlphaTrack 8 8 AlphaTrack.mst AlphaTrack UseZoneLink NoAutoMapSends NoAutoMapFX NoAutoMapFXMenu NoAutoMapFocusedFX
MidiSurface BCF2000Right 0 1 BCF2000.mst BCF2000Right UseZoneLink NoAutoMapSends NoAutoMapFX NoAutoMapFXMenu NoAutoMapFocusedFX
MidiSurface BCF2000Left 10 10 BCF2000.mst BCF2000Left UseZoneLink NoAutoMapSends NoAutoMapFX NoAutoMapFXMenu NoAutoMapFocusedFX
MidiSurface FCB1010 1 2 FCB1010.mst FCB1010 UseZoneLink NoAutoMapSends NoAutoMapFX NoAutoMapFXMenu NoAutoMapFocusedFX
|
Very close
.mst/.ost/.zon files are local to a surface.
You need to change "9-16" to "1-8" in the second .zon file.
The order in CSI.ini determines the overall actual channels.