Happy Otter Scripts for Vegas Pro

Comments

wwaag wrote on 3/17/2019, 4:34 PM

@MikeLV

"You can only have one loop region defined on the timeline right?" That's correct. But you can select a loop, render and then select another loop and render again from the same long event. In such cases, you have the same Active Take Name, so you need a way of differentiating between the 2 renders--hence the frame numbers.

"But then for the next many events, they're all going to have the same settings, but I can't do render regions, because then it will start over from the beginning."

The next version, which will be out toward the end of the week, now has an option to select events. In such cases, you can then apply the same settings to multiple events which should solve your problem.

 

rainer-d wrote on 3/18/2019, 8:49 AM

I've done a few tests now.
With MagicYUV the files become very big.
I think I'll take the GrassValley codec.
The file size is o.K. and I have found no difference to original.


I've taken the Grass Valley HQX right for 4K?


Now I have only the problem that it turns the clips all 180 degrees when I use VirtualDub.
with ffmepeg this is not so.

How can I solve this.

Thanks for the support.

 

By the way, HOS works very well.
I just have to fight through the many possibilities ;-))
Thank you for it. It definitely upgrades Vegas.

wwaag wrote on 3/18/2019, 10:17 AM

@rainer-d

"Now I have only the problem that it turns the clips all 180 degrees when I use VirtualDub."

Don't know exactly what you mean by this? Upside-down? Could you post an example?

rainer-d wrote on 3/18/2019, 11:09 AM

Yes, upside down
I have found that it is only the case with some clips.
Probably has to do with the automatic alignment of the GoPro.

wwaag wrote on 3/30/2019, 12:05 PM

New version 1.0.2.55 released with some added features, and numerous bug fixes. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf The public beta testing period has been extended for another 6 weeks to 15 May.

New Features include:

Lossless conversion from variable frame rate recording to constant frame rate without transcoding using ImportAssist. Only the timecode is changed.

Render+ now supports render of events in addition to the loop region, regions, and project.

Render+ now supports use of VirtualDub for rendering which permits use of intermediate codecs such as ProRes, Cineform, GrassValley HQX and any other VFW codecs that are installed

Added pre and post-filtering support to Deshaker

Comments are welcome.

MikeLV wrote on 3/30/2019, 12:05 PM

When I opened Vegas today, it said there's a new version. I clicked yes to download, but nothing seems to happen? Wow we posted at the same time :)

wwaag wrote on 3/30/2019, 12:11 PM

@MikeLV

Downloads for the new version now go through your browser. If there is a problem for whatever reason, you can always Launch help and click on Check Now. There is an option to download again.

MikeLV wrote on 3/30/2019, 12:16 PM

@wwaag, That's what I mean. I click help, check now, and then "yes" to download, but nothing happens after I click on yes

wwaag wrote on 3/30/2019, 1:26 PM

It should work like this. As of yet, I've had no other reports of problems.

 

MikeLV wrote on 3/30/2019, 3:24 PM

No browser action after I click yes on mine 😞

wwaag wrote on 3/30/2019, 3:38 PM

It would appear that you most likely have a security issue with your system. I changed the default browser to Chrome on another system and it worked without issue. Again, I've had no other reports of problems. Regardless, here's a direct link. https://tools4vegas.com/8uhdmflg/ Let me know if that works OK.

MikeLV wrote on 3/30/2019, 3:42 PM

Hmm strange, I have no idea. My default browser is Chrome, and it's actually open too when I try. Thanks for the direct link, that worked just fine :-)

MikeLV wrote on 3/30/2019, 3:56 PM

Render + option added to render selected events

To use this, do we select the events to be rendered by defining a loop region (that spans multiple events)? I ask because I notice the tool tip mentions the loop region when you hover over Events.

wwaag wrote on 3/30/2019, 4:03 PM

Just select the event. Guess I forgot to change the tool tip. Will fix for next release. Thanks for pointing it out.

rraud wrote on 3/30/2019, 5:53 PM

Downloads and installs fine here. I click HOS> Help> Check for updates> Check now> Yes> Happy Otter Scripts for Vegas Pro, Public Beta Trial, Version 1.0.2.55... Click here to download the setup file.. .. Download... opens your default browser... in my case, Pale Moon), save and install

MikeLV wrote on 3/30/2019, 7:26 PM

Can't seem to figure it (the new Events option) out, I selected a bunch of events, across multiple tracks. I started getting several very short rendered files that cut off at random points.

I'm not getting email notifications of new replies here either. Anyone else experiencing this?

wwaag wrote on 3/30/2019, 8:17 PM

I would not recommend selecting events on different tracks. You can think of the events option in R+ to be the same as regions, except that you just select one or more events for render without having to set up the individual regions.

MikeLV wrote on 3/30/2019, 8:25 PM

I think I got the hang of it, looks like you just need to select the longest event. Before I was choosing all the events that make up the "event" like lower thirds, etc. One suggestion, don't know if it's possible, but it would be great if the file names could be taken from the marker or region names.

Jep wrote on 3/31/2019, 10:15 AM

I've downloaded and installed the latest versions of HOS on two machines (Win 10 and Win 7) both running Vegas Pro 13. I get the following HOS warning on both machines as soon as I open Vegas

I have working internet connections on both machines, so I'm not sure why this is appearing. Not a big issue but thought you should be aware of it.

Also I'm very interested in the following feature of the latest version

Lossless conversion from variable frame rate recording to constant frame rate without transcoding using ImportAssist. Only the timecode is changed.

Variable frame rate video is the bane of my life. In particular video generated from my cell phone camera. They don't work very well in Vegas and even the output results are choppy at best. Just wondering if this feature will essentially change the footage from variable to fixed frame rate and will it improve output from Vegas?

Thanks again for HOS - I use it almost every day now. Hope it continues to thrive.

MikeLV wrote on 3/31/2019, 10:24 AM

Rendering Events is good. However, I've discovered that if I have multiple events that make up a single rendered file, e.g. to events cross faded, that it will render those as separate files as expected.

Another suggestion to achieve better selective rendering - Suppose I have multiple regions on the timeline. What would be handy is if I could select a span of regions with loop and tell HOS to render only the regions inside the loop area. Do you think it's a good idea?

wwaag wrote on 3/31/2019, 10:47 AM

@Jep

Thanks for letting me know about the warning regarding news alerts. I just added that feature for this release. Would you do the following? Click Launch Help and then click on Check for Messages. A message regarding the latest version should then be opened. Let me know if this works. My suspicion is that this might be a security-related issue since messages are stored on DropBox and are uploaded directly when Vegas starts if new alerts are found.

Regarding VFR video, all I can say is that you should try it using ImportAssist. I have tried it on Samsung Note 9 hevc, Samsung NX1 hevc, and iPhone avc and it does work. It only changes the timecode itself--the video and audio are untouched. You can verify by looking at MediaInfo before and after. In all cases in my tests, it came back as constant frame rate. I intend to post a demo later today which also includes use of the Duplicate Frames Finder, an app for detecting duplicate frames in Vegas that can occur when VFR footage is used.

@MikeLV

"What would be handy is if I could select a span of regions with loop and tell HOS to render only the regions inside the loop area." That's a good idea and one that would be fairly easy to implement. The main issue would be real estate on the GUI. I'll take a look.

Jep wrote on 3/31/2019, 11:23 AM

@Jep

Thanks for letting me know about the warning regarding news alerts. I just added that feature for this release. Would you do the following? Click Launch Help and then click on Check for Messages. A message regarding the latest version should then be opened. Let me know if this works. My suspicion is that this might be a security-related issue since messages are stored on DropBox and are uploaded directly when Vegas starts if new alerts are found.

Regarding VFR video, all I can say is that you should try it using ImportAssist. I have tried it on Samsung Note 9 hevc, Samsung NX1 hevc, and iPhone avc and it does work. It only changes the timecode itself--the video and audio are untouched. You can verify by looking at MediaInfo before and after. In all cases in my tests, it came back as constant frame rate. I intend to post a demo later today which also includes use of the Duplicate Frames Finder, an app for detecting duplicate frames in Vegas that can occur when VFR footage is used.

Thanks for the prompt reply Wayne.

I clicked on Launch Help and then on Check for Messages. When I did I got the same HOS warning that I posted above. Hope that helps you out.

I'll take a closer look at the ImportAssist VFR feature in the next couple of days.

Thanks for everything.

 

MikeLV wrote on 3/31/2019, 1:05 PM

Oh no!

I copied this out of the RenderAbort.log file:

2019/03/31  11:42:13 --
2019/03/31  11:42:13 --RenderPlus-Vegas ProcessID 4916 Encoder ffmpeg
2019/03/31  11:42:13 --CommandLine: avs2pipemod -y4mp "C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\RenderPlus.avs"  | ffmpeg -y -f yuv4mpegpipe -i -  -itsoffset 0.0444 -i "C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\wav_4916.wav" -map 0:0 -map 1:0  -c:v libx264  -pix_fmt yuv420p -crf 23 -preset superfast -c:a aac -b:a 320k  "S:\xxxxxxxxxx-Frame 0 to 50680.mp4"
2019/03/31  11:42:13 --FS Setup Window Open: 330144
2019/03/31  11:42:13 --FS Setup window inputs disabled
2019/03/31  11:42:13 --Button found: 2491134
2019/03/31  11:42:13 --Button press sent
2019/03/31  11:42:13 --FS temp file exists
2019/03/31  11:42:13 --FS Setup Window closed: 0
2019/03/31  11:42:15 --FS Status handle found: 461442
2019/03/31  11:42:15 --FS window moved
2019/03/31  11:42:15 --FS window inputs disabled
2019/03/31  11:42:15 --Run Minimized: False
2019/03/31  11:42:15 --Success--FS Status Handle 461442 4916
2019/03/31  11:42:15 --Start registry values  
2019/03/31  11:42:15 --avs2pipemod Processes count:1
2019/03/31  11:42:15 --avs2pipdmod Processes id:9648
2019/03/31  11:42:15 --ffmpeg Processes count:1
2019/03/31  11:42:15 --ffmpeg Processes id:3868
2019/03/31  11:59:19 --Render Error ProcessID:9648 3868
2019/03/31  11:59:19 --ExitCode=99

And this from the LastRenderLogFile.txt:

2019/03/31  11:42:15  --ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
2019/03/31  11:42:15  --  built with gcc 8.2.1 (GCC) 20181017
2019/03/31  11:42:15  --  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
2019/03/31  11:42:15  --  libavutil      56. 22.100 / 56. 22.100
2019/03/31  11:42:15  --  libavcodec     58. 35.100 / 58. 35.100
2019/03/31  11:42:15  --  libavformat    58. 20.100 / 58. 20.100
2019/03/31  11:42:15  --  libavdevice    58.  5.100 / 58.  5.100
2019/03/31  11:42:15  --  libavfilter     7. 40.101 /  7. 40.101
2019/03/31  11:42:15  --  libswscale      5.  3.100 /  5.  3.100
2019/03/31  11:42:15  --  libswresample   3.  3.100 /  3.  3.100
2019/03/31  11:42:15  --  libpostproc    55.  3.100 / 55.  3.100
2019/03/31  11:42:16  --avs2pipemod[info]: writing 50681 frames of 30000/1001 fps, 1920x1080,
2019/03/31  11:42:17  --                   sar 0:0, YUV-420-planar-8bit progressive video.
2019/03/31  11:42:17  --Input #0, yuv4mpegpipe, from 'pipe:':
2019/03/31  11:42:17  --  Duration: N/A, start: 0.000000, bitrate: N/A
2019/03/31  11:42:17  --    Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p(progressive), 1920x1080, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc
2019/03/31  11:42:17  --Guessed Channel Layout for Input Stream #1.0 : stereo
2019/03/31  11:42:17  --Input #1, wav, from 'C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\wav_4916.wav':
2019/03/31  11:42:17  --  Metadata:
2019/03/31  11:42:17  --    TCOD            : 0
2019/03/31  11:42:17  --    TCDO            : 16910236667
2019/03/31  11:42:17  --  Duration: 00:28:11.02, bitrate: 1536 kb/s
2019/03/31  11:42:17  --    Stream #1:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, stereo, s16, 1536 kb/s
2019/03/31  11:42:17  --Stream mapping:
2019/03/31  11:42:17  --  Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264))
2019/03/31  11:42:17  --  Stream #1:0 -> #0:1 (pcm_s16le (native) -> aac (native))
2019/03/31  11:42:17  --[libx264 @ 00000000004098c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
2019/03/31  11:42:17  --[libx264 @ 00000000004098c0] profile High, level 4.0, 4:2:0, 8-bit
2019/03/31  11:42:17  --[libx264 @ 00000000004098c0] 264 - core 157 r2935 545de2f - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=1 deblock=1:0:0 analyse=0x3:0x3 me=dia subme=1 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 pb_ratio=1.30 aq=1:1.00
2019/03/31  11:42:17  --Output #0, mp4, to 'S:\xxxxxxxxx-Frame 0 to 50680.mp4':
2019/03/31  11:42:17  --  Metadata:
2019/03/31  11:42:17  --    encoder         : Lavf58.20.100
2019/03/31  11:42:17  --    Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080, q=-1--1, 29.97 fps, 30k tbn, 29.97 tbc
2019/03/31  11:42:17  --    Metadata:
2019/03/31  11:42:17  --      encoder         : Lavc58.35.100 libx264
2019/03/31  11:42:17  --    Side data:
2019/03/31  11:42:17  --      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
2019/03/31  11:42:17  --    Stream #0:1: Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 320 kb/s
2019/03/31  11:42:17  --    Metadata:
2019/03/31  11:42:17  --      encoder         : Lavc58.35.100 aac
2019/03/31  11:58:06  --avs2pipemod[info]: finished, wrote 15163 frames [29%].
2019/03/31  11:58:07  --avs2pipemod[info]: total elapsed time is 949.669 sec.
2019/03/31  11:58:07  --avs2pipemod[error]: only wrote 15163 of 50681 frames.
2019/03/31  11:59:19  --video:271874kB audio:56907kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.231421%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] frame I:61    Avg QP:21.42  size:223169
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] frame P:3949  Avg QP:22.49  size: 41363
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] frame B:11153 Avg QP:23.79  size:  9095
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] consecutive B-frames:  0.9%  1.9%  3.1% 94.0%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] mb I  I16..4:  6.0% 30.4% 63.7%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] mb P  I16..4:  1.9%  3.9%  1.6%  P16..4: 60.3%  0.0%  0.0%  0.0%  0.0%    skip:32.2%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] mb B  I16..4:  0.1%  0.2%  0.1%  B16..8: 12.4%  0.0%  0.0%  direct:10.9%  skip:76.4%  L0:28.4% L1:50.2% BI:21.4%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] 8x8 transform intra:48.7% inter:41.0%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] coded y,uvDC,uvAC intra: 78.2% 76.5% 29.7% inter: 10.6% 9.9% 0.0%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] i16 v,h,dc,p: 30% 22% 35% 13%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 13% 26%  8%  7%  8%  7%  7%  8%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 17% 22% 11% 10%  9%  7%  9%  6%  9%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] i8c dc,h,v,p: 33% 27% 25% 14%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] Weighted P-Frames: Y:0.8% UV:0.5%
2019/03/31  11:59:19  --[libx264 @ 00000000004098c0] kb/s:4402.09
2019/03/31  11:59:19  --[aac @ 0000000000435b40] Qavg: 58518.121

All I did was change the filename for privacy..

Update: I ran it again, this time walked away from the machine and came back and it finished encoding. Perhaps the crash was due to the fact that I was working on other tasks while it was encoding.

Jep wrote on 3/31/2019, 6:53 PM

Hi Wayne. Just another little issue on the HOS Alerts bussiness. I went into the About dialog through LaunchHelp, and ticked the "Turn off notifications" option. I thought this might stop the HOS Alerts warning popup every time I open Vegas. This didn't work. It would appear that HOS is not saving that option when I exit the About dialog. If I tick the "Turn off notifcations" option, exit, and then immediately open About dialog the option isn't ticked.

Again, a very minor issue, but I though you might like to know about it.