4K render looks like crap!

[jungleexplorer]

Okay. I got a new camera. It shoots 4K footage. The footage out of the camera is good, but when I render it in VS 2019, the resulting footage looks awful. I have tried everything in VS.

Test 1. Add sample 4K clip to the timeline. Go to Share. Select VS 4K preset. Render. RESULT = Video that looks like you are watching a movie through a glass window on a rainy day.

Test 2. Add sample 4K clip to the timeline. Go to Share. Select "Same as First Clip". Render. RESULT = Video is jittery and loops in about 1-second intervals over and over while audio track plays on normally

Tets 3. Add sample 4K clip to the timeline. Click on SAVE. Select "Save Trimmed Video". Result = Video is jittery and loops in about 1-second intervals over and over while audio track plays on normally.

[Ken Berry]

In VS Preferences, have you ticked the create Proxy files box? If so, do you wait for the proxy files to be created? Have you thought about changing the preset template for proxy files to something of your own creation e.g. 720p? Have you tried it with proxy turned off?

I ask because I believe there is a serious problem in VS 2019 with the proxy files -- with the final video being in fact the proxy files instead of the edits made during the proxy process being in the end applied to the original files... The problem with not producing proxies for 4K files is that even with a powerful computer like yours, editing 4K clips without the proxy will be pretty awful. So think about creating your own template for the proxies instead of using the preset...

[jungleexplorer]

In VS Preferences, have you ticked the create Proxy files box? If so, do you wait for the proxy files to be created? Have you thought about changing the preset template for proxy files to something of your own creation e.g. 720p? Have you tried it with proxy turned off?

I ask because I believe there is a serious problem in VS 2019 with the proxy files -- with the final video being in fact the proxy files instead of the edits made during the proxy process being in the end applied to the original files... The problem with not producing proxies for 4K files is that even with a powerful computer like yours, editing 4K clips without the proxy will be pretty awful. So think about creating your own template for the proxies instead of using the preset...

I have all proxy and smart render settings turned on. I was shooting on three cameras simultaneously when I took the footage I am having trouble with only the footage out of the V50 pro.
Camera 1: Akaso V50 Pro (shooting 4K).
Camera 2: SJCam SJ7 Star (shooting 4K).
Camera 3: Samsung Galaxy S8 smartphone (shooting HD).

I have rendered the footage out of the Sj7 and the Galaxy S8 with no problems. The rendered footage out of those cameras looks as good as the original files. So it is not the VS settings that are the problem.

There is a difference, however. The SJ7 and the S8 both record to an MP4 file, whereas, the V50 Pro records to a MOV file. So, to eliminate this as a factor, I converted the 4K file with Handbrake to an MP4. The resulting MP4 file out of Handbrake, looks as good as the original MOV file out of the V50. But when I rendered the new MP4 file that I produced with handbrake in VS, I got the same final result as I did when I rendered the original MOV file. The original 4K MOV file is too large to upload (3.6GB), and since I can find no way to trim it down to give you just a sample without destroying it, I will provide you with a sample of the rendered footage so you can see what is happening. This sample file was rendered using the VS 4K/30p preset.

https://www.dropbox.com/s/ui30ajbl1qk8t ... 1.mp4?dl=0


Here are the technical details of the original file extracted with Mediainfo.


General
Complete name :Akaso V50\20170101_121110.MOV
Format : MPEG-4
Format profile : Base Media
File size : 1 005 MiB
Duration : 2 min 9 s
Overall bit rate : 65.3 Mb/s
Encoded date : UTC 2017-01-01 12:11:10
Tagged date : UTC 2017-01-01 12:11:10

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High
Format level : 5.1
Format settings, CABAC : Yes
Format settings, Referenc : 1 frame
Muxing mode : Container profile=Main@5.1
Codec ID : avc1
Duration : 2 min 9 s
Bit rate : 65.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.262
Stream size : 1 003 MiB (100%)
Encoded date : UTC 2017-01-01 12:11:10
Tagged date : UTC 2017-01-01 12:11:10
Color range : Full
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec_configuration_box : avcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec
Codec ID : mp4a-40-2
Duration : 2 min 9 s
Source duration : 2 min 9 s
Bit rate mode : Constant
Bit rate : 128 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 : 1.97 MiB (0%)
Source stream size : 1.97 MiB (0%)
Encoded date : UTC 2017-01-01 12:11:10
Tagged date : UTC 2017-01-01 12:11:10

[jungleexplorer]

I figured it out. The issue is with the AVC codec. I rendered the file with the HEVC 4K preset in VS and it turned out great.

[jungleexplorer]

Well, I thought I had it fixed, but not quite. The video quality was good, but something did not seem right with the video. On close observation, the video was slightly jumpy. Dang! Well, it is back to the drawing board.