See my other post for history of my problem:
http://phpbb.ulead.com.tw/EN/viewtopic.php?t=28106
Now I am wondering about rendering to h.264, the newest version of flash player is supposed to read this.
I have tried several settings and have been very unimpressed with the quality. I have read many posts stating Ulead's h.264 is not the best. I have been unable to make a custom sized video in h.264. It seems to only allow preset settings. I usually render to 480x360 (biggest size that will fit in my web site design) The custom size setting in h.264 is grayed out. Anyone know a way around this?
Also, rendering to h.264 always crashes VS at the end of render, but still produces the file. I have version 11.5. Any reason for this?
Jason
H.264 size restriction?
Moderator: Ken Berry
VS will allow you to output to H.264 at 368x208 for widescreen or 320x240.
I wonder if you're not being over optimistic having a higher resolution on a web page. You would be limiting users to those having the fastest connections.
From my experiments with encoding digital camera video clips to H.264 with VS, I've settled on using AMR audio. Using AAC results in clicks towards the end of the clip, even with the latest patch and update. Taking a test 28,552KB 848x480 30fps .mov file, which uses mjpeg compression, I get reasonable picture quality encoding to 368x208 using H.264 Main compression, and a bitrate of 512 kbps, with a resulting file size of 1,536 KB. Using AAC audio the file size is reduced to 1,258 KB, but the audio is corrupted. By contrast, encoding the .mov file to 16:9 mpeg-2, 8000 kbps with Dolby 2.0 results in a file size of 18,994 KB.
I can successfully encode to H.264 with AAC audio if I first encode the source .mov clip to mpeg-2, but that workflow involves re-encoding the video twice, which will result in lower final quality.
If you're not satisfied with the output quality, you should increase the video bitrate - but if you can't achieve the desired picture quality for a given file size, you'll have to reduce the resolution.
I've found that a freeware program called MeGui can give better results when encoding to H.264 than VS, and can also output to any resolution you choose - so you might give it a try - but it's certainly not as user-friendly as VS!
As for why your VS is crashing - you might look in the Event viewer logs for clues. There are just too many possible configurations of software and hardware for it to be possible to come up with a cause without more information.
I wonder if you're not being over optimistic having a higher resolution on a web page. You would be limiting users to those having the fastest connections.
From my experiments with encoding digital camera video clips to H.264 with VS, I've settled on using AMR audio. Using AAC results in clicks towards the end of the clip, even with the latest patch and update. Taking a test 28,552KB 848x480 30fps .mov file, which uses mjpeg compression, I get reasonable picture quality encoding to 368x208 using H.264 Main compression, and a bitrate of 512 kbps, with a resulting file size of 1,536 KB. Using AAC audio the file size is reduced to 1,258 KB, but the audio is corrupted. By contrast, encoding the .mov file to 16:9 mpeg-2, 8000 kbps with Dolby 2.0 results in a file size of 18,994 KB.
I can successfully encode to H.264 with AAC audio if I first encode the source .mov clip to mpeg-2, but that workflow involves re-encoding the video twice, which will result in lower final quality.
If you're not satisfied with the output quality, you should increase the video bitrate - but if you can't achieve the desired picture quality for a given file size, you'll have to reduce the resolution.
I've found that a freeware program called MeGui can give better results when encoding to H.264 than VS, and can also output to any resolution you choose - so you might give it a try - but it's certainly not as user-friendly as VS!
As for why your VS is crashing - you might look in the Event viewer logs for clues. There are just too many possible configurations of software and hardware for it to be possible to come up with a cause without more information.
JVC GR-DV3000u Panasonic FZ8 VS 7SE Basic - X2
-
jasonrn2000
- Posts: 7
- Joined: Fri Sep 29, 2006 12:57 pm
Thanks for the info. I looked into MEgui but it does not solve my problem - reduce encoding time. Right now is a 2 step encode process: final edit to .mov then .mov to .flv. This process produces pretty good results, but is very time consuming. If I use Megui - it is still a 2 step process. I was looking to either encode once using the smart render - which is fast, then to .flv. Or encode directly to h.264 being that the newest flash player supports this.
I tied other editors such as the trial of Vegas. This worked for h.264, however it does not give progressive download like the h.264 file from Ulead. Strange? Plus I'm used to VS.
I like the look of the bigger video size. With larger monitors these days, 320x240 seems so small. I guess I didn't think of the limits because of the progressive download feature with .flv.
Jay
I tied other editors such as the trial of Vegas. This worked for h.264, however it does not give progressive download like the h.264 file from Ulead. Strange? Plus I'm used to VS.
I like the look of the bigger video size. With larger monitors these days, 320x240 seems so small. I guess I didn't think of the limits because of the progressive download feature with .flv.
Jay
Have you tried the "Export To Mobile Device" Selection(s)?
These are presets but may work.
One problem could be the codec that VS is using to read the MJPEG video file from your camera. If you are getting errors at the end of an encode then before encoding trim a few seconds off the end of the file, there may be some corruption at the end of the video.
These are presets but may work.
One problem could be the codec that VS is using to read the MJPEG video file from your camera. If you are getting errors at the end of an encode then before encoding trim a few seconds off the end of the file, there may be some corruption at the end of the video.