I finally got this PC upgraded and up and running with Windows 10. Got Vegas running, installed HOS again. I went to the GPU Encoder check and got this:

which I thought was strange because my Device Manager shows the display adapters (and the drivers are fully up to date too:

I have connected my main monitor to the 590, and I connected my secondary monitor to the port on the motherboard, which I guess? activates the integrated GPU.

When I go to the video tab in the preferences, it does show the AMD card under the GPU acceleration setting:

So two questions:

1. Do you know why HOS is showing all x's for available encoders?
2. Should the Intel 3000 also be showing up under the GPU acceleration setting as an option?

Thanks, feel like I'm almost back up and running. I don't want to change operating systems for another 10 years!

@MikeLV

Regarding QuickSync, it appears that you are out-of-luck for running HD3000 under Windows 10. Win 7 is supported, but not Win 10. Here's an Intel link. https://www.intel.com/content/www/us/en/support/articles/000005526/graphics-drivers.html

Regarding VCE, here's how to test. From the command prompt, run the following command "vceencc64 --check-hw" without the parentheses. You should get a response indicating whether vce is available or not.

Another thing to check is whether vce shows up as render option inside of Vegas. Let me know what you find.

Well that is interesting. If it's not supported in Windows 10, how come it shows up in the device manager recognized as HD3000 and I am able to connect a monitor to it, have correct resolution, etc? Oh and the other thing, the little icon and control panel for the Intel graphics displays down in the tray. I'm able to open it, run the wizard and alter the settings.

I will test the command prompt thing when I get back to my computer later and let you know.

@MikeLV

"If it's not supported in Windows 10, how come it shows up in the device manager recognized as HD3000...."

It still works as a display adapter--you just can't render QuickSync with it.

Oh bummer ☹️

@wwaag, I did some googling, and came across this thread, different CPU, but apparently one guy got his working when it wasn't supposed to work? Maybe there's hope to get mine working I don't know, I'm going to dig a little more:

https://steamcommunity.com/groups/homestream/discussions/0/490125737470838086/

Regarding the command prompt test, here's what I got:

VCEEncC (x64) 5.01 by rigaya, build Dec 24 2019 13:55:36
AMF Version 1.4.14
reader: raw, avs, vpy, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9]
VCE available

When I go to to the encode settings under magix avc, is this what you're referring to? I do see AMD VCE in this drop down menu:

Right after checking that, I go back to HOS and run the GPU check again, and still all red X's

New version 1.0.2.68 released. Change log may be found here. https://tools4vegas.com/wp-content/uploads/HappyOtter-Change-Log.pdf

New Tool

o FxAssist – simple tool to help user manage effects in Vegas

•  Create and save sets of individual favorites and filter chains that can be applied to events, media, tracks, or output buses
•     Actions include adding, replacing, removing, enabling, bypassing and searching for individual Fx and filter chains
•     Insert at index allows user to add filter to an existing filter chain at a specific position
•     Easily select track and events for applying Fx

New Features

o    RenderPlus

•     Specific option added to include alpha channel during render
•     Added Apple Animation and Motion-PNG codecs for alpha channel support
•     Added support for Wave64 long program renders including use of FDK-AAC encoder

o    RenderEvents – additional alpha channel rendering support
o    Select Regions-option to render only selected regions added to Render+, RenderEvents, AudioTrim, AviDub, and DeshakerRedux.  In Loop regions render option added to RenderEvents.
o    AudioTrim – added By Tracks option which allows the loop region, regions or project to be rendered for selected tracks.  Also enables choice of Fx to bypass/enable for such renders.
o    ImportAssist

•     Added support for import of Webm media with alpha—can be imported into Vegas as lossless PNG’s or rendered to a lossless file
•     Added Apple Animation codec to import  render options

 Bug Fixes

o    Deshaker-Redux

•     Non English filenames caused crash when using turbo option—fixed
•     Reworked dialog logic to ensure  compatibility between main UI and Advanced Options UI

o    Setup—failed when registry entries from previous Vegas versions not removed—fixed
o    AviDub--Virtualdub scripts  with frame rate changes not working--fixed
o    GPU Check—failed to show VCE encoding available with new render app--fixed

Hi Wayne,

Just installed version 1.0.2.68. When using R+, Vegas crashes as soon as I click on the Encoder gear wheel when using Advanced options. I've tried it several times and it but it fails every time. I've tested it on both Vegas Pro 13 and Magix Vegas Pro 15. Same thing happens with both versions of Vegas.

Just thought you should be aware of the problem.

@Jep

That's a major problem. Try resetting the R+ script. Right-click on R+ and select Reset Script Settings.

Hi Wayne,

Just installed version 1.0.2.68. When using R+, Vegas crashes as soon as I click on the Encoder gear wheel when using Advanced options. I've tried it several times and it but it fails every time. I've tested it on both Vegas Pro 13 and Magix Vegas Pro 15. Same thing happens with both versions of Vegas.

Just thought you should be aware of the problem.

Just one additional piece of information. I went back to version 1.0.2.67 and when I tried using R+ I had exactly the same problem. So I tried doing a full uninstall of HOS and then reinstalled 1.0.2.67 and that fixed the problem.

I guess our messages crossed. The script reset should have cured the problem. Try installing v68 again with the script reset and see if that works.

@Jep

That's a major problem. Try resetting the R+ script. Right-click on R+ and select Reset Script Settings.

Ahh!!! OK - that seems to have fixed the problem. Many thanks for the quick reply.

That's good news. As you can see there were major changes to the encoder settings dialog and my attempts to make it upgrade seamlessly obviously failed. If Vegas crashes, when launching a script or opening a dialog within the script, the user should always first try to simply reset the script settings since they sometimes becomes corrupted. Just a tip for anyone else having such problems.

I'll be testing the new audio options this snowy weekend!

Good luck. I tested up to 11 hrs with FDK-AAC encoding and it seemed to work OK. After writing the Wave64 file, it next recodes to Raw Audo which can be accepted by FDK. I would suggest some shorter encodes first just to see how it works and also how long it takes. There is a progress indicator for the final encode, but not for the conversion to Raw.

Unfortunately, the one I downloaded last night closes Vegas when I click R+ Render Settings wheel. I'll let an error report go through.

I may need more guidance on employing fdk.

@Musicvid

Reset the script settings before starting R+ and it should work OK. Jep reported the same problem.

Got through a long program render to x264/AAC by way of W64, and pretty fast!

With FDK encoder, it either works, or it hangs at a message, "Converting to raw PCM" and doesn't finish. Haven't figured out the variables involved.

At the moment, there is no progress indicator when Converting to raw PCM so there is no way for the user to know that it's still "working". It can sometimes take a very long time. During testing, I inadvertently cancelled a render even though it was still working. I will see about adding some type of progress indicator for the next build.

Same input file, same encode settings, different results.

Trial 1, failed and locked computer.

Trial 2, succeeded 1:30 total hours

Trial 3, failed, screen remained overnight.

Trial 4, aborted after four hours.

As I said, I'm looking for a common variable, but haven't found yet.

Just did it again.

Vegas has 0% disk /memory activity, hung for 3+ hours.

But I have one successful encode in FDK that looks and sounds great!

By way of explanation, I'm transferring 2 and 3 hour PBS musical specials, and a few 5.1 DD broadcasts.

Question. Does it work OK when converting to straight AAC through FFmpeg? Regardless, I'll try to debug the raw conversion.