AFAIK it shouldn't. The main reason for the latest reason was to prevent crashing when a user attempted to use HOS with Vegas 23.

I have the trial version of V23 so I am waiting for the update to be able to try Render+ with V23. Many thanks

Great, no issues with update in V22. Loaded in V23 and Otter2 bar working fine. Looking forward to the fix to be able to test Render+ in V23.

Hello Wayne,
Is it possible to provide an update on the progress of reviving the rendering functions in HappyOtterScripts, given that there is little hope for Voukoder before the beginning of 2026?

I am awaiting changes to the FrameServer by its developer. Once completed, a new version of HOS should be available fairly quickly. I am hoping by the end of the month, but don't hold your breath. Ha!

@wwaag

https://www.instagram.com/thesurfingotter/p/DP7oo92ifqN/

lol

@john_dennis

Are you sure that being an otter isn't a crime, especially a HappyOtter???

From the HOS website:

Why the name Happy Otter?  Perché no?  Why not?  I love otters even though I’ve only filmed a few in the wild.  I liked the smooth-talking character Otter in the film Animal House.  And more importantly, it’s a term of endearment from my significant other.

Actually, I filmed some playful sea otters at Morro Bay last week.

New build 1.0.3.37 is now available.

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

IMPORTANT 

• Full support for Vegas 23 rendering tools
• AudioSyncR now included as part of HOS toolset and vice-versa
  • To activate, launch Help and click on blue Refresh License Information button

New Versions of DebugMode FrameServer, Nvencc64, Qsvencc64, Vceenc64, MPC-HC
New Tools and Features

• RenderPlus—added MP4 chapter support options

Here is the link where the new build can be downloaded.

https://tools4vegas.com/ru4f7l9rxql9ykg/

Important New Licensing Information

Licensing for HOS has changed, including a substantial price reduction. Heretofore, HappyOtterScripts and AudioSyncR were licensed separately. Both are now included when purchasing a new license. For more information, go to: https://tools4vegas.com/get-a-license/

For those users who have purchased only a HappyOtterScripts license, AudioSyncR can now be used in the latest build (1.0.3.37). Likewise, for anyone who has purchased an AudioSyncR only license in the past, the full HappyOtterScripts toolset can now be used. To activate, install the latest HOS build and then click on the Refresh License Information button as shown.

You should get a message indicating both are licensed.

@john_dennis

Two happy otters.

https://vimeo.com/1130732937/f6abf20f7a?share=copy&fl=sv&fe=ci

Important New Licensing Information

Licensing for HOS has changed, including a substantial price reduction. Heretofore, HappyOtterScripts and AudioSyncR were licensed separately. Both are now included when purchasing a new license. For more information, go to: https://tools4vegas.com/get-a-license/

For those users who have purchased only a HappyOtterScripts license, AudioSyncR can now be used in the latest build (1.0.3.37). Likewise, for anyone who has purchased an AudioSyncR only license in the past, the full HappyOtterScripts toolset can now be used. To activate, install the latest HOS build and then click on the Refresh License Information button as shown.

You should get a message indicating both are licensed.

Hi wwaag. I have the older HappyOtterScript that I have not installed on my newest PC. If I download the new build 1.0.3.37 and my old license will be accepted? Can you please confirm.

PS. Awesome. I sucessfully install and activated newest HappyOtterScript with included AudioSyncR.

@BruceUSA

Glad it worked for you.

@BruceUSA

Glad it worked for you.

wwaag. In future build. Please include a option for ProRes LT, Standard and HQ. Thank you.

@BruceUSA

Those options are already there.

A quick question I have been meaning to ask. I use Render+ with AV1 (NVENC) with VBR of 53 ave 106 max (V22 or V23) with project template 8bit full range, 4K XAVCS 25p (PAL). The rendered video has slightly brighter, more saturated and more deep blacks. When rendering with same setting except Avisynth set to limited rather than default, the rendered video is identicle to the preview screen (perfect) but why? Thanks.

@BruceUSA

Those options are already there.

Ah, awesome and again thank you.

A quick question I have been meaning to ask. I use Render+ with AV1 (NVENC) with VBR of 53 ave 106 max (V22 or V23) with project template 8bit full range, 4K XAVCS 25p (PAL). The rendered video has slightly brighter, more saturated and more deep blacks. When rendering with same setting except Avisynth set to limited rather than default, the rendered video is identicle to the preview screen (perfect) but why? Thanks.

When you use avisynth "limited" option, the full range RGB file created by the frameserver is correctly clamped to video levels as expected by the encoder. So when you play the rendered file, the player automatically expands to full range, giving the same as your preview screen.

With the avisynth "default" option, the full range RGB is not clamped property before encoding, so giving you crushed black and blown out highlights when you play the rendered file.

This is only valid with 8bits full project. With 8/32bits video level, "default" should give you a rendered file identical to your output.