Wayne Waag
2
COW Coins
Forum Replies Created
-
[John Rofrano]
Vegas Pro 12 & 13 has broken GoPro support.
Not completely correct. There was a major GoPro “fix” in Build 453 in V13. Using my Hero 4 Black, I did an hour long shoot yesterday at 4K. Just to confirm, I imported the footage onto the timeline this morning. At 4K project settings (3840 x 2160), the preview at Best/Full remained at 29.97 fps. I then added a Color Curves Fx and a Sharpen FX. Preview remained at 29.97 fps, even with my weak video card (Nvidia 650). I even changed the Project Settings to HD (1920 x 1080) and preview performance remained the same. For me at least, there are no problems with GoPro footage in the latest V13 build.
I then opened the same project in V12 and I can confirm that smooth playback is impossible. Even at the Preview/Auto setting, preview fell to roughly 2 fps, completely unusable. Conversion to an intermediate is essential.
wwaag
-
I just completed a 12 day road trip documentary project using roughly 8 hrs of 2.7K 60P GoPro footage. Here was my workflow.
1. For each day, import GoPro footage directly to Vegas Pro timeline and do cuts editing. Even with my limited spec video card (Nvidia 650), I could still get 50 to 60 fps preview set to Preview Full–certainly good enough for cuts editing. In this way, I kept roughly 20% of the original footage.
2. Correct for fisheye distortion. I have a script that uses the Defish filter in Avisynth to correct distortion. I select the events to be “defished”, and the script renders a lossless avi into Avisynth for processing. Virtualdub then writes a lossless “defished” file which is then added as a Take to the original event in Vegas. The process is pretty automatic–simply select the events, run the script from Vegas, and it processes all of the selected events and adds the result as a Take–pretty slick IMHO.
3. Apply whatever pan/cropping that seemed appropriate for each event.
4. Then batch render converting the lossless “defished” avi’s using an XAVC S Long Gop 1080 60P template.
Once happy, I would then delete the lossless avi files and simply use the XAVC S files in the final project. In this way, there was simply no need to convert the original GoPro files to avi and waste a lot of storage space.
wwaag
-
[Brendan Abel]
I had forgotten about this Izotope Demo I did for someone else having a similar problem. It explains how to use Spectral Repair and Denoise in Izotope. Hopefully, it will be of use to you.
Question. Does your version of Izotope have the Dialog Denoiser. I use the automatic setting all the time for audio captured inside a moving car. You can vary the amount of noise reduction (in my case to reduce vehicle road noise) and then increase the output to increase the volume of the dialog itself.
wwaag
-
-
That should work. Again, there is no problem with higher bit rates other than increased file size and demands on Vegas. If it were me, I would still render to a higher bit rate. In that way, you could render to Blu-ray in the future without having to re-render from Proshow if the need arose. Remember that Blu-ray will look dramatically better for still animation than DVD. However, if all you’ll ever want is DVD, then a lower bit rate is fine.
wwaag
-
A rule of thumb I use is to, at least, double the bit rate of your final delivery format. E.g. if you want to render a blu-ray MPEG-2 at 25 mbps, then the MPEG-2 from Proshow should be at least 50 MBPS. Vegas Pro 13 has no problem with the MPEG-2 at 60 mbps. As far as an avi file, I don’t believe that Proshow Gold supports avi. I use Proshow Producer, which does support avi output, but sadly the compressed avi output option is “broken” and simply doesn’t work and Photodex has been unwilling to fix it (sound familiar?). You can render uncompressed avi, but the file sizes become enormous.
wwaag
-
No. My suggestion would be to to search for applications of the convolution filter in Photoshop which is known as the Custom Filter. It has an actual matrix, while Vegas uses sliders. The operations appear to be the same though. Here is a link to a tutorial that may be of value. https://www.youtube.com/watch?v=JDFVdl6wEPg In just a quick search, I didn’t find very much. There is also a convolution filter in Gimp, another search possibility.
wwaag
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Thomas Roberts]
IMHO, there are lots of advantages of using the new Titles and Text over Legacy Text. Here is a recent thread from the Vegas Pro forum.
https://www.sonycreativesoftware.com/forums/showmessage.asp?messageid=936151.
Sounds like the same problem you are having. In that thread, I posted a fairly easy workaround for using Arial black which did not show up in Text and Titles. Here was my post.
Here’s an easy workaround, at least for Arial Black on V13. Open Word (I used Word 2007). Select Arial Black font and type something, then copy. Open Vegas, Insert Text Event. Highlight and then Paste. The same title from Word will now display in the Text and Title box in arial black.. Then save as a Preset. Now add new titles and simply apply that preset. It indicates Verdana but displays Arial Black. You can then change font size. If you have Vegasaur, you can apply the preset it to multiple text events. Try it. Sure beats fooling around with Legacy Text.
Don’t know if it will work for your particular font, but it may be worth a try.
wwaag
-
Okay well ill find a way to get izotope. How do i do it then?
My suggestion is to download the trial version. The module that you will probably use most often judging from just the first few seconds of the YT video is Spectral Repair. In simple terms, you can usually visually identify the noise you want to eliminate using the spectrogram. It has a variety of tools for making a selection, much like those available in Photoshop, e.g. lasso, magic wand, etc. Once you’ve made a noise selection, there are different ways that it can be processed. You’ll have to experiment to try and find the one that works best for your noise selection. Most often, I use the Attenuate or Replace. The help files in Izotope are actually pretty good. Bear in mind that reducing or eliminating noise in this manner is pretty tedious. Moreover, there are occasions when it may be next to impossible to really do a good job. For example, wind noise. Still, this is about the best set of tools around. Again, I would first try to simply replace the noise rather than filter it.
wwaag
-
So id like to manipulate my audio rather that cutting and pasting.
Just to be clear, you only need to cut and paste the audio track while leaving the video track intact. If you still want to “fix” the noise in your audio track, then be prepared to purchase something like Iztotope RX4 or the newer version 5. It’s about $350. Audacity simply doesn’t have the tools you will need. If may help some, but it will still sound pretty bad.
wwaag