Happy Otter Scripts for Vegas Pro

Comments

wwaag wrote on 12/12/2019, 9:18 PM

@lan-mLMC

I see the problem. If only V17 is installed, then the Magix V13-V17 checkbox is not ticked automatically during setup. If any of the previous Magix versions or Sony versions are found, the boxes will be ticked. That was an oversight on my part and will be fixed with the release of next build. Thank you for bring this to my attention.

lan-mLMC wrote on 12/12/2019, 9:23 PM

@lan-mLMC

I see the problem. If only V17 is installed, then the Magix V13-V17 checkbox is not ticked automatically during setup. If any of the previous Magix versions or Sony versions are found, the boxes will be ticked. That was an oversight on my part and will be fixed with the release of next build. Thank you for bring this to my attention.

OK, thanks!

rainer-d wrote on 12/28/2019, 2:56 AM

Hello everybody
I have a little problem with the Deshaker.
I selected a clip on my timline and edited it in the Deshaker.
Everything with the default settings.
But the clip that was output did not match the selected clip.
The part that I previously cut and deleted was edited.
A mistake on my part or a bug?

Edit:

I tried another clip with the same result.

Then I tried a loop region.
But I get the following error message.

rainer-d wrote on 12/28/2019, 4:44 AM

I have now found another "problem".
I get an error message when I try to remove the fish eye from the GoPro footage.

But it works. I'm just writing this for troubleshooting.

.

 

MikeLV wrote on 12/30/2019, 5:09 PM

 

@wwaag, I just updated to the latest version of HOS, and went to run x264 and got this fatal error. I'm on ver 16 if that makes a difference. Any suggestion? Thank you :-)

wwaag wrote on 12/30/2019, 7:13 PM

@MikeLV

Such errors usually indicate that FFmpeg doesn't like the Command Line that has been generated. The best source of information is the FFmpeg log file which can be found at "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus\LastRenderLogFile.txt" for Magix versions of Vegas. I've sent a PM on what to upload. Thanks.

wwaag wrote on 1/13/2020, 6:39 PM

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

Beta period extended once again to 15 March.

New Features

o    MediaRenamer—can now rename veg files

o    FileInfo—option to copy stream information to clipboard

o    KwikPreview

  • Three split-screen options (Fx on/off, compare two tracks, Active Take vs original)
  • Default render template now uses high bit rate Mpeg-2 encoding (faster than GPU encoding in my tests)

o    RenderPlus

  • Mpeg-2 Encoding--Modes include cq, abr, cbr, and 2-pass--Supports HD and UHD at 60 fps
  • VP9 additional two pass render options  (2 pass-cq and 2-pass-abr)

o    OtterPlay—use of Avisynth decoding filter added in addition to use of Windows DirectShow

Bug Fixes

o    RenderPlus – last commandline not properly loaded—fixed

o    AviDub

  • 32 bit defish not working with new FrameServer—fixed (requires uses of direct render option)
  • Option to use media properties for rendering did not included frame rate adjustments—fixed

Comments are welcome.

Jep wrote on 1/14/2020, 2:18 PM

Hi Wayne. A while ago HOS started adding "Project" to the end of any file I name in R+. Just wondering if there is any way I can stop that behaviour and have R+ output the exact file name I enter. It's not a huge deal - but it is tiresome to have to rename files - especially if you're rendering large numbers of clips.

Thanks for all the hard work.

wwaag wrote on 1/14/2020, 2:40 PM

@Jep

You are the 2nd person to mention this. Guess I forgot to change that back in the latest build. Will do so now.

 

Jep wrote on 1/14/2020, 2:52 PM

@Jep

You are the 2nd person to mention this. Guess I forgot to change that back in the latest build. Will do so now.

 


Thanks Wayne - look forward to that. ;)

wwaag wrote on 1/14/2020, 4:05 PM

@Jep

Done. Here's a link where the Magix version of R+ can be downloaded. https://www.dropbox.com/s/66u6hljdn8okihb/RenderPlus.dll?dl=0

To install, download and copy to the following folder: C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\Scripts. Just make sure that Windows does not block the file. To check, right-click on file properties. If blocked, you will an a large Unblock button.

Jep wrote on 1/14/2020, 7:05 PM

@Jep

Done. Here's a link where the Magix version of R+ can be downloaded. https://www.dropbox.com/s/66u6hljdn8okihb/RenderPlus.dll?dl=0

To install, download and copy to the following folder: C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\Scripts. Just make sure that Windows does not block the file. To check, right-click on file properties. If blocked, you will an a large Unblock button.

Thanks Wayne. Will that also work with Sony Vegas Pro 13 and if not will you be providing a fix for that as well?

wwaag wrote on 1/14/2020, 7:55 PM

@Jep

For Sony, here is the link. https://www.dropbox.com/s/4d37v5lmmnw6eds/RenderPlus.dll?dl=0

The file should be copied into this folder: C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\Scripts

 

Jep wrote on 1/14/2020, 9:11 PM

@Jep

For Sony, here is the link. https://www.dropbox.com/s/4d37v5lmmnw6eds/RenderPlus.dll?dl=0

The file should be copied into this folder: C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\Scripts

 

Excellent!!! Thank you. Your speedy response is as always greatly appreciated.

Musicvid wrote on 1/15/2020, 2:26 AM

Actually, I liked the behavior, because it differentiated R+ files from those rendered in Vegas. JMO

wwaag wrote on 1/15/2020, 10:38 AM

Such differences in opinion point to the need for a set of user-defined options applicable to all HOS tools. Basically, HOS can render projects, a loop region, regions, and events. Additionally, if a file exists, HOS automatically adds a suffix so that the file is never overwritten. Some users may prefer the usual overwrite question. In any case, suggestions for naming options would be appreciated.

Ralf wrote on 1/15/2020, 12:03 PM

[...] suggestions for naming options would be appreciated.

.owa (otter/waag) or .wag / .wgg ......

Grazie wrote on 1/15/2020, 8:43 PM

@Ralf 😂.....

wwaag wrote on 1/15/2020, 9:47 PM

@Ralf

Thanks so much for the suggested extensions. I'll be sure to include them in the next build. LOL!

fred-w wrote on 1/16/2020, 4:58 PM

Question: it had seemed to be the case, per the HOS Videos, that one could trim or split video clips, using HOS. ON a recent discussion on these boards, that idea was somewhat contradicted, at least per my understanding, as you and others discussed a dedicated program to effect such a split (not HOS, something else).....Can you clear that up for me Wayne? Thanks.

wwaag wrote on 1/16/2020, 5:28 PM

@fred-w

Could you provide a link to that discussion to refresh my memory?

HOS does have a tool, VideoSmartTrim, that can losslessly trim clips that have been added to the timeline. It's useful if you only want to use a small part of a much larger file which happens quite frequently for some workflows. However, that is probably not what you are looking for.

In any case, that link would be useful.

Wayne

 

 

boffy wrote on 1/25/2020, 8:03 AM

Hi, I'm very excited to try out your Deshaker Redux, but am encoutering a couple of issues which are stopping me. I'm stabilising some footage where I was indecisive with the zoom, so I kept zooming in and out over the course of the shot. For a lot of these, I don't have any other angle or b-roll to cut away to. I've used Deshaker on its own to correct the same problem in the past. However, doing this for dozens of shots quickly becomes tedious. It'd be very helpful if I could do it right from Vegas.

With a very high value in "Adaptive Zoom Smoothness" and "Motion Smoothness: Zoom", Deshaker turns my mess of multiple zooms into one long, slow, deliberate zoom. It naturally comes out a bit softer in places where the original was zoomed out, but I find this less distracting than the constant zooming.

However, I'm unable to input the same settings in Deshaker Redux. If it try to put them in to the main "HappyOtter DeshakerRedux" window, it won't let me enter some of the extreme values necessary to salvage my shaky camerawork. E.g., I usually enter 1000 in most of the "Max correction limits" boxes but the HODR window won't accept values above 100 for them. The values I'm trying to enter are valid and work if I enter them directly in Deshaker.

If I press the blue gear icon to get into your "Advanced Options"/"Deshaker Parameters" dialog, I can enter my usual values but not save them. Pressing "Save Settings" brings up an error about the source not being found. This doesn't come up if I enter more normal values. Here is a screenshot of the values I'm trying to enter, and the error which comes up. There are a few values which aren't properly visible because of their length.

"Adaptive Zoom Smoothness" and "Motion Smoothness: Zoom" are both 1000000 (1 million)

"Extra zoom factor" is 0.333333... to zoom the video out to 1/3 of the frame's width and height.

You may note that I've got Deshaker set to output a different frame size. My timeline is 1280x720, but I have Deshaker outputting UHD 3840x2160 - 3 times the original in both dimensions. Combined with the 0.333... zoom, this means I can crop it back down in Vegas, and move or pan the clip if Deshaker would otherwise be cropping off something important or framing the shot weirdly. (Would the change of frame size cause a problem with HOS's split-screen preview option?)

Finally, something which is more of a feature request than a bug. I believe that if you set the "motion smoothness" values to -1, this locks the shot as if camera stayed rock-steady in the position of the first frame. Is it possible for it instead to lock the camera in the position of a chosen frame of the shot?

Thanks
B

wwaag wrote on 1/25/2020, 11:29 AM

@boffy

Just sent you a PM with a link where you can download the revised dll for testing.

"Would the change of frame size cause a problem with HOS's split-screen preview option?"

If frame sizes are different, the larger is resized to the dimensions of the smaller, so it "should" work. Try it.

"Is it possible for it instead to lock the camera in the position of a chosen frame of the shot?"

At the moment, ticking the Fix Pan checkbox sets all of the smoothness parameters to -1. The internal workings of Deshaker is a mystery and cannot be changed externally. The only thing that I can change is the log file that is generated with the pan values. In fact, this is how the "turbo" option works. Once the log file is created it may be possible to adjust the individual frame values based on the differences between the first frame and the frame that you have selected. I can certainly take a look.