Wayne Waag
2
COW Coins
Forum Replies Created
-
This may be a bit simplistic, but really whats most important is to avoid simultaneously reading and writing to the same drive. Usually, this means that your assets are on one drive (the faster or possibly spread across drives) and you’re rendering to a second drive. An SSD can definitely speed things up, especially if you’re using digital intermediates that take up quite a bit of space and require a lot of “reading”. The drive that you render to is usually not that speed dependent since the actual “writing” is usually the quickest part of the rendering process. Just another opinion.
wwaag
-
The short answer is “no”. For vinyl restoration, suggest you try Izotope RX4. I do believe they have a trial. It’s an indispensable bit of software for those working with audio IMHO. Depending upon the nature of the “pop”, one alternative using Vegas would be to zoom in and simply cut/paste an adjoining section. Kind of crude, but it may work although I guess I really wouldn’t recommend it.
wwaag
-
One other thing you might try is to simply disable GPU in your video preferences. It shouldn’t have any effect since I didn’t see that you’ve added any visual effects, but it might be worth a try. I presume that you are seeing these problems during “preview”. I would also set up a short time selection around the problem area and do a test render of that loop only. If the resulting render shows the same flicker, then you can try transcoding to another codec.
wwaag
-
I mean whats the difference anyways ?
The frame rate for NTSC video is 29.97 fps. The frame rate of your Action file is 30.00 fps. Here is a detailed explanation and probably more than you ever care to know.
https://www.ecuad.ca/~mrose/pdf_documents/timecode.pdf
If you’ve set your project frame rate to a true 30fps, there is no need to Disable Resample, assuming that the recording was made at 30 fps. If recorded at 60 fps, then you should Disable Resample.
Since you are still having problems, have you tried simply “playing” the file in something like VLC or Media Player Classic-Home Cinema and if so, do you get the same flicker?
If the answer is “no”, you could always transcode your Action avi file using Virtualdub into an avi file with a codec that is known to work well with Vegas such as Cineform, Magic YUV, UT video, or Lagarith.
You could also upload a short clip for testing by other forum members or render the clip to YT.
wwaag
-
I’ve used Mirilli’s Action avi’s without any problem. In looking at your screenshot, it appears that your project settings indicate a frame rate of 29.97. Action only records at a frame rate of 30 fps, not 29.97 fps. For the problem clips, suggest that you Disable Smart Resample and see if you get the same glitch. In fact, I would Disable Smart Resample for all of your Action clips.
wwaag
-
[Steve Rhoden]
the thing that peeves me off the most at times, is just
because someone doesn’t uses a particular feature they are ready to claim its
useless.I can’t speak for everyone else, but I for one, never claimed it to be useless. I use it on occasion, but just not for cuts editing. To me, it’s part of the beauty of Vegas–it gives one choices on how to approach basic editing. Some use it, some don’t, and the end result is the same. One needs to make choices based on their own workflow. To me, it’s a win-win situation for everyone.
wwaag
-
whats the work around for this problem?
First, confirm that you indeed have a full range (0-255) by looking at your histogram. If so, you need to add a “Computer RGB to Studio RGB” levels effect somewhere in the chain. I usually add it to the Video output bus.
wwaag
-
Can we check the Start all new Projects tick box and see if that’ll produce this Default position
Just tried it. It does on my machine. Here are a couple of screenshots. First, normal. Then, with the OP’s settings.
wwaag
-
[Graham Bernard]
Is it possible that Vegas IS doing this by defualt?
He may have inadvertently (or purposefully) ticked the box “Start all new projects with these settings” and then it would become his default.
wwaag
-
[Kevin]
That is definitely the problem. I changed my project settings to 32 bit and then selected ACES RRT (sRGB) as the view transform and now my colors look just like yours. Just change the pixel format to 8-bit or set it up correctly for 32-bit. Hopefully, the problem is solved.
wwaag
