Problem rendering - wierdness

Moderator: Ken Berry

Post Reply
meshuken

Problem rendering - wierdness

Post by meshuken »

I have edited about 20 projects on VS10+, half of them probably had some quirky Ulead issue that was solved by using this forum but I'm currently stumped and after 3 hours thought I'd finally ask.

I have a 4 minute 10 second project that consists of about 50 short video clips with a single song mp3 playing along. I only used about ten transitions.

The video is from a DV cam, and it shows I imported it as NTSC DVD MPEG2 video with LPCM audio 48000. These are the factory VS10+ settings that I have used for many other projects that have not had this problem.

My troubles began when I tried to create an MPEG file that I will then put on a DVD. I followed all the directions in the sticky like I normally do, and here is what happened:

1st attempt: Rendered all 4:10 but did not have any audio.
2nd attempt: Rendered 2:32 and froze program
3rd attempt: Rendered 2:08 and froze program
4th attempt: (I removed the mp3 to see if that was the problem) Rendered 2:32 and froze program.

I watched it while it rendered and here is the weird part: The status bar showing rendering progress would go to 20% and seem to hang up, then the preview screen would go black and it would zip up to 30% in a matter of two seconds, then seem to render normal again. Then at 42% it would race to 50% and finally it would hit 92% (when it was only on the second minute of the four minute video) and it would race to 99% where it would freeze the program and I would have to use alt-ctrl-delete to shut it down.

So I'm not sure what's up. Because I really massaged the 50 video clips to where I want them perfectly I will be pretty irritated if I have to redo the whole video again (several hours work or more).

Any suggestions on VS10+ bad behavior and how to coax my video out of it would be appreciated.

Thanks,

Mike

Windows XP
2.4 Ghz pentium
1 gig ram
320 GB HD w/ 250GB free
lancecarr
Advisor
Posts: 1126
Joined: Sat Dec 11, 2004 6:34 am
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: eMachines ET1861
processor: 3.20 gigahertz Intel Core i5 650
ram: 12GB
Video Card: ATI Radeon HD 5400 Series
sound_card: ATI High Definition Audio Device
Hard_Drive_Capacity: 700GB
Location: Taipei, Taiwan
Contact:

Post by lancecarr »

Just off the top of me head I am thinking that somewhere in there you have a corrupt MPEG file. Not the sort of corruption that will reveal itself on playback as the playback software generally has inbuilt correction. This is a sneaky kind of corruption that will only reveal itself when rendering a project. The fact that you captured directly to MPEG from the cam makes me think that. I'm sure you have had nothing but success doing that in the past but it only takes a little glitch in the works for it to happen. Personally I only capture to DV AVI then render to MPEG for burning.

I guess that's not really what you wanted to hear!

Oops! Forgot to give you a solution!

Load the project and try to render the first half only, then try to render the second half. By process of elimination you can keep rendering sections until you find the offending piece if that is, in fact, the problem.
Have you tried some general house keeping on the computer first? Defrag, clean out the garbage and temp files etc.
meshuken

Post by meshuken »

Ok, thanks I'll try your solutions... I just checked some old files I imported and they were all AVI-DV I have no idea why this camera is now importing as MPEG. Nuts. I wonder if I can recapture as AVI and just relabel the file so it substitutes and fits in where my MPEGS were? probably not...
meshuken

Post by meshuken »

ok, strange as this may sound:

I deleted the first half of the project and it still didn't render properly.

So I restored the first half and deleted the second half and still again it didn't render properly!

So that made me think maybe it was something else - I reloaded a project that I rendered last week with no problems at all and tried to render it again - guess what? Same problem! So something outside of the project itself is causing this.

Any ideas about ways to trouble shoot the issue?

Thanks!

Mike
lancecarr
Advisor
Posts: 1126
Joined: Sat Dec 11, 2004 6:34 am
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: eMachines ET1861
processor: 3.20 gigahertz Intel Core i5 650
ram: 12GB
Video Card: ATI Radeon HD 5400 Series
sound_card: ATI High Definition Audio Device
Hard_Drive_Capacity: 700GB
Location: Taipei, Taiwan
Contact:

Post by lancecarr »

First I would try some house keeping. Defrag and a clean up.
Then I would make sure I have NOTHING running in the background, screen savers, anti-virus etc., then try again.
Failing that I would use the repair function to repair VS by going to the control panel and choosing to remove VS then selecting repair.
Post Reply