Wayne Waag
2
COW Coins
Forum Replies Created
-
My Panasonic HC-V770 encodes video using the MPEG-4 AVC/H.264 codec, and was told, this codec is not suitable for editing in most non linear editors including Vegas, Adobe Premiere and Apple. This problem seems to be found throughout the Panasonic camcorder product line.
Whoever told you this does not know what they’re talking about. The vast majority of consumer cameras use the MPEG-4 AVC/H.264 codec as well as many prosumer products. I have a couple of Sony Handycams that use this format and there is no problem editing in Vegas. I also have a number of Panasonic products including a ZS3, ZS20, and FZ200 that record with that codec and they all work just fine in Vegas. Both the ZS20 and FZ200 record at 1080 60P and there has never been a problem with low audio. Something is either wrong with your particular camera or the way you have it set up.
There is also the odd chance that something is amiss with your PC. Suggest you upload a short 5 sec clip to something like Dropbox so someone have a look just to confirm that there is a low volume problem with your clip and not your PC.
wwaag
-
Knowing nothing about your specific camera, are you sure you haven’t set the audio record level to manual with a very low gain. If it’s set to auto-gain, have you tried simply “playing” the recorded files in your PC’s media player such as Windows Media Player or VLC? If they are all “low”, then you may have a problem with the camera itself.
wwaag
-
E-mail accounts often have a fairly small file size that can be attached. Rather than re-render and lose a significant amount of quality, why not create a Dropbox account, upload it, and then give your recipient the URL so that it can be easily downloaded.
wwaag
-
I use a GoPro Hero4 Black with Vegas Pro 13. I just import 2.7K or even 4K files directly to the timeline –no need to transcode to Cineform. This is by far the best approach, unless your system is not sufficiently robust. You’ll need to provide your system specs for someone to answer.
wwaag
-
The easiest way would be to simply create a fairly large image (or series of images if you have lots of titles) along with the text titles in something like Photoshop or any image editing/graphics program. Then drag that image to the timeline and use keyframes in the Pan/Crop window to create the movement from one text title to the next. BTW, I enjoyed watching the video–very nice.
wwaag
-
That’s not your problem since Vegas Pro V10 does NOT support GPU for effects processing. AFAIK, V10 only supports GPU rendering using the Sony AVC format If this is what you are using for renders, simply open the render dialog box, select the custom button which will bring up the Customs Settings-Sony AVC window. In the very bottom under Encode mode, select using CPU only.
If this doesn’t solve your problem, you will need to provide detailed information about the media you are using (screenshot from MediaInfo), Project Settings and Render Settings (screenshots). All in all, it seems highly unlikely that your problem has anything to do with GPU.
wwaag
-
The problems you describe have been around for a long time and I doubt that they will be resolved. Users often report that they can access certain fonts in Legacy Text but not Text and Titles. However, there are so many advantages of using the newer Text and Titles, especially if you use Vegasaur, that it seems a shame to use the older Legacy Text.
Here’s something to try if you haven’t already. It’s one way of getting fonts to show up in Text and Titles that normally don’t. I just did this with a font named Allcaps. It would show up in Legacy Text but not Text and Titles. First open Word and if it shows up there, select the font and type something. Then copy and paste into your Text and Titles window. Then save that as a Preset. It will still show the font to be Verdana, but the actual font will be the one pasted from Word–in my case Allcaps. You can change the usual things such as font size, Bold, Italics, etc. Whether this technique will work for Hansen or its special characters, I have no idea but it might be worth a try. Good luck.
wwaag
-
You should really try to figure out why you can’t render from your own computer. For help, you would need to provide details about your source media, project settings, and render settings, as well as information about your PC.
If you must send your project to someone else, you must include all of your media files as well as your project file. Since your media files are probably located in different folders, the easiest thing is to create a new folder and then do a project “save as” to that folder, making sure that the “Copy media with project” box is ticked. In this way all of your source media will be copied to the same folder, making it much easier for someone else to open your project and do a render.
wwaag
-
Smart resample is checked for all clips!
That is the default and for most situations, it really shouldn’t matter matter so long as all frame and render rates are the same. It’s only a problem if you have mixed rates. For example, filming at 60P and rendering at 30P with smart resample checked leads to interpolated frames and a ghosting effect. To be on the safe sides, it’s probably best to always disable resampling.
wwaag
-
[John Parks]
First-time poster!
First, welcome to the forum.
Since both were shot at 1080 30P, I presume that you are also rendering at 1080 30P. You will always get some judder if there is any significant movement at this frame rate. If both your media frame rate and render frame rate are the same (30P), it shouldn’t matter, but I’d still Disable Resample for all of your events to see if that makes a difference. From what you describe, it sounds like Vegas is trying to smart resample for some reason.
wwaag