Problem with rendering to Android on Sony Vegas 13 Pro

laimaidan wrote on 9/10/2023, 7:20 AM

Folks, I have a problem with rendering in Sony Vegas 13 Pro for the android.

I'm taking the vertically videos via my phone without changing any video and audio options.
On PC BEFORE and after rendering it looks like this: https://i.ibb.co/6DnfbJ3/Clipboard01.jpg

After I upload it to any of my android phones it looks like this: https://i.ibb.co/QbLdmRw/Clipboard02.jpg

I tried to change the codec, frame and bit rate and frame size but nothing helped. 
My Android keep showing me this small videos regarding of parameters i chose.

Please advise what's wrong as on PC everything looks good.

Comments

Dexcon wrote on 9/10/2023, 7:47 AM

You probably need to change Vegas Pro's project properties to the H / W dimensions of the phone video. If project settings are at the default 16:9 or 4:3 aspect ratio, then your phone is going to see the render as a TV ratio and therefore display it that way.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

laimaidan wrote on 9/10/2023, 9:36 AM

You probably need to change Vegas Pro's project properties to the H / W dimensions of the phone video. If project settings are at the default 16:9 or 4:3 aspect ratio, then your phone is going to see the render as a TV ratio and therefore display it that way.

I did change from 1920x1080 to 1080x1920 but still got the same result

john_dennis wrote on 9/10/2023, 9:41 AM

@laimaidan

john_dennis wrote on 9/10/2023, 10:02 AM

"I'm taking the vertically videos via my phone ..."

Quit it!

laimaidan wrote on 9/11/2023, 5:56 PM

@laimaidan

thanks, but this is not working.

Once I hit apply, it shrinks picture again to https://i.ibb.co/QbLdmRw/Clipboard02.jpg

 

john_dennis wrote on 9/11/2023, 6:04 PM

Share a source file. I'll make it work and record the process.

laimaidan wrote on 9/11/2023, 6:51 PM

here you go a piece of it: https://www.filemail.com/d/ojtuxylzbobwybz

mark-y wrote on 9/11/2023, 7:21 PM

I thought this was the problem all along, but I bit my tongue bc John has a handle on this stuff. Your file is 1920x1080 horizontal, with a pillarboxedboxed vertical image measuring only 608x1080 pixels. That is caused by turning your phone sideways. That is the best you will do in Vegas 13 without it being fuzzy.

"I'm taking the vertically videos via my phone ..."

Quit it!

@john_dennis will take you the rest of his way with one of his mini-tuts, or -toots.

 

 

john_dennis wrote on 9/12/2023, 8:42 AM

@laimaidan

Based on the encoded date and time for the sample file that you uploaded, I suspect it is not the "original camera file". I need the original camera file or I'll just add to the confusion. It doesn't have to be your scenic shot. It could be a video of your cat.

General
Complete name                            : C:\Users\John\Downloads\Untitled.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (mp42/isom)
File size                                : 1.16 MiB
Duration                                 : 467 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 20.9 Mb/s
Frame rate                               : 29.970 FPS

Encoded date                             : 2023-09-11 23:49:51 UTC
Tagged date                              : 2023-09-11 23:49:51 UTC

Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Baseline@L4
Format settings                          : 3 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 3 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 467 ms
Bit rate mode                            : Variable
Bit rate                                 : 20.7 Mb/s
Maximum bit rate                         : 18.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 29.970 (30000/1001) FPS
Standard                                 : NTSC
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.333
Stream size                              : 1.15 MiB (99%)
Language                                 : English
Encoded date                             : 2023-09-11 23:49:51 UTC
Tagged date                              : 2023-09-11 23:49:51 UTC
Color range                              : Limited
Codec configuration box                  : avcC

Audio
ID                                       : 1
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 427 ms
Bit rate mode                            : Constant
Bit rate                                 : 192 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 9.91 KiB (1%)
Language                                 : English
Encoded date                             : 2023-09-11 23:49:51 UTC
Tagged date                              : 2023-09-11 23:49:51 UTC

 

laimaidan wrote on 9/13/2023, 5:22 AM

Sorry John, I no longer have original files.

The method you described above worked with them, but not working with rendered files and I dont udnerstand why.

Dexcon wrote on 9/13/2023, 6:25 AM

I no longer have original files.

That's a problem because the video that you've uploaded is in the horizontal 16:9 aspect ratio (AR). The original 9:16 phone video vertically fills the 16:9 AR but with extensive black bars L and R of that image. The black bars are part of the 16:9 image - that it contains a 9:16 AR image does not make that video a 9:16 AR video. So what you get on your phone after rendering is completely expected. To have avoided this, the original 9;16 phone video should have been rendered in Vegas Pro using 9:16 sizes in Project Properties, not 16:9 as seems to be the case.

What you can do now is, in Vegas Pro, set up Project Properties to 9:16 dimensions. Doing that, I get this in Vegas Pro (20):

Then use Track Motion to zoom the image to fill the whole 9:16 frame (i.e. no black bars). In 'Render As...' choose your render template and click on 'Customise Template'. Click on 'Frame size' and in that field choose 'Custom Frame size' and manually set the W/H sizes to the 9:16 ratio. Then render ... the render should then be a vertical 9:16 render and show full-frame on your phone in vertical mode.

Unfortunately, the quality will not be good because the original vertical phone footage (presumably 1920 or higher) has been squished to 1080 when it was rendered to that 16:9 mp4 video, and then blown up to 1920 using the above process. The only thing that would help is an uprez FX ... but you would need a recent version of Vegas Pro to get that FX or have a 3rd party FX package that includes an uprez FX. But it's doubtful that even such an FX would make much difference because the zoom in using Track Motion will something like a 3x zoom in.so the vertical resolution will likely be around 360 lines - a big drop from the original 1920 lines or higher. That's getting back to VCD/SVCD video resolutions of the late 1990s.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

Former user wrote on 9/13/2023, 6:49 AM

Then use Track Motion to zoom the image to fill the whole 9:16 frame

@Dexcon Hi, Is Track motion better then using Pan/Crop to correct video? Is there any difference?

Dexcon wrote on 9/13/2023, 7:17 AM

@Former user  ... Yes ... in Pan/Crop 'Lock AR' needs to be turned off and, for the OP's video, the pan/crop frame had to be manually sized to match the full size of the 9:16 frame particularly the height. Track Motion was a simple resize of the borders. That of course is not to say that that will always apply to all 9:16 videos. It was much more straightforward using Track Motion.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

mark-y wrote on 9/13/2023, 7:26 AM

This is not complicated ;?)

Use Event Pan/Crop (not Track Motion).

I used Vegas Movie Studio 13.

Your image is 608x1080 on a 1920x1080 screen.

  • 1. Set Project Properties to 608x1080
  • 2. Set Event Pan/Crop to 608x1080
  • 3. Set Render Template to ........ (you guessed it!)
  • 4. Here is your file. Same as Source Aspect Ratio. 608x1080 9:16
  • *Please don't try to upscale 1.78x in Vegas 13. Download the trial of Vegas 21 if you want to experiement with the newer technology.
Former user wrote on 9/13/2023, 7:34 AM

@Dexcon Ok, thanks, yes Lock AR' needs to be turned off, personally I'd find Pan/Cop easier but I guess it depends how familiar with the controls you are. I don't see the 'particularly the height' issue tho?

Dexcon wrote on 9/13/2023, 7:41 AM

but I guess it depends how familiar with the controls you are

Very familiar - some 13 years familiar with pan/crop and track motion.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

Former user wrote on 9/13/2023, 8:02 AM

@Dexcon I was ref to the OP who didn't seem to know what the problem is or how to fix it (or anyone else new to VP), obviously not you.

Dexcon wrote on 9/13/2023, 8:11 AM

@Former user ... Thanks for the clarification. The misunderstanding arose because the "but I guess it depends how familiar with the controls you are" phrase was in the sentence addressed to me by the use of the @myname tag.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

Former user wrote on 9/13/2023, 8:24 AM

@Dexcon Ok my apologies, text can be easily misinterpreted if not fully spelt out 👍

laimaidan wrote on 9/14/2023, 5:58 AM

I no longer have original files.

That's a problem because the video that you've uploaded is in the horizontal 16:9 aspect ratio (AR). The original 9:16 phone video vertically fills the 16:9 AR but with extensive black bars L and R of that image. The black bars are part of the 16:9 image - that it contains a 9:16 AR image does not make that video a 9:16 AR video. So what you get on your phone after rendering is completely expected. To have avoided this, the original 9;16 phone video should have been rendered in Vegas Pro using 9:16 sizes in Project Properties, not 16:9 as seems to be the case.

What you can do now is, in Vegas Pro, set up Project Properties to 9:16 dimensions. Doing that, I get this in Vegas Pro (20):

Then use Track Motion to zoom the image to fill the whole 9:16 frame (i.e. no black bars). In 'Render As...' choose your render template and click on 'Customise Template'. Click on 'Frame size' and in that field choose 'Custom Frame size' and manually set the W/H sizes to the 9:16 ratio. Then render ... the render should then be a vertical 9:16 render and show full-frame on your phone in vertical mode.

Unfortunately, the quality will not be good because the original vertical phone footage (presumably 1920 or higher) has been squished to 1080 when it was rendered to that 16:9 mp4 video, and then blown up to 1920 using the above process. The only thing that would help is an uprez FX ... but you would need a recent version of Vegas Pro to get that FX or have a 3rd party FX package that includes an uprez FX. But it's doubtful that even such an FX would make much difference because the zoom in using Track Motion will something like a 3x zoom in.so the vertical resolution will likely be around 360 lines - a big drop from the original 1920 lines or higher. That's getting back to VCD/SVCD video resolutions of the late 1990s.

Thank you but I still have the above question: why on PC everything looks good ?

Dexcon wrote on 9/14/2023, 6:33 AM

... why on PC everything looks good ?

Because your Vegas Pro project is in the horizontal 16:9 aspect ratio. In that video, the vertical phone footage fills the height of the 16:9 frame - but that image also includes black bars L and R of the phone video. Those black bars are part of and embedded in that 16:9 image That you only see the vertical phone image does not in any way make that the video is a 9:16 video - it is a horizontal 16:9 video with a lot of black surrounding that vertical phone video. The black L/R bars are not an invisible element of that video - they are part of the image and could easily be turned another color.

If your phone allows rotation of images/video, turn your phone to horizontal and your Vegas Pro project should display on your phone as you see it on your PC.

When editing vertical phone footage and you want to keep it in vertical 9:16 for viewing vertically on a phone, every step of the editing process must be done with project properties set for the 9:16 aspect ratio. Unfortunately with your project, the Vegas Pro project has been done using horizontal 16:9 which has resulted in that 16:9 video displaying the way it does on your phone when viewed vertically.

It is surprising that you haven't kept a copy of the original camera video - storage (e.g. memory stick, memory card, external HD) is just so inexpensive these days, and it has always been wise thing to do to keep at least one backup copy of video for times when things go awry.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16, 17, 18, 19, 20 & 21, HitFilm Pro 2021.3, DaVinci Resolve Studio 18.5, BCC 2023.5, Mocha Pro 2023, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

laimaidan wrote on 9/20/2023, 5:22 AM

 

Thank you Decxon. This is how it looks on my PC. Why I cant just cut the part in the middle and adopt it to the phone ? Or Vegas do not have this feauture ?

Former user wrote on 9/20/2023, 7:44 AM

@laimaidan Hi,

Why I cant just cut the part in the middle and adopt it to the phone

You can & this has been explained, what you see on your PC is either 16:9 or 9:16, it's hard to see the difference on a media player on your PC.

This is your 16:9 pic in the comment above, I cropped it & rendered it as 9:16, you see they both look the same on the VLC player, How does it looks on your Android?

This is how that rendered 9:16 video looks on my phone.

 

mark-y wrote on 9/20/2023, 8:31 AM

Why I cant just cut the part in the middle and adopt it to the phone ? Or Vegas do not have this feauture ?

🙂

This is not complicated ;?)

Use Event Pan/Crop (not Track Motion).

I used Vegas Movie Studio 13.

Your image is 608x1080 on a 1920x1080 screen.

  • 1. Set Project Properties to 608x1080
  • 2. Set Event Pan/Crop to 608x1080
  • 3. Set Render Template to ........ (you guessed it!)
  • 4. Here is your file. Same as Source Aspect Ratio. 608x1080 9:16
  • *Please don't try to upscale 1.78x in Vegas 13. Download the trial of Vegas 21 if you want to experiement with the newer technology.