I have just gone thru a process of carefully changing some mixer plugin levels and then using File Menu → Save As
to save an new iteration of the Gig file.
Then I closed the program. Then I reopened the program. My edits were not there.
Am I mistaken to think that edits made to rackspaces are saved “up-to-current” when Save As is used?
Do I need to do a manual process of ‘Update (save) Rackspace to Gig File’ before I do every Save As?
The manual states:
Update (save) Rackspace to Gig File - saves the selected rackspace to the currently open .gig file; make sure to save a gig first for this feature to work. Note: this option saves only the currently selected rackspace, and changes made to all other rackspaces will not be saved; if you want to save/update all rackspaces, click on File → Save instead. Also note that you cannot add and save new rackspaces this way - the rackspace must exist and must be saved to the gig file first (you cannot add a new rackspace and then select this menu item to update it because it is not in the gig file yet).
which I interpret as “do File → Save As and you are all-up-to-date with your latest edits”, but this does not seem to be what I just observed.
In case it is relevant, my edits to the mixer were all double-clicks on sliders to return them to 0db. (Possibly that particular action isn’t sticking?)
I just created a new gig, added a 4ch mixer, mapped two slider widgets to the Gain parameters of 1/2 and 3/4, changed the slider values, saved, re-opened, double clicked the sliders to return to 0db, Save As…closed, re-opened —the sliders remained at 0db.
Can you try with that simplified example I just gave and see if you can verify the behavior?
I wonder if, instead of opening up an “empty gig” and then selecting a recent gig, you instead opt for “recent” gig file and directly open the recently created gig file? Does that change anything?
OK, I found a 2nd widget on a lower panel mapped to the same plugin/parameter.
Deleting that solved this problem. Thanks to all who offered their assistance!
I now recall that at one point I did explicitly want to control that mix level from either of two different places (widgets) in different panels. I now take it that that is a bad idea to pursue …
But if there is a foolproof “proper” way to do that, I would like to know.
It’s called widget linking - you map one widget to the parameter you want to control and then you link it with other widgets that don’t do anything other than respond to MIDI messages
If you ever get unexpected behaviour with widgets, always remember that Window → Widget Mappings will quickly show you the widgets and their mapped parameters. It is a great tool to help with troubleshooting.
When using 2 or more linked widgets (i.e on different panels) to control a single plugin parameter, it seems that only one of the widgets can display the [value], yes?
