And by the way, the smears and wrong pan/crop issue does not go away in rendering. So it is not just a preview issue. I tried changing some stuff like a different settings of pan/crop and I/O HW decoder, but to no avail. The same picture zoomed in VP21 pan/crop still works fine.

Reproduced. Thank you. I will inform the team.

@VEGASDerek I found the root cause (and a work-around).

VP22 b93 has the pan/crop issues with photos which are created with a horizontal and vertical DPI of 150.

(apparently this is the default DPI of the Samsung S22 ultra phone photos).

Workaround: Converting the same photo to 300 DPI (e.g. via photo editor such as DXO) and the issue goes away (which is a workaround for the issue until a Vegas patch solves it so a convert is not needed anymore)

Note that it does not matter if the aspect ratio is horizontal or vertical.

@bitman Hi, all my S23 Ultra photos say 72dpi in their Properties & when I drag into GIMP. how did you determine the dpi of yours.

I get the smears with Portrait 9:16 photos but not 16:9, my phone has 12m, 50m, & 200m options, I've tried all 3.

Hi @Gid

I check the properties by windows on the files by right clicking and then tab details, but I suppose that is not what you ask right? Most of my photos on the S22 ultra come out as 150 DPI, but there a few also with 72 DPI, I am guessing that the phone decides this autonomously (maybe based on the lens used?).

I am not sure if I can force the phone itself to deliver on a fixed 300 DPI.

Anyway even if it would be possible, then this will create bigger files, so until this is fixed in a Vegas 22 patch, I will use external photo editing sw (like DXO) to open only those the files I will use in a project and save them to 300 DPI before importing them in Vegas.

@bitman Thanks, yep I had a look through the setting & online, but a quick search didn't reveal an option to change the dpi 🤷‍♂️ I didn't zoom anything tho

Something interesting: photos from my S21 show XResolution and YResolution as '72' with resolution unit '2' which means inches, as read from the file's EXIF properties (i.e. the 'metadata').

Also, Photoshop (Elements) shows '72' dpi.

But Windows properties says '150'. Also, the Windows GDI+ interface returns '150' as the DPI, and Windows 'Photos' shows 150. 'Irfanview' shows 149. 'Paint' and 'Windows Photo Viewer' show '150'.

Obviously DPI is arbitrary. The number of pixels is what determines the file size. I don't know where Windows gets '150'. DPI is often offered as an initial suggestion as to the printable size of a photo, given some arbitrary determination of how much resolution a printer can show on a piece of paper.

Vegas shouldn't care about DPI. Only the number of pixels vs. the project dimensions.

P.S. Also I haven't found anywhere Vegas exhibits 'DPI' as a property of an image.

 

Workaround: Converting the same photo to 300 DPI (e.g. via photo editor such as DXO) and the issue goes away (which is a workaround for the issue until a Vegas patch solves it so a convert is not needed anymore)

Note that it does not matter if the aspect ratio is horizontal or vertical.

Strange if DPI affecting the image handling. So far I know DPI is only for printing.

What resolution in terms of pixels you have now, between the 'original 150 dpi' and the '300 dpi converted' image ?

What I found so far, smaller resolution images works correct rather than higher resolution images.

@bitman I just created a file in GIMP at 150 dpi/ppi using an S23 200m image & it behaves normally in VP22 🤷‍♂️

@set 

The original S22 photo size 2,96 MB (3 107 243 bytes), dimension 2252 x 4000 pixels, 150 DPI

The "converted" same photo in DxO (just open and save, no edit action): size 9,77 MB (10 249 097 bytes), dimension 2252 x 4000 pixels, 300 DPI

Strange if DPI affecting the image handling. So far I know DPI is only for printing.

Indeed, just my thoughts too, but I cannot see any thing different between the 2 files except the size and DPI reported by windows. It must be some file compression reading issue that VP22 b93 cropping/zooming action using pan/crop is unhappy about, whereas VP21 b315 is OK ...

@Gid @set @VEGASDerek

It seems that converting (or just saving) these Samsung phone photos using a third party photo editor DxO or Gimp etc.. is a workaround for the issue, and even after the save/convert it does not have to be 300 DPI, 150 DPI works as well...

I have to conclude it is not the DPI which is the issue, but the inability of Vegas 22 b93 to treat a Samsung phone photo file in its default compressed delivery.

NOK: The original S22 ultra photo size 2,96 MB (3 107 243 bytes), dimension 2252 x 4000 pixels, 150 DPI

OK: The "converted" photo in DxO: size 9,77 MB (10 249 097 bytes), dimension 2252 x 4000 pixels, 300 DPI

OK: The "converted" photo in DxO: size 9,77 MB (10 249 097 bytes), dimension 2252 x 4000 pixels, 150 DPI

@bvideo you are right, the DPI is an arbitrary value to help the printer

Thx for more info @bitman. Something in the metadata properties causes the issue

Thx for more info @bitman. Something in the metadata properties causes the issue

Now we have a culprit, I'm sure that helps the team identify the solution much easier now.

We already have a solution...(this was fixed over the weekend.) We are in the process of testing it now. Hopefully this will be resolved in the first update.

Like others, it's only with some portrait images from my camera. Great the a fix is on the way!!

I see the same. Not consistent for all images. JPG images from a Sony 100IV.