Happy Otter Scripts for Vegas Pro

Comments

PhilippZ wrote on 4/16/2019, 11:58 AM

@MikeLV I have many problems with GPU rendering in Vegas Pro. So I hope, that I can "fix" it with HOS. :-D
Because my last Rendering was over 2 hours (only CPU) and this is too much for a small project.

@wwaag - thank you - I will update my driver asap!

MikeLV wrote on 4/16/2019, 12:07 PM

I'm still using my GTX 570 card, wonder if I should try using the GPU in HOS. CPU seems to be doing find for me, but I'm only encoding 720P so it doesn't take all that long

wwaag wrote on 4/16/2019, 12:31 PM

For anyone interested, here's a link to exactly which Nvidia cards support which codecs for encoding and decoding.

https://developer.nvidia.com/video-encode-decode-gpu-support-matrix

@PhilippZ

HOS may or may not have any appreciable effects on your problems. GPU support occurs in two places--first, the internal processing of each frame and application of any Fx--and second, the actual encoding of each frame to a video format. HOS only deals with the second. If there are problems in the first part of the pipeline, they will be remain.

@MikeLV

I'd stay with CPU renders. I'm not even sure that your card would support GPU encoding, but you might want to give it a try.

Steven-Porchet wrote on 4/23/2019, 11:30 AM

I am working with the new Canon XF705. And Canon has decided to use their new XF-HEVC h.265 codec with this camera. At the current time Avid and Davinci Resolve 15 are the only ones that can deal with it. Will Happy Otter allow me to work with it in Vegas 14-16?

john_dennis wrote on 4/23/2019, 12:02 PM

"Will Happy Otter allow me to work with it in Vegas 14-16?"

I tried a number of media types in Import Assist in Happy Otter Scripts build 56 and had no luck.

wwaag wrote on 4/23/2019, 1:10 PM

@Steven-Porchet

"Will Happy Otter allow me to work with it in Vegas 14-16?"

No. It does not and highly unlikely to do so in the future. At the moment, the codec is proprietary and cannot be decoded by the open source tools used by HOS.

wwaag wrote on 4/25/2019, 10:19 AM

@Steven-Porchet

"Will Happy Otter allow me to work with it in Vegas 14-16?"

"No. It does not and highly unlikely to do so in the future."

I was wrong. The latest nightly build of FFmpeg now supports the new XF 705 codec. ImportAssist allows conversion to avc as well as Lossless MagicYUV or UtVideo. You can use it by downloading the latest nightly build (Windows 64 bit Static) at https://ffmpeg.zeranoe.com/builds/.

Unzip and copy ffmpeg.exe into the following folder C:\Program Files\HappyOtterScripts". It's probably best to rename the existing file. I'm a bit reluctant to include a nightly build in HOS, but it does seem to work OK. Although FFmpeg works, you still cannot use any of the codecs within VirtualDub.

One note. The audio is still incorrect. Only the 1st of 4 channels is included in either avc or avi output. One solution would be to create a two track, 4 channel wav file as a second pass.

GJeffrey wrote on 4/25/2019, 6:00 PM

@wwaag

Bmx should work, but using it the other way around, then wrap to mp4. There should not be any reencoding needed.

PAP wrote on 4/27/2019, 11:31 PM

Just fyi: Install failed (wanted Vis C). I have a ton of Vis C already as I develop my own apps, and test software QA for a number of companies etc. So this is an odd one. Seems I already have a newer version and therefore this one cannot be installed. Of course I will sort it at this end but thought you may find the info useful.

 

[36A0:3374][2019-04-28T08:26:31]i001: Burn v3.7.3813.0, Windows v10.0 (Build 17763: Service Pack 0), path: C:\Users\Phil\OneDrive\Stores\Vegas\Other\Happy Otter\vcredist_x64.exe, cmdline: '/norestart -burn.unelevated BurnPipe.{7FB04F47-450F-4BB5-9671-39FB9DB146CE} {10E9D06F-073F-4081-87E7-BE4965DED68F} 11568'
[36A0:3374][2019-04-28T08:26:32]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Phil\AppData\Local\Temp\dd_vcredist_amd64_20190428082632.log'
[36A0:3374][2019-04-28T08:26:32]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Phil\OneDrive\Stores\Vegas\Other\Happy Otter\vcredist_x64.exe'
[36A0:3374][2019-04-28T08:26:32]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Phil\OneDrive\Stores\Vegas\Other\Happy Otter\'
[36A0:3374][2019-04-28T08:26:32]i000: Setting string variable 'WixBundleName' to value 'Microsoft Visual C++ 2017 Redistributable (x64) - 14.13.26020'
[36A0:3374][2019-04-28T08:26:32]i100: Detect begin, 10 packages
[36A0:3374][2019-04-28T08:26:32]i000: Setting version variable 'windows_uCRT_DetectKey' to value '10.0.17763.404'
[36A0:3374][2019-04-28T08:26:32]i000: Setting numeric variable 'windows_uCRT_DetectKeyExists' to value 1
[36A0:3374][2019-04-28T08:26:32]i107: Detected forward compatible bundle: {5b295ba9-ef89-4aeb-8acc-b61adb0b9b5f}, type: Upgrade, scope: PerMachine, version: 14.14.26405.0, enabled: No
[36A0:3374][2019-04-28T08:26:32]i102: Detected related bundle: {5b295ba9-ef89-4aeb-8acc-b61adb0b9b5f}, type: Upgrade, scope: PerMachine, version: 14.14.26405.0, operation: Downgrade
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.3 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.3 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.2 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.2 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.1 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.1 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.0 AND NOT VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i052: Condition '(VersionNT = v6.0 AND VersionNT64) AND (windows_uCRT_DetectKeyExists AND windows_uCRT_DetectKey >= v10.0.10240.0)' evaluates to false.
[36A0:3374][2019-04-28T08:26:32]i108: Detected compatible package: vcRuntimeMinimum_x64, provider: Microsoft.VS.VC_RuntimeMinimumVSU_amd64,v14, installed: {BCA8F863-9BAB-3398-B8E4-E1D0959D0943}, version: 14.14.26405, chained: {221D6DB4-46E2-333C-B09B-5F49351D0980}
[36A0:3374][2019-04-28T08:26:32]i103: Detected related package: {BCA8F863-9BAB-3398-B8E4-E1D0959D0943}, scope: PerMachine, version: 14.14.26405.0, language: 0 operation: Downgrade
[36A0:3374][2019-04-28T08:26:32]i108: Detected compatible package: vcRuntimeAdditional_x64, provider: Microsoft.VS.VC_RuntimeAdditionalVSU_amd64,v14, installed: {A2999714-5C2C-3729-A911-4AE198B7B2FD}, version: 14.14.26405, chained: {C5ECDB9A-D9B0-3107-BA85-1269998A5B3E}
[36A0:3374][2019-04-28T08:26:32]i103: Detected related package: {A2999714-5C2C-3729-A911-4AE198B7B2FD}, scope: PerMachine, version: 14.14.26405.0, language: 0 operation: Downgrade
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows81_x86, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows81_x64, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows8_x86, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows8_x64, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows7_MSU_x86, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: Windows7_MSU_x64, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: WindowsVista_MSU_x86, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: WindowsVista_MSU_x64, state: Absent, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: vcRuntimeMinimum_x64, state: Obsolete, cached: None
[36A0:3374][2019-04-28T08:26:32]i101: Detected package: vcRuntimeAdditional_x64, state: Obsolete, cached: None
[36A0:3374][2019-04-28T08:26:32]i052: Condition 'VersionNT64 >= v6.0 OR (VersionNT64 = v5.2 AND ServicePackLevel >= 1)' evaluates to true.
[36A0:3374][2019-04-28T08:26:32]i199: Detect complete, result: 0x0
[36A0:1CBC][2019-04-28T08:26:35]e000: Error 0x80070666: Cannot install a product when a newer version is installed.


 

Jep wrote on 4/30/2019, 6:39 AM

Hi Wayne,

Still loving HOS but I'm having a small problem and don't know if its just me.

While using Render Plus the following sequence of events happen.

1. On clicking the Render button HOS starts preparing a .wav file.

2. When the .wav preparation finishes a new popup appears - writing signpost avi.

3. When the signpost avi popup disappears, the DebugMode Framserver popup appears along with the HOS progress bar, and it starts encoding the video.

The problem I'm having is that if after clicking the Render button I switch to another application window - e.g. my Firefox browser, MS Word etc, the application window that I've switched to freezes as soon as the DebugMode Frameserver appears and encoding starts, and I can't do anything with it. The only ways out seem to be:

a. Stop the encoding process by clicking the red X on the HOS progress bar. The frozen application then becomes active again, but I have to start the HOS render operation from scratch again.

b. Closing down the frozen application by right clicking the Task bar and going into Task Manager. I can then re-open the frozen application and continue what I was doing.

Today I had it actually freeze the task bar as well as my browser so I had to stop the HOS encoding process completely. That's never happened before.

Just wondering if anyone else has experienced this kind of bug. It's not a huge problem - I just have to remember to wait until the DebugMode Frameserver pop appears and video encoding starts before switching to another application.

Anyway - though you might like to know about it. Thanks for all the hard work.

wwaag wrote on 4/30/2019, 10:39 AM

@Jep

By far, the easiest thing to do is simply wait the few seconds that it takes to get started (I would recommend this regardless). Once you click Render, a "watcher" app is started that "waits" for the sequence of events to occur that you have outlined. The final event is the receipt of data from Vegas and the starting of the render, Anything that interrupts that flow will cause problems. Once the render starts, it should be OK. For cpu renders, the progress bar shows progress pretty quickly. For some reason (unknown to me), it always takes longer for GPU renders to show progress--most like that they are not using FFmpeg. Have you been using the "run minimized" option? I'm not sure that would make any difference, but it may be worth a try.

One other thing that may be of interest to you. The next HOS version will also have the capability to "fill-in" duplicate frames. A new "interpolated" frame is computed using motion vectors which can replace either the first or second duplicate frame.

john_dennis wrote on 4/30/2019, 11:12 AM

@Jep

If it is any consolation, even I have stopped going to Vegas forum within 7.3 ns after starting an encode with RenderPlus.

MikeLV wrote on 4/30/2019, 11:35 AM

Hi Wayne,

Still loving HOS but I'm having a small problem and don't know if its just me.

While using Render Plus the following sequence of events happen.

1. On clicking the Render button HOS starts preparing a .wav file.

2. When the .wav preparation finishes a new popup appears - writing signpost avi.

3. When the signpost avi popup disappears, the DebugMode Framserver popup appears along with the HOS progress bar, and it starts encoding the video.

The problem I'm having is that if after clicking the Render button I switch to another application window - e.g. my Firefox browser, MS Word etc, the application window that I've switched to freezes as soon as the DebugMode Frameserver appears and encoding starts, and I can't do anything with it. The only ways out seem to be:

a. Stop the encoding process by clicking the red X on the HOS progress bar. The frozen application then becomes active again, but I have to start the HOS render operation from scratch again.

b. Closing down the frozen application by right clicking the Task bar and going into Task Manager. I can then re-open the frozen application and continue what I was doing.

Today I had it actually freeze the task bar as well as my browser so I had to stop the HOS encoding process completely. That's never happened before.

Just wondering if anyone else has experienced this kind of bug. It's not a huge problem - I just have to remember to wait until the DebugMode Frameserver pop appears and video encoding starts before switching to another application.

Anyway - though you might like to know about it. Thanks for all the hard work.

Jep, yep, I know exactly what you're talking about. On a single long render, it's ok because like wwaag said, you just wait for the render process to begin, then you can switch to another application. Where the problem comes in is if you have a bunch of regions to encode to multiple files. If you're working, and don't notice when one render completes, after it produces the wav file, it will throw up the frameserver window on top of whatever you're working on. Even when you run it minimized, it still needs to switch back momentarily. It would be great if the entire process could simply run in the background without any interruption.

Jep wrote on 4/30/2019, 8:31 PM

@Jep

By far, the easiest thing to do is simply wait the few seconds that it takes to get started (I would recommend this regardless). Once you click Render, a "watcher" app is started that "waits" for the sequence of events to occur that you have outlined. The final event is the receipt of data from Vegas and the starting of the render, Anything that interrupts that flow will cause problems. Once the render starts, it should be OK. For cpu renders, the progress bar shows progress pretty quickly. For some reason (unknown to me), it always takes longer for GPU renders to show progress--most like that they are not using FFmpeg. Have you been using the "run minimized" option? I'm not sure that would make any difference, but it may be worth a try.

One other thing that may be of interest to you. The next HOS version will also have the capability to "fill-in" duplicate frames. A new "interpolated" frame is computed using motion vectors which can replace either the first or second duplicate frame.

Thanks for the explanation Wayne. As I said it's a pretty minor issue, but if HOS gets launched as a commercial product it would probably be best if it could be sorted out before that - particularly in light of MikeLV's comments above. Just a nice little refinement.

And YES - I'll be very interested in seeing the next HOS version with the fill-in duplicate frames feature.

As always thanks for all the hard work and dedication to the HOS project. 👍

wwaag wrote on 4/30/2019, 9:06 PM

@jep and @MikeLV

I wholeheartedly agree that this problem "should" be resolved before release. However, the root cause is not HOS, but rather the DebugMode FrameServer (DMFS). It is during its launch that problems can occur and as such I have no way of making changes. HOS simply waits until DMFS has done its thing. Although it's open-source, it is well beyond my pay grade at the moment to attempt a rewrite of the software. The developer has pretty much abandoned the project, the last release being 5 years ago with changes necessary to support Vegas 13. Someone has rewritten DMFS for Premiere (it's now called Advanced FrameServer) but as of yet, no one has done the same for Vegas and the two are incompatible.

 

wwaag wrote on 5/14/2019, 12:33 AM

New version 1.0.2.57 released with a new tool, added scripts, features, and bug fixes. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

First and foremost--the beta period has been extended once again--this time to 1 Aug.  

A new tool has been added--MediaFinder. 

Some of its features include:
    Search and replace with options for all media, selected media, or missing media
    Include/exclude folders, media extensions, and parts of the media file name
    Search for new media with option to add to project media
    Wildcard support for all search options
    Template creation for all media search options for easy reuse

A number of frame detection and replacement scripts have been added to AviDub including:
    Optical scene detection with option to add markers at predicted scene change location
    Duplicate frame finder with option to add markers at  duplicate frame location
    Black frame finder with option to add markers at black frame location
    Duplicate frame replacement with interpolated frames computed from motion vectors

Option to add comments to metadata for rendered and trimmed files using Render+ and SmartVideoTrim

And for anyone who likes to read, the help files have finally been updated.

Comments are welcome.

lan-mLMC wrote on 5/14/2019, 4:30 AM

New version 1.0.2.57 released with a new tool, added scripts, features, and bug fixes. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

First and foremost--the beta period has been extended once again--this time to 1 Aug.  

A new tool has been added--MediaFinder. 

Some of its features include:
    Search and replace with options for all media, selected media, or missing media
    Include/exclude folders, media extensions, and parts of the media file name
    Search for new media with option to add to project media
    Wildcard support for all search options
    Template creation for all media search options for easy reuse

A number of frame detection and replacement scripts have been added to AviDub including:
    Optical scene detection with option to add markers at predicted scene change location
    Duplicate frame finder with option to add markers at  duplicate frame location
    Black frame finder with option to add markers at black frame location
    Duplicate frame replacement with interpolated frames computed from motion vectors

Option to add comments to metadata for rendered and trimmed files using Render+ and SmartVideoTrim

And for anyone who likes to read, the help files have finally been updated.

Comments are welcome.

Add to script become unchecked.