LOL, "duet" is a musical ensemble, but you "dueted" it, hallelujah! I watched your video, will have to watch it in steps to get it down, but am confident, with your ingenious help, I will get this going, so, now, my heart goes pitapat that I will be able to use this Pixel 2 to create video that I can edit in Vegas Pro.

Thank you, Sir.

DelCallo

@DelCallo

This is Howie Duet.

Hi John, Thanks for posting this. It seems I have been rotating videos in Vegas all wrong by using the pan/crop tool when there is a simpler way. So thanks for this!

One question I had. In your example, the video had a 2160x3840 aspect ratio. For your render setting you set it to 1080x1920. I get that is just reducing the aspect ratio proportionately by 1/2 of the source video, but was there a particular reason you did this, instead of setting the render settings to 2160x3840?

@Rednroll

"In your example, the video had a 2160x3840 aspect ratio. For your render setting you set it to 1080x1920. I get that is just reducing the aspect ratio proportionately by 1/2 of the source video, but was there a particular reason you did this, instead of setting the render settings to 2160x3840?"

@DelCallo said, "My Pixel 2 has a viewing area of roughly 2 5/8" x 5".

Aside from the fact that the Pixel 2 screen is only 1080x1920 the way everyone else holds it, few people have the eyesight to resolve the difference in detail between 2160x3840 and 1080x1920 on a screen that size at the common viewing distance. Then there's the dirt and oil smudges on the screen and the grandkids grabbing the screen while you're watching. I was just delivering the right output for the target audience on the target hardware, while saving a few bits of Google and Microsoft's disk space. I have a Google drive and OneDrive, but I don't pay money to large monopolies for extra disk space over what they "give me for free". I don't skimp on the duplicate drives that I use to save the source and all the versions that I render, however.

Imho, this is a known bug. Vegas Pro does not add the needed portrait metadata into the rendered file. Portrait output only works as long as you don't start turning the display – what actually happens most of the time when using smartphones.

This is the correct assessment to the best of my knowledge.

Now for the rest of the story. Rotation metadata is an Apple invention (imagine that), and just like VUI flags, m4v chapter points, and VFR (until very recently), Vegas does not recognize them nor create them (no imagination required).

It's possible the Pixel 2 footage does not even contain the rotation flag, because one user reports Handbrake laid it on it's side, but we'll likely never know, because a whole truckload of talk has not proved a worthy substitute for the one definitive proof requested -- a sample file, @DelCallo!

So, given the history and benefit of experience :-), @john_dennis solution may be what we've got, hang all the speculation.

Although his posts are often overlooked because of their simplicity, I instinctively believe Marco until proven otherwise. I've now caught him twice today giving spot-on facts that would end a whole lot of discussion if they had actually been recognized and considered as such...

@Rednroll

"In your example, the video had a 2160x3840 aspect ratio. For your render setting you set it to 1080x1920. I get that is just reducing the aspect ratio proportionately by 1/2 of the source video, but was there a particular reason you did this, instead of setting the render settings to 2160x3840?"

@DelCallo said, "My Pixel 2 has a viewing area of roughly 2 5/8" x 5".

Aside from the fact that the Pixel 2 screen is only 1080x1920 the way everyone else holds it, few people have the eyesight to resolve the difference in detail between 2160x3840 and 1080x1920 on a screen that size at the common viewing distance. Then there's the dirt and oil smudges on the screen and the grandkids grabbing the screen while you're watching. I was just delivering the right output for the target audience on the target hardware, while saving a few bits of Google and Microsoft's disk space. I have a Google drive and OneDrive, but I don't pay money to large monopolies for extra disk space over what they "give me for free". I don't skimp on the duplicate drives that I use to save the source and all the versions that I render, however.

Your thoughts are the same as mine. I just wanted to make sure there wasn't any technical reason I may have missed in fixing the original problem and you had done it just for the purposes of reducing the resolution to the target screen and thus reducing file size.

Thanks again!

Imho, this is a known bug. Vegas Pro does not add the needed portrait metadata into the rendered file. Portrait output only works as long as you don't start turning the display – what actually happens most of the time when using smartphones.

This is the correct assessment to the best of my knowledge.

Now for the rest of the story. Rotation metadata is an Apple invention (imagine that), and just like VUI flags, m4v chapter points, and VFR (until very recently), Vegas does not recognize them nor create them (no imagination required).

It's possible the Pixel 2 footage does not even contain the rotation flag, because one user reports Handbrake laid it on it's side, but we'll likely never know, because a whole truckload of talk has not proved a worthy substitute for the one definitive proof requested -- a sample file, @DelCallo!

So, given the history and benefit of experience :-), @john_dennis solution may be what we've got, hang all the speculation.

Although his posts are often overlooked because of their simplicity, I instinctively believe Marco until proven otherwise. I've now caught him twice today giving spot-on facts that would end a whole lot of discussion if they had actually been recognized and considered as such...

That makes a lot of sense. I have a Samsung Galaxy S9 phone that I shoot video with, the OP a Pixel 2 so obviously Apple is no longer the only ones doing this.

Bug or not, what frustrates me the most is that when I view the video on my phone screen, the video is displayed in portrait mode as it was shot, while I'm holding the phone in portrait mode. When I copy the video file to my PC and play it in VLC media player, the video is displayed in portrait mode. When I import it onto the Vegas timeline, then Vegas lays it on its side with the improper orientation. So I guess, if it's due to rotation metadata being present like you describe, whatever VLC media player is doing to deal with that same rotation metadata, I sure wish Vegas Pro would do the same with it instead of laying it on its side or at least prompt you during import if its unsure about the video's orientation due to metadata, so I can tell Vegas what it is unable to figure out at that time, instead of Vegas just assuming incorrectly for the user it's landscape. Afterall, Vegas is supposed to be the "Pro" application where most would assume it would be the better suited application to be able to better manage modern video files shot by smartphones.

Rednroll:

I am missing something. The footage when transferred from my Pixel 2 shows 1920 x 1080. If I run it through Handbrake, I reverse the dimensions, but the output shows 1080 x 1080, so I'm doing something wrong there. When I import to Vegas Pro, the orientation is landscape, but the media is still 1080 x 1080.

What am I doing wrong?

I've been away from the forum, so sorry to be late with this additional question.

Thanks.

DelCallo

BTW, I now shoot in landscape orientation using a gimbal, and that footage plays back find from the cloud by just rotating the smartphone during playback to landscape position. Still, I would like to fix the footage I shot originally in portrait orientation because it is nice footage.

Thanks again.

DelCallo