kyma•tweaky . Know . GlobalMapConflicts

Problem

Hi Carla,

I'm still having problems with conflicting mappings between faders controlled by Max (via hot values specified in a custom global map) and faders that have appeared in the VCS without mappings (they say "VCS" when the mouse is over them, instead of the controllers that have been set in the global map). I'm not sure why multiple controllers with the same name but conflicting mappings are ending up in the VCS - I haven't intentionally mapped any controllers to them other than the ones determined by the global map.

I've tried deleting all layouts except the top, deleting or remapping the extra faders, etc, all with no luck.

Do you have any suggestions for how these conflicts could be appearing, and how they could be solved?

-- PhilCurtis - 25 Sep 2006

Solution

.Hi Phil,

It looks like some of the Sounds may have been added to the timeline without your global map selected.

The timeline makes its mapping using the selected global map on the first time you save a Sound into the timeline. Right now, the only way to fix this is to cause the timeline to think that the controller is new, forcing the timeline to lookup the mapping again.

Here are two ways to do this:

A. If your Sound does not have any complex settings in the timeline that would need replicating:

1. Select a Sound in the timeline; check to see if it contains a controller with a conflict. If so, continue; otherwise, proceed to the next Sound.

2. Highlight the controller with the conflict in the controls area at the bottom left of the timeline. Check to see if the source of control is showing your MIDI mapping or just the same name as the controller (which means it is not mapped).

3. If the controller has the same name (and therefore is not mapped using your global map), select the Sound and Edit>Cut. Paste the Sound into a Sound file window. Drag the Sound back to the timeline into its old position. It should maintain its original duration. That will fix it.

B. If your Sound has many settings that would make the above method difficult, you can do the following:

1. Select a Sound in the timeline; check to see if it contains a controller with a conflict. If so, continue; otherwise, proceed to the next Sound.

2. Highlight the controller with the conflict in the controls area at the bottom left of the timeline. Check to see if the source of control is showing your MIDI mapping or just the same name as the controller (which means it is not mapped).

3. If the controller has the same name (and therefore is not mapped using your global map), double click on the Sound. Locate all instances of the controller and change its name (by adding a letter, for instance). Close the Sound editor. You should see the new controller in the list. Now, double-click again on the Sound. Go through and change all of the names back. Close the Sound editor. The old name should be back in the list, but you should see that it is now using the mapping from your global map.

Please let us know if this fixes the problems you are having.

Best regards,

Kurt

-- KurtHebel - 25 Sep 2006

WebForm
TopicClassification: Solved
BriefDescription?: Hot values assigned via global map appear twice in VCS, with conflicting mappings
OperatingSystem:
LapOrDesk?:
HostProcessor?: PowerPC? G5
ClockSpeedInMHz?:
RAMInMB?: 1024-2047
CapyInterface?: Flame
KymaVersion?: KymaX?
CapybaraVersion?: Capy320
ExpansionCards?: 2
VirtualMemory?: On
MonitorSize?:
NumberMonitors?:
NumberColors?:
GraphicsCard?:
OtherHardware?:
OtherSoftware?:

----- Revision r1.1 - 25 Sep 2006 - 06:03 GMT - PhilCurtis
Copyright © 1999-2014 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding kyma•tweaky? Send feedback.