I'm having trouble creating a complete video file in v9.
The first half (or so) of the video file works fine, but then the second half is not included in the output file except for a few seconds towards the very end. The project file works (play/edit/etc) OK all the way through in the hVideoStudio application so I'm mystified. I tried recreating the project file and got much the same results.
If I turn the Windows performance tool on, I can see that at about half way through creating the video file the 'writing to disk' stops which is consistent with the symptoms above.
Any ideas anyone ???
The original file is about 5gig and 90minutes long. The project attributes are ....
PAL (25 fps)
MPEG files
24 Bits, 720 x 576, 25 fps
Upper Field First
(DVD-PAL), 4:3
Video data rate: Variable (Max. 8960 kbps)
Audio data rate: 256 kbps
MPEG audio layer 2, 48 KHz, Stereo
Cheers
Only half a video file being created
Moderator: Ken Berry
-
Trevor Andrew
Hi Jeff
Strange!
We need a bit more information.
What do you mean by ‘output file’?????
If you create a Mpeg 2 file of your project you can play the file on your pc.
Quote:
The first half (or so) of the video file works fine, but then the second half is not included in the output file except for a few seconds towards the very end.
Unquote:
Where are you playing this file, is it a dvd or a Mpeg 2 file.
Before burning a dvd you should create a video file ( share-create video file)
You indicate that your file is 5 Gb (are you using a dual layer burner?) If not:-
If you have a 90 minute video you will have to reduce the bit-rate to 6000 Kb/s in order to fit to Dvd.
I would change the project settings to 6000 Kb/s, leaving all the other settings as is.
To be sure about the rate use a bit-rate calculator http://dvd-hq.info/Calculator.html
Now Share - Create Video File / Same as Project Settings. (may take some time to render)
Use the new file to create a disc.
You can create a dvd folder (TS folder) which you should be able to play on your pc.
The frame ‘upper field’ indicates that the footage was an analogue source?
Hope this helps
Trevor
Strange!
We need a bit more information.
What do you mean by ‘output file’?????
If you create a Mpeg 2 file of your project you can play the file on your pc.
Quote:
The first half (or so) of the video file works fine, but then the second half is not included in the output file except for a few seconds towards the very end.
Unquote:
Where are you playing this file, is it a dvd or a Mpeg 2 file.
Before burning a dvd you should create a video file ( share-create video file)
You indicate that your file is 5 Gb (are you using a dual layer burner?) If not:-
If you have a 90 minute video you will have to reduce the bit-rate to 6000 Kb/s in order to fit to Dvd.
I would change the project settings to 6000 Kb/s, leaving all the other settings as is.
To be sure about the rate use a bit-rate calculator http://dvd-hq.info/Calculator.html
Now Share - Create Video File / Same as Project Settings. (may take some time to render)
Use the new file to create a disc.
You can create a dvd folder (TS folder) which you should be able to play on your pc.
The frame ‘upper field’ indicates that the footage was an analogue source?
Hope this helps
Trevor
-
jeffmagrath
Hi Trevor,
Let me tackle your questions first ...
Yes the output file is an mpeg2 file from v9/share/create video file function. I havn't burnt a DVD for this yet - but do have a LiteOn external dual layer burner/DVD's.
I'm playing it with WinDVD v5 on the IBM laptop (IBM 1.5 Ghz, 1gig ram, 50 gig disk, USB2, latest version of XP pro).
The source is analogue Hi8 camcorder, with an avermedia mpeg2 compression device into video studio v7. Then I run v9 for editing.
Interestingly ... when I look at the properties for the input/output mpeg2 files they are both similar in size (as I would expect given the minor editting I'm doing) in terms of file duration (5699/5562 sec), video frames (142k/139k) and audio samples (273m/266m), but the file size is dramtically different (5.7/2.3 GB). All other attributes are the same (format: DVD, Type:MPEG2 UFF, 24 bits, 720,576, 4:3, Rate: 25 fps, Data: variable max 8960, audio mpeg2 layer2 48000hz 16bit, stereo, 256kbps).
Very strange (& frustrating).
Let me tackle your questions first ...
Yes the output file is an mpeg2 file from v9/share/create video file function. I havn't burnt a DVD for this yet - but do have a LiteOn external dual layer burner/DVD's.
I'm playing it with WinDVD v5 on the IBM laptop (IBM 1.5 Ghz, 1gig ram, 50 gig disk, USB2, latest version of XP pro).
The source is analogue Hi8 camcorder, with an avermedia mpeg2 compression device into video studio v7. Then I run v9 for editing.
Interestingly ... when I look at the properties for the input/output mpeg2 files they are both similar in size (as I would expect given the minor editting I'm doing) in terms of file duration (5699/5562 sec), video frames (142k/139k) and audio samples (273m/266m), but the file size is dramtically different (5.7/2.3 GB). All other attributes are the same (format: DVD, Type:MPEG2 UFF, 24 bits, 720,576, 4:3, Rate: 25 fps, Data: variable max 8960, audio mpeg2 layer2 48000hz 16bit, stereo, 256kbps).
Very strange (& frustrating).
-
Trevor Andrew
My first impression is that you have inadvertently removed a portion of footage.
Start a new project,
insert your raw video clip.
click the ‘project’ word adjacent to the start button
click the 3rd button from the right to take you to the last frame.
What is the duration in the digital timer.
Open your edited project and repeat the above
The times should be about the same, assuming you haven’t removed many frames?
Start a new project,
insert your raw video clip.
click the ‘project’ word adjacent to the start button
click the 3rd button from the right to take you to the last frame.
What is the duration in the digital timer.
Open your edited project and repeat the above
The times should be about the same, assuming you haven’t removed many frames?
-
jeffmagrath
-
Trevor Andrew
Hi
I am thinking corrupt video files, but this is a little out of my league.
The only thing I can suggest at the moment is to switch off smart render when creating a video file.
Share / create video file / same as project settings / Options / un-tick perform smart render.
This should force VS to render all frames.
The process will take a lot longer to complete, but is worth a go.
Can anyone else suggest a solution to this problem?
With thanks Trevor
I am thinking corrupt video files, but this is a little out of my league.
The only thing I can suggest at the moment is to switch off smart render when creating a video file.
Share / create video file / same as project settings / Options / un-tick perform smart render.
This should force VS to render all frames.
The process will take a lot longer to complete, but is worth a go.
Can anyone else suggest a solution to this problem?
With thanks Trevor
-
jeffmagrath
Thanks Trevor,
Have tried Smartrender on/off with same results. Have also tried re-capturing the video - again same results.
The success I've had is capturing with a constant bitrate - this works just fine which is a relief.
Not sure why variable bitrate hasn;t worked for me - not sure if the 'project' bitrate settings (ie 9800) need to be aligned to the capture/mpeg setting of 8000/peak 9000?
Anyway thanks for taking the time to help out.
Have tried Smartrender on/off with same results. Have also tried re-capturing the video - again same results.
The success I've had is capturing with a constant bitrate - this works just fine which is a relief.
Not sure why variable bitrate hasn;t worked for me - not sure if the 'project' bitrate settings (ie 9800) need to be aligned to the capture/mpeg setting of 8000/peak 9000?
Anyway thanks for taking the time to help out.
-
heinz-oz
Do I get you right here? You have tried capturing with variable bit rate and had trouble, when capturing at constant bit rate, it was ok?
AFAIK, you cannot capture with variable bit rate because the system would need to scan the whole clip first to find out where there is a lot of motion content and to increase the bit rate there. If your device can actually do that (we don't know what you are using) your processor may not be able to handle the conversion in real time and corrupt the capture.
Please let us have a bit more info on what you are doing and how, with what equipment on what hardware/software base.
AFAIK, you cannot capture with variable bit rate because the system would need to scan the whole clip first to find out where there is a lot of motion content and to increase the bit rate there. If your device can actually do that (we don't know what you are using) your processor may not be able to handle the conversion in real time and corrupt the capture.
Please let us have a bit more info on what you are doing and how, with what equipment on what hardware/software base.
-
THoff
-
doctor
VS9 create video truncation problem
I've seen the "truncated output file" problem often with VS9, and managed to find a workaround for it: the key is never try to do more than 3 or 4 cuts in multi-trim at one time, and never load more than one clip into the timeline if you're going to do any cuts with multi-trim. If I break these rules I see the truncation problem at least 25% of the time.jeffmagrath wrote:Hi Trevor,
...
Interestingly ... when I look at the properties for the input/output mpeg2 files they are both similar in size (as I would expect given the minor editting I'm doing) in terms of file duration (5699/5562 sec), video frames (142k/139k) and audio samples (273m/266m), but the file size is dramtically different (5.7/2.3 GB).
...
Very strange (& frustrating).
As an example, imagine editing 9 ad breaks, call them B1 to B9, out of a 2 hour movie. To avoid the truncation problem reliably, I have to
1) load and trim out B1, B2 and everything after start B3, write file1.mpg
2) load and trim everthing up to the end of B3, B4, B5, everything after start B6, write file2.mpg
3) load and trim everthing up to the end of B6, B7, B8 and B9, write file3.mpg
4) load file1.mpg, file2.mpg, file3.mpg and write the final file.
It's a right pain, but it works for me, YMMV. With smartrender on it's acceptably quick. But there may be some other causes of the truncation problem that I haven't hit for which this workaround is ineffective or irrelevant.
I have to say VS9 is one of the buggiest pieces of software I've ever worked with, but it does the job if you treat it with kid gloves. I've also managed to avoid the audio synch problems I initially suffered (never normalize). The many import bugs I've had less success with.
Anybody heard any word on when VS9 will get it's first update?
I sure hope it's soon.
On the plus side, I was recently amazed to find that VS9 did a great job of converting some NTSC TV captures to PAL. Slow as hell but good PQ.