Comments

wwaag wrote on 9/23/2019, 12:29 AM

@Jep

Just uploaded a new version of fs2enc. You can use the same link. I tested it with projects over 2 hrs and it now seems to work OK. For whatever reason, DMFS takes the same amount of time to render the signpost avi file regardless of the whether the "Write audio as pcm....." is ticked or not. Regardless, I eliminated a time check to start the status window and it now seems to work OK.

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 9/23/2019, 1:27 PM

@Jep

Just uploaded a new version of fs2enc. You can use the same link. I tested it with projects over 2 hrs and it now seems to work OK. For whatever reason, DMFS takes the same amount of time to render the signpost avi file regardless of the whether the "Write audio as pcm....." is ticked or not. Regardless, I eliminated a time check to start the status window and it now seems to work OK.

Excellent!!! Works perfectly now!!!

Many thanks Wayne.

apvv wrote on 9/27/2019, 6:14 AM

@Jep

Excellent!!! Works perfectly now!!!

Many thanks Wayne.

Sorry but it still does not work for me Wayne.

I sent you a private message and an email to the support address with 4 logs also.

Thank you again for your support and patience,too.

Jep wrote on 9/30/2019, 6:40 AM

I'm currently running Vegas Pro 13 64bit. A couple of years ago I purchased an upgrade to Vegas Pro 15 64bit, but for reasons I won't go into I didn't like it and went back to 13. I want to have another look at Vegas Pro 15 and will be installing it so I have both 13 and 15 available on my system.

I'm wondering if it is possible to install HOS for Vegas Pro 15 when I already have it installed and running on my Vegas Pro 13 setup?

Many thanks.

wwaag wrote on 9/30/2019, 8:40 AM

@Jep

Yes. Just re-install the latest version and it should work for both v13 and v15.

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 9/30/2019, 10:40 AM

@Jep

Yes. Just re-install the latest version and it should work for both v13 and v15.


Thanks Wayne.

wwaag wrote on 10/9/2019, 9:55 AM

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

New Features include:

  • RenderPlus – render image sequences in bmp, dpx, jpg, png or tif formats
  • ImportAssist
    • Import images in dpx format
    • Import stereo images in mpo format
  • FrameFixer – added option to select number of reference frames for flash detection

Bug fixes: Creation of signpost avi file taking longer than 5 sec led to crash – fixed

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.

Sylk wrote on 10/9/2019, 10:45 AM

Thanks @wwaag i'll try FrameFixer asap.

Would it be too hard make a region tool, to limit detection area to a part of the frame?

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
wwaag wrote on 10/9/2019, 11:05 AM

"Would it be too hard make a region tool, to limit detection area to a part of the frame?"

I think that you can already do this. First, use the pan/crop tool to select the region of interest. Then use RenderEvents to render to a new track making sure that under "What to Keep", you tick pan/crop. The result should be a new track consisting of only the region of interest. Then run FrameFixer as usual. The resulting markers should also apply to the original track. Try it and see if it works.

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 10/30/2019, 3:38 PM

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

Beta period extended for final time to 15 Jan 2020

New Features include:

  •     RenderPlus – option to add a custom video thumbnail to the rendered file
  •     FrameFixer – split at markers will now split audio track as well as the video track
  •     ImportAssist
    • Improved MKV support including selection of audio stream for import
    • Option to import AC3 directly for media files with dolby digital audio
    • New crop/resize GUI
    • Option to change project settings to match media file properties

Bug Fixes

  • Kwik Preview—would crash Vegas if launched in project without video tracks-fixed

  • AviDub—incorrect frame rate with frame doubling option in QTGMC-fixed

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.

Grazie wrote on 10/30/2019, 3:51 PM

Hi Wayne. I’ll be on it tomorrow. What is, “Kwik Preview—would crash Vegas if launched in project without video tracks-fixed”

Whats that?

G

 

wwaag wrote on 10/30/2019, 4:06 PM

@Grazie

If you inadvertently clicked on KwikPreview in a project with no Video tracks, the frameserver and Vegas would crash--requiring killing Vegas altogether and restarting. I only learned of the problem when I was working on ImportAssist and mistakenly clicked on KP rather than IA. I finally traced the cause of the crash to having no VideoTracks.

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 10/30/2019, 10:03 PM

@wwaag - Ah, thanks.

Last changed by Grazie on 10/31/2019, 12:03 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Grazie wrote on 10/31/2019, 12:32 AM

@wwaag - We have a Problem.

A specific KwikPreview Crashing using MOCHAPRO:

A] Using their Composite Render - Good > KP works perfectly

B] Using their Remove Render - Bad > Crash VegasPro17

As we HAVE to use their Remove Render-er, back in VP, what can you suggest?

wwaag wrote on 10/31/2019, 12:52 AM

@Grazie

I haven't a clue since I don't have Mocha. Have you tried just the default render option in KP? Does it work OK when you do the traditional Shift-B? Perhaps a screen recording?

Last changed by wwaag on 10/31/2019, 12:53 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.

Grazie wrote on 10/31/2019, 1:03 AM

I haven't a clue since I don't have Mocha.

@wwaag - Wanna download a DEMO and try it out?

Have you tried just the default render option in KP?

@wwaag - What's that? Aren't I using that already?

Does it work OK when you do the traditional Shift-B?

@wwaag - Yup, that works, but is limiting. Your KP is brilliant at giving me a full sweep of the Video. Yopu've now spoilt me 😜 . . .

Perhaps a screen recording?

@wwaag - For quick preview, as in your very successful KP, not the way I now roll 😁 .

 

wwaag wrote on 10/31/2019, 11:33 AM

There was a problem with the new beta license for 1.0.2.65. For anyone who has already downloaded and installed this version, the license expiration remains at 1 Nov. That has now been fixed. There are 2 solutions. You can Launch Help , click Check Now, download, and run setup again. Or, you can download the new license at https://www.dropbox.com/s/8pvu07x6dmhf68p/Otter.lic?dl=0 and simply copy it into "C:\Program Files\HappyOtterScripts". Then Launch Help click on the Enter License button. Sorry about the problem.

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.

MikeLV wrote on 11/6/2019, 3:34 PM

I just encoded a video and was expecting it to be around 300-400MB and instead it came out to 3.7GB!

I used h264-vce as the encoder, CQ at 23, preset was Slow. 1080i source, using setting Superfast setting for deinterlace, and double frame rate. The video is 28 minutes long

When I used to use the old Vegas2Handbrake script, the file sizes were much smaller than this. Can you tell me where I've gone wrong? Which encoder should I actually be using, QSV, VCE, or x264cpu, or x264-10bit?

wwaag wrote on 11/6/2019, 3:46 PM

@MikeLV

Let's take a look. First, post your MediaInfo from the rendered file.

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.

MikeLV wrote on 11/6/2019, 3:51 PM 
General
Complete name                            : S:\xxxxxx\xxxxxx.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 3.51 GiB
Duration                                 : 27 min 53 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 18.0 Mb/s
Writing application                      : Lavf58.33.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, RefFrames               : 2 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 27 min 53 s
Bit rate                                 : 17.7 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.143
Stream size                              : 3.45 GiB (98%)
Color range                              : Limited

Audio
ID                                       : 2
Format                                   : AAC
Format/Info                              : Advanced Audio Codec
Format profile                           : LC
Codec ID                                 : mp4a-40-2
Duration                                 : 27 min 53 s
Duration_LastFrame                       : -9 ms
Bit rate mode                            : Variable
Bit rate                                 : 288 kb/s
Maximum bit rate                         : 320 kb/s
Channel(s)                               : 2 channels
Channel positions                        : Front: L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 57.9 MiB (2%)
Default                                  : Yes
Alternate group                          : 1
GJeffrey wrote on 11/6/2019, 5:01 PM

300 to 400 MB file for a 28min 1080-60p video will lead to a very low quality. (bitrate will be around 1.4 to 1.8Mb/s).

X264 cpu will provide a better compression than GPU option but still. X264 10bits is useless because the encoder is fed thru a frameserve file which is 8bits, whatever your source or project properties are.

You can use vbr setting instead of CQ one and set it up to the bitrate i write above. You gonna have a file the size you need. Let us know whether it the quality is good enough for you.

You could also use x265/hevc which provide better compression than x264/avc

MikeLV wrote on 11/6/2019, 5:06 PM

I did make a mistake on my post. The videos in the past that were 300-400MB were sized down to 720P. I will try to re-encode using x264 cpu, at 720 and see what comes out.

wwaag wrote on 11/6/2019, 5:10 PM

@MikeLV

GJeffrey is right. The resulting video would be pretty bad. If you want to see the trade-off between bit rate and file size, there is a built-in bitrate calculator inside the EncoderSettings dialog. To use you must first select either abr or cbr as the Mode in the dropdown box. Once you do that, the calculator icon becomes enabled and you can switch back and forth between file size and bit rate.

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.

Marco. wrote on 11/7/2019, 2:59 AM

Also, if you use the FFmpeg CQ mode for different source videos you can't compare the file sizes of the results because the CQ mode will automatically adopt the bit rate.