[Wayne Waag]

Hi Rina,

What you probably need to do is create your own low-resolution proxies for all of your still images. If all of your images are in the same folder or can be moved to a common folder, then it’s pretty easy. Simply make a copy of the folder and batch process the image files of your copy to make the low resolution images. Then batch replace your still images in your Vegas project with the low res proxies to do your editing. When editing is complete, then replace the proxy files with the original high-resolution images.

There is a fairly long thread about this issue on the Vegas Pro Forum at https://www.vegascreativesoftware.info/us/forum/proxy-for-still-images–117706/?page=1

Another option, mentioned in the thread, would be to use the ProxyAssist tool in Happy Otter Scripts which can be found here. https://tools4vegas.com/
In addition to proxy creation for video images, there is also an option for still images. Here is a screen grab.

HOS is still in beta at least through mid-January. If you want to try it, I’d suggest waiting until the next build 1.0.2.66 will be released later today or tomorrow.

wwaag

[Wayne Waag]

Thanks for uploading a sample clip. It works fine for me in all versions of Vegas 12-17. I am also using build 18363 on Win Pro system. I also tried it on another system with Win Home build 1862 and it worked OK in Vegas 15. Have you tried rolling back any updates since the time you successfully edited such files? You can go to Settings|View Update History and see what’s been installed. Sorry that I can’t be of any assistance. Good luck.

wwaag

[Wayne Waag]

Could you upload a sample clip that could be downloaded?

wwaag

[Wayne Waag]

If the first 30 secs is the same, I would suggest creating a loop region and then rendering to a lossless intermediate such as Magic YUV or UtVideo. You can use the built-in Render to New Track to create your intermediate. Depending upon the complexity of your 6 to 8 generated media clips, subsequent final renders may or not be a lot quicker. If they are very complex such as some of the HitFilm Fx, you can save quite a bit of time.

wwaag

[Wayne Waag]

Have you looked in your “junk” folder? Most likely, it is there. I see that you have attempted a couple of times. If it’s not there send me a request at https://tools4vegas.com/contact/. Thanks for your interest.

wwaag

[Wayne Waag]

You can use the RenderPlus tool in HappyOtterScripts which can be found at https://tools4vegas.com/.

There are two ways that you can produce a 6K render. First, after editing you can simply change the project resolution to the desired frame size and then render. Here’s a short demo of that approach. Since I didn’t have any true 8k footage, I created an 8k png file and used that as my video source. One note I should add. Depending on your source, you may have to disable GPU processing. For the demo, it became necessary.

https://youtu.be/TXqUtcJsvvI

A second way would be to render at full 8k resolution from Vegas and then resize in R+. Here’s a screen shot of the dialog.

HOS is still in beta, so it can be freely downloaded and used at least through 15 Jan.

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.

[Wayne Waag]

I’m sure that others may violently disagree, but It’s pretty simple IMHO. If $ is no object, just get the best Nvidia card you can afford, at a minimum a 1660 or 2060 card (I still use a 1050 ti). In other words, stay away from AMD cards. In V17 hardware decoding is supported only for Nvidia cards at the moment. Moreover, if you look at external apps that support GPU encoding, most everyone supports QuickSync and Nvenc, but virtually no one supports AMF. That may change in the future, but for the moment I’d go with an Nvidia. They also have a “studio driver” version designed for creative apps such as editing as well as the usual driver for “gaming”. One other recommendation–buy from a retailer where you can return it if not satisfied. Some well-known sellers do not permit video card returns.

wwaag

[Wayne Waag]

A “quick and dirty” way of doing this inside of Vegas is to use the “Generate Loudness Log” tool which was available starting with V13. Drag Audio A to one audio track and Audio B to another. Run the Loudness tool on each track while muting the other. You can then adjust the volume of one track to match the other, or you can adjust both to match a certain loudness level.

wwaag

[Wayne Waag]

Hi Roger,
Glad that it worked OK for you.

wwaag

[Wayne Waag]

Hi Roger,

Rather than re-post the old Giles script, I wrote a new one which you can download here. https://www.dropbox.com/s/u4kyy9q9i9gt2ib/GroupSelectedEvents.dll?dl=0

To install, download the file and copy it into your ScriptMenu folder. First make sure that the file is not “blocked” since Windows often blocks files downloaded from DropBox. To check, right-click and choose properties. If blocked, you will see a button on the lower right part of the dialog with the text Unblock. Simply click to Unblock.

A few caveats. First, it assumes that the audio track is right below the video track. In other words, if the audio track is on top of the video track or there is another track in between the video and audio tracks, the events will not be grouped. Second, it assumes that the start times and event lengths for both the audio and video are the same. If the audio and video are not synced or not the same length, they will not be grouped. Third, it assumes that the audio and video are from the same media file. If not, the events will not be grouped.

To use, simply select the events and run the script. Let me know if there are problems.

wwaag