Comments

wwaag wrote on 8/20/2019, 11:33 AM

@MikeLV

Not really. Your new card may or may not speed up your renders in general depending upon your project. If you have quite a few GPU-supported Fx, you should see a speed increase within Vegas itself. For the render itself, you should now be able to use VCE rendering which is definitely faster than CPU-only renders. You will need to judge whether the quality is acceptable. If you haven't done so, you will need to enable VCE rendering by opening the Encoder Settings dialog in Render+ and click on the blue Information icon next to "Encoders". You will then see what rendering options are supported.

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 8/22/2019, 10:01 AM

Ok, I just ran the GPU check, and all have red x's except for the last two options for AMD VCE which have green check marks. But when I click the drop down for the list of Encoders, I don't see anything that says VCE, just what you see in the screenshot. Does that mean something is wrong? Should I see VCE as an option in the list?

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

Yes, you should see the two vce 0ptions (avc and hevc). Close R+ and try it again. As I recall, it doesn't show up immediately. You have to reload R+.

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 8/22/2019, 10:53 AM

Right you are (as always!) Thanks, will give this a try :-)

MikeLV wrote on 8/22/2019, 12:08 PM

It did not seem to work (VCE). I started the render, it wrote the wav file first like it always does, then it looks like it's going to encode, and the encode window just disappears, and the render progress window shows on the bottom right with no activity.

Then when I click the red x to close the render progress box, I get this:

And when I click details, I get this info:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\renderLogFile_3052.txt'.
File name: 'C:\ProgramData\HappyOtterScripts\Sony Vegas Pro\RenderPlus\renderLogFile_3052.txt'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
   at fs2enc.Form1.Form1_FormClosing(Object sender, FormClosingEventArgs e)
   at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
   at System.Windows.Forms.Form.RaiseFormClosingOnAppExit()
   at System.Windows.Forms.Application.ExitInternal()
   at System.Windows.Forms.Application.Exit(CancelEventArgs e)
   at fs2enc.Form1.abortRenderClick(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
fs2enc
    Assembly Version: 1.0.11.18
    Win32 Version: 1.0.11.18
    CodeBase: file:///C:/Program%20Files/HappyOtterScripts/fs2enc.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3353.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Does it mean anything to you? I sure hope this card wasn't a mistake. I notice Vegas running strangely since I installed it. Clicking on track FX button and going from window to window, there's a long lag, the screen re-writes slowly. I know my machine needs more memory, it only has 8GB (but ran ok with the old GTX570), can the addition of this graphics card cause a demand for more system memory?

wwaag wrote on 8/22/2019, 1:41 PM

@MikeLV

For some reason, vce encoding is not starting. The next build includes better error handling, so you won't get a message like that in the future, plus HOS will return to Vegas without having to kill the project.

I just did a couple of test renders using 1.0.2.61 in Vegas 13. Both avc and hevc worked OK. However, I am still using an old amd 550 card and since you're using a 590, something may have changed. To test, open the command prompt dialog and enter:

1. "vceencc64 --check-hw" (without parentheses) The last line should state "VCE Available: H.264/AVC, H.265/HEVC

2. If available, you can then enter "vceencc64 --check-features" to see exactly which features are supported.

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.

john_dennis wrote on 8/22/2019, 3:29 PM

My RX480 presents these results:

C:\Users\John>vceencc64 --check-hw
VCEEncC (x64) 4.02 by rigaya, build Dec 11 2018 21:03:34
AMF Version 1.4.9
reader: raw, avs, vpy, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1]
VCE available: H.264/AVC, H.265/HEVC.

C:\Users\John>vceencc64 --check-features
H.264 Encoder Capability
acceleration:   Hardware-accelerated
max profile:    High
max level:      5.2
max bitrate:    100000 kbps
ref frames:     1-16
Bframe support: no
HW instances:   1
max streams:    16

H.264/AVC encoder input:
Width:       64 - 4096
Height:      64 - 2160
alignment:   32
Interlace:   no
pix format:  NV12(native), YUV420P, YV12, BGRA, RGBA, ARGB
memory type: DX9(native), OPENCL, OPENGL, HOST

H.264/AVC encoder output:
Width:       64 - 4096
Height:      64 - 2160
alignment:   32
Interlace:   no
pix format:  NV12(native)
memory type: DX9(native), OPENCL, OPENGL, HOST


HEVC Encoder Capability
acceleration:   Hardware-accelerated
max profile:    main
max level:      6.2
max bitrate:    2147483 kbps
ref frames:     1-16
max streams:    16

H.265/HEVC encoder input:
Width:       192 - 4096
Height:      128 - 2176
alignment:   32
Interlace:   no
pix format:  NV12(native), YUV420P, YV12, BGRA, RGBA, ARGB
memory type: DX9(native), OPENCL, OPENGL, HOST

H.265/HEVC encoder output:
Width:       192 - 4096
Height:      128 - 2176
alignment:   32
Interlace:   no
pix format:  NV12(native)
memory type: DX9(native), OPENCL, OPENGL, HOST

I'm able to use Render Plus to produce h.264 and h.265 in release 60.

MikeLV wrote on 8/22/2019, 3:32 PM

Yes, it does say VCE available just like you stated. And here's what it returns for the features:

H.264 Encoder Capability
acceleration:   Hardware-accelerated
max profile:    High
max level:      5.2
max bitrate:    100000 kbps
ref frames:     1-16
Bframe support: no
HW instances:   1
max streams:    16

H.264/AVC encoder input:
Width:       64 - 4096
Height:      64 - 2160
alignment:   32
Interlace:   no
pix format:  NV12(native), YUV420P, YV12, BGRA, R
memory type: DX9(native), OPENCL, OPENGL, HOST

H.264/AVC encoder output:
Width:       64 - 4096
Height:      64 - 2160
alignment:   32
Interlace:   no
pix format:  NV12(native)
memory type: DX9(native), OPENCL, OPENGL, HOST


HEVC Encoder Capability
acceleration:   Hardware-accelerated
max profile:    main
max level:      6.2
max bitrate:    2147483 kbps
ref frames:     1-16
max streams:    16

H.265/HEVC encoder input:
Width:       192 - 4096
Height:      128 - 2176
alignment:   32
Interlace:   no
pix format:  NV12(native), YUV420P, YV12, BGRA, R
memory type: DX9(native), OPENCL, OPENGL, HOST

H.265/HEVC encoder output:
Width:       192 - 4096
Height:      128 - 2176
alignment:   32
Interlace:   no
pix format:  NV12(native)
memory type: DX9(native), OPENCL, OPENGL, HOST

Does any of that explain why it didn't run in HOS?

wwaag wrote on 8/22/2019, 3:56 PM

Here is a link to the new fs2enc.exe file I mentioned. https://www.dropbox.com/s/3hd88ry6jd61u4f/fs2enc.exe?dl=0

Download and copy it to "C:\Program Files\HappyOtterScripts". Make sure that the file is not "blocked". Then try a render again. If the render fails to start in a couple of seconds, it will terminate and you should then be able to send me a crash report.

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 8/25/2019, 10:17 AM

Ok, thank you, I will give this a try and let you know what happens. When you say make sure that the file is not "blocked," what exactly do you mean?

wwaag wrote on 8/25/2019, 10:38 AM

Sometimes, win 10 will "block" a file downloaded from the internet, especially if it's an executable (.exe or .dll). To find out, right-click and select file properties. If it is blocked, a dialog like this will appear allowing you to "unblock" it. Otherwise, it will remain blocked and the file cannot be executed.

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.

jrb101 wrote on 8/26/2019, 2:59 AM

@AVsupport

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.

 

Just tried to download 1.0.2.61 and Windows Defender keeps blocking it as having "Trojan:Win32/Zpevdo.B" embedded. Not sure whether to proceed and allow it through as I trust @wwaag to have not put in anything dodgy (and I did have a previous version in VP16 - thanks for the awesome tools!), but it's relatively easy to insert code on download servers I believe...

Jon Baker - Experienced in music creation, still a newbie at the video game 😉

(YouTube and Instagram - "Jon's Musical Musings")

PC: AMD Ryzen 3 2200G Desktop w/16GB DDR4 and Radeon RX570 (4GB) , ~5TB of storage across various HDDs, Focusrite Scarlett 6i6 audio interface, Mackie CR5BT studio monitors, 24" 1080p monitor (not anything special!)

For capture: Olympus PEN E-PL6 camera (1080p30) with external mic input adaptor and Olympus ME51S electret lavalier and Takstar SGC-598 shotgun mic and a Samsung Galaxy S10e (4K30 or 4K60) with Filmic Pro or stock video apps and external mic adaptor.

wwaag wrote on 8/26/2019, 10:46 AM

I've also received that same warning from a downloaded version of 1.0.2.61 (also 1.0.2.60). If you do a bit of searching regarding that particular virus, you can't (or at least I couldn't) find anything specific other than just generalized warnings that could apply to almost any malware. I'll re-post the hash so that at least you can be assured (somewhat) that the original version on my system and the downloaded version are indeed the same.

Here's the SHA256 Hash for the original setup file.

38A288C904A8A5E5E683CF335C7490FF75B53A9D02B2B9C585698E20560FD60C

Before release of the next build, I'll include the hash on the download page and hopefully have the setup file "signed" although that's no assurance that the same warnings won't appear.

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.

Musicvid wrote on 8/26/2019, 8:57 PM

I have no idea if something "similar" to this can lead to a temporary fix for unsigned software, but it got my old Spyder 2 Pro up and running with Argyll on Windows 10.

https://www.maketecheasier.com/install-unsigned-drivers-windows10/

MikeLV wrote on 8/29/2019, 12:43 PM

Here is a link to the new fs2enc.exe file I mentioned. https://www.dropbox.com/s/3hd88ry6jd61u4f/fs2enc.exe?dl=0

Download and copy it to "C:\Program Files\HappyOtterScripts". Make sure that the file is not "blocked". Then try a render again. If the render fails to start in a couple of seconds, it will terminate and you should then be able to send me a crash report.

@wwaag I just tried to do a test render with R+ again, after downloading the file you supplied (and ensuring it was unblocked). This time when I started the render, it made the wav file normally, and then the render window comes up,, stays on the screen for a few and then disappears. Doesn't appear to "crash" Where would I find a crash report if there is one?

wwaag wrote on 8/29/2019, 1:02 PM

@MikeLV

If the encoder fails to start after a couple of seconds, it still "crashes" but does so a bit more gracefully. You should receive this dialog. Simply click on Send and I should receive it. The dialog also shows the location of the crash folder in the event your system is preventing the sending of the report.

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 8/29/2019, 1:04 PM

I'm not getting that dialog box, all the render windows just disappear.

wwaag wrote on 8/29/2019, 1:43 PM

Does CPU rendering still 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.

Sylk wrote on 8/29/2019, 11:29 PM

Hi wwaag. Does HOS work with VP17 ?

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 8/29/2019, 11:49 PM

@Sylk

AFAIK, yes. I haven't received any reports to the contrary. The "hooks" were included well before its release. If anyone has seen problems, please advise.

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 8/30/2019, 1:56 AM

Ok thanks. Available into the script menu.

But i got this messagebox:

Why that? *GTX1080 in my system.

Also got an error when i attempt to rewrap HEVC NVENC from ImportAssist. Why that? A link with the full red GPU encoders list?

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.
Sylk wrote on 8/30/2019, 4:09 AM

If anyone has seen problems, please advise.

Not sure if looks like expected with all these lil crosses:

Otherwise, why that?

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 8/30/2019, 10:59 AM

@Sylk

You can try to rescan for available GPU again. To do so, open Render+, select Advanced and click on the blue gear icon for encoders which will bring up the encoder settings dialog. Then click on the info icon as shown here.

If you still get all red X's the problem most likely is that you are using an old driver. I used to display the following warning. "If you intend to render using Nvenc, the Nvidia driver version must be 418.81 or later."

Regarding Nvenc hevc rewrapping, it doesn't work in all cases. E.g. Nvenc hevc from Bandicam is one that Vegas does not accept. It can be easily transcoded with the added advantage of conversion to a constant frame rate, but re-wrapped media are still not considered valid by Vegas. If at all possible stay away from the use of hevc for acquisition--use avc. It's much easier and faster to decode and there are far fewer problems.

And finally, OtterBar and OtterInfoBar are dockable toolbars. The little crosses are just locations where additional icons can be added. E.g. you can add any script to those "placeholders". There is also an option to "turn off" those crosses. The two toolbars look like this in my system.

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.

john_dennis wrote on 8/30/2019, 11:43 AM

@Sylk

"Not sure if looks like expected with all these lil crosses:"