Thank you for comment and taking interest in helping, and sorry I forgot about mediainfo. I'm slightly confused as I open up the veg file and only get this:

General
Complete name                            : C:\Users\inzad\FILMS\Capture\Steve music\Correstwo\Corest3-8K-render.veg
File size                                : 27.0 MiB

however I get this info on the vegas rendered output file that won't load back into vegas (but plays fine on my VR pc, so not a corrupt file), is that what is needed?:

General
Complete name                            : C:\Users\inzad\FILMS\Capture\Steve music\Correstwo\Renders\Corestwo-8K-render.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 15.9 GiB
Duration                                 : 3 min 12 s
Overall bit rate                         : 711 Mb/s
Writing application                      : Voukoder (VEGAS)

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L6
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 3 min 12 s
Bit rate                                 : 711 Mb/s
Width                                    : 8 192 pixels
Height                                   : 4 096 pixels
Display aspect ratio                     : 2.000
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.706
Stream size                              : 15.9 GiB (100%)
Writing library                          : x264 core 164 r3065 ae03d92
Encoding settings                        : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=17.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 3 min 12 s
Source duration                          : 3 min 12 s
Bit rate mode                            : Constant
Nominal bit rate                         : 320 kb/s
Maximum bit rate                         : 320 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
Source stream size                       : 7.32 MiB (0%)
Default                                  : Yes
Alternate group                          : 1
mdhd_Duration                            : 192044

You can render and upload 1~2s of sample video for everyone to test.

yes of course ...only it takes about 30mins + to upload the veg file (it's pretty big!!) so you'd have to wait

I post that I tried and didn't get much so was confused...

General
Complete name                            : C:\Users\inzad\FILMS\Capture\Steve music\Correstwo\Corest3-8K-render.veg
File size                                : 27.0 MiB

what exactly should I be doing? Excuse my not understanding here. Are the encoder setting not on the mp4 file data I've posted?

Sorry, my bad. Did you try unchecking legacy AVC decoding? That is the normal state.

We were asking about your rendered mp4 file, not your .veg project file. It contains no media.

Thanks - if you look at my attached jpegs it shows that I checked the legacy AVC coding (on help tips from Josh at Scrapyard films - youtube channel) and jpeg also shows all the setting changes from default I made in vegas, if that helps

lol, 'English not my native language' - I'm as English as you get 😂 but sometimes not very good at typing quick responses. Not sure if you are being sarcastic re first language, but I thought you meant not checking the AVC for when I rendered the video rather than for when I tried reloading the video back into vegas; sorry I misunderstood that. I have this checked after watching a video by Josh at Scrapyard films and he states having this unchecked means SV uses (to quote) 'SO4 compound reader DLL code written to help boost the performance but it causes crashes' - link here starting at the point of interest (just checked and the video start time doesn't work on this hyperlink - it's at 1min 50 secs into the video):

Has he got a valid point in suggesting always ticking the legacy AVC box? Also this veg file was actually crashing lots (around the 60% rendered mark) doing this veg file render before I did the changes recommended in this video. I even had dynamic ram at zero prior to these changes, as someone posted on a help video that zero helps solve some problems I was having a while back - I'm guessing that wasn't helping! I'm in the process of doing a render with this very same file and so my SV18 is engaged in that atm but will try asap. I have done a 2 sec clip but want to check it first on my own vegas but currently doing this other 4k mp4 render while the veg is loaded (as it takes so long to load up) - it says I have about 40 mins remaining and once done I shall try relaoding this clip into vegas and if same error I will post clip on here and also try your helpful AVC box unchecked suggestion.

Thank you again for your help

I encourage you to undo all of those setting changes as they degrade performance and media compatibility in the name of stability. Unless you're having crashes avoid them, and even if you are it's better to try to address the cause (likely related to media type) than these workarounds.

A reset will put them all back at once.

For the render in versions of Vegas <19 when using the GPU (VCE, QSV or NVENC) if you have crashes you can temporarily set dynamic ram preview to 0MB and disable GPU in preferences/video if needed to complete the render, but restore them before editing again or performance will suffer.

Thanks RogerS. I have to say I'm very confused now. Josh, the guy at Scrapyard films is obviously no novice and makes a lot of excellent videos using Vegas. His tips certainly worked in me getting a render from this veg file that was crashing (crashed continually before changes - worked after) but you are saying don't stick with them? He seems to suggest it improves performance but you say not. If you could spare the time, I'm sort of only imtermediate vegas standard, can you educate me as to why his recomendations degrade performance and compatibility?

Josh is here on the forum as well. He's giving generic advice that helps some systems and I don't begrudge anyone trying to help people. In past videos he didn't really disclose the downsides of these fixes, though in the VP 19 videos he did a better job.

If you enable legacy AVC, no 10-bit files or other recent file types will load. You also lose GPU decoding that can help with performance if you are using a reasonably modern GPU that Vegas supports. Legacy HEVC is a little trickier- I'd keep it checked unless you're working with iPhone or other HEVC that won't load otherwise.

Dynamic ram preview is a preview buffer. Disable it and you somewhat reduce performance for both preview and render. You can test this yourself. Go to the other extreme and set half your system ram to this and Vegas has little other ram to work with, especially if you have other ram-hungry programs in the background.

For VP 18 and 19 I'd reset to defaults, update GPU drivers (help/driver update), and if you use variable framerate media or difficult to edit HEVC, re-encode it constant framerate AVC and your problems will likely disappear without disabling major parts of the program. But the best advice is specific and requires specific information about system hardware, drivers, media and Vegas settings.

(I have no idea about 8K VR and there may be bugs related to it I am completely unaware of as it's not something I have any use for)

Thank you for taking time to explain all that. tbf to Josh he did say in the video that enabling legacy AVC would stop 10 bit but I got the impression if not using 10 bit then it was better to tick the box. I am confused about dynamic ram though. I have seen videos that say put it to zero to avoid certain rendering problems (it's a while since I saw that video so can't direct to it). I understand assigning a load of it would restrict other software use of ram but, otherwise, is there any possible downside to having, say, half your ram assigned to vegas? The variable framerate thing was really interesting, thank you, I had no idea of that. In this video though everything was a single frame jpeg or png but I have used all sorts of different framerate video together in the past and probably will again (like downloads from youtube, old video footage etc).

I understand if English is not your native language. Did you try not checking legacy AVC decoding, like this?

Then:

• Click Apply
• Click OK
• Close Vegas
• Open Vegas again
• Try loading your MP4 rendered file

I hope that is clear enough for you to follow, and best of luck. I am on vacation, so other conscientious members may be able to help you further. Also, uploading a very short sample to Drive or Dropbox will help, as @lan-mLMC suggested.

Instructions for resetting Vegas to default values are here, if you should ever need them.

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

 

just to confirm this solved my problem about reloading an 8k mp4 video, a video I had rendered in vegas using Voukoder. The video rendered fine with this boxed tick, and the legacy box ticked was one of a number of changes I did (thanks to Josh at Scrapyard Films) that stopped this render constantly crashing, so I can't say specifically which change solved it (the list of them is on the jpeg attached). However the video wasn't reloading with this legacy AVC box ticked - also to confirm English is my first (and, embarrassingly, only) language 😄 but tbf I wasn't clear (justifiably I think) what exactly was meant on the first response.

Thank you very much 'musicvid' for solving this and also to RogerS and Ian for offering help and advice. I hope this helps others that may experience the same problem. Steve 🙂

Legacy AVC most likely conforms to standards, above 4K is not legal for AVC, while default allows AVC above 4K but without GPU decode, which begs the question why even using x.264 8K AVC without gpu decode, playback is going to be horrible, takes a long time to encode, why not use NVENC 8K HEVC for which should be faster at encoding and then you have GPU decode on playback in media players and on timeline when you bring it back in. 8K in vegas is still not going to be a pleasant experience.

Thank you Todd-b. I think I understand (most of) that. 😄 I really struggled to find a way to render in Vegas at 8k in this 360 format (2:1 frame size ratio) and I got pointed, on this forum, to Voukoder, which was the only thing I found that worked. However the 8k 360 videos really struggle to get played back ....is that what you are saying with gpu decode missing? VLC media player is supposed to do it but it either didn't even load my 8k renders or stuttered really badly. like playing only 1 frame every 200 (and my workstation is no slouch). These videos do play back on YT (once it puts its VP9 codec on it) and Steam VR (although still struggled to find an 8k VR player that worked, but Mermaid was one that did). I also found that, with the Voucoder CRF set to 17 it stutters a bit (this with a i9 32Gb ram and RTX Geforce 3090!), whereas a render with CRF set to 21 plays back smoothly. I guess it has to do with the filesize as the former is about 16Gb whereas the latter about 5Gb. So, a tad confused; is NVENC 8K HEVC an option to use in Vegas for doing these renders?

And don't despair, lots of English speakers don't speak good video, such as the difference between encoding and decoding. This basic glossary may clear up some things as you're getting started. Best of luck, welcome to the forums, and trust those who will ask you over those who tell you what is best for you.

https://www.vegascreativesoftware.info/us/forum/speaking-good-video-a-beginner-s-guide--104463/

Further resources are found here:

https://www.vegascreativesoftware.info/us/forum/got-questions-consult-the-tutorials-first-please--120282/

AVC is restricted to 4K, so in case of your Nvidia GPU it will not hardware encode above 4K, and strangely won't decode above 4K at all, Because above 4K is not legal for AVC you get strange things happening with software encoders also. Therefore people will normally use 8K HEVC encode via Nvenc which is legal, and the created files will playback with GPU decoding.

What you were doing with converting the 8k to 4k is creating a legal format which then uses GPU decode, so it appeared 4K was so much easier to playback but it was the combination of lower resolution AND gpu decode now working.

You should find 8K HEVC files created via NVENC will playback smoothly in media players(software) with hardware media players (connected to your tv etc) they probably would playback if modern enough, while older devices will have a 4K limit.

But as for editing 8K AVC(no decoder) vs 8K HEVC(gpu decoder) at PREVIEW/QUARTER, I'm not sure who would win on a Vegas timeline

MusicVid - lol, ok fair point. However I'm not on vegas much of the time, just use it to compile images made in other software, so don't be too judgemental. As a highways designer I bet I could pick you up on a lot of road use definition that is constantly misused (esp by the like of journalists at the BBC and such). It's something I have to live with but try not to get too arsey or sarcastic about, as I understand it's reasonable most people aren't familiar with the correct terms. 🙂

Todd-b - wow thank you, I had no idea about NVENC with 8k or that I had the option to use in with Voukoder. This sounds like it could be sooo helpful to me!! So, if I can pester you again. what would be the best format to render in to upload into youtube? Would there be a difference given youtube compresses it, whatever, with its VP09 codec or would the HVEC option somehow give better results? So if I render in HVEC, it should playback much better on my pc in media players, as it is able to use my gpu (have I understood that correctly?)

I think you misinterpreted my purpose, and for that I will remain quiet and keep my promise not to post on the general forums again until after the New Year.

Best of luck, sorry you felt slighted; it was not my intention. I'm very glad you found your solution, and welcome to the forums, unconditionally.

@vkmast

MusicVid - Please don't remain quiet, you are clearly very excellent, and I think operate at a high IQ level, at understanding problems and solving them, and very generous of you to give people, like me, your time in helping them, and I thank you lots for doing that; it's wonderful this option is here with people like you to answer questions, really appreciated. However, it can be intimidating for people, not as experienced as you and not using video editing that much, to dare to ask more novice or intermediate questions, if they think they will feel belittled by unfamiliarity of terminology. We're not all as good as you using Vegas and understanding video editing. encoding/decoding - you are right of course but I (probably wrongly) thought a coding bit of software, if loaded, just sat there and did both en & decoding

. what would be the best format to render in to upload into youtube? Would there be a difference given youtube compresses it, whatever, with its VP09 codec or would the HVEC option somehow give better results? So if I render in HVEC, it should playback much better on my pc in media players, as it is able to use my gpu (have I understood that correctly?)

Yes HEVC 8K should playback on your media player better compared to 8K AVC. for me HEVC 8K uses between 15-30% cpu, but AVC 8K up to 65%. This is with 12cores, so you're going to max out your CPU quicker with the 8K AVC on a lower spec CPU. If a particular player is terrible at playback with HEVC 8k check task manager to ensure it's using GPU decode, there may be a setting you can change if it's not

No quality differences between HEVC and AVC, and I recall reading that the time it takes YouTube to encode your videos is about the same, there is no decompression processing penalty for uploading HEVC