Bob Peterson
Forum Replies Created
-
I’ve got egg on my face again! Fair enough. I learned something very useful in this exchange. Thanks guys!
-
You are not looking closely enough. I also said you can move them. Perhaps you missed the point I made that you can only move them from one frame boundary to another when the Quantize option is turned on. Apparently, this is close enough for you, but it is bad information to tell people that the Quantize control does not need to be used. If you want to move audio within frames, you MUST turn off the Quantize control.
-
Not true. Yes, audio tracks can be moved when quantize is turned on, but they can only be moved in frame increments. Quantize is turned off so that audio can be precisely adjusted which is not possible when movements are limited to frame boundaries. I am usually synchronizing an audio file to audio which is part of a video event. Precise alignment is necessary to insure that the sound synchronizes with a speaker’s moving lips.
Just remember to turn quantize off after you are done synchronizing, or before you do things like splitting or moving video.
-
I think you would need to do this with a green screen. The background would then be shot independently.
-
64 gigs is probably enough for Windows, but I work hard to minimize the space used by applications on my 80 gig SSD. Whenever possible, I install applications to a much larger normal hard drive. Since your trouble began when you moved Vegas to the SSD, move it back to the hard drive.
-
How are you selecting the sample that you want the software to learn? The sample duration should be very short, and should not contain anything except the sound you want eliminated. Also, how loud is the hum or noise versus the voice you are trying to preserve?
-
My first guess is that your computer monitor needs to be calibrated, but you do not say what your comparison is. How do you know what the footage, as shot, looks like? In any event, Vegas can adjust the contrast if that is the only problem.
-
I am saying that the compressor produces slightly different results if you start at different points on the timeline. It is almost as if it is using something like a moving average in its computations. If it has more history, it will produce one result at a particular point on the time line. If it doesn’t have the same history, it produces a different result. I see this when the compressor flags a clip (i.e. the volume is too high and is clipping) at specific points. If I go back and replay the audio to see if the clip is audible, the compressor usually will not flag a clip (the meter turns red) at the same point. Naturally, I do not go back to the beginning of the timeline to replay the point in question. Instead, I start perhaps 10 or 15 seconds before the clip point.
I don’t know if the difference is audible, but I have observed this behavior for a long time now.
-
Are you applying a compressor to the audio track? I have noticed that compressor output differs slightly if you start at different points on the timeline. For example, if I start from the beginning and see it clip at some point, restarting at a point near the clip does not always reproduce the clip behavior.
-
Yes, there is. Take along a Zoom H4N. It can handle XLR mics, and can record in at least two formats (MP3 and Wav) at several different levels of precision and sampling frequency. Your camera should also record the audio to give you the ability to synch the Zoom’s file to the camera’s video. I do this as standard procedure, and it works like a charm.