I will warn anyone who uses this tool...hacking the project is not supported and is very likely to cause instability. If you do this with your project, customer support will not help when you if you contact them with issues.

Thank you already for improving this open source program. I must say that I am not a specialist in this type of program, when I go to your link there are several .exe, should I download all the files that you offer and put them in a single folder? I downloaded the first .exe at first but Windows, as it did not know it, tried to block it but when it accepted it, this .exe did not open any window but apparently you seem to mention that it is the other file msvpvf_gui.exe that must be used. I have not had time to try this one yet. My idea is to downgrade a Vegas 22 project to Vegas Pro 19 to secure this project in case V22 has some bugs.
If you have a specific tutorial for your open source, I am interested, otherwise I will see what is causing me problems!

Thank you already for improving this open source program. I must say that I am not a specialist in this type of program, when I go to your link there are several .exe, should I download all the files that you offer and put them in a single folder? I downloaded the first .exe at first but Windows, as it did not know it, tried to block it but when it accepted it, this .exe did not open any window but apparently you seem to mention that it is the other file msvpvf_gui.exe that must be used. I have not had time to try this one yet. My idea is to downgrade a Vegas 22 project to Vegas Pro 19 to secure this project in case V22 has some bugs.
If you have a specific tutorial for your open source, I am interested, otherwise I will see what is causing me problems!

@davewire msvpvf.exe is a command line program that needs to be run using command lines. For general users, msvpvf_gui.exe is recommended. Download msvpvf_gui.exe and run it. If it's blocked by any anti-virus software, trust it and allow it to run.

After that, open (or drag and drop) the project file to import, select the version number you want to export, and finally save it. The project file name is automatically renamed according to the version number you select, for example your project name is "Untitled.veg" and you select 19, the new project name is "Untitled_19.veg". You can also change it to the name you want.

Just be careful with features, plugins, media gens, transitions, or fx not available in the older version. And resave in the older version right away.

The safer way is to open both Vegas versions at once and copy/paste events and keyframes from newer to older. Fx can be saved as presets in the newer and will show up in the older if the fx is supported. Regions and markers can be copy/pasted using the Edit Details window. More tedious this way but more reliable.

@zzzzzz9125, @mark-y, @davewire I'm wondering which advantage you expect from opening a VP22 project in a previous Vegas version?

@zzzzzz9125, @mark-y, @davewire I'm wondering which advantage you expect from opening a VP22 project in a previous Vegas version?

Vegas 22 is still full of bugs and I know that my Vegas 19 works perfectly and therefore I want to ensure my video editing and not lose the work already done. The current bug with vertical lines on images when cropped is serious so I can't move forward with my editing.

Thank you already for improving this open source program. I must say that I am not a specialist in this type of program, when I go to your link there are several .exe, should I download all the files that you offer and put them in a single folder? I downloaded the first .exe at first but Windows, as it did not know it, tried to block it but when it accepted it, this .exe did not open any window but apparently you seem to mention that it is the other file msvpvf_gui.exe that must be used. I have not had time to try this one yet. My idea is to downgrade a Vegas 22 project to Vegas Pro 19 to secure this project in case V22 has some bugs.
If you have a specific tutorial for your open source, I am interested, otherwise I will see what is causing me problems!

@davewire msvpvf.exe is a command line program that needs to be run using command lines. For general users, msvpvf_gui.exe is recommended. Download msvpvf_gui.exe and run it. If it's blocked by any anti-virus software, trust it and allow it to run.

After that, open (or drag and drop) the project file to import, select the version number you want to export, and finally save it. The project file name is automatically renamed according to the version number you select, for example your project name is "Untitled.veg" and you select 19, the new project name is "Untitled_19.veg". You can also change it to the name you want.

I tried yesterday but it didn't work, it starts loading my project (VP22) converted for VP19 and at 5% it gives me an opening error! Perhaps a build compatibility issue. It's true that the technique of copying and pasting from one Vegas to another works but you have to put back all the track plugins and everything, it's a bit cumbersome. Vegas should imagine backward compatibility of its products like game consoles etc. can do.

@davewire Normally a new Vegasversion has less bugs than a previous version, only due to adding new features in a new Vegasversion it can happen that new bugs are introduced, serious bugs like you described are solved in a next update, which I expect very soon.

Tell my an editing software which has backward compatibility? Even Vegas is one of the few editors which have forward compatibility, mostly in other editors you have to finish the edit in the version where you started the project.

I tried yesterday but it didn't work, it starts loading my project (VP22) converted for VP19 and at 5% it gives me an opening error! Perhaps a build compatibility issue.

@davewire Just found an interesting fact: when any 21 build 300+ (including 22) project contains one or more video events (even if it's an empty video event), it can't be converted to a 19 - 21 build 208 compatible project via MSVPVF. That is, only audio-only projects can be converted to lower versions. I had previously only tested on blank projects, so I came to the wrong conclusion that VP22 projects could be directly converted to VP19 projects. If I had to study this from the file contents, it would take a while, and I'm not sure if I could do it.

I am working on a simple 4K project in VP22. DJI Mini 3 Pro footage along with Panasonic 4k footage. I haven't used any specific VP22 effects, but have used Sapphire S_Aurora effect in the project.

I opened VP18, changed the project settings to match the VP22, did a copy/paste to the VP18 timeline and it plays back.

@zzzzzz9125 since you find VP19 stable for you, why not copy the timeline and paste it into VP19?

since you find VP19 stable for you, why not copy the timeline and paste it into VP19?

@Reyfox I don't actually use 19, I have 21 build 208 and 22 build 93. I'm thinking about the possibility of downgrading the latter to the former to make it easier to go back to 21 build 208 in case of an error in 22. As for 21 build 300+, I have a poor first impression of them, so I'm hesitant to use them.

I just tested a 4k project in both versions and found that 22 build 93 is twice as fast as 21 build 208. I also had another VP21 project added some complex FX that performed well in 21 build 208 but had various preview twitching issues in VP22. I can't judge which version is really better, so I'm leaving myself open to possible fallbacks.

One drawback to copy & paste on the timeline is that you can only copy events, not tracks, and for parameters such as track FX, you still need extra effort to transfer them.

@zzzzzz9125, yes, if you have track fx, you will have to do them over again. I don't know the complexity of what is being used at the track level, but while it will take a few extra steps to do them over again, sometimes that's the price we have to pay. At least getting all the events over is easy until issues are fixed.

As for VP21 B315, it has worked pretty good for me. And then VP22 came out....

@davewire Normally a new Vegasversion has less bugs than a previous version, only due to adding new features in a new Vegasversion it can happen that new bugs are introduced, serious bugs like you described are solved in a next update, which I expect very soon.

Tell my an editing software which has backward compatibility? Even Vegas is one of the few editors which have forward compatibility, mostly in other editors you have to finish the edit in the version where you started the project.

You are right there is little retro compatible software but from VP22 to VP19 there is not a huge GAP between the creation of the two software either, I just ask that he can open it even if it means it removes fx and plugins only managed by VP22.
Concerning VP22, the bug of photos with vertical lines when you crop is really too annoying, after 22 version of vegas, I find it incredible that there is a bug like that present so it bothers me to be stuck in the advanced in my project or having to think about it differently while waiting for the problem to be resolved.

@zzzzzz9125, yes, if you have track fx, you will have to do them over again. I don't know the complexity of what is being used at the track level, but while it will take a few extra steps to do them over again, sometimes that's the price we have to pay. At least getting all the events over is easy until issues are fixed.

As for VP21 B315, it has worked pretty good for me. And then VP22 came out....

That's what's really annoying, what a waste of time to have to reintegrate all the track effects, plus I rename each of my tracks and when I copy and paste from one version of Vegas to another, it's not not taken into consideration. Maybe small details for you but I prefer to focus on something else especially since it takes time to put together a film

Maybe the aforementioned problems are an example which go to support those who have recommended on the forum over the years that it is best to finish a project in the Vegas Pro version that it was commenced in. I must admit that I don't follow that advice but there have been times - including recently - when I've had to copy/paste projects back to an earlier VP version including having to rebuild track level FX. C'est la vie!

.. but from VP22 to VP19 there is not a huge GAP between the creation of the two software either

Yes, I think that there is a gaping gap. Vegas staff have mentioned on the forum that Vegas Pro's engine is being updated. From VP21 build 300's announcement:

We are happy to announce the release of VEGAS Pro 21 Build 300. This is a large update which includes phase 1 of our new Video Engine work

If I remember correctly, this is when projects saved in build 300 were not able to be opened in build 208 and any earlier Vegas Pro version/build. It stands to reason that Vegas Pro 22 continues further work on the 'engine'.

The only time I can recall when a Vegas Pro new version was backwards compatible with the previous version was Sony Vegas Pro 12 which allowed SVP12 projects to be opened in problem-plagued SVP11 because - apparently - SVP12 didn't have any new features over SVP11.

If I remember correctly, this is when projects saved in build 300 were not able to be opened in build 208 and any earlier Vegas Pro version/build. It stands to reason that Vegas Pro 22 continues further work on the 'engine'.

This change (which we hate doing mid-release) was due to a bug in Adjustment Events, not because of the new video engine.

The only time I can recall when a Vegas Pro new version was backwards compatible with the previous version was Sony Vegas Pro 12 which allowed SVP12 projects to be opened in problem-plagued SVP11 because - apparently - SVP12 didn't have any new features over SVP11.

I believe this was actually between SVP12 and SVP13. This happened by mistake. We did not intend to release SVP13 with the same project version number.

If I remember correctly, this is when projects saved in build 300 were not able to be opened in build 208 and any earlier Vegas Pro version/build. It stands to reason that Vegas Pro 22 continues further work on the 'engine'.

This change (which we hate doing mid-release) was due to a bug in Adjustment Events, not because of the new video engine.

@VEGASDerek However, in 21 build 315, Adjustment Events are still buggy: https://www.vegascreativesoftware.info/us/forum/is-this-a-bug-script-that-launches-adjustment-event-on-vegas-pro-22--146794/#ca922015

For 21 build 315, without an additional fix, users can only downgrade to 21 build 208 or upgrade to 22. I'd like to ask how VEGAS developers feel about this.

@zzzzzz9125, @mark-y, @davewire I'm wondering which advantage you expect from opening a VP22 project in a previous Vegas version?

The superiority of later versions, their plugins capabilities, their import capabilities, and their output options are not always unilateral on the positive time (x) axis.

@zzzzzz9125, @mark-y, @davewire I'm wondering which advantage you expect from opening a VP22 project in a previous Vegas version?

The superiority of later versions, their plugins capabilities, their import capabilities, and their output options are not always unilateral on the positive time (x) axis.

No idea what you want to say...I never had the need to import a project into an earlier Vegas version, but very often continue earlier projects in a newer Vegas version, which works without issues. For safety reasons I save each project with a Vegas version number.

Certain newer builds are downgrades is the clear meaning.

MxCompound still has quite a number of bugs, regressions and incompatibilities to address vs so4compound/compoundplug.