Since I placed a load of instruments in global, with their own Waves ssl EQ plugins, controlled from local via widgets, I have found that my patches weren’t sounding correct and I couldn’t fathom out what was going on. I’d EQ a song, move on and later, when I came back to the previously EQ’d song, I found it sounding strange. Didn’t give it much thought until I started to see details that I had eq’d in other songs suddenly appear reflected in the song that was now sounding weird… for example, a piano that had a low pass and high pass set to extremes to sound honky for a certain song, all of a sudden had been set to other songs with the SAME preset name.
SO, even though I have variations with specific EQs for each part/song SET in the local rackspace via widgets, If I don’t save that exact eq config WITHIN the waves plugin itself, the widgets in local are “reset” to the default preset in waves OR the last saved config.
It’s as though the local widgets are being over-ridden by the waves default/last saved preset.
Is this normal behaviour?
Up until now, I had all instruments in local and the widgets in each panel controlled the EQ knobs in waves, I didn’t save anything within the actual WAVES plugin or anything. Just set the widgets as needed and moved on. NOW that I have certain instruments in global with their EQs, I’m finding that this is happening. I don’t know if it is because those EQs are in Global and global overrides everything set in local or what on earth is causing this but it’s driving me crazy..
ok… so I’ve just gone through a rackspace that has about 6 variations, each with a piano and EQ setting. Imagine each song has a different EQ and I have named them EQ1, EQ2….. EQ6. Now I go to another rackspace with the same piano and different EQ settings yet the Waves plugin PRESET name shows as EQ1 or EQ2 or whatever… IN A RACKSPACE that isn’t using those EQ setting or preset from the previous rackspace… The widgets in each variation move accordingly and I can see the knob in Waves move accordingly… but, for some reason, SOME setting set in other rackspaces are affecting other rackspaces… not all though…
I’ll give it a little more head scratching and let you know what else I can pin down… right now, it’s very random so I can’t really give more info.
I’ve been all week EQing the whole gig to start on the 1st of May (day after tomorrow) and each day I’d find things sounding strange … I’d go and eq again and the next day again and I just realized that SOMETHING was happening that is not normal..
In the Waves plugin there is a button DYN TO CH OUT which, basically places the compression section before or after the EQ… IN my widget panel I did not include this button because there is no need to change this setting from one song to another so I set it to “OFF” as I like to compress the raw signal and EQ afterwards.
AT SOME POINT, without me noticing, I must have activated it in one song and it has stayed active for the whole repertoire because it is the piano EQ plugin in Global. And, because I did not place it as a controllable widget, it has affected every song..
YET, this does not explain WHY I cut the HFFilter and LFFilter in one song in a certain rackspace and it DEFINITELY affected at least one other song in another rackspace. Because the EQs are very subtle from one song to another, it’s quite difficult to detect this same thing happening in other rackspaces. It’s only because in ONLY ONE song I have that filter cut effect applied to the piano and I was able to detect it in another song..
It’s a mystery but right now I have to rush and sort things out. I only have today and tomorrow.
I have run into similar issues. It is usually because I have missed something regarding the relationship between widget settings in variations and song parts.
I might try to go into each song part and save the settings so they are perfect using the “capture variations” little window (aka, snapshot). See if that fixes this.(?)