Crash When Rendering 4k

[Ken]

Greetings -- I have searched "4k" and only found 1 thread that included this criteria, so i apologize if this subject has been previously discussed. I read the other thread and learned a lot. However, i would like to post my issue in hopes of finding a possible solution (although i believe i already know what the solution may be).

I created a *.vsp file and would like to render it to a 4k video. However, when i try, the software VSU-2021, crashes and shuts down. I see the file name gets created, but the new file file size is zero. I'm working within the "Create a Video You Can Play on a Computer" "ACV/H.264" Share option. My everyday Profile is: AVC (1920x1080, 30p 20mbps). I have made many videos with great success using this resolution. However, when i change the profile to: AVC 4k(3840x2160,30p 40mbps) leaving all the other settings the same, the software crashes and shuts down in about 60 seconds.

After reading a previous post on a related 4k subject, i understand that a Faster CPU and/or more RAM is needed to render to 4K.

The

The file size of the *.vsp file is only: 205kb
The file size of the *.m2t file using my everyday resolution settings is: 3.3g

I'm running Windows 10 on a 280gh Intel CPU with 16gb Ram.

Any ideas will be very helpful.

[Ken Berry]

Is the original video in the vsp 4K or HD (1920 x 1080)? If it's 4K, are you using SmartProxy to create lower resolution copies ("proxies") of the original which are much easier to edit and don't flicker? (When satisfied, the edits are applied to the 4K originals.) Is there a specific reason why you chose AVC 4K e.g. because the original video is AVC HD? Have you tried using the button to the right of the AVC/H.264 button i.e. MPEG-4? You still end up with a video calling itself mp4 but using a different codec?

[Ken]

All very good questions, Ken. The original files out of the camera are a *.m2ts, 1920x1080. The original *.vsp is (if i understand) as i mentioned in the OP. I'm not sure i understand what the Smart Proxy is. I have attached a screen shot of the Share Tab if that will help. No, i have not tried using the MPEG-4 button. I will certainly try that and get back. Meantime, would you be kind enough to point me to some information about the Smart Proxy. This sounds like a subject i need to learn about as it was also mentioned in another post. Thanks, Ken, for your help!

[lata]

Hi
Please provide a little more information regarding you original video files.
From the timelines right click one of you mts clips for properties......
Either copy the details to your post or create an image of that panel to attach here.

Now go to Settings – Project Properties, these ideally should be the same as the video clips properties.
I suspect your original video properties to use 1920 x 1080, using a frame rate 29.97 and interlaced.
Assuming the project properties are same as your clip a process called Smart Render will help when using Share.

From Share – top left is an option “same as project settings”, place a tick in the box to activate this option, now change option to ”same as first video clip”
Take note of the settings showing in the properties panel, create an image as your earlier post.

[Ken]

Hello Trevor -- attached are three screen shots. The first is the properties of the *.m2ts file. The second is the Project Properties. I made the changes you suggested. However, i no longer have the option to render to 4k file. In fact, i have no output options at all.

So, i followed an earlier suggestion from Ken by changing to an MPEG-4. See screen shot called Share 4k. The file was created and my software DID NOT crash! I am now uploading the video to YouTube to see if i notice any difference from the others.

My feeling is it will be the same. I'm also wondering if i need to change some settings in my camera to accommodate for a 4k video.

Back story: I don't have the hardware to view a 4k video, except my iPhone. The reason why i would like to make a 4K video (on occasion) is so the viewer (me and others) can enjoy a higher resolution video when accessing the video on YouTube. I hope that makes sense.

[Ken Berry]

You'll find an explanation of SmartProxy on pp. 42-43 of the PDF User Guide to VS 2022 under Help in the VS menu.

I am, however, a little confused. You obviously don't currently film anything in 4K resolution (3840 x 2160), but in high definition (1920 x 1080). And essentially you are wanting to upgrade this to 4K. I am hoping you realize that doing so is unlikely to improve the quality of your original video. As the old saying goes, you can't make a silk purse from a sow's ear. If anything, you will be lowering the visual quality of the final product. I realize the YouTube is moving towards 4K but that doesn't mean they will be dropping High Definition video. I would in fact imagine that they would prefer to receive good quality HD video than poorer quality 4K.

You say you don't have the hardware to play 4K video. That doesn't mean you can't play it. Depending on what software you have, the freeware VLC player will happily play your 4K even if what you are seeing on your non-4K monitor is not quite 4K quality.

I might also comment on your Project Properties screen shot. You said in your own comment on it that you no longer have any output options at all. But of course you still do. The Project Properties shot is just of... well ... properties, not output options. They are still there under the Share tab for AVC/H.264 and MPEG-4.

Anyway, you appear to have successfully produced a 4K using MPEG-4 without VS crashing, which is progress. But you still have to make up your mind as to whether you really want to convert your HD video up to 4K.

As for your camera, what is it? Did you buy it because it can film in 4K, or is it limited to HD? Look up the camera's manual to see what resolutions it can film in, and how to set them if it can in fact film 4K.

[Ken]

Hi Ken and thank you for your insight. This is where my ignorance of the subject matter enters in. Every word of your reply makes perfect sense. I have some reading to do.

Thanks for your help!!