Happy Otter Scripts for Vegas Pro

Comments

musko wrote on 3/23/2020, 2:26 AM

@wwaag thank you.
Now seems to working fine (with new DLL).

Jep wrote on 3/31/2020, 7:50 PM

Hi Wayne. I recently installed HOS version 1.0.2.71 and R+ has stopped working. When I try to render with R+ everything freezes as soon as the DebugMode FrameServer and HOS progress popups appear. If I click on the red X in the HOS progress popup to stop the render - nothing happens and I have to shut everything down with Task Manager. I tried resetting R+ scripts and then did a clean install of version 1.0.2.71, but that didn't help.

I mostly use Sony Vegas Pro13 64bit, but I also have Magix Vegas Pro15 64bit on my machine. Same thing happens in both versions of Vegas. I tried going back to 1.0.2.70 but that won't work either as my licence has expired.

Your help would be greatly appreciated. TIA

Jep wrote on 3/31/2020, 8:08 PM

Just another bit of info with regard to my previous post.

I tried installing 1.0.2.71 on my old backup PC - a Win 7 machine. I did a clean install and ran a quick test. It appeared to be working OK and rendered a short clip. To double check I ran the test again and evrything locked up again like on my Win 10 machine. Strange.

Jep wrote on 3/31/2020, 8:25 PM

Sorry for yet another post in such a short space of time, but I think I may know what is causing the problem.

I had been using a number of the Advanced options in R+. I went back and turned off all the options that I had selected and rendered several small clips without a problem. I then turned on the Sharpen option and set it to 50. I hit the render button and the freeze was back. I tried it several times with Sharpen at different amounts and got the same result. As soon as I turned off the Sharpen R+ was back working perfectly again.

Not sure why Sharpen would freeze everything, but that appears to be the problem.

john_dennis wrote on 3/31/2020, 10:33 PM

@Jep @wwaag

I observed a hang when the Sharpen box is checked. An Otter Reset will allow you to get back to business minus the Sharpen option.

wwaag wrote on 3/31/2020, 10:47 PM

@Jep

I know the problem. In the last build, I updated quite a few of the Avisynth plugins, one of which has caused HOS and Vegas to hang. The next build should be out tomorrow which addresses the issue. Use of QTGMC will also lead to a crash. You can only go back to an older build if you do a complete uninstall. Just make sure to save the current license file Otter.lic found in the main program folder to another location. Once the previous version is loaded simply copy the new license file and activate in Help.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Jep wrote on 3/31/2020, 10:54 PM

@Jep @wwaag

I observed a hang when the Sharpen box is checked. An Otter Reset will allow you to get back to business minus the Sharpen option.

Thanks for the reply John. I can't click the Otter Reset as evrything is frozen and Task Manager is the only way out. Hope the Sharpen feature can be fixed as it's one of my favorite HOS features.

Jep wrote on 3/31/2020, 10:56 PM

@Jep

I know the problem. In the last build, I updated quite a few of the Avisynth plugins, one of which has caused HOS and Vegas to hang. The next build should be out tomorrow which addresses the issue. Use of QTGMC will also lead to a crash. You can only go back to an older build if you do a complete uninstall. Just make sure to save the current license file Otter.lic found in the main program folder to another location. Once the previous version is loaded simply copy the new license file and activate in Help.

Many thanks Wayne - look forward to the new build, and I'll give the license file trick to go back to a previous version in the meantime.

Thanks for all the hard work.

wwaag wrote on 4/1/2020, 11:11 AM

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

New Versions: Virtualdub2

New Features

  • RenderPlus
    • Added Preview mode that renders selectable number of frames starting from the position of the timeline cursor

    • Avisynth Filter Settings Dialog

      • Added Fisheye Removal dialog  for removing barrel distortion when using ultra wide angle lenses such as those found on a GoPro

      • Improved dialog for selecting slow motion and fast motion effects

      • Added LSFmod filter as a sharpening option

      • Improved selection of custom frame sizes in both Avisynth and Crop Settings dialogs

    • Improved exception handling for errors involving incorrect Avisynth script settings (no longer hangs)

    • Requires installation of latest Microsoft Visual Studio Redistributable Packages (included in Setup)

  • Bug Fixes

    • SmartVideoTrim—failure to remove temp render track upon completion—fixed

    • QTGMC crash due to incorrect update of needi3.dll in last build—fixed   

Here's a screengrab of the new Avisynth Settings dialog

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Jep wrote on 4/1/2020, 1:52 PM

Hi Wayne. Just installed version 1.0.2.72. Unfortunately I'm having problems in R+ again.

I wanted to enter a new frame size. I clicked the Custom option and then noticed the manual entry fields have been removed from the frame size option. So I clicked on the Resizer option as I presumed that is where I could manually enter a new frame size. As soon as I clicked the Resizer icon everything froze up and I got the Vegas "Problem Report" popup that you get when Vegas crashes. Tried it again with the same results.

wwaag wrote on 4/1/2020, 2:06 PM

To enter a custom frame size you must select Custom from the DropDown list and then enter the dimensions separated by an x--e.g. 1200 x 600. Then click on the green + button to add. I added those instructions to the Tooltip, but that is very easy to overlook.

Just verified that you can open the crop settings and select a different resizer once you have correctly entered the new frame size. I'll add a check to avoid such crashes in the future when custom is selected, but no values are entered.

Thanks.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

wwaag wrote on 4/1/2020, 3:21 PM

There is now a check if you try to open Crop Settings without entering the Custom FrameSize.

Build 1.0.2.72 has been updated. You can re-download the file and install or just remember to enter the Custom FrameSize first.

 

Last changed by wwaag on 4/1/2020, 3:23 PM, changed a total of 1 times.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/1/2020, 5:21 PM

Hi @wwaag, just updated to 1.0.2.72 and when I click R+, Vegas (17) locks up on me.

wwaag wrote on 4/1/2020, 5:44 PM

Try resetting the R+ script settings first.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/1/2020, 6:18 PM

Try resetting the R+ script settings first.

How is that accomplished?

wwaag wrote on 4/1/2020, 6:23 PM

Right-click on R+ icon in OtterBar or OtterInfoBar. Then select Reset Script Settings. Works pretty much the same if using OtterMenu.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/1/2020, 6:29 PM

Hmm, I'm not sure I follow. I have an R+ icon on my toolbar (where the save icon and others are) but when I right click on that nothing happens. Also, nothing shows up under the Tools, Scripting menu in Vegas. Where is the OtterBar or OtterInfoBar, or OtterMenu?

wwaag wrote on 4/1/2020, 6:38 PM

It sounds as if you are using the Vegas taskbar (top) and/or the Vegas script menu? You cannot reset the script from those locations. For that reason, their use is not recommended. Here's a screen grab of the toolbars I mentioned.

To use these, go View|Extensions. These two plus the OtterBar and shown there. How to install and how to use are explained in the Help file.

 

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/1/2020, 6:42 PM

Got it, I found it under Extensions. I right clicked and reset script settings. Then I clicked R+ and Vegas locked up again. I then killed Vegas, restarted it, clicked R+ again, and still locking up :(

Jep wrote on 4/2/2020, 4:24 AM

To enter a custom frame size you must select Custom from the DropDown list and then enter the dimensions separated by an x--e.g. 1200 x 600. Then click on the green + button to add. I added those instructions to the Tooltip, but that is very easy to overlook.

Just verified that you can open the crop settings and select a different resizer once you have correctly entered the new frame size. I'll add a check to avoid such crashes in the future when custom is selected, but no values are entered.

Thanks.

Ahh! OK that works. Not quite as intuitive as the previous layout with the dedicated frame size entry box, but that's OK as long as it works.

Many thanks.

wwaag wrote on 4/2/2020, 10:12 AM

The reason for the the change was the addition of Fisheye Removal. It seemed like a way of finding the space since I really didn't want to expand the overall size of the GUI.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/7/2020, 5:04 PM

Then I clicked R+ and Vegas locked up again. I then killed Vegas, restarted it, clicked R+ again, and still locking up :(

@wwaag, just came back to encode a diff project and R+ is still causing a lockup on me. Is there any way I can go back to the previous version of the script? Thank you

wwaag wrote on 4/7/2020, 5:17 PM

@MikeLV

Sure. Just uninstall completely and re-install the previous version.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

MikeLV wrote on 4/7/2020, 5:22 PM

Thank you, I will do that - last question on that, how do I obtain the install file for the previous version?