Rendering m2v to m2v

-tom wrote on 4/29/2015, 9:23 AM
Hi, I see I can finally import m2v files to the timeline (though they can take a loooong time for Vegas to load - not sure what it's doing there). The problem is when I try to render the m2v on the timeline to another m2v, the render dialog comes up but sits at 0%, for hours, and I end up killing the process.

I have 2-3 m2v's on the timeline to render out to one. The reason I have multiple m2v files and can't do a complete render from my original source files is because Vegas consistently crashes before my renders complete, so I have to do it in pieces. This is becoming very frustrating. I have color matching filters, so I turn on GPU otherwise the build will take days. To render 2 hours of timeline, I get random length renders before the crashes, so I restart the render from that point and continue the process till done. However, I have photos and text for credits, and generated text + GPU = sure fire crash.

I thought I'd swallow the crash issues and accept them and just take my piecemeal m2v renders and do a final one so I don't have to re-render transitions, color filters, etc, but just build the single file out of the 3 or 4 piece m2v's I have on the timeline.

Is there a trick to getting the timeline m2v files to render out?

Thanks
Tom

Comments

musicvid10 wrote on 4/29/2015, 9:39 AM
m2v is the HDV MPEG-2 camera format, one of the oldest and most stable in Vegas since HD was introduced a decade or so ago. It will smart-render in Vegas, taking only minutes instead of hours if everything is set to match.

Find out where the crashes and slow system are happening first. That is far from normal, and even modest systems will handle HDV with ease.

Have you by chance installed a codec "pack" at some point? You "might" have to start with a clean OS install.
Are you trying to work off some kind of NAS drive?

-tom wrote on 4/29/2015, 11:19 AM
HDV, MTS, m2ts are no problem, just the elementary stream rendered m2v placed back on the timeline it seems. Elementary mpg is no problem either.
I did try a clean install of Win7 Ultimate to an SSD with only Vegas installed, but crashes, or I should say just frozen/ sopped renders still happened.
Interesting that when pulling the m2v into DVDA, it takes an excessive amount of time as well to digest. Once done, playing, scrubbing, etc. is fine, but it takes forever to digest the elementary stream.
musicvid10 wrote on 4/29/2015, 12:45 PM
Your Vegas version?
-tom wrote on 4/29/2015, 2:54 PM
Version 13 build 444. Running on an older Dell 690 workstation with dual xeons, 12gb ram, gtx 560ti and ssd. Win 7 ultimate. 6 camera multicam editing with 4 hdv streams and 2 avchd.
VidMus wrote on 4/29/2015, 3:23 PM
What cameras (models) are your source files from?
-tom wrote on 4/29/2015, 3:28 PM
Canon HV 20/30 HDV and Canon HF G10 for the MTS avchd files
PeterDuke wrote on 4/29/2015, 7:36 PM
Try "muxing" your raw .m2v file (single stream) to .ts with tsMuxer or similar. Vegas doesn't like inputting elementary streams.
-tom wrote on 4/29/2015, 7:55 PM
May have found the issue - When loading up the project, I noticed the message "reading closed captioning from file" in the bottom left of the workspace. I usually cancel this (not sure why it's on in the first place). This time, I let it finish doing whatever it was doing. Now it's rendering out the m2v. So.... perhaps related to CC or perhaps hitting "cancel" on the "reading captions" operation doesn't really kill the thread but keeps it or suspends it and the render is forever "blocked" by that thread. A hypothesis at least.
musicvid10 wrote on 4/29/2015, 8:41 PM
Vegas has had trouble with text tracks before.
Glad you found a direction to follow; along the same lines, the suggestion made to run it through TsMuxer is a good one.

john_dennis wrote on 4/29/2015, 8:52 PM
Use the procedure I described in this thread to turn off scanning for closed captions. Scanning is on by default but is completely unnecessary and undesirable if you don't care or you don't have any.
-tom wrote on 4/29/2015, 9:31 PM
Short lived happiness till the render froze part way (again). tsmuxer is great and fast but that appears to be forcing vegas to re-render what I already rendered, or at least it seems that way. When vegas can digest the m2v file it renders out with "no recompression necessary". Turning off the caption reading didn't seem to help.
So my choices now seem to be wait an hour for it to read the captioning and digest the m2v's then pray for a complete render or let it start re-rendering the mux'd files faster and hope for no noticeable loss in quality (and hope that render completes as well). Look like a roll of the dice and a long night no matter which way I go. It shouldn't be this difficult.
PeterDuke wrote on 4/30/2015, 2:24 AM
Don't take too much notice of what Vegas says about smart rendering MPEG2. See my large post on 1/15/2015 12:32:24 PM towards the end of the thread in Vegas does not truly smart render MPEG2

Edit

The time/date of the post I referenced is for GMT+11. You may need to adjust for your time zone. I wish this forum had post numbers within a thread.