(VP22) Bug loading presets (from VP19) vegas plugin

davewire wrote on 8/14/2024, 3:18 AM

Hello everyone, I don't know if my title is very clear but I wanted to know if you were also facing this problem.

Basically until recently, I was working on vegas pro 19 in which I imported my presets (created on an earlier version like vegas pro 14) for vegas plugins like "color corrector" or "brightness and contrast " etc.. I had no problem loading them on VP19, they were taken into account and applied perfectly.

On the other hand, in VP22, I can find my presets with their titles but when I load them nothing happens, the settings are not taken into account. I had to open my VP19, copy the data one by one and re-record it again. Is this a bug that will be fixed or compatibility will not be supported.

It's a bit cumbersome because I have quite a few presets and they are also recognized but not loaded.


Thank you.

Comments

zzzzzz9125 wrote on 8/14/2024, 4:49 AM

On the other hand, in VP22, I can find my presets with their titles but when I load them nothing happens, the settings are not taken into account. I had to open my VP19, copy the data one by one and re-record it again. Is this a bug that will be fixed or compatibility will not be supported.

@davewire I can confirm that this bug does exist.

I've just found a temporary solution. Go to My Documents\OFX Presets and find your preset files. The UID changes for the built-in plugins happen in VP17, "sony" before that, "vegas" after that. For the presets of Brightness and Contrast in old versions, it's My Documents\OFX Presets\com.sonycreativesoftware_brightnessandcontrast\Filter\yourpresetname.xml. Open them with Notepad and change sonycreativesoftware in Line 2 to vegascreativesoftware. Just changing this one thing works for me. Of course, this will make it impossible for older versions to read these presets again. A better idea is to make copies and replace all "sony" words (including those in the file paths) with "vegas", which will take you more time however.

If VP19 can actually read them normally, it means this feature has been broken since VP22. This may be a problem that needs a fix.

Using VEGAS Pro 22 build 122 & VEGAS Pro 21 build 208.

Information about my PC:
Brand Name: HP VICTUS Laptop
System: Windows 11.0 (64-bit) 10.00.22631
CPU: 12th Gen Intel(R) Core(TM) i7-12700H
GPU: NVIDIA GeForce RTX 3050 Laptop GPU
GPU Driver: NVIDIA Studio Driver 560.70

davewire wrote on 8/14/2024, 7:35 AM

On the other hand, in VP22, I can find my presets with their titles but when I load them nothing happens, the settings are not taken into account. I had to open my VP19, copy the data one by one and re-record it again. Is this a bug that will be fixed or compatibility will not be supported.

@davewire I can confirm that this bug does exist.

I've just found a temporary solution. Go to My Documents\OFX Presets and find your preset files. The UID changes for the built-in plugins happen in VP17, "sony" before that, "vegas" after that. For the presets of Brightness and Contrast in old versions, it's My Documents\OFX Presets\com.sonycreativesoftware_brightnessandcontrast\Filter\yourpresetname.xml. Open them with Notepad and change sonycreativesoftware in Line 2 to vegascreativesoftware. Just changing this one thing works for me. Of course, this will make it impossible for older versions to read these presets again. A better idea is to make copies and replace all "sony" words (including those in the file paths) with "vegas", which will take you more time however.

If VP19 can actually read them normally, it means this feature has been broken since VP22. This may be a problem that needs a fix.

You're a genius ahah 😍 I'm not at home but I will try this, exactly it was sony vegas before ! hope they will fix it too, i will do copy like you said !

davewire wrote on 8/19/2024, 5:46 AM

On the other hand, in VP22, I can find my presets with their titles but when I load them nothing happens, the settings are not taken into account. I had to open my VP19, copy the data one by one and re-record it again. Is this a bug that will be fixed or compatibility will not be supported.

@davewire I can confirm that this bug does exist.

I've just found a temporary solution. Go to My Documents\OFX Presets and find your preset files. The UID changes for the built-in plugins happen in VP17, "sony" before that, "vegas" after that. For the presets of Brightness and Contrast in old versions, it's My Documents\OFX Presets\com.sonycreativesoftware_brightnessandcontrast\Filter\yourpresetname.xml. Open them with Notepad and change sonycreativesoftware in Line 2 to vegascreativesoftware. Just changing this one thing works for me. Of course, this will make it impossible for older versions to read these presets again. A better idea is to make copies and replace all "sony" words (including those in the file paths) with "vegas", which will take you more time however.

If VP19 can actually read them normally, it means this feature has been broken since VP22. This may be a problem that needs a fix.

it works !! thx you so much !