Alludo USER to USER Web Board

Trying both v9 & v11 to chop up a 8Gb mpg file (Sony Hi8 cassette imported via CapWiz), but unable to get far enough into cutting (eg, by recording day) to do so. Ends up locking up and becoming "not
responding" within task manager or the hourglass just doesn't go away.

So how do I chop up an 8Gb file to edit further?


Product Level 1: VideoStudio
Product Level 2: Version 11+
Category Level 1: How-To
Category Level 2: Perform Task
win xp pro sp2
1.5Gb ram,
ext HD (30Gb+ free)
HP Pavilion dv5234us

Can you re-capture it in several smaller lengths, instead of one large one?

Welcome to the forums,

8GB MPEG file is rather large for a single file. This can be done however I think you're having problems due to a lack of resources.

30+ Gig of free space sounds like a lot, however when you're working with a large file, VS needs at least double the file size of free space to be able to work with it. If you just have 1 hard drive, this can take more time and resources, because VS must read and write to the same drive. When you don't have sufficient free space on your hard drive for large swap files, and RAM is lacking, things tend to bottleneck, which will lead to the program crashing.

I do most of my editing work on my desktop, which runs XP SP3 Home, using an AMD 2.0 Ghz processor, and only 1 Gig RAM. However I have more than 1 hard drive, so I can make up for the lack of RAM and processor, by splitting up the work a hard drive must do. I have the program reading from one disk, and writing to another.

I would highly recommend investing in a second hard drive. If you're running XP increasing the RAM ½ Gig really is not going to benefit you much more.

If you manage to get the whole clip inserted into VS, you may have to cut it, select the remaining clip and delete it. Now render (Share>Create Video File), the saved part. May or may not work, as I've not ran into this problem...

Before editing, do some PC house cleaning. Run Disc Clean-up and Defrag utilities. They are found in the Start>All Programs>Accessories>System Tools. Running Disc Clean up should allow you to clear the Temp files from the Temp folder, which over time can become quite full, and slow down a system.

Next you could try shutting down all background applications that are not necessary to run. Applications like your internet connection, antivirus, antispyware, chat or messenger apps, network connections. These tend to hog resources that VS needs..

Or, you might have a corrupted MPEG. This could be caused by a problem during capture, such as background operations interrupting the CPU, or by low-quality capture hardware & software.

An 8GB file won't fit onto a single-layer DVD, but there is no file-size limit for MPEGs, and size alone won't make Video Studio crash. (Although, I'm not sure what happens if you run out of disk space.)

You might be able to "repair" the file by re-encoding the MPEG with SUPER (FREE!!!). Since MPEG is lossy (as are most video compression formats) it's generally best to avoid recoding, but sometimes you are desperate...

For re-coding, you can choose a bitrate that's similar to the current bitrate for minimum quality loss, or if you're going to squeeze the file onto a single-layer DVD, you'll need to re-code to a lower bitrate anyway.

Or, a couple of programs that include "MPEG repair" tools are:
VideoReDo ($50 USD and up)
Womble ($50 USD an up)
These repair tools don't fix every problem, but both offer a free trial, so they are worth a try.

I've used 4.5GB mpg files in VS11.5 with no problems, and they don't take long to load. I found that disabling audio whilst scrubbing made the program significantly more responsive, and that's something you might try.

In VS11.5, go to "File>Preferences" or hit F6, and in the "General" tab, it's the very bottom checkbox.

I would tend to agree with Doug's suggeston that the most likely cause may be a corrupted mpg file, however.

Thanks for all your ideas.

1. mpeg
Was FINALLY able to break it up in 11, but then could get no further (feature bloat?). Had to re-edit in v9. So mpg is in fine shape.

2. resources
have had v9 running with 500Mg & 40+Gb. Seems File does NOT save directory preferences, so have changed ALL work/temp drives to External HD.

3. Am creating VOB & ISO files -- no burn, but this is the worst part:

IT HAS TAKEN 65 HOURS and shows no sign of completing!

I have reduced the file to <2hrs/3+Gb so what is the prob?!!!

Only thing I can think of is just have it create the VOB files and use Nero for the ISO conversion & final burn ...?

Hi ama3

Have to agree with Doug in a corrupt file.
You may be best to capture again to smaller sizes.

Have you used CapWiz successfully before or is this the first used?

You do not give any indication of the captured video properties, nor the properties used to render/create the new files. If these are not the same then rendering will take a long time. But 65 hrs is very long and only enforces the idea of a corrupt file.
Once you have created the new files from Share Create Video File (which should be the worst part) you should have no problem creating the ISO.

As a guide:-
You will get 60 minutes of full quality video to a standard single layer DVD. (8000kbps)
You will get 120 minutes of video at VHS quality (4000kbps)

How long is your video?

I have had no probs with CapWiz before; as you are aware the "properties" are Video clip 7.5 Gb. Nothing else.

Task Mgr is still showing 5-12% usage and everything looks fine. I was able to pass entire mpg thru v9, cutting up pieces, so I still don't see where mpg could be a prob. I have added effects, menus, so far ... I am creating VHS [SP] quality, to keep the entire script down to 3 DVDs (this is the 1st of 3)

Almost up to 3 full days of conversion ...

It finally locked up after 70+ hours ...

Now have input on one [external] drive and output on another [external] drive and am only creating VOB files. It has taken over an hour so far ...

It has now run over 26 hours. Task Mgr shows no change w/ PF usage @ 1.24 Gb and CPU usage is ~20%. CPU usage for vstudio is running 0-12%. Mem usage was 176K now 180K.

How do I know when to quit it and try something else?

I would have quit 25 hours ago.

I still think you have a corrupt file. Could be video, audio, etc. I think you would be better off chopping up your video and rendering in smaller chunks.