Bob Peterson
Forum Replies Created
-
There is always, of course, the option of training material such as those John mentioned. I suspect that, if you think parent-child is the “big” issue that is not fully explained, that you have not yet begun to grasp the capabilities of Vegas. There is a LOT to understand, and I’m not so sure that such things can be included in the documentation that comes with a modestly priced software package such as Vegas Pro. That’s why there is a market for third party training. It wasn’t that long ago that VASST used to do two day training sessions in various cities around the country. Those didn’t begin to cover everything either.
-
How then do you know that the stutter is not being produced by your playback software for any one of several possible reasons? I suspect that it needs to be burned to the appropriate disk format, and played by a player before you can point at Vegas.
-
How are you viewing this rendered video?
-
If the original dimensions of the image are 700×1073, then you have a VERY low resolution image. It would be challenged to produce anything larger than a 4×6, and the 4×6 would be a bit marginal. However, if 700×1073 is a cropped size and the crop is being done in Photoshop, then the image must be saved in Photoshop. If you use a low quality setting (i.e. high, lossy compression) when performing this save, then the image will deteriorate.
Low resolution images tend to look “soft” or somewhat out of focus. They do not look blurred. Blurred photos look “smeared” rather than “soft”. I have never seen a soft image rendered as blurred unless a filter is applied to it.
I have never seen Vegas blur a still photo. I don’t think it is capable of making that large of a change in a photo. I would check for filters on the track where the still image is being placed. As far as format, I prefer PNG. It is lossless, and Vegas handles it very quickly and easily.
-
How do you know that the image is not blurry when you capture it? You should know that jpeg is not a great format for images. The format itself will create problems in the image if the compression used when saving it is too high. You should also crop the image so that it is roughly the size that Vegas needs within the video. A rule of thumb is that it should be no more than twice the video resolution as measured by horizontal and vertical pixels.
If your preview is set to best/full, you are seeing the image as it was delivered to Vegas.
-
If you don’t use high quality disks, you can’t blame the software when your disks do not work. The name of the game is high quality media. You cannot try to minimize media costs, and obtain good results. You might want to check into Tiger Direct for TY media in quantity packages. I find large cylinders of Verbatim DVD-R disks at Sam’s Club.
-
What is the brand name of your DVDs, and what burning speed are you using?
-
Yes, they were properly encoded, and, as I said, DVDA 3.0 prepared and successfully burned the disk using the exact same file that DVDA Pro 5 refused to play. 3.0 did so without rerendering the files. The burned disk plays successfully on the computer using WMP, and on a TV using a Sony Blu-ray player.
Unfortunately, these files were occupying roughly 26 gigs of hard drive. Once I successfully burned my disks, I deleted the original source files. Further experimentation is not possible. I will have to chalk it up as a possible “feature” in DVDA Pro 5.
-
I’m at a loss then to explain it. The file used by DVDA played in its entirety with WMP although without sound, but the preview function in DVDA cut off after four seconds just as it did on the burned DVD.
-
I just rendered a 2 hour video on my single processor, 1 gig memory system with 9.0c. It did not crash at all on any of the renders. The last one took about 22 hours to complete, but, as noted, finished successfully. However, the source was a DV file which seems to be one of the easiest to render. A lot depends on the difficulty of handling the source file format.