Bob Peterson
Forum Replies Created
-
No, it was centered at 20112 hz with a volume which was about 70db higher than the frequencies below and above it. It began spiking at, if I’m reading Rx 3 correctly, 19906 hz, reached its peak, and returned to the average volume level at 20276 hz. There are no other significant peaks on the frequency curve. Rx3 displays the frequencies in a wave form as a secondary scale on its horizontal axis. There was a very narrow band which was quite loud. That was what made it easy to remove. I simply selected the band, and attenuated everything within the selection. The denoiser may have removed a few other peaks that perhaps complicated the issue.
I’m afraid I have no idea what caused it. In writing this note, I decided to be a little more precise with the repair by taking out just the band I mentioned above. In the first attempt, I simply drew a circle around the bar, so it took out a bit more of the high frequencies. I plan to send you this revised version.
-
OK, I figured out the upload and link. I also downloaded and accessed the file. So all is working for me. Yes, I’ll be glad to send you my email.
-
OK,here is the link to the uploaded file;
https://forums.creativecow.net/readpost/334/8792
Now, I’ve got to try and remember how to add a link.
-
I processed the file in Izotope rx3 advanced. It does indeed have a 20khz tone which is quite large in amplitude, and which I can hear. I used the spectral repair tool in rx3 to remove this 20khz tone. There was still a little noise in the recording which I heard during the silent periods between the words the speaker was saying. I used rx3’s denoiser to reduce this noise substantially. It sounds much better to me, but I’m old enough that I’ve lost some of my ability to hear high frequencies. See what you think.
I’ve tried twice now to upload the file using the upload file icon, and it has not worked. Sorry, but it may be tomorrow before I can try to figure out how to do this upload.
-
20khz is at the upper limit of human hearing. That, plus the inability of the EQ to kill it, suggests that the noise is below 20khz. If you haven’t tried it, the Graphic Equalizer should absolutely kill any sound in that range. Just add two points to the curve, and pull the last section of the curve (15khz to 20khz for example)to -inf. If that does do it, you can slide those two points down to lower frequencies until it hits your noise. That will at least tell about what frequency it is.
BTW, you can render out a wav file by simply choosing wav for the kind of file you want the render to generate.
-
One thing you could try is to render the video to a wav format. Check that file to see if your noise is still present. If the noise is not present, bring the wav file into your project, and use it as your audio source for the mp4. If it is present, you can either adjust your fxs in Vegas, or analyze/remove the noise from the wav file with an audio editor if you have one.
-
I suggest you start by telling us what format is being used by the recorded videos.
-
It could simply be your preview setting. To see full quality video in preview, you should use Best -> Full. However, if you leave it set to best/full, your frame rate in preview will probably drop.
-
There is one aspect of photos which you are missing. Although the jpeg of a given photo always retains the same number of pixels, it does not always retain the same level of quality, or sharpness. That is because varying levels of compression are used in jpegs. Thus, a jpeg with a resolution of 655×480, or 655 pixels x 480 pixels, can be saved in one rendition with a file size of 78kB and in another rendition with a file size of 200kB. Those two versions of the image, when reopened, will both still have the same pixel count, but one will be substantially less sharp than the other. It will have noticeably less quality and detail. That is because jpeg uses a lossy form of compression when it saves the photo. Lossy means that pixels are literally discarded when saving the image to a file, and an algorithm recreates them when the image file is reopened for viewing. Within Photoshop and probably other photo programs, the amount of lossiness can be set when the image is saved.
Images saved in the tiff format are compressed, but the compression is lossless. When reopened, the image is perfectly recovered so that the reopened image is the same as the image which was originally saved. I’m not sure about pngs, but is looks to me like they are not compressed at all.
-
That depends on your project, and how you are capturing the image. I have a project which is set to use 720×480 which is standard definition. If I use Photoshop to capture the image placed on the clipboard by Vegas, Photoshop reports an image size of 655×480 which, Photoshop says, is a bit over 921kB. If I save the image from Photoshop as a jpeg with maximum quality, I get a 200kB image. If I save it as a PNG, I get the full 921kB (actually 924kB). So, 78kB on an SD image says Vegas is using lots of compression for jpeg. You should probably use software which is designed to work with still images if you want good results for still images.