Bob Peterson
Forum Replies Created
-
By the way, Vegas splashes two big upgrade advertisements on its screen every time you start it.
-
I experienced something like this in an mpeg-2 file. It was skipping random frames. The solution in that case was to right click on the event -> choose switches -> click on reduce interlace flicker. Also change smart resample to force resample on the same menu.
If that doesn’t work, the standard advice is to tell us what formats Mediainfo says the video and audio streams are using.
-
It is not unusual for the camera’s “clock” to be slightly off from the “clock” on another camera. That will cause a drift when compared to another camera or recording device. I use the audio from a camera to synch the camera to a second camera, and to an audio recorder so that all three are synchronized. The audio recorder is what produces the master audio track. Thus, there is no opportunity loss of synchronization in the audio. However, the video can still drift out of synch, and need correction.
From what I have seen, there is a substantial boost in the price of a camera if you want it to synch with a common time signal to avoid this kind of drift.
-
I would try renaming the veg file in Windows. Then replace it with the veg backup file. If that doesn’t work, search the forum for “unmanaged exception”. Steve Mann used to post the procedure for dealing with an unmanaged exception fairly frequently.
-
What does Mediainfo say about these files? Specifically, what does it say about the file type for the video part of the file? Also, what are you rendering to, and at what bit rate?
BTW, I do not know about Win 10. I have not installed it, and I have no plans to do so.
-
I’m confused. Are you saying you checked the source files on a normal video player, and they looked fine? Then, “Rendering didn’t change the look as well”. What look was not changed by rendering?
-
There is one strategy which may help. It is called the binomial rule. Establish an upper boundary on the bit rate and render it. If it is OK, pick a much lower bit rate as a lower boundary. Something that is reasonable, but perhaps too ambitious. Render it. If it looks OK, use it as a new upper boundary. Then, try an even lower bit rate, and start over. If it is NOT OK, pick a bit rate half way between the upper and lower boundary. If its OK, set it as a new upper boundary and try again. If its not OK, set it as a new lower boundary and try again.
You will zero in on the right bit rate much more quickly than if you try to work it down one step at a time.
It is really much simpler and easier than it sounds. I hope that description is not too confusing.
-
The first thing I would try is to put the tape in a new VHS cassette. If you have a new or spare VHS cassette, very carefully take it apart. Pay close attention to the tape path, and what pieces go in what place. Then, take the tape out, and put your old tape into the new housing, and put the housing back together. Be sure that you don’t touch the oxide surface of the tape which is what will face inward when the cassette is reassembled. If you don’t want to try it, perhaps a friend or a place that transfers VHS tapes can do it for you. Putting the old tape into a new cassette shell may resolve the audio problem.
If not, I would try the denoiser in RX4. Find a small section of the audio which has nothing except the noise that you are trying to eliminate. Select that area, and press the “Learn” button. I usually set the reduction to 21db. Expand the selection to include the entire audio file, and press the “Process” button. Listen to a portion of the audio to be sure that it has not been adversely affected. If you like it, save it and move on. If not, back out the denoiser and post again. Perhaps another suggestion will surface.
-
Yes, if you double click on the cursor position (lower right corner of the time line), you can type in a specific cursor position. You can do the same thing in the pan/crop screen, and, I suspect, any other screen which supports keyframes. Once the cursor is positioned, you can create the keyframe. For the loop boundary, once the cursor is positioned, press the “i” key (input) for the left boundary of the loop on the time line, or the “o” key (output) for the right boundary.
-
Actually, I upgraded from CS3 to CS6 not too long before Adobe announced they were moving to the cloud, so I did not pay the retail price for CS6 although, as I recall, I thought the price was steep enough. I did, however, skip a few upgrades and expected that they would want a little more money.
My current cameras are already covered by the raw processor in CS6, and I’m still not seeing cameras that might induce me to buy a new one. If I do, Adobe’s raw converter to DNG is, so far, free, so I would try that first as a work around. Worst case will be to rent Lightroom to run my raw images through the converter.
$10 a month doesn’t sound too bad, but Adobe can increase that any time they want if they get enough people to buy into rental via the cloud. If it works for Adobe, I expect a lot more people to take that route. Microsoft is already trying the same approach with Office. Get enough applications on a rental basis, and pretty soon you are talking real money.
Right now, I have no need to upgrade. If I ever do have a need, I will look first for the competition which I think might develop by that time. I am already hearing about a few alternatives to Adobe.