is it possible to convert a vegas pro 22 project so that it can then be opened in my vegas pro 19 and therefore compatible?

Unfortunately, no. A project created in a Vegas Pro version is not backwards compatible with a previous Vegas Pro version.

But what can be done is to open an empty new project in VP19 and then copy paste the timeline from VP22 onto VP19's timeline (click on VP22's timeline, click Ctrl-A and then Ctrl-C and then click on VP19's timeline and click Ctrl-V). Any FX in the track headers will have to be coded again, and any FX used in VP22 that are not available in VP19 will not copy/paste.

Sorry, but I can't help on the other issues.

Thank you already for this valuable help, indeed I had already done this but I was wondering if there was an easier solution. I also read the export as a DE text file but when opening it in vegas 19, it could not find certain elements like my text sequences. It's a shame, it could be an option to imagine backwards compatibility for what is possible.

In vegas pro 22, the loop is done once and when you stretch it afterwards it remains static, it's quite painful, is there an adjustment to be made or is this a bug?

Go to Preferences -> Edit and disable Default Event Loop. For single events without loops in your timeline, Right-click -> Switch -> Loop to enable loop.

 

Regarding importing photos (from my iPhone), I have exactly the same problem as this guy on this forum https://www.vegascreativesoftware.info/us/forum/vp22-pan-crop-bug-on-zoomed-still-photo-smears--146669/

For this issue, you may have to wait until the 22 new build fix patch.

 

Otherwise, I had one last question, is it possible to convert a vegas pro 22 project so that it can then be opened in my vegas pro 19 and therefore compatible? Thank you for your help.

It's possible, and there's an open source tool called MSVPVF, which supports the downgrading of high version Vegas projects to the low ones. In my tests, the projects of VP22 can be downgraded to those of VP19. The original author didn't provide a compiled exe program, but I compiled one myself. I'll start a new thread later to post it.

Thank you very much for these proposed solutions, I'm going to test it all this afternoon at home and I'll get back to you! Excellent open source software, I didn't know about it, I'm going to study it more closely in any case!

Otherwise, I had one last question, is it possible to convert a vegas pro 22 project so that it can then be opened in my vegas pro 19 and therefore compatible? Thank you for your help.

It's possible, and there's an open source tool called MSVPVF, which supports the downgrading of high version Vegas projects to the low ones. In my tests, the projects of VP22 can be downgraded to those of VP19. The original author didn't provide a compiled exe program, but I compiled one myself. I'll start a new thread later to post it.

@davewire See this post: https://www.vegascreativesoftware.info/us/forum/msvpvf-a-useful-tool-to-downgrade-the-version-of-your-project-files--146899/

In vegas pro 22, the loop is done once and when you stretch it afterwards it remains static, it's quite painful, is there an adjustment to be made or is this a bug?

Go to Preferences -> Edit and disable Default Event Loop. For single events without loops in your timeline, Right-click -> Switch -> Loop to enable loop.

 

Regarding importing photos (from my iPhone), I have exactly the same problem as this guy on this forum https://www.vegascreativesoftware.info/us/forum/vp22-pan-crop-bug-on-zoomed-still-photo-smears--146669/

For this issue, you may have to wait until the 22 new build fix patch.

 

Otherwise, I had one last question, is it possible to convert a vegas pro 22 project so that it can then be opened in my vegas pro 19 and therefore compatible? Thank you for your help.

It's possible, and there's an open source tool called MSVPVF, which supports the downgrading of high version Vegas projects to the low ones. In my tests, the projects of VP22 can be downgraded to those of VP19. The original author didn't provide a compiled exe program, but I compiled one myself. I'll start a new thread later to post it.

Otherwise to give some feedback to the solutions you gave me, strangely in my options the box to loop events was checked but it did not work for gifs. I unchecked it and re-checked it and it seems to work! Otherwise, the right-click option works too! Good for the photo bug, we will actually have to wait for a corrective patch! And if not for your open source program I will answer you on your thread, thank you again in any case for the help provided.

@davewire I am the 'guy' from the original post on smeared photo after pan crop from a direct import on a Samsung phone. Some reported the issue on iphone import as well, some have only the issue on vertical aspect size, I had it on both vertical and horizontal aspect sizes.

A workaround is to a default edit and save in an external photo editor before importing in Vegas. This can be quick as you can select all the photo's and save all. And by the way the DPI 72 - 300 was a false lead, it is a confirmed bug in the current Vegas 22 b93.

@davewire I am the 'guy' from the original post on smeared photo after pan crop from a direct import on a Samsung phone. Some reported the issue on iphone import as well, some have only the issue on vertical aspect size, I had it on both vertical and horizontal aspect sizes.

A workaround is to a default edit and save in an external photo editor before importing in Vegas. This can be quick as you can select all the photo's and save all. And by the way the DPI 72 - 300 was a false lead, it is a confirmed bug in the current Vegas 22 b93.

Hey thank you in any case, it's thanks to your post that I was able to understand that several people were impacted, for my part I have the impression that it is mainly on vertical photos (I tried photo d iPhone, photo of a Canon SLR... the same issue). I don't know when the next patch is planned to correct this, it's still incredible to see such a bug after so many versions of Vegas, a bit like the photo import base. I then read your thread better and understood that the DPI was not actually the cause of the problem. So the idea would be to import several photos into Photoshop type software for example? and then re-save them in the same format? Would that be enough?

Are there any Photoshop scripts to do this quickly rather than one by one?

@davewire I do not have photoshop, but in DXO you can browse to a folder where your photo's are, select them all, then use default template to e.g. improve a bit (not sure this step is needed), then save all, it will save them in a proper format which seems less compressed than the original, but hence quite the increased file size. I did not try out other photo editors, but I suppose the principle is the same.

@davewire I am the 'guy' from the original post on smeared photo after pan crop from a direct import on a Samsung phone. Some reported the issue on iphone import as well, some have only the issue on vertical aspect size, I had it on both vertical and horizontal aspect sizes.

A workaround is to a default edit and save in an external photo editor before importing in Vegas. This can be quick as you can select all the photo's and save all. And by the way the DPI 72 - 300 was a false lead, it is a confirmed bug in the current Vegas 22 b93.

@bitman I believe this whole problem with the photos is a result of one of the EXIF parameters in the metadata that imposes an "orientation" on the photo. That is, if the photo is vertical, say X by Y = 1000 X 2000, some cameras will describe it as being 2000 X 1000 with an orientation that is rotated 90 degrees. When photoshop rewrites such a file, it is then described as 1000 X 2000 with no rotation. I believe Vegas is troubled by the "orientation" metadata.

I have wondered if another workaround is to use the Vegas "rotate" property to cancel out the bug.

A workaround for the problem seemingly induced by the "orientation" metadata:

* right click on the media and select properties

* in the [media] tab, look for the rotation dropdown near the bottom and select 0 degrees

* then reedit the pan-crop.

It's a pain, but so is rewriting the files. Hopefully, a proper fix to V22 will not mess up the workaround.