yes, now the waveset parameters are under <object>.visual.waveset rather than just <object>.waveset
this was changed for 1.5.0, so if this just started happening after a plugin upgrade, the reason is that you're looking at a default waveset and your settings aren't being applied.