FabFilter User Forum

Vegas Pro 10 and FF Total Bundle version conflict

Hi FF,

Here's a new challenge:

Recently i have updated FabFilter Total Bundle ver.20101203 to ver.20110411
(I don't use RTAS, only VST2 and VST3)

After the update, when i try to load a Vegas Pro 10 project (made a few months ago), there appears to be a conflict with the used FabFilter plugins by the Vegas project file.

A popup window says:

Warning: an error occured while loading <projectname>.veg

An error occured while loading one or more plugins.
The settingsgroup of the plugin can't be loaded.

The user settings group for plugin 'Fabfilter Pro-Q' can't be loaded. Default settings are restored (This last message repeats for every Pro-Q instance used).


Well, after closing Vegas, deinstall FFTB ver.20110411, reinstall FFTB ver.20101203, opening the Vegas project, everything is fine - no messages at all.

Then, after closing Vegas again, deinstall FFTB ver.20101203, reinstall FFTB ver.20110411 again, opening the Vegas project, the error messages are back.


As far as i can see and hear, every instance of Pro-Q still has all settings (the way it was saved in the project), so at least it's an annoying message everytime i open an older project.

Have a clue ?


santé

VascoMusic

We'll try to reproduce the problem and will get back to you.

Cheers,

Frederik (FabFilter)

I could reproduce the problem, but got a slightly different message, and Vegas did not restore the previous settings at all, so the Pro-Q instance was restored to its default state.

In order to support the new features in Pro-Q 1.11, we had to add new parameters to the plugin. The host should just ignore these when restoring the state of the plugin, but it looks like Vegas doesn't handle this correctly. The old version of Pro-Q had 177 parameters. Going to 178 and 179 is handled fine, but the step to 180 parameters triggers the error message.

We'll try to contact the Vegas developers. If you can contact customer support, explain the problem and ask them to contact us, that would certainly help.

At this point, I would recommend to you to re-save the projects with the latest version of Pro-Q after you've verified that all settings were restored correctly. If not, you could manually save a preset using the old version of Pro-Q, and then reload it using the new version and then save the project.

Cheers,

Frederik (FabFilter)

Reply to this topic: