Happy Otter Scripts for Vegas Pro

Comments

Grazie wrote on 7/21/2019, 5:38 AM

@wwaag - User Error.

Musicvid wrote on 7/22/2019, 6:56 AM

@wwaag

My steps to reproduce aren't very well identified, but it seems when working with the custom command line, I must reload it each time I run it, otherwise the audio portion goes away, and the render routine just shoots blanks. Does this make any sense?

wwaag wrote on 7/22/2019, 10:33 AM

Not really. I've not experienced such problems. However, John Dennis has used CCL's extensively and might be able to confirm.

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.

Musicvid wrote on 7/22/2019, 12:07 PM

I will test further and be more specific.

john_dennis wrote on 7/22/2019, 12:14 PM

"...but it seems when working with the custom command line, I must reload it each time I run it..."

I've not had any problems with Custom Command Lines not being persistent across multiple renders or even reboots.

I'll share a few ground rules though:  

If you run Sony and Magix versions of Vegas Pro, you should populate the folders:

C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\Custom CommandLines

and

C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus\Custom CommandLines

if you want to use the scripts in both versions. (Show hidden and Protected O/S files in Control Panel.)

I rendered old projects all day yesterday only changing the Custom Command Line a couple of times.

This is what I saw when I opened Vegas Pro 15 this morning...

 

Musicvid wrote on 7/22/2019, 12:22 PM

Yes that's what I get unless calling the audio from separate window.

Musicvid wrote on 7/22/2019, 1:34 PM

@wwaag @john_dennis

This is what happens when I try to save and reuse a custom command line that uses the audio dialog box.

Shooting blanks, audio doesn't stick in dialog. Am I doing it wrong?

 

 

john_dennis wrote on 7/22/2019, 1:58 PM

It appears that the Audio Encode/Remux CommandLine box contents is not persistent like the Video Encode CommandLine box. 

wwaag wrote on 7/22/2019, 5:44 PM

@Musicvid

I see the problem. It only affects renders using GPU encoders since a separate CL is required for the audioRemux unlike FFmpeg which does it all in one pass. That should be an easy fix (famous last words!). I'll upload a new R+ for you to try.

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.

Musicvid wrote on 7/22/2019, 6:14 PM

I figured as much, without really knowing much about command lines, except I'm having fun using them again.

Musicvid wrote on 7/23/2019, 8:15 AM

@wwaag

I did a completely fresh install of 1.02.60, replaced RenderPlus.dll with the new one, and unfortunately Render+ does not launch. Render Events does launch normally, however.

wwaag wrote on 7/23/2019, 11:51 AM

@lan-mLMC

Whenever the beta period ends (I will be extending it again to sometime this Fall.), there will be an option to download a 30-day trial.

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.

Musicvid wrote on 7/23/2019, 2:55 PM

Here you go:

[Removed because preview is confusing]

 

wwaag wrote on 7/23/2019, 3:22 PM

Something is definitely amiss and has been corrupted in your system. After installation when you first start Vegas, the R+ dialog is shown. That should not happen--I've never seen that before. After you switch R+ dlls, it is still shown when Vegas starts.

Also, why did you not install the Redistributable package when prompted right at the outset? There are still 32bit components even though it is considered a 64bit app.

I would suggest you first uninstall HOS through the normal app removal process in Settings. Then make sure everything is removed including the HappyOtterScripts folders in Program Files and Program Data. Also make sure that the DebugMode FrameServer folder is removed in Program Files. Then try a re-install and attempt a render without changing the R+ dll. If successful, then swap it out for the new one.

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.

Musicvid wrote on 7/23/2019, 6:04 PM

@wwaag , if it's working on your end, I can easily wait for the next beta. I truly appreciate your responsiveness and asking me to test. It means a lot. I have no production deadlines to worry about.

 

Musicvid wrote on 7/24/2019, 11:24 AM

@wwaag

Mystery Solved! It opens!

I woke up with a clearer head and imagined it might be a security setting. Testing it now, and now I know . . .

wwaag wrote on 7/30/2019, 5:52 PM

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

New Features Include:

o    ProxyAssist—added option to resize stills to proxy resolution in addition to video

o    ImportAssist—added still images import option

  • High quality crop/resize with choice of save formats
  • Option to import small images (less than Project frame size) without timeline “zooming”

o    AudioTrim—additional options for selecting which event and track Fx to keep including gain, pan, volume and track envelopes

To download the new version, Launch Help and click on Check Now.

Comments are welcome.

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.

AVsupport wrote on 8/3/2019, 10:28 PM

Just realized this morning my previous version has expired. After the 1.0.2.61 download, I get a virus warning. This is the first time ever I came across this. hence I am a little apprehensive.. anyone else? (using Win10/chrome/Chrono download manager

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

wwaag wrote on 8/3/2019, 10:59 PM

@AVsupport

I too, the HOS creator, received a warning from Windows Defender for a 1.0.2.60 download that I had done awhile back just a couple of days ago. Running the original file through the virus scan showed clean. Apparently, some update to either Win 10 or Defender led to that update as containing suspected "malware". Googling the suspected malware showed quite a few threads about false positives. The only major change in 1.0.2.60 was the new FrameServer from Satish, plus updates from Rigaya (for QSV and Nvenc) and VirtualDub. There were no new app updates in 1.0.2.61. HOS seems particular vulnerable since all of these are "unsigned". Additionally, all updates are stored on DropBox which often leads Windows to block such downloads unless they are "unblocked".

I don't think there's a problem, but If you're worried just delete it.

I would be interested if anyone else is having such problems since this is potentially a showstopper.

 

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.

AVsupport wrote on 8/3/2019, 11:02 PM

yeah not worried yours is the best 'malware' ever!! sorry don't want to create panic, I realize this is annoying from your end, just wanted to provide feedback ;-)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

wwaag wrote on 8/4/2019, 12:29 AM

Glad you did. Thanks for the info.

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.

rraud wrote on 8/4/2019, 10:25 AM

I always get warnings as well. When initiating the HOS installs, Norton's Security suite warning details state:

- Very Few Users: Fewer than 5 users in the Norton Community have used this file.
- Very New: This file was released less than 1 week ago.
- Unproven: There is not enough information about this file to recommend it.

Based on that info, I always assume it is 'safe' and choose to "run the installer anyway".

wwaag wrote on 8/6/2019, 10:23 AM

For HOS users who upgrade to V17, don't forget to copy the frameserver file found in the Vegas program directory, for example, "C:\Program Files\VEGAS\VEGAS Pro 16.0\Frameserver.x64.fio2007-config" to the V17 directory. Alternately, you can just re-run the setup file "HappyOtterSetup-1.0.2.61.exe" and it will re-install the frameserver including the new version file. Please let me know if there are any issues with HOS for the new Vegas version. 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.