[Wayne Waag]

Make use of PasteEventAttributes. To do so, add the desired Fx to the first audio event. Then select the event and “Copy” (Ctrl-V). Then select the events to which you want to add the Fx. Once selected, right-click on any one of the new events and select “Paste Event Attributes”. The Fx you added to the first event will be added to the selected events. That’s it.

wwaag

[Wayne Waag]

Since you want to add the new file at the end, it is very easy using 3rd party tools. You could try the freeware MP4 File Joiner which can be found at https://www.mp4joiner.org/en/.

There is also a free MP4 File Joiner program in the HappyOtterScripts free tools library which can be found at https://tools4vegas.com/mp4-file-joiner/. The only downside is that you must install the HOS package since it includes a number of the tools required by MP4 File Joiner.

Or, you can have a look at the TMPGEnc products or VideoReDo. Any of these solutions should work.

wwaag

[Wayne Waag]

Unfortunately, most codecs that “smart-render” in Vegas are NOT delivery codecs–they are usually digital intermediates. Formats that are designed for delivery such as avc (h264), hevc (h265), or VP9 cannot be smart-rendered. You must re-render the entire project if you want to only use Vegas.

wwaag

[Wayne Waag]

“Now, having said that, there maybe software, external to VP, that could create a single File from separate Video files.”

Graham is absolutely correct. There is available software that will do this, but you can’t do it inside of Vegas. There are a couple of TMPGEnc products that will do this–Video Mastering Works or MPEG Smart Renderer. Or you could take a look at VideoReDo. These products will “smart-render” so that only transition points are “re-rendered” and the main clips are “copied”. If you want to add the new clips to the end of your original video, there are even freeware tools that can easily accomplish this. Lots of options–just not in Vegas.

wwaag

[Wayne Waag]

New version 1.0.2.71 released. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

New Versions: Virtualdub2, Nvencc64. QSVencc64, VCEencc64 plus most Avisynth plug-ins including 64bit version of Defish

New Features

• ImportAssist—crops gif files to make sure frame size is mod2 compatible necessary for x264
• RenderPlus—added PSNR and SSIM metrics to render stats when available
• ProxyAssist—added 4:3 frame sizes plus an option for a custom frame size
• AviDub—added support for both YUV and RGB FFmpeg renders for MagicYUV and UtVideo
• OtterMenu—added a “traditional” menu for launching HOS tools for those not using OtterBar or OtterInfoBar

Significantly faster launch times for most HOS tools

Bug Fixes

• DeshakerRedux-mask creation not displayed correctly for 4:3 footage—fixed
• ImportAssist—import of multiple audio streams not added to timeline correctly–fixed
• RenderPlus—render folder location not saved correctly after new HOS install–fixed

wwaag

[Wayne Waag]

Over a year ago, I started a thread on the Magix vegas forum at https://www.vegascreativesoftware.info/us/forum/tool-for-measuring-render-quality–114398/?page=1 which described a tool, Render Quality Metrics (RQM) for measuring the quality of renders from Vegas. Admittedly, RQM was pretty “clunky” in that it required the user to render an image sequence of BMPs for both the Original and Rendered files. A new version is available in the Happy Otter Free Tools Library which greatly simplifies and speeds up its use. In addition to Mean Squared Error (MSE) and Power Signal to Noise Ratio (PSNR), RQM now has an option to compute the Structural Similarity Index Metric (SSIM) although it is very slow. RQM now has two apps, a script that renders the image sequence from Vegas and a standalone app that does the computation.

Rather than render two sets of BMPs, RQM makes use of the track compositing mode in Vegas. The rendered file is placed on the top track and its compositing mode is set to “Difference”. Another difference is that the BMPs are now directly rendered using the DebugMode FrameServer (DMFS) which speeds up rendering. I’ve done testing to make sure that BMPs from DMFS are identical to those produced by Vegas. I’ve also done testing to make sure that the single BMP based on the composite difference in Vegas is the same as the difference from separately rendered BMPs.

There are also options to “speed up” the process by selecting the pixel block size during creation of the BMPs and also an option to select every nth frame during processing. Here are screen grabs of both the script and standalone app.

Here’s a demo.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” 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.

The new version is titled Vegas Render Quality and can be downloaded at https://tools4vegas.com/library/ The zip file contains both the script and the standalone app.

Comments and suggestions for improvement are welcome.

wwaag

[Wayne Waag]

The easiest way is to “Copy snapshot to clipboard” and then paste in IrfanView which is freeware–or you could use any photo editor. In IrfanView you can create a selection and the pixel dimensions will be shown on the taskbar. Here’s an example.

wwaag

[Wayne Waag]

Just added a new tool, Save and Restore, that enables the user to “save” the cursor position when a project is closed and then “restore” the cursor to that position when the project is re-opened. There is an option to select the amount of “zoom” in terms of how many seconds will be displayed on the timeline. Here’s a shot of the UI and a short demo in an 11 hour project I had used for audio testing.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” 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.

It can be downloaded here. https://tools4vegas.com/library/

wwaag

[Wayne Waag]

New version 1.0.2.70 released. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

New Versions of VirtualDub2, Nvencc64, Qsvencc64, Vceencc64**

New Features

o Added 422 x264 rendering support to RenderEvents and AviDub
o SmartVideoTrim

Option added to select bit rate when aac recoding is necessary

For PCM audio in MP4 files, option to use older FFmpeg which copies PCM or newer version which demands the audio be recoded to AAC. Newer version used for other file types.

Bug Fixes

o ImportAssist– Newly created x264 templates not being immediately shown—fixed
o ProxyAssist– Selected encoder template in EncoderSettings not updated to main dialog—fixed
o AudioTrim– Selection of AAC renderer crashed Vegas—fixed
o RenderEvents–GPU assisted renders not working—fixed
o Preferences—crashed Vegas on some systems when running ToolFileSetup—fixed
o SmartVideoTrim—option to add audio from different source not working correctly—fixed

** For AMD Radeon Users: The newest version of VCEEncC64 that supports VCE rendering, cannot be used in Win7. To continue using Win7, you must go to the folder “C:\Program Files\HappyOtterScripts” and delete the file “VCEEncC64.exe”. Then rename “VCEEncC64_Win7.exe” to “VCEEncC64.exe”.

wwaag

[Wayne Waag]

No problem. As I said, it’s been on my “to do” list for quite some time. So yesterday, I wrote a few apps to more or less “automate” the process so that in the future, both versions will be immediately available.

wwaag