Happy Otter Scripts for Vegas Pro

Comments

MikeLV wrote on 9/8/2019, 10:40 AM

Hi @wwaag, so it happened again this morning. My computer was asleep overnight (Vegas was closed), and when I went to R+ a new project, it didn't work. As soon as I rebooted and went back in, it rendered fine. Is this normal for HOS to not work after the computer was asleep. Perhaps some setting somewhere causing it to happen? Just want to let you know in case anyone has this kind of issue.

Grazie wrote on 9/8/2019, 10:48 AM

"I MUST be doing something wrong?" Yes, you are.

@wwaag - And by the Bucket Load!! - OK, now I understand more. Are there any ways I can change the KWIK Render Template without needing to Reset every time? Also, can sonmebody suggest some neat quality Renders for KWIK that are faster than what I'm getting?

Wayne, thanks again for the guidance. KWIK is working well. Is there any way it can use MORE of my GPU RAM?

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

wwaag wrote on 9/8/2019, 10:50 AM

@MikeLV

"Is this normal for HOS to not work after the computer was asleep."

I honestly don't know since I always shut down at the end of the day. Good question. I'll have a look although offhand I don't see why it would make a difference.

Grazie wrote on 9/8/2019, 11:00 AM

@wwaag - I wish to use more of my GPU to make KWIK . . . KWIKer? Here's a ScreenGrab of Win Task Manager:

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

wwaag wrote on 9/8/2019, 11:05 AM

@Grazie

"Are there any ways I can change the KWIK Render Template without needing to Reset every time?"

No. If you want to change the render template, you must right click and choose reset. I could eliminate the "nag" about "Do you really want to do this?" but that would be a bit risky since that dialog appears for resetting all scripts.

"Also, can sonmebody suggest some neat quality Renders for KWIK that are faster than what I'm getting?" Use of Nvenc is probably the fastest. If your cpu supports QuickSync, you might try that, although it's always a bit slower on my system than Nvenc.

"Is there any way it can use MORE of my GPU RAM?" I presume that you are using Nvenc for rendering. AFAIK there is no way to control the amount of GPU RAM that is being used. However, that's a question for Rigaya, the developer of the Nvenc rendering app. HOS is just the messenger between Vegas and that app.

supergafudo wrote on 9/8/2019, 1:08 PM

Thank you very much for this amazing tool.

I have imported a lot of still images as a sequence, with the idea of rotoscoping in photoshop every frame of the sequence. The problem is that when I was going to use photoshop the script does not recognize it as an image (obiously btw). Is any way to bypass this? This feature would be really usefull.

thank you for this tools.

Musicvid wrote on 9/8/2019, 1:19 PM

You export and import image sequences for Photoshop directly in Vegas, using the "Render As" and "Open" dialogues. Another script couldn't do it better, I think. I do it every day. Here's a new clipping demo I did just the other day..

 

wwaag wrote on 9/8/2019, 4:05 PM

@supergafudo

Thanks for the compliment. For the moment, Musicvid is correct. Just use Vegas.

Having said that, I have thought of adding the option to render Sequences, with the added advantage of being able to apply the Avisynth filters in Render+ such as denoising, slow motion, etc. If there is any interest, this could easily be added.

zdogg wrote on 9/8/2019, 4:22 PM

If you're going to be doing serious Rotoscoping, you might try to use FXHome's Hit Film express (free) and you can ad the Mocha module for $50. at least it has been that price in the past year. That will get you the sort of results that are pro. Or rent After Effects and it comes with Mocha, then you can use the rotoscope and paint tools in AE to clean up if necessary, depends on how exact you'd want. IF it was ONE job that was involved and critical, and I did not have a ton of cash, I would rent AE for a month (I think you can do that)...you really do need the paint tools sometimes, rotoscope plus clean up..... You don't want to do frame by frame cutting out by hand for more than a few frames....not only will it be frustrating but your results are just not going to be very good....If Hitfilm Express has anysort of paint tools, I could also recommend that as a first choice.

 

zdogg wrote on 9/8/2019, 4:31 PM

If HOS does not render out image sequence (don't see why not, but I don't know) , Vegas absolutely does that. Please guys, don't come in with you can do it all in Vegas, again, Rotoscoping is something I have quite a lot of experience with, it would really depend, there might be an instance or two, certain objects with fixed shapes, or objects in the background where it's not hypercritical, but otherwise, no. You need the higher end tools that Vegas just doesn't have, though there is a Mocha FOR Vegas as well, but it's expensive.

 

Musicvid wrote on 9/8/2019, 4:52 PM

with the added advantage of being able to apply the Avisynth filters in Render+

Well, for rotoscoping in PS that would be way cool because one could control noise, smoothing and color blending, etc. going in, using custom avs scripts. As @supergafudo knows, preprocessing the details can have a huge impact on the line and chromatic output. Personally, I do some of this in Illustrator. Do you use a custom Action for Photoshop?

wwaag wrote on 9/8/2019, 5:33 PM

"Well, for rotoscoping in PS that would be way cool because one could control noise, smoothing and color blending, etc. going in, using custom avs scripts."

I'll add that to the next build since it's a really simple addition (famous last words). It will be awhile since I'm away from my development machine for the next 3 weeks.

zdogg wrote on 9/8/2019, 11:36 PM

Yes, Photoshop, I could see, might be a viable tool, though I haven't personally done frame to frame editing with PS, though I've seen that it does have some basic functionality. The problem with frame to frame without some sort of tool that bridges the frames is that you can cut out each frame "correctly" but there is more than one way to cut and still be more or less correct, but the slight variance frame to frame is just going to kill the illusion, and of course, if it's just too many frames that gets quite tedious as well as really tricky, especially if you're talking about the outline of human head with wispy hair or the like.

 

Jep wrote on 9/9/2019, 2:24 AM

Hi Wayne. I updated to the latest version of HOS and R+ is behaving strangely.

When I start the a render it goes through the wav stage normally and then switches into the DebugMode Framserver stage and the progress box pops up in the bottom left of my screen. But after 15 or 20 seconds the rendering appears to freeze, and also there is no render info displayed in the progress box. It's just a black box with the progress bar all white and the red X to stop render operations. If I do nothing it will just stay like that. However if I click the red X to stop the render, the progress box disappears - but - the render actually unfreezes and I can see the render continue in Vegas. Finally when the render completes DebugMode Frameserver does not close down. Nothing happens if I click on DebugMode Frameservers's "Stop Serving" button. I then have to open Task Manager and End Task Vegas and open a new instance of Vegas.

R+ was working perfectly until I installed the new HOS update. Not sure if this is just a bug on my system or something wrong with HOS.

Thanks for all the hard work.

Jep wrote on 9/9/2019, 9:07 AM

Hi Wayne. I updated to the latest version of HOS and R+ is behaving strangely.

When I start the a render it goes through the wav stage normally and then switches into the DebugMode Framserver stage and the progress box pops up in the bottom left of my screen. But after 15 or 20 seconds the rendering appears to freeze, and also there is no render info displayed in the progress box. It's just a black box with the progress bar all white and the red X to stop render operations. If I do nothing it will just stay like that. However if I click the red X to stop the render, the progress box disappears - but - the render actually unfreezes and I can see the render continue in Vegas. Finally when the render completes DebugMode Frameserver does not close down. Nothing happens if I click on DebugMode Frameservers's "Stop Serving" button. I then have to open Task Manager and End Task Vegas and open a new instance of Vegas.

R+ was working perfectly until I installed the new HOS update. Not sure if this is just a bug on my system or something wrong with HOS.

Thanks for all the hard work.

Just a quick update. I reverted to version 1.0.2.61 and that fixed the problem. I also tried going back to 1.0.2.62 but had the same problems with that version.

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

@Jep

If you start a render and nothing happens as described, try this. Open task manager and under Background processes, make sure that "ffmpeg" is not found. If it's there, kill the process. Then go to "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus" and make sure that there is no fs*.avi file. Then retry it. In any case, I will have another look. I'm away from my development machine for 3 weeks, but can still make some changes "on the road". If anyone else is having similar problem, please advise. Thanks.

Musicvid wrote on 9/9/2019, 10:42 AM

For the uninitiated, frame based processing in Photoshop doesn't usually involve hand-tracing or colorizing individual frames, although it can certainly still be done that way.

Photoshop edge tracing and chroma decimation is usually done by batch processing using an Action, which is really just Photoshop's name for a Macro. At least that's the way I was shown, twenty-five years ago. No, there was typically no motion estimation involved, until ILM and the early Star Wars era.

the slight variance frame to frame is just going to kill the illusion,

And here, for a half century, I thought that was part of its inborn character and appeal; most of you were introduced to it (used in concert with traditional animation) in Yellow Submarine, 1968.

Back then, guys at Technicolor were also purposely manipulating the re-exposure lamps on Kodachrome II film processors to achieve some really wild effects. At that time KII processors were already being phased out because of worker health issues, and they were almost gone from non-EK houses by 1970, when I first started working there.

Millenials' views may need to take a bow to history, here. The examples below were hand-drawn over real frames being projected onto glass plates, millions of them.

 

BTT, and sorry for the history break, Wayne.

 

 

Jep wrote on 9/9/2019, 1:30 PM

@Jep

If you start a render and nothing happens as described, try this. Open task manager and under Background processes, make sure that "ffmpeg" is not found. If it's there, kill the process. Then go to "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus" and make sure that there is no fs*.avi file. Then retry it. In any case, I will have another look. I'm away from my development machine for 3 weeks, but can still make some changes "on the road". If anyone else is having similar problem, please advise. Thanks.

Thanks for the quick reply Wayne. I'll try that, but it may be a few days before I come back with results as I'm about to "go on the road" myself for a couple of days. I'll try it out as soon as I get back. In the meantime there's really no rush unless a lot of other people are having the same problem.

Many thanks for everything. 👍

Sylk wrote on 9/14/2019, 10:18 AM

Hi @wwaag , does this script allow to detect high light variations between 2 frames?

I have tons of many hours of lightnings footages, sometime at 120 or 240fps, and it's impossible to watch each one frame by frame. So a script to detect and mark where part and/or overall brightness of the frame brutaly change would be extremely helpfuuuul!

[OS] : Windows 10 Ent. x64 v1903 (18362.356) // (18362.295 if posted before 9/24/19)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 431.86 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)

[GPU] : Gainward GeForce 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 850 Pro 256GB
[MOB] : Asus P8P67 Deluxe (Rev.1), doesn't support iGPU
[PSU] : Corsair HX750

[DSP1] : 30" DELL UltraSharp U3011 @2560x1600
[DSP2] : 26" iiyama ProLite E2607WS @1920x1200

[UPS] : Eaton 5PX 2200i RT

[DEVICES] : GoPro Hero3 Black, Hero4 Black. Apple iPhone 6S.

wwaag wrote on 9/14/2019, 10:34 AM

@Sylk

I presume that you mean the FrameFixer tool. It was designed to detect bad frames including "camera flash" which may work. You will probably have to play around with the detection threshold setting. I would suggest starting with a small sample where you know the location of flashes to set the threshold.

Here is a screenshot.

Sylk wrote on 9/15/2019, 1:27 PM

@wwaag Nice, works fine. Possible to add a field to set the number of reference frames, to change the default 5 (at least for Flash analyse), please ?

And why not, also add an upper limit threshold. To detect lower, but not higher (and vice versa), to select a detection range, in fact. No?

Last changed by Sylk on 9/15/2019, 1:47 PM, changed a total of 1 times.

[OS] : Windows 10 Ent. x64 v1903 (18362.356) // (18362.295 if posted before 9/24/19)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 431.86 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)

[GPU] : Gainward GeForce 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 850 Pro 256GB
[MOB] : Asus P8P67 Deluxe (Rev.1), doesn't support iGPU
[PSU] : Corsair HX750

[DSP1] : 30" DELL UltraSharp U3011 @2560x1600
[DSP2] : 26" iiyama ProLite E2607WS @1920x1200

[UPS] : Eaton 5PX 2200i RT

[DEVICES] : GoPro Hero3 Black, Hero4 Black. Apple iPhone 6S.

apvv wrote on 9/15/2019, 4:20 PM

@Jep

If you start a render and nothing happens as described, try this. Open task manager and under Background processes, make sure that "ffmpeg" is not found. If it's there, kill the process. Then go to "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus" and make sure that there is no fs*.avi file. Then retry it. In any case, I will have another look. I'm away from my development machine for 3 weeks, but can still make some changes "on the road". If anyone else is having similar problem, please advise. Thanks.

Hi all.
VP 17 and HOS (1.0.2.61) on W 8.1 operating system.
The previous project worked correctly. The next project just started to freeze. I resumed. Every time it stopped (at the same time or a little later). The renderer stopped.
Uninstalled HOS (1.0.2.61), without saving the previous settings and installed the latest version (1.0.2.63).
The same thing happens this time: it freezes the project/rendering and stops.
Uninstalled VP17 and installed VP16 (latest version:16.0.424).
The same thing happens again (stops) but if I close the small window in the lower right corner (HOS) which shows the time remaining and the percentage,rendering/projects continues and now the project is completed/rendered. PS: I redo the project and the same manifests itself.
What happens? What could be the cause and what would be the solution/solutions?
Thanks in advance,first of all,to the HOS author and to the other members for their support.

Jep wrote on 9/16/2019, 4:39 AM

@Jep

If you start a render and nothing happens as described, try this. Open task manager and under Background processes, make sure that "ffmpeg" is not found. If it's there, kill the process. Then go to "C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus" and make sure that there is no fs*.avi file. Then retry it. In any case, I will have another look. I'm away from my development machine for 3 weeks, but can still make some changes "on the road". If anyone else is having similar problem, please advise. Thanks.

Hi Wayne. I finally got around to testing out your suggestion. This is what I found:

ffmpeg showed up in Task Manager so I killed the process. I went to "C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus" and deleted the fs*.avi file I found there. (Note - I'm on Sony Vegas Pro 13 64bit). I then had to kill the process for Sony Vegas in Task Manager to shut it down. I restarted Sony Vegas and opened the same project and ran R+ with the same render settings and it completed the render without the previous problems. I ran it a couple of times just to make sure.

I then rebooted my PC opened the same project in Sony Vegas and tried to run the render again in R+. The problems were back again with the render freezing after a few frames. I again killed ffmpeg in task manager and deleted the fs*.avi file, restarted Sony Vegas and tried again. Render completed without any problems.

So your suggestion worked, but after a reboot you have to go through the same process of killing the ffmpeg process and deleting the fs*.avi file before restarting Sony Vegas to get the render to work correctly.

Hope that information helps.

wwaag wrote on 9/16/2019, 10:57 AM

@Sylk

Glad it's working. I had never thought of the detection of lightning strikes as a possible use. I'll consider your suggestions when I return to my main development machine in a couple of weeks.

@apvv

Do you ever get the crash dialog with the option to send it. If so, please send the crash report with "appv" so I know it's from you. I have only received a couple of R+ crash reports is the last month or so. My suspicion is that it is the same issue that Jep is having.

@Jep

Thanks for the info. That is indeed helpful. The "bug" is in the main app that links Vegas to ffmpeg. For some reason, ffmpeg is not closing after a successful run in V13. I must admit that I don't do as much testing with Sony versions since most are now using Magix versions. Hopefully, I can post a fix in the next couple of days. One question the same as to appv. Do you ever get the crash report dialog? If so,i please send with some identification that it's from you.