Render Issue

Sging2 wrote on 7/22/2022, 6:20 PM

I really hope someone can help with this as its driving me insane. I rendered a video of 1 hour 12 minutes, it plays great up to around 45 minutes and then says when played on the PC players, unsupported encoded settings, how can it play 45 minutes and then say this, when uploaded to Vimeo it also only uploads to the 45 minutes. I have tried all settings including default Vegas settings to render. Its 4K and at one point it all rendered ok and played but I had to make a few small changes but now cant get it to render and play the full video. I rendered from just before the 45 minutes to the end to see if there was something causing this but that section renders and plays fine so there's no issues with the content. Any ideas before I change to another editing program as this has cost me so much lost time, I have a client waiting in it.

Comments

john_dennis wrote on 7/22/2022, 9:17 PM

Post the Mediainfo report for the failing rendered file. Focus on C1 from this:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

I would also like to see a graph from Bitrate Viewer for the failing file.

Sging2 wrote on 7/23/2022, 6:40 AM

Hi John, thanks for your time. This is a strange one and I had it before on a long render, but when I changed the Preset back to Default it rendered ok but not this time, I have also tried AVC instead of NVENC but it was the same. All the shorter renders up to around 30 minutes with exactly the same settings and media content are all fine so it seems it happens when a project is heading to around an hour.

I couldn't do the graph as the Mediainfo wouldn't show this format. I just copied the project into a another Vegas file hoping this would sort and I watched it render right up to the last frame in the preview window but when I played it I get the same message, graphic attached. I thought it may be the Windows video player but Vimeo only upload just over the first half as well. Hopefully the images attached will help you spot something. But advise if I can supply anything else that may help.

I may try rendering now without GPU as I have a good PC.

Video File Mediainfo 

Render Settings

This is what I get when i play it but over the first half plays fine.

PC SPEC

Cheers and thanks again for your time.

 

PS On this project, New Blue Tilter 7 crashes when I open it to edit as well, fine on the other two related project files which is also strange.

Stephen

Musicvid wrote on 7/23/2022, 7:54 AM

And does the same thing happen when you use the software Mainconcept encoder?

Have you updated your Nvidia drivers?

rraud wrote on 7/23/2022, 9:37 AM

Does this happen on all media players? Try MPC (Media Player Classic) and VLC (VideoLAN). The default Win players are quirky.

3POINT wrote on 7/23/2022, 10:35 AM

The default Win players are quirky.

Not my experience, actually I prefer it above third party players.

Sging2 wrote on 7/23/2022, 10:56 AM

I have, it happens on both players. I have also tried rendering using the AVC and NVENC so far but even Vimeo wouldn't upload the second half after 45 minutes, it has to be the rendering as I watched it render up to the last frame in the preview window.

If I render the first half and second have separately they will both play ok. It seems to render differently as it goes on if the render is a long one. I just rendered a 30 minute one with the same content from the same cameras and that finished successfully. I will see if there's an update for the GPU now but I do keep it up to date and its the studio one.

I haven't tried Mainconcept  yet. Problem is every test of it takes over 2 hours as I have to do it all each time and I have now run it several times with different settings.

 

Thanks for all your time on this.

john_dennis wrote on 7/23/2022, 1:11 PM

@Sging2

Suffer me one more silly question.

45 / 72 X 6.89GiB ~= 4.3 GiB

What is the file system of the disk where your output file is stored?

  • Bitrate Viewer is a separate application from Mediainfo that can be downloaded from here:

https://www.videohelp.com/software/Bitrate-Viewer-2

If you put your failing rendered file back on the Vegas timeline, what do you see? Can you play in Vegas?

Sging2 wrote on 7/24/2022, 4:10 AM

The file is stored on a 1TB Scratch Drive a Samsung NVMe SSD, there's about 5GB spare on it at the moment. Strangely I rendered it again last night with settings I used and failed before with and it all rendered successfully using using this template. I still need to try and get to the bottom of this as I don't want to lose this much time again just trying get it rendered.

I dropped the last failed one on the timeline and this one only rendered up to 25 minutes this time, the last one showed up to 45 minutes but here's what it shows on the timeline, the full file with only 25 minutes that's playable.

Bitrate Graph, the file is 1hr 10 but the graph only mapped the 25 minutes

matthias-krutz wrote on 7/24/2022, 7:44 AM

@Sging2

I would try to free up more space on the destination drive. From my observation, Vegas needs twice the free space on the destination drive to render. Unfortunately, there is no error message when there is not enough space.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

j-v wrote on 7/24/2022, 8:06 AM

Render Settings

Why are you not using the standard template for this kind of rendering?
Bitrate is much higher than the normal template as it shows with me

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

john_dennis wrote on 7/24/2022, 9:48 AM

@Sging2

I tend to agree with @matthias-krutz that you are on the edge of a cliff with "about 5GB spare" on the target disk. There is probably a file management or hardware solution to your problem. Surely, your 1TB disk is showing red in Windows File Explorer.

Notice that my ARCHIVE-0 disk is close enough to full that I've added ARCHIVE-1.

Howard-Vigorita wrote on 7/25/2022, 9:19 AM

@Sging2 Another possibility is that your disk format might be Fat32. That would truncate render files to 4gb. Check disk properties. Fwiw, all my Samsung t5's come in pre-formatted exFAT and work fine for big renders.

Sging2 wrote on 7/25/2022, 1:49 PM

Thanks guys for looking into it. I seem to be getting it to render ok now all of sudden but using the AVC standard template with no changes. I keep two wedding projects on this scratch drive, one I have just about finished and one I am just starting. We use around six cameras for weddings, including drone footage so the space soon get swallowed up especially if its UHD. I have nearly finished one of two project as work in progress so I can move this one off there over to the archive drive as soon as I have had the thumbs up from the client.

 

Thanks again everyone.

Stephen

Former user wrote on 7/25/2022, 9:27 PM

Render Settings

Why are you not using the standard template for this kind of rendering?
Bitrate is much higher than the normal template as it shows with me


@j-v He's using GPU encoding, If the results from this Benchmark using low latency gaming encoding profiles tracked the same way for MagixAVC default profiles then he needs higher than 24mbit for best quality. That's the trade off, larger files compared to software encode for comparable quality.

As an example when using Voukoder using quality settings(23) and using identical file format 3 reference frames, 3 B frames, GOP250 GPU encoded files are 25% larger for a 4K30 8bit encode. 68mbit/s for Nvenc vs 54mbit/s x264 software encode, and personally I don't use a CRF of 23 if the output is being fed into another encoder such as YouTube or Vimeo, I"ll use a smaller CRF with much higher bitrates.

Based on this, the default MagixAVC template bitrate is too low