Hello, with the import assistant I was able to successfully import my 4K / 60 HEVC material into Vegas, thank you very much. I've used the Grass Valey codec to do this. It's running so well in the preview that I do not even need a proxy server.
With the latest version of Happy Otter Scripts, the error message when starting is gone. Everything works fine.
The "white" background only occurs if you select "Vegas 14-Default" as the color theme. The "normal" Vegas 14 theme is simply "Vegas 14". If it is missing, you probably deleted it by accident. When you update HOS, it does not "overwrite" the existing "ColorThemes.xml" located in "C:\ProgramData\HappyOtterScripts" since you may have created your own color themes. If you find one or more templates missing and want to restore the defaults, delete or rename that file and then run Setup again. It will load the defaults.
The red X delete button is not located in a good place. In fact, I just accidentally deleted a V15 template. I will definitely move that to another location to reduce the chance of accidental deletions.
Answers to both questions--I really don't know at this point. The current beta period runs through May 15 and may be extended again for a number of reasons. The same is true for expected cost. Whatever the cost, it would be for a lifetime license including all updates and new tools. Like everyone else, I really don't like having to pay for an "update" every year, although that seems very common practice these days.
Just a quick heads-up for other Happy Otterers [proxy workflow]:
Ran into an issue when copying a project ('save as') and continue working with 2 different versions of those with the same Proxies (created GV HQX, in same media folder / proxy).
Trying to revert back to originals broke the functionality, and had to be done manually (via 'replace' command). Some clip takes 'disappeared' as not active, hence clip information wasn't immediately obvious
Trying to replicate so this bug can be identified.
Ok, so i have installed HOS so far. The main tool i use is RenderPlus, for the simple reason that it uses NVENC more efficient and the intigration and workflow of Frameserver is good. I mean now a video of 10 minutes with Filters takes about 3,5 minutes in 1080p instead of 5,5 its an improvement!
The other tools might come handy one day but at the moment i have no need for them.
So thumbs up for the good work. But i really hope the price will be reasonable. 50-60 USD would be very good. 90-100 usd will be ok, above that it would start to hurt.
I've downloaded the Duplicate Frames Finder tool from the HOS web page, but I'm not really sure how to use it.
First, I'm not really sure how to go about generating the sequence of .bmp frame images. I do have a Vegas script that allows me to generate a sequence of .jpg frame images, but DFF didn't find any duplicate images on a short test I performed, though I know for a fact the original footage has a lot of duplicate frames. Is that because I used .jpg instead of .bmp? If so how can I generate the .bmp images?
Secondly, I'm presuming that the purpose of finding duplicate frames is so that they can be removed prior to rendering. Am I mistaken, and if not how would I go about removing the duplicate frames?
Any clarification would be greatly appreciated, as well as any advice on how I can go about removing duplicate frames prior to rendering to smooth up output.
If duplicate frames are the result of using variable frame rate (VFR) video from devices like phones, you can try the ImportAssist tool which converts VFR to constant frame rate (CFR) video.
If duplicate frames are the result of using variable frame rate (VFR) video from devices like phones, you can try the ImportAssist tool which converts VFR to constant frame rate (CFR) video.
Thanks for the comment Wayne - but that isn't really my problem. The original video is a screen capture using OBS - constant 30fps frame rate, and it has a lot of duplicate frames. I was able to produce a sequence of .bmp images after reading AVsupport's post and DFF identified 33 duplicates in a total of 263 frames.
So I'm still not sure that I fully understand the purpose if Duplicate Frames Finder. I thought perhaps it might find and delete the duplicate .bmp images, you could then drag all the remaining .bmp images to the timeline in Vegas and output that as a smooth video in .mp4. But DFF just finds the duplicate images and it would be quite tedious to delete all the duplicate .bmps by hand to make a video of any length. Not to mention of course the audio and sync issues that would follow on from that. Enlightenment gratefully accepted.
DFF is strictly a diagnostic tool. It only tells you IF you have a problem and the extent of the problem. In your case-- over 10% which is a real problem. Duplicate frames is a common problem if you are using cell phone video which is usually variable frame rate, although footage from my iPhone produces no duplicate frames even though it is VFR. Since you are capturing CFR footage using OBS, it most likely means that your system is simply not fast enough to keep up--hence the duplicate frames. Simply deleting the duplicate frames is no solution since it interrupts the smooth motion flow and would produce "jerkiness". Even skipped frames for 60fps video can be noticeable.
I would suggest that you upload some sample footage that I could download to have a detailed look. Also detailed info on your OBS settings would be helpful.
DFF is strictly a diagnostic tool. It only tells you IF you have a problem and the extent of the problem. In your case-- over 10% which is a real problem. Duplicate frames is a common problem if you are using cell phone video which is usually variable frame rate, although footage from my iPhone produces no duplicate frames even though it is VFR. Since you are capturing CFR footage using OBS, it most likely means that your system is simply not fast enough to keep up--hence the duplicate frames. Simply deleting the duplicate frames is no solution since it interrupts the smooth motion flow and would produce "jerkiness". Even skipped frames for 60fps video can be noticeable.
I would suggest that you upload some sample footage that I could download to have a detailed look. Also detailed info on your OBS settings would be helpful.
Wayne - many thanks for taking the time to educate me. I knew before I ran DFF there were duplicate frames just by stepping through the timeline frame by frame. Thought DFF might be a cure - but no problem - can't have everything in life or video editing for that matter.
I won't bother uploading samples, because in this case I don't think the juice is worth the squeeze, and I really don't want to waste your time. But many thanks for the offer to look it over, as well as all the other HOS good stuff. 👍
Hey, I'm new with HOS but I want to try it now. I have my first problem: If I started HOS the first time and the script checked my GPU, the programm can't found any GPU (codec?!). I want to render with CPU and GPU and now I can only render with CPU. How can I fix the problem?
To perform GPU supported renders, you must have the requisite hardware which can include one or more of the following: an Intel processor with graphics, an Nvidia graphics card or an AMD graphics card. The GPU check that is performed when HOS first starts checks for the availability of such hardware. If they are not found, then only CPU renders are supported.
To recheck again, do the following. First, launch Render+. You will get this screen:
Open the Encocder dialog by clicking on the blue Options button as shown. You will get this.
The click on the Blue "I" button as shown which will run the GPU check again. If your system supports GPU renders, the result will look something like this.
On this system, I can perform either QuickSync renders or Nvenc renders. The available codecs are also shown such as avc or hevc.
I would suggest that you re-run the GPU check and post a screen grab of the results.
I remember reading in one of the posts on this forum that it's not good to use the GPU for encoding. Can't remember what exactly it was that I saw, but ever since then I've just been using the CPU
Your driver is the problem. You must install 418.81 or later. The app that HOS uses for Nvenc encoding was updated last Fall to the latest Nvidia SDK and as such requires a later driver than yours. In the last version I had a warning at the end of HOS setup. Perhaps I need to add it back.