Hi Jep,

Question. Why did you choose to use a custom script when the RenderPlus GUI supports frame rate changes and also correctly sets levels? The underlying script is the same. If you use a custom script, then you have to correctly set these levels yourself inside the Avisynth script.

In any case, just change ConvertToYV12() to ConvertToYV12(interlaced=false,matrix="PC.709"). This tells Avisynth to maintain PC levels with HD color coefficients.

"Perhaps it's those missing requirements causing the problem." No. All of the required plug-ins can be found in "C:\Program Files\HappyOtterScripts\AvisynthRepository\AVSPLUS_x86\plugins".

Regarding the Vegas 2 Handbrake script, it should work with the version of Avisynth+ that is already installed. If you were to install a regular version of Avisynth such as 2.58 or 2.6MT, then HOS would not work at all since it requires Avisynth+.

 

 

Hi Wayne - sorry for taking so long to reply, but I was laid low by a bad dose of flu for the last few days.

To explain why I used a Custom script boils down to the way I "surveyed" HOS when I first installed it. I clicked through every option and button available to try and see what it could do. When I saw the Custom script titled "Change Frame Rate.avs" and checked it's contents, I just presumed that was the correct tool for the job. I completely missed the fact that the drop down list in the "Frame Rate" box would do what I wanted. Since reading your reply I've tried it out and it works perfectly with the output being for all intents and purposes the same as the original. I did find it interesting what you said about setting levels in Custom scripts. For that piece of information alone it was worth asking the question imo. Many thanks for all your time and effort to educate me.

For others like Marco who asked why I wanted to bother with Send2HandBrake when I had HOS up and running the answer is quite simple. I had Send2HandBrake doing what I wanted and was struggling to get the same results with HOS. So at least until I sorted out what I was doing wrong with HOS I wanted to keep the option to use Send2HandBrake available. I'm pretty sure I'll be using HOS exclusively from now on. Which raises another small query:

I'm pretty sure during the HOS install process there was a popup that said the HOS licence expires on 31 Jan 2019. Just wondering what will happen after that. Will HOS die? Maybe the licence will automatically renew? I suppose bottom line I'm asking how safe can we feel about the continued use HOS into the future? I'd really hate to see it disappear. I'd have no problem signing up for a paid version.

Thanks again, and a Happy New Year to all.

For some reason I do not know, I can no longer use SlowMotion of the HOS. Anyone else here have this problem?

For some reason I do not know, I can no longer use SlowMotion of the HOS. Anyone else here have this problem?

I think the erorr is due to the beta licensing is for only 1 month of usage. I could be wrong. The slow motion in hos is painfully slow. But the results is very good,

@BruceUSA

"I think the erorr is due to the beta licensing is for only 1 month of usage. I could be wrong."

That's not the issue. Everything will work until the expiration date and even after that, the toolbars and some of the scripts will continue to work.

@Jep

Regarding the future of HOS, no it won't die. Until "language" problems are sorted out (most likely Joelson's problem), HOS will remain in Beta.

Ciao,

today I've started a render using RENDER+ and I was notified about the new update, a popup screen informed me to check the download folder for the new file to install, maybe it would be useful to have some sort of download progress bar in a separate window to know that download is working.

Moreover, after the render was started, I aborted it to change something in my project, and now HO not works anymore, clicking on any icons don't open anything, just icons to customize the gui.
After installing the new version I was able to use again HO.

Ciao
Rocco

@Musicvid

Downloaded the mkv without issue. Easily imported into Vegas with ImportAssist, even with the unusual frame size.

@Yarin VooDoo

Good point. I've had someone else identify the same problem. Will fix with next release.

Can I encode interlaced project with Render+ and x264?

The answer depends on what you are trying to accomplish. It is my understanding that X264 does not natively support traditional interlacing. If your output must be interlaced (E.g. for BluRay), it won't work. In such cases, you'll have to use either Sony AVC or the MainConcept encoders. However, if you want your output to be progressive, then it will. In such cases, it is best to apply de-interlacing as part of your render using the Avisynth settings dialog. Or you can just render "as is". A warning will appear that you are rendering an interlaced project and de-interlacing is recommended. However, that warning can be ignored and rendering will still occur. You can use this option at your own risk. Hope this helps.

For awhile I use Debugmode Frameserver + RipBot264, but output image is less contrasted and so I'm looking for alternative. I'm trying to avoid Sony AVC or the MainConcept encoders because they are not very good. I don't have problems with interlaced footage with RipBot264, however i try to ignore the warning and do encode with HOS - image is great, but the output is flagged as progressive and there is interlaced lines. I think there must be option in x264 for interlaced footage.

Sorry my English :)

@max9

Your English is great. I will definitely have another look at this. After a bit of searching, I've found that you can apparently render to interlaced with just a few changes. I'll do some testing, and if successful, will post a Custom Command Line for you to try. Thanks for trying HOS.

No, I thank you for your work. It's great tools!

@max9

Here is a custom command line using the Default settings but with the addition of the command for interlaced rendering.

avs2pipemod -y4mp <inAVS>  | ffmpeg -y -f yuv4mpegpipe -i -  -itsoffset 0.0444 -i <inTempWav> -map 0:0 -map 1:0  -c:v libx264  -pix_fmt yuv420p -crf 23 -preset medium -x264opts tff=1  -c:a aac -b:a 128k  <outFile>.mp4

Note that you only have to add "-x264opts tff=1" to whatever command line you are using. For lower field first, change "tff" to "bff". The correct Avisynth flags had already been encoded.

Of interest, rendered files (upper field first) are shown to be UpperField using Media Info. However, Vegas decodes them as LowerFieldFirst.

I will add this functionality to the next release of HOS.

Thank you again for pointing out this omission.

@wwaag How would one go about improving 8mm 16fps film in terms of de-shaking, noise reduction and maybe framerate conversion to 24p? Any tutorials to watch? The films have been scanned with a RetroScan 8 Pro to an image sequence. Is that something HOS would be useful at?

These are from the author of the original Deshaker Script.

https://m.youtube.com/watch?v=4Gy9ZG23TTk

https://m.youtube.com/watch?v=uzMFodrGHDs

@Musicvid

Here's another YT of JMs work--it's a lot longer. It's really some amazing restoration work that he does.

How to go about improving 8mm is a major topic in itself and there's a lot of stuff already published. Most notably the work of VideoFred, https://forum.doom9.org/showthread.php?t=144271 and https://forum.doom9.org/showthread.php?p=1592567#post1592567and a good thread on Dirt Removal https://forum.doom9.org/showthread.php?p=1592567#post1592567.

Another resource is the Restoration subforum on VideoHelp where John Meyer used to be active. There are active threads on 8mm restoration. I've pretty much abandoned VidHelp since, for whatever reason, each page takes about a minute to load.

Can HOS help? Of course (LOL), since many of the underlying scripts are based on JM's work--in particular, temporal denoising, deshaking, and frame rate changes. Having said that, I suspect that one's results would pale in comparison with those seen on the YT vids. I did a few restorations years ago using these scripts (long before HOS) with just camcorder captures and they turned out OK, especially the reduction of grain and artifacts using temporal denoising. My old 8mm's were too shaky to even bother with stabilization. I still have most of the original Avisynth scripts and could make those available to you if would like.

That's the video I was looking for!

I did research JM and VideoFred in the past, will rewatch it again. I am just wondering, does have HOS have any issue with image sequence as a source? Does it need a proper video file? Does a frame rate conversion from 16fps to 24fps even make any sense; I am trying to get a smoother playback.

At the moment, HOS can't import an image sequence. However, that would be an easy option to add to ImportAssist. Just finished a short project importing a sequence of Tiff images, so I'm familiar with the code. Regarding the frame rate conversion from 16 to 24--that would seem to be fraught with problems. A better conversion might be to import the sequence at 15 fps and then do a double to 30. Why don't you upload a 5 to 10 sec image sequence and I'll play with it this weekend? If need be, I can send you a PM with a Dropbox location.

@wwaag I would really appreciate your help. I will upload an image sequence and post the link here.

Edit: here is a link to a short sequence, it’s still 5GB but you can download less.

New version 1.0.2.51 released with improved non-English language support, some added features, and bug fixes. Change log may be found here https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf. Beta period has been extended to 3/31/2019. Feedback to date has been much appreciated.

Any plans for a windowed scalable UI?

I get eye fatigue easily.

Am I correct in understanding that I should uninstall all previous scripts/programs associated with the Vegas2Handbrake workflow if I intend to use HOS? Thank you for producing this by the way. I'm excited to see how it performs with deinterlacing and resizing SD footage.