Happy Otter Scripts for Vegas Pro

Comments

Musicvid wrote on 6/3/2019, 1:13 PM

rraud wrote on 6/3/2019, 10:35 AM

I have no problems with HOS on my laptop, which has a max res of 3840x2160 which I have set to 1920x1080 with a 175% DPI setting. I need the larger text and GUI for my less than perfect aging eyes.

+10

wwaag wrote on 6/3/2019, 1:45 PM

@Musicvid

@rraud

This is not meant to be snarky by any means, but why use a 4K display when you have to enlarge the content, especially for editing? Since preview of 4K material is usually pretty poor once Fx are added, we often resort to the use of lower resolution proxies. So what's the added value? Just curious.

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 6/3/2019, 2:18 PM
 

@Jep

Obviously, something is wrong. If possible, could you upload a screen recording? Here's a recording showing how it "should" work using the example in the demo.

The RemoveDups button is only for dups that you have added, not for dups already in the footage. For that reason, it is grayed out.

Thanks Wayne - I think I've figured it out. I was taking exactly the same steps as in your tutorial vid (with the exception that I had to jack the duplicate frame detection threshold up to 0.0020 to detect duplicate frames), but I didn't have MagicYUV installed. As soon as I installed MagicYUV it worked OK and added the clips to a new track above the timeline.

The only comment I'd have is that if I step through the timeline frame by frame, the duplicate frames all appear to be still there - including the clips added above the timeline. So unless I'm doing something wrong (a good possibility) it doesn't really seem to fix anything. I'd be interested in your comments on that.

Thanks again.

Musicvid wrote on 6/3/2019, 2:58 PM

Wwaag, your question is well received, and not even a little bit snarky.

I am often on an old 15.4" laptop with a 1280x768 display, font scaling 125%, and cannot converge properly on the GUI windows in HOS for 5 minutes without stopping from eyestrain. I am fine with Vegas set the same way, but I lose some buttons at the bottom of windows.. Enabling accessibility and back every few minute makes me frustrated.

I have a friend who is a retired Martin Marietta aerospace machinist, now 80, who has eyes like yours. What he calls a ding I can't even see when he points at it. Unfortunately, that acuity is not commonplace with people who were born farsighted and astigmatic, even with professional correction.

I told you I am a buyer. You have put an incredible amount of time into this that you will never recoup through sales. I will gladly PayPal a donation for even crude 2x raster scaling, which even I have done in my VB class decades ago. Please?

wwaag wrote on 6/3/2019, 3:14 PM

@Musicvid

No problem. I will definitely see what I can do.

@Jep

Since you had to increase your threshold by that much, the frames are not true duplicates and hence, they are not being replaced. The detection process is completely independent of the replacement process. Here's something to try which may work. First run the duplicate analysis in order to identify duplicates. Then switch from Duplicates to Flash. At that point, you can add true duplicates. Then run the replacement. Let me know if that works.

If you upload some sample footage, I will take a look as well. Regarding duplicates, it's always best to replacement them "before" doing this analysis and replacement if at all possible. For example, if you have variable frame rate video, first try the VFR to CFR conversion in ImportAssist.

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 6/3/2019, 3:41 PM

In deference, a lot of guys like @rraud and me studied audio engineering in college because we can't see worth a s**t.

rraud wrote on 6/4/2019, 10:06 AM

@Musicvid

@rraud

This is not meant to be snarky by any means, but why use a 4K display when you have to enlarge the content, especially for editing? Since preview of 4K material is usually pretty poor once Fx are added, we often resort to the use of lower resolution proxies. So what's the added value? Just curious.


My laptop (Dell XPS 9550 w/ Nvidia GTX 960M) display is set to 1920xI080, It's max ("recommended") setting is 3840x2160, but if I set it to that, the Vegas toolbar icons appear (to my f'kd up eyes) as tiny dots, the size of pin heads. I would have to increase the DPI to be well beyond 175% to be able read the GUI.. if it even goes much higher than175%. I do however usually use an external monitor for picture. I've tried most of VP's display options with different PC display and DPI settings, so I set it with something I can 'live with'. Unless of course I'm doing something wrong.. a distinct possibility, I'm just a dumb audio guy.

As I stated, I have no problem with the HOS display, though having a larger size option would be nice.

wwaag wrote on 6/4/2019, 11:29 AM

@Musicvid

@rraud

I think I have found a solution. Not the most elegant perhaps, but it works and is easy to implement. What do you think?

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 6/4/2019, 12:27 PM

That looks good to me Wayne. Plenty elegant for most of us, I would think. Magix should hire you.

Musicvid wrote on 6/4/2019, 1:30 PM

Now that would be a treat. I'm sure i could work with it.

wwaag wrote on 6/4/2019, 1:52 PM

I should have a new version out in the next couple of days with these changes.

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 6/5/2019, 7:15 PM

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

Only one new feature has been added. All dialogs are now scalable with a selection of three font sizes from the title bar. Additionally, the default font size may also be changed from inside the Theme Designer.

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.

Musicvid wrote on 6/5/2019, 10:37 PM

Will test tomorrow. Like Christmas in June!

ryclark wrote on 6/6/2019, 6:58 AM

Excellent. Thanks Waag for all the hard work and continued support for your app. 😀

Jep wrote on 6/9/2019, 4:52 PM
 

@Jep

Since you had to increase your threshold by that much, the frames are not true duplicates and hence, they are not being replaced. The detection process is completely independent of the replacement process. Here's something to try which may work. First run the duplicate analysis in order to identify duplicates. Then switch from Duplicates to Flash. At that point, you can add true duplicates. Then run the replacement. Let me know if that works.

Hi Wayne. Sorry for taking so long to reply - been really busy over the last week. Finally got around to trying your suggestion, and it seemed to work reasonably well. Not perfect - but it did remove a lot of the judder when I rendered the results to .mp4 from Vegas. Many thanks for all your help.

BTW - really like the new scaleable dialogs feature. Excellent refinement.

 

Jep wrote on 6/28/2019, 2:30 AM

I'm having some problems while using Render Plus. I'm running Vegas Pro 13 64 bit on Windows 10. I've been using Render Plus for quite a while now without any problems, so this appears to be somewhat weird.

About 10 days ago I set up Render Plus to render a video. Vegas crashed. I tried several more times and Vegas kept crashing. The crash came When HOS switched from the Writing Signpost Avi popup to DebugMode Frameserver operations.

So I did a clean install of HOS (including removal of the existing HOS). I set Render Plus to render the video again and it rendered without any problems. However, the next time I tried to render with Render Plus, Vegas crashed again. As before it was just as HOS switched from Writing Signpost Avi to DebugMode Frameserver operations.

After a lot of playing around I've found that after every successful Render Plus render, Vegas reverts to crashing at any attempt to render with it after that, and the only way I can use it is by doing a clean reinstall of HOS.

I also tried to install a previous version of HOS, but experienced the exact same problems.

I also have the same Vegas Pro setup on a Win 7 machine, and Render Plus and HOS seem to be working fine on it.

The only major change to my setup that I think might be having an impact is the installation of an AVerMedia Live Gamer HD II video capture card along with AVerMedia RECentral 4 software about a month ago. I'm not sure if that might have done something to my system that is resulting in Vegas crashing.

I'd be very interested in hearing from anyone who might know what's going on and what I could do to fix the problem.

TIA

wwaag wrote on 6/28/2019, 7:15 AM

HOS Bug Alert--Vegas Crash after FrameServer Starts

I've had a number of users report that Vegas crashes right after the frameserver starts (which I have reproduced using 1.0.2.59). Thanks to some detective work by John Dennis, the problem stems from the introduction of a new build of the FrameServer. It occurs whenever the older FrameServer versions attempt to "check for updates". The issue affects not only HOS, but anyone using the previous version for use in such scripts as Vegas2Handbrake, For non-HOS users, simply download and install the new FrameServer version. For HOS users, I've kluged a workaround which blocks the FrameServer from checkng for updates in the app that links Vegas to the encoder. It can be downloaded at. https://www.dropbox.com/s/rxtne1htpxp73gc/fs2enc.exe?dl=0 The file should be copied into the following folder "C:\Program Files\HappyOtterScripts".  Be advised that this "fix" may or may not work for your specific installation.


The new FrameServer version will be incorporated into the next HOS build.

 

Last changed by wwaag on 6/28/2019, 7:18 AM, 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.

wwaag wrote on 6/28/2019, 9:45 AM

Just a short note to add that Satish, the FrameServer developer, is now aware of the problem and will provide a fix next week sometime.

Last changed by wwaag on 6/28/2019, 9:45 AM, changed a total of 2 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.

Yarin VooDoo wrote on 6/28/2019, 2:47 PM

Thanks for the workaround, finally HOS works again! 😉

Jep wrote on 6/28/2019, 3:52 PM

Thanks for the workaround Wayne, HOS now working fine again. 👍

Quindor wrote on 7/1/2019, 10:14 AM

@wwaag I need to give you a big thank you! I recently opened a topic about issues rendering in 4K60 and I've been having two issues trying to render my projects in 4K60 for a while now, one if that the render will get stuck at a random point (which it doesn't rendering in 720p or 1080p), I have some tips for that in the topic I made.

But another problem I would often encounter is that during some cross-fades there would be all kind of corrupted colors (I have an example in the topic) during that fade and sometimes in all the footage after it until a big scene change happened. As a last resort to try and solve my original problem, the hanging issue, I tried to use the Otter scripts but alas they can't prevent that from happening.

But!!! they do prevent the rendering bug I see with the color corruption after certain cross-fades! So while the rendering getting stuck issue is somewhere in the Vegas Pro compositing engine the color corruption issue seems to be in it's compression pipeline which gets by passed using your scripts.

Anyway, as I said, a big thank you, Vegas has a bug to solve (they have had this bug for at least a year) but your scripts provide a perfect workaround! :)

IAM4UK wrote on 7/7/2019, 3:12 PM

@wwaag Great job with HOS!
I am "beta testing" this month. I haven't found a Purchase link on your site, but I have a 48 Hour Film Project coming up in early August, so I'll probably want to purchase your scripts before that time...assuming you don't extend the beta test through that time.
Some things I've found:
"RenderEvents" won't work for me at all. It just doesn't function. But what I was trying to do with RenderEvents is to Render project Regions with names, using MagicYUV CODEC in AVI containers, and I have found that I can do that with "RenderPlus."
"ImportAssist" works, but NOT if the video to be imported contains no audio. I solve that in the obvious way...shoot with audio, even if I'm going to use a different audio source for my project.

wwaag wrote on 7/7/2019, 8:22 PM

@IAM4UK

No worry. The beta will be extended again. The next build will include a new license--probably next week sometime.

Regarding "RenderEvents". To render to MagicYUV in an avi container, you must select "Vegas" as the render option. You must first create your MagicYUV template inside of Vegas. Once the template is created, exit Vegas and then restart for the template to be shown. This should work. Sorry that I can't test it. I'm near the end of a month-long road trip with just a laptop that doesn't have the MagicYUV installed. Try it and if there are problems, let me know.

Thanks for the kind words regarding HOS.

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.

Grazie wrote on 7/8/2019, 12:54 AM

Wayne, beautifully delivering a precisely constructed ToolSet. Well, This Otter, is Otterly Pleased! Working on my new MONSTA! and using my favourite for years now, RenderEvents (really liking that RE Icon. Work of Art 😉) makes my narrative creation super quickly, slickery.

I've got the Otter Bar sitting under the Preview Screen. Sheer Genius.