Sony Vegas renderd file has codec problems

[Hellis 0]

I have a project that is 23:30 min long.
It currently concists of three videoclips, nine musicfiles, ~70 text.

I use the following settings at render:
Sony AVC
Video render quality: Best

Vido format: AVC
Frame size: Custom
width 1920, height 1080
Allow source to adjust frame size, No.

Profile Baseline
Entropy coding CABAC
Frame rate 60
Allow source to adjust frame rate, Yes

Field order: none(progressive)
pixel aspect ratio: 1
Bit rate: 15 000 000

Audio format: AAC
Sample rate: 48 000
Bit rate: 160 000


Format: mp4


The three videofiles used in the project is also render in Sony Vegas with the exact same settings.
Each of those files are a "workaround" due to the issue of large number of files will take up to much memory.
So by editing smaler files and then combining them Vegas can handle the load.

The problem is when I render this file Sony Vegas completes it but the file is corrupt after finnish.
Media player says it's codec issues, Quicktime says it's "a file quicktime don't understand".

if I render a smal part of this project, that file works.
Is there some "sizelimit" when creating mp4's in Sony Vegas?

[DSE 3]

nope, no size limitation on mp4.
Question; can you put the rendered file back on the Vegas timeline to edit it?
Also, what are the source file formats?

[Hellis 0]

DSE

nope, no size limitation on mp4.
Question; can you put the rendered file back on the Vegas timeline to edit it?

Good question!
Don't know. I deleted the file and are trying to render it again (fourth or fifth time now)
Will try it if it fails again.

Quote

Also, what are the source file formats?

It's from a GoPro black 1080@60 fps, and still images from a old canon DSLR.
The still images were 4000x3000 pixles but I resized them to 1920x????
Can't remember the exact size. But it was because Vegas has to resize them otherwise.
So in order to make it easier for Vegas, I resized them.

But the "current" project is video only since everything has been renderd once.

[Hellis 0]

Render is done again.
Nope, the file can't be played nor be pulled in to Vegas again.

Vegas says: "None of the files dropped on Vegas Movie studio Platunum could be opened".

So it creates files it can't open. Great...

[DSE 3]

likely, you're killing your RAM with the stills. In preferences, set the RAM to 0, see if that fixes things.

[Hellis 0]

DSE

likely, you're killing your RAM with the stills. In preferences, set the RAM to 0, see if that fixes things.

No, the render I'm doing now has no stills at all.
It's a video that is already renderd that contains images.

But at this stage Vegas only have videos, that in some areas are "the same" because the images has been renderd to a video.

But you are correct that having stills in the project was too much for Vegas, it ran nicely untill it hit a still image and then Vegas crashed.

But this render finnishes without any problems, with plenty of ram to spare.
Normally Vegas crashes at about 1150 MB, but rendering this project it only reaches a max of ~1060 MB of RAM.

[DSE 3]

I still don't know the source files.
If the source is a rendered video already, then it's no longer files from a GoPro. it's something else.

[Hellis 0]

DSE

I still don't know the source files.
If the source is a rendered video already, then it's no longer files from a GoPro. it's something else.

In that case the answer is, the same as this projects settings.

[DSE 3]

The project settings don't address the bitrate nor output format/file format.
They only address framerate and resolution for display/project purposes.
You had to have chosen a format for output. It may have been mp4, uncompressed, XDCAM, DV, HDV, REAL, Windows Media/WMV, mpeg2 any number of formats.

This is likely where you're getting bogged down, not understanding file formats and what you're outputting.

[Hellis 0]

Read post #1

All the settings are listed there.
Those are the output/render settings.
If those are not the ones you are looking for then I don't understand.

As I said earlier I have used the same settings every time

[DSE 3]

OK, we're missing an important component of the conversation.
If you're rendering the individual clips to mp4, you may well be pushing the CPU beyond its limits.

Right click one of the subclips/previously rendered clips. Open the Properties menu, and grab a screenshot of the "General Properties" tab such as the one attached here.
That'll help a lot

[Hellis 0]

By some reason I can't resize the window to fit all the info so I just copied the info.

Quote

General
Name: part2.mp4
Folder: C:\Users\Hellis\Documents\Vegas Movie Studio PE 9.0 Projects\Project\Renders
Type: MainConcept AVC/AAC
Size: 1,06 GB (1 086 272 040 bytes)
Created: den 6 november 2013, 18:20:15
Modified: den 6 november 2013, 18:55:31
Accessed: den 6 november 2013, 18:20:15
Attributes: Archive

Streams
Audio: 00:09:48,245, 48 000 Hz; Stereo, AAC
Video: 00:09:48,225, 59,960 fps progressive, 1920x1080x32, AVC

Summary
Title: Project

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: mcmp4plug.dll
Folder: C:\Program Files (x86)\Sony\Vegas Movie Studio Platinum 9.0\FileIO Plug-Ins\mcmp4plug
Format: MainConcept AVC/AAC
Version: Version 1.0 (Build 2210)
Company: Sony Creative Software Inc.

Part 1 is the same settings, but the filesize is 1,39 GB (1 425 341 485 bytes).
And part 3 is about 68 MB.

[DSE 3]

you're rendering to p60. That alone is killing the encoder, based on what appears to be a not-optimal system.
You're also losing a lot of quality rendering the submaster to .mp4, then re-encoding to mp4 again.
The data doesn't show the bitrate, but that's not terribly important (and I'm too lazy to do the math).

Anyway...I'd have rendered the subs to something more manageable, such as sequential png or even uncompressed.

The issue *likely* is that your system can't manage the decode/encode at the same time. If you still have the master project (before you rendered the subclips) then you might be able to still set the RAM to zero, and try a master render from there.

[Hellis 0]

Will try to render it as uncompressed, and then using the files in the project.

The mp4 we talked about earlier has a Data rate of 14683 kbps and total bitrate of 14771 kbps.
(according to windows details properties)


And i changed the RAM to 0, but I'm not sure it's a memory issue.
The render just finnished (again) and failed (again) and I noticed Vegas only used 960 MB of RAM in the task manager.


But I see now that I run it uncompressed it is only 193 MB.

[Hellis 0]

uncompressed was too large for my harddrive.
Could not find a way to make both part 1 and 2 to fit, so I had to abandon that.

I managed to render it in 30 fps mp4, but I wanted 60.
Tried other Mov settings and failed, tried a bunch of wmv settings that also failed.

After probably 15 failed attemps I downloaded the trial version of Vegas 12.
And it worked on the first try, quicker and with great result.

I think I need to upgrade my Vegas....

[DSE 3]

why do you want p60? It's mostly for acquisition, not for playback.

[Hellis 0]

It flows better