My steps to reproduce aren't very well identified, but it seems when working with the custom command line, I must reload it each time I run it, otherwise the audio portion goes away, and the render routine just shoots blanks. Does this make any sense?
I see the problem. It only affects renders using GPU encoders since a separate CL is required for the audioRemux unlike FFmpeg which does it all in one pass. That should be an easy fix (famous last words!). I'll upload a new R+ for you to try.
I did a completely fresh install of 1.02.60, replaced RenderPlus.dll with the new one, and unfortunately Render+ does not launch. Render Events does launch normally, however.
Something is definitely amiss and has been corrupted in your system. After installation when you first start Vegas, the R+ dialog is shown. That should not happen--I've never seen that before. After you switch R+ dlls, it is still shown when Vegas starts.
Also, why did you not install the Redistributable package when prompted right at the outset? There are still 32bit components even though it is considered a 64bit app.
I would suggest you first uninstall HOS through the normal app removal process in Settings. Then make sure everything is removed including the HappyOtterScripts folders in Program Files and Program Data. Also make sure that the DebugMode FrameServer folder is removed in Program Files. Then try a re-install and attempt a render without changing the R+ dll. If successful, then swap it out for the new one.
@wwaag , if it's working on your end, I can easily wait for the next beta. I truly appreciate your responsiveness and asking me to test. It means a lot. I have no production deadlines to worry about.
Just realized this morning my previous version has expired. After the 1.0.2.61 download, I get a virus warning. This is the first time ever I came across this. hence I am a little apprehensive.. anyone else? (using Win10/chrome/Chrono download manager
I too, the HOS creator, received a warning from Windows Defender for a 1.0.2.60 download that I had done awhile back just a couple of days ago. Running the original file through the virus scan showed clean. Apparently, some update to either Win 10 or Defender led to that update as containing suspected "malware". Googling the suspected malware showed quite a few threads about false positives. The only major change in 1.0.2.60 was the new FrameServer from Satish, plus updates from Rigaya (for QSV and Nvenc) and VirtualDub. There were no new app updates in 1.0.2.61. HOS seems particular vulnerable since all of these are "unsigned". Additionally, all updates are stored on DropBox which often leads Windows to block such downloads unless they are "unblocked".
I don't think there's a problem, but If you're worried just delete it.
I would be interested if anyone else is having such problems since this is potentially a showstopper.
yeah not worried yours is the best 'malware' ever!! sorry don't want to create panic, I realize this is annoying from your end, just wanted to provide feedback ;-)
I always get warnings as well. When initiating the HOS installs, Norton's Security suite warning details state:
- Very Few Users: Fewer than 5 users in the Norton Community have used this file. - Very New: This file was released less than 1 week ago. - Unproven: There is not enough information about this file to recommend it.
Based on that info, I always assume it is 'safe' and choose to "run the installer anyway".
For HOS users who upgrade to V17, don't forget to copy the frameserver file found in the Vegas program directory, for example, "C:\Program Files\VEGAS\VEGAS Pro 16.0\Frameserver.x64.fio2007-config" to the V17 directory. Alternately, you can just re-run the setup file "HappyOtterSetup-1.0.2.61.exe" and it will re-install the frameserver including the new version file. Please let me know if there are any issues with HOS for the new Vegas version. Thanks.