Comments

RogerS wrote on 4/24/2023, 7:58 PM

I think you're beyond what we as users can really help with. I'd file a support request.

VP did change significantly post build 550. 648 had some fixes but if it's still a problem I'd go back to 550 as it works well.

Wolfgang S. wrote on 4/25/2023, 1:05 AM

@Ecquillii have you turned off Hardware Acceleration for the GPU? I'm not sure your AMD GPU meets the specs for Vegas, as per the requirements: Does your card have 4GB RAM and support VCE 3.0?

AMD/ATI® Radeon with 4GB and VCE 3.0 or higher

As far as I see, the AMD Radeon R9 370 has 2GB ram only.

https://www.techpowerup.com/gpu-specs/radeon-r9-370.c2726

It that is correct that your GPU does have 2 GB ram only, then it is quite clear that the R9 370 does NOT meet the specs for Vegas Pro 20,where @ Reyfox is right: we need 4GB and VCE 3.0, see here:

https://www.vegascreativesoftware.com/us/specifications/

I wonder why users complain that they did not have errors with Vegas Pro 19 - and ignore that the technical specifications have changed for Vegas Pro 20.

However, the i-GPU on the Intel Core i76700 Processor seems to meet the minimum specifications as it was said here, since that processor has the Intel® HD Graphics 530 integrated:

https://ark.intel.com/content/www/us/en/ark/products/88196/intel-core-i76700-processor-8m-cache-up-to-4-00-ghz.html

So, maybe it helps to set the specifications to the i-GPU (both in the I/O settings and the GPU settings), and to disable the R9 370 everywhere. I would check that. If the i-GPU does not show up, that could be also a question of the Windows settings. The i-GPU would be the only way that could help you, since the R9 370 is outdated.

What could make a difference is going to graphics settings and assigning Vegas to the power saving GPU. In Windows 11, there is by now an option to allow Windows to  decide, what graphic settings Windows will use for Vegas. That helped me at least, to allow the i-GPU to show up again on my Win11 system (but I do not know if and how that works for Win10).

You also should be aware that the CPU with 4 cores may work with HD footage at the best, since you are also here on the minimum specifications for HD with 4 cores.

So, one way would be to invest a new GPU. A second one to try that the i-GPU shows up. A third one to think about a new PC that meets the technical requirements in a better way. My impression: the whole system seems to be outdated or at the best at the limit, sorry to say so.

 

Last changed by Wolfgang S. on 4/25/2023, 1:37 AM, changed a total of 2 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

andyrpsmith wrote on 4/25/2023, 4:41 AM

andyrpsmith, thanks for your suggestion and questions. I'm not sure what you are referring to. With Vegas Pro 19.0 (Build 550) I do not get the So4 error message. With Vegas Pro 19.0 (Build 636, and following), and all builds of Vegas Pro 20.0, I get the So4 error message. (This is only on my desktop computer; the error message does not occur on my laptop.)

In the previous post, I listed the differences that I could see between the gpu logs for VP 19 Build 550 and the most recent build of VP 20 using the same graphics card.

If the error message is generated in a later build of VP 19, but not in an earlier build, why would the graphics card be implicated?

Post the full file from V20 so we can see what Vegas finds.
So4 is the decoder library which handles many video formats and provides GPU acceleration so elements of it are not going to work if the GPU is not compatible.

Last changed by andyrpsmith on 4/25/2023, 4:46 AM, changed a total of 1 times.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

Wolfgang S. wrote on 4/25/2023, 7:21 AM

Yes, it would be great if you could post in addition the full So4HardwareDetectionOutput.xml file, that you find here:

c:/User/name/AppData/Local/Magix/FileIO/1.0

That should show all your GPUs, as detected by Vegas in your system.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Ecquillii wrote on 4/25/2023, 5:47 PM

To be clear, I am not complaining about VEGAS Pro 20.0 not working on my older desktop computer. The reason I responded in this thread is because I recognized a similar problem as the original poster. I originally reported my problem when VEGAS Pro 19.0 Build 550 was replaced by Build 636, which was when the So4 error message first appeared.

I understand that my GPU is under-powered. It worked fine in the earlier builds of 19.0, before the error message appeared with Builds 636 and 643.

I appreciate the Vegas Forum Community, and my report was not a complaint, but factual reporting of the same error message as the original poster occurring on my under-powered system, which may or may not be hardware-related.

My needs with VEGAS are modest, and I am one of those people who uses Sony Vegas Pro 13 regularly because it does what I need. And I own most of the versions since Magix took over (15, 17, 18, 19, and 20). As a user since version 3, I remember those old days when Vegas was hardware agnostic very fondly.

The two files requested are appended below.

This is the gpu_video_x64.log for VP 20 from two days ago:

INFO 2023-04-23 20:39:24 *** Start of GPU-accelerated video processing log ***
INFO 2023-04-23 20:39:24 VEGAS Pro 20.0
INFO 2023-04-23 20:39:24 Version 20.0 (Build 370)
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24 OpenGL_Initialize
INFO 2023-04-23 20:39:24 DC: 0000000065012E11
INFO 2023-04-23 20:39:24 GLC: 0000000000010000
INFO 2023-04-23 20:39:24 GL 10-bit Available: FALSE
INFO 2023-04-23 20:39:24 GL 10-bit Pixel Format Index: 0
INFO 2023-04-23 20:39:24 GL_VENDOR: ATI Technologies Inc.
INFO 2023-04-23 20:39:24 GL_RENDERER: AMD Radeon R9 370
INFO 2023-04-23 20:39:24 GL_VERSION: 4.5.13399 Compatibility Profile Context 15.200.1065.0
INFO 2023-04-23 20:39:24 GLEW Init OK
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24 OpenCL_Initialize
INFO 2023-04-23 20:39:24 Platforms: 2
INFO 2023-04-23 20:39:24 Platform: 0
INFO 2023-04-23 20:39:24   Vendor:     Intel(R) Corporation
INFO 2023-04-23 20:39:24   Name:       Intel(R) OpenCL HD Graphics
INFO 2023-04-23 20:39:24   Version:    OpenCL 3.0
INFO 2023-04-23 20:39:24   Profile:    FULL_PROFILE
INFO 2023-04-23 20:39:24   Extensions: cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_intel_command_queue_families cl_intel_subgroups cl_intel_required_subgroup_size cl_intel_subgroups_short cl_khr_spir cl_intel_accelerator cl_intel_driver_diagnostics cl_khr_priority_hints cl_khr_throttle_hints cl_khr_create_command_queue cl_intel_subgroups_char cl_intel_subgroups_long cl_khr_il_program cl_intel_mem_force_host_memory cl_khr_subgroup_extended_types cl_khr_subgroup_non_uniform_vote cl_khr_subgroup_ballot cl_khr_subgroup_non_uniform_arithmetic cl_khr_subgroup_shuffle cl_khr_subgroup_shuffle_relative cl_khr_subgroup_clustered_reduce cl_intel_device_attribute_query cl_khr_suggested_local_work_size cl_intel_split_work_group_barrier cl_khr_fp64 cl_khr_subgroups cl_intel_spirv_device_side_avc_motion_estimation cl_intel_spirv_media_block_io cl_intel_spirv_subgroups cl_khr_spirv_no_integer_wrap_de
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24   Devices: 1
INFO 2023-04-23 20:39:24   Device: 0
INFO 2023-04-23 20:39:24     Type:            GPU
INFO 2023-04-23 20:39:24     Vendor:          Intel(R) Corporation
INFO 2023-04-23 20:39:24     Name:            Intel(R) HD Graphics 530
INFO 2023-04-23 20:39:24     Profile:         FULL_PROFILE
INFO 2023-04-23 20:39:24     Version:         OpenCL 3.0 NEO
INFO 2023-04-23 20:39:24     C version:       OpenCL C 1.2
INFO 2023-04-23 20:39:24     Extensions:      cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_intel_command_queue_families cl_intel_subgroups cl_intel_required_subgroup_size cl_intel_subgroups_short cl_khr_spir cl_intel_accelerator cl_intel_driver_diagnostics cl_khr_priority_hints cl_khr_throttle_hints cl_khr_create_command_queue cl_intel_subgroups_char cl_intel_subgroups_long cl_khr_il_program cl_intel_mem_force_host_memory cl_khr_subgroup_extended_types cl_khr_subgroup_non_uniform_vote cl_khr_subgroup_ballot cl_khr_subgroup_non_uniform_arithmetic cl_khr_subgroup_shuffle cl_khr_subgroup_shuffle_relative cl_khr_subgroup_clustered_reduce cl_intel_device_attribute_query cl_khr_suggested_local_work_size cl_intel_split_work_group_barrier cl_khr_fp64 cl_khr_subgroups cl_intel_spirv_device_side_avc_motion_estimation cl_intel_spirv_media_block_io cl_intel_spirv_subgroups cl_khr_spirv_no_integer_
INFO 2023-04-23 20:39:24     Driver version:  31.0.101.2111
INFO 2023-04-23 20:39:24     Available:       Yes
INFO 2023-04-23 20:39:24     Compiler:        Yes
INFO 2023-04-23 20:39:24     Image support:   Yes
INFO 2023-04-23 20:39:24     Unified memory:  Yes
INFO 2023-04-23 20:39:24     Vendor ID:       32902
INFO 2023-04-23 20:39:24     Compute units:   24
INFO 2023-04-23 20:39:24     Work dimensions: 3
INFO 2023-04-23 20:39:24     Clock Frequency: 1150
INFO 2023-04-23 20:39:24     Image reads:     128
INFO 2023-04-23 20:39:24     Image writes:    128
INFO 2023-04-23 20:39:24     Samplers:        16
INFO 2023-04-23 20:39:24     Workgroup size:  256
INFO 2023-04-23 20:39:24     Image width:     16384
INFO 2023-04-23 20:39:24     Image height:    16384
INFO 2023-04-23 20:39:24     Parameter size:  2048
INFO 2023-04-23 20:39:24     Maximum alloc:   3405217792
INFO 2023-04-23 20:39:24     Memory size:     6810435584
INFO 2023-04-23 20:39:24     Local memory:    65536
INFO 2023-04-23 20:39:24     Work item sizes: 256, 256, 256
INFO 2023-04-23 20:39:24     Out of order Q:  Yes
INFO 2023-04-23 20:39:24     Profiling Q:     Yes
INFO 2023-04-23 20:39:24 Device is compatible.
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24 Platform: 1
INFO 2023-04-23 20:39:24   Vendor:     Advanced Micro Devices, Inc.
INFO 2023-04-23 20:39:24   Name:       AMD Accelerated Parallel Processing
INFO 2023-04-23 20:39:24   Version:    OpenCL 2.0 AMD-APP (1800.8)
INFO 2023-04-23 20:39:24   Profile:    FULL_PROFILE
INFO 2023-04-23 20:39:24   Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24   Devices: 2
INFO 2023-04-23 20:39:24   Device: 0
INFO 2023-04-23 20:39:24     Type:            GPU
INFO 2023-04-23 20:39:24     Vendor:          Advanced Micro Devices, Inc.
INFO 2023-04-23 20:39:24     Name:            Pitcairn
INFO 2023-04-23 20:39:24     Profile:         FULL_PROFILE
INFO 2023-04-23 20:39:24     Version:         OpenCL 1.2 AMD-APP (1800.8)
INFO 2023-04-23 20:39:24     C version:       OpenCL C 1.2
INFO 2023-04-23 20:39:24     Extensions:      cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_spir cl_khr_gl_event
INFO 2023-04-23 20:39:24     Driver version:  1800.8 (VM)
INFO 2023-04-23 20:39:24     Available:       Yes
INFO 2023-04-23 20:39:24     Compiler:        Yes
INFO 2023-04-23 20:39:24     Image support:   Yes
INFO 2023-04-23 20:39:24     Unified memory:  No
INFO 2023-04-23 20:39:24     Vendor ID:       4098
INFO 2023-04-23 20:39:24     Compute units:   20
INFO 2023-04-23 20:39:24     Work dimensions: 3
INFO 2023-04-23 20:39:24     Clock Frequency: 925
INFO 2023-04-23 20:39:24     Image reads:     128
INFO 2023-04-23 20:39:24     Image writes:    8
INFO 2023-04-23 20:39:24     Samplers:        16
INFO 2023-04-23 20:39:24     Workgroup size:  256
INFO 2023-04-23 20:39:24     Image width:     16384
INFO 2023-04-23 20:39:24     Image height:    16384
INFO 2023-04-23 20:39:24     Parameter size:  1024
INFO 2023-04-23 20:39:24     Maximum alloc:   1409286144
INFO 2023-04-23 20:39:24     Memory size:     2147483648
INFO 2023-04-23 20:39:24     Local memory:    32768
INFO 2023-04-23 20:39:24     Work item sizes: 256, 256, 256
INFO 2023-04-23 20:39:24     Out of order Q:  No
INFO 2023-04-23 20:39:24     Profiling Q:     Yes
INFO 2023-04-23 20:39:24 Device is compatible.
INFO 2023-04-23 20:39:24 This is the selected device.
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24   Device: 1
INFO 2023-04-23 20:39:24     Type:            CPU
INFO 2023-04-23 20:39:24     Vendor:          GenuineIntel
INFO 2023-04-23 20:39:24     Name:            Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
INFO 2023-04-23 20:39:24     Profile:         FULL_PROFILE
INFO 2023-04-23 20:39:24     Version:         OpenCL 1.2 AMD-APP (1800.8)
INFO 2023-04-23 20:39:24     C version:       OpenCL C 1.2
INFO 2023-04-23 20:39:24     Extensions:      cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_media_ops2 cl_amd_popcnt cl_khr_d3d10_sharing cl_khr_spir cl_khr_gl_event
INFO 2023-04-23 20:39:24     Driver version:  1800.8 (sse2,avx)
INFO 2023-04-23 20:39:24     Available:       Yes
INFO 2023-04-23 20:39:24     Compiler:        Yes
INFO 2023-04-23 20:39:24     Image support:   Yes
INFO 2023-04-23 20:39:24     Unified memory:  Yes
INFO 2023-04-23 20:39:24     Vendor ID:       4098
INFO 2023-04-23 20:39:24     Compute units:   8
INFO 2023-04-23 20:39:24     Work dimensions: 3
INFO 2023-04-23 20:39:24     Clock Frequency: 3408
INFO 2023-04-23 20:39:24     Image reads:     128
INFO 2023-04-23 20:39:24     Image writes:    64
INFO 2023-04-23 20:39:24     Samplers:        16
INFO 2023-04-23 20:39:24     Workgroup size:  1024
INFO 2023-04-23 20:39:24     Image width:     8192
INFO 2023-04-23 20:39:24     Image height:    8192
INFO 2023-04-23 20:39:24     Parameter size:  4096
INFO 2023-04-23 20:39:24     Maximum alloc:   4256522240
INFO 2023-04-23 20:39:24     Memory size:     17026088960
INFO 2023-04-23 20:39:24     Local memory:    32768
INFO 2023-04-23 20:39:24     Work item sizes: 1024, 1024, 1024
INFO 2023-04-23 20:39:24     Out of order Q:  No
INFO 2023-04-23 20:39:24     Profiling Q:     Yes
WARN 2023-04-23 20:39:24 Device type not supported
WARN 2023-04-23 20:39:24 Device is not compatible.
INFO 2023-04-23 20:39:24
INFO 2023-04-23 20:39:24 Attempting to create CL interop context on device 'AMD Radeon R9 370'
INFO 2023-04-23 20:39:24 Interop context: 0000000036267370
INFO 2023-04-23 20:39:24 Command queue: 000000001524B7D0
INFO 2023-04-23 20:39:24 Buffer write mapping flags: 0x4
INFO 2023-04-23 20:39:24 HWBL: 1
INFO 2023-04-23 20:39:24 OCL compile, bin: 94f09332, kernels: kbf243cf20 kbf243cf21 kbf243cf22
INFO 2023-04-23 20:39:24 CPWB successful
INFO 2023-04-23 20:39:24 BP successful
INFO 2023-04-23 20:39:24 OCL compile, bin: aa490cb6, kernels: k3588f3c20 k3588f3c21 k3588f3c22 k3588f3c23 k3588f3c24
INFO 2023-04-23 20:39:24 CPWB successful
INFO 2023-04-23 20:39:24 BP successful
INFO 2023-04-23 20:39:24 OCL compile, bin: dc7ab1ce, kernels: kaf5099dd0 kaf5099dd1 kaf5099dd2 kaf5099dd3
INFO 2023-04-23 20:39:24 CPWB successful
INFO 2023-04-23 20:39:24 BP successful
INFO 2023-04-23 20:39:24 OCL compile, bin: 671c9ecb, kernels: kd6cf29e80 kd6cf29e81 kd6cf29e82 kd6cf29e83 kd6cf29e84 kd6cf29e85 kd6cf29e86 kd6cf29e87 kd6cf29e88 kd6cf29e89 kd6cf29e810 kd6cf29e811 kd6cf29e812 kd6cf29e813 kd6cf29e814 kd6cf29e815 kd6cf29e816
INFO 2023-04-23 20:39:24 CPWS successful
ERR  2023-04-23 20:39:24 BP ** FAILED **, -11
ERR  2023-04-23 20:39:24 Build log: "C:\Users\timot\AppData\Local\Temp\OCL9DCA.tmp.cl", line 1: error: expression
          must have pointer-to-struct-or-union type
  __constant sampler_t v0 = CLK_FILTER_NEAREST | CLK_ADDRESS_CLAMP | CLK_NORMALIZED_COORDS_FALSE ; __kernel void kd6cf29e80 ( read_only image2d_t v1 , __global uchar * v2 ) { const int2 v3 = { get_global_id ( 0 ) , get_global_id ( 1 ) } ; const int2 v4 = get_image_dim ( v1 ) ; if ( v3 . x < v4 . x && v3 . y < v4 . y ) { const float4 v5 = read_imagef ( v1 , v0 , v3 ) ; const float v6 = 0.299f * v5 . s0 + 0.587f * v5 . s1 + 0.114f * v5 . s2 ; const uint v7 = v6 * 255.0f ; const int v8 = get_global_id ( 0 ) + v4 . x * get_global_id ( 1 ) ; v2 [ v8 ] = convert_uchar ( v7 ) ; } } __kernel void kd6cf29e81 ( read_only image2d_t v1 , __global float * v2 ) { const int2 v3 = { get_global_id ( 0 ) , get_global_id ( 1 ) } ; const int2 v4 = get_image_dim ( v1 ) ; if ( v3 . x < v4 . x && v3 . y < v4 . y ) { const float4 v5 = read_imagef ( v1 , v0 , v3 ) ; const float v6 = 0.299f * v
INFO 2023-04-23 20:39:24 OCL compile, bin: 3123b46b, kernels: k6fe03b080 k6fe03b081 k6fe03b082 k6fe03b083 k6fe03b084 k6fe03b085 k6fe03b086 k6fe03b087 k6fe03b088 k6fe03b089 k6fe03b0810 k6fe03b0811 k6fe03b0812 k6fe03b0813 k6fe03b0814 k6fe03b0815 k6fe03b0816 k6fe03b0817 k6fe03b0818 k6fe03b0819 k6fe03b0820 k6fe03b0821 k6fe03b0822 k6fe03b0823 k6fe03b0824 k6fe03b0825 k6fe03b0826 k6fe03b0827 k6fe03b0828 k6fe03b0829 k6fe03b0830 k6fe03b0831 k6fe03b0832 k6fe03b0833 k6fe03b0834 k6fe03b0835 k6fe03b0836 k6fe03b0837 k6fe03b0838 k6fe03b0839 k6fe03b0840 k6fe03b0841 k6fe03b0842
INFO 2023-04-23 20:39:25 CPWB successful
INFO 2023-04-23 20:39:25 BP successful
INFO 2023-04-23 20:39:25 Readback profiling: [31, 31], selected 0
INFO 2023-04-23 20:39:25 DX12_HDR_Initialize
INFO 2023-04-23 20:39:25 DX12 HDR Available: FALSE
INFO 2023-04-23 20:39:25
INFO 2023-04-23 20:40:18 OpenCL_Shutdown
INFO 2023-04-23 20:40:18 OpenGL_Shutdown
INFO 2023-04-23 20:40:18
INFO 2023-04-23 20:40:18 *** End of GPU-accelerated video processing log ***

And this is the So4HardwareDetectionOutput.xml file:

<?xml version="1.0" encoding="utf-8"?>
<hardware_detection>
    <operating_system>
        <version>2009</version>
        <build_number>19045</build_number>
        <updated_build_revision>2846</updated_build_revision>
    </operating_system>
    <compute>
        <num_platforms>2</num_platforms>
        <platform_0>
            <name>Intel(R) OpenCL HD Graphics</name>
            <vendor>Intel(R) Corporation</vendor>
            <version>OpenCL 3.0 </version>
            <num_devices>1</num_devices>
            <device_0>
                <name>Intel(R) HD Graphics 530</name>
                <version>OpenCL 3.0 NEO </version>
                <driver_version>31.0.101.2111</driver_version>
            </device_0>
        </platform_0>
        <platform_1>
            <name>AMD Accelerated Parallel Processing</name>
            <vendor>Advanced Micro Devices, Inc.</vendor>
            <version>OpenCL 2.0 AMD-APP (1800.8)</version>
            <num_devices>2</num_devices>
            <device_0>
                <name>Pitcairn</name>
                <version>OpenCL 1.2 AMD-APP (1800.8)</version>
                <driver_version>1800.8 (VM)</driver_version>
            </device_0>
            <device_1>
                <name>Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz</name>
                <version>OpenCL 1.2 AMD-APP (1800.8)</version>
                <driver_version>1800.8 (sse2,avx)</driver_version>
            </device_1>
        </platform_1>
    </compute>
    <hardware_decoders>
        <num_decoders>1</num_decoders>
        <preferred_decoder_0>
            <vendor_id>2</vendor_id>
            <vendor_name>Intel QSV</vendor_name>
        </preferred_decoder_0>
    </hardware_decoders>
</hardware_detection>

Desktop:ASUS M32CD

Version of Vegas: VEGAS Pro Version 20.0 (Build 370)
Windows Version: Windows 10 Home (x64) Version 21H2 (build 19044.2846)
Cameras: Canon T2i (MOV), Sony HDR-CX405 (MP4), Lumia 950XL, Samsung A8, Panasonic HC-V785 (MP4)
Delivery Destination: YouTube, USB Drive, DVD/BD

Processor: 3.40 gigahertz Intel Core i7-6700
RAM: 16 Gigabytes
Graphics Card 1: AMD Radeon R9 370; Driver Version: 15.200.1065.0
Graphics Card 2: Intel HD Graphics 530; Driver Version: 31.0.101.2111
GPU acceleration of video processing: Optimal - AMD Radeon R9 370
Enable Hardware Decoding for supported formats: 'Enable legacy AVC' is off; 'Enable legacy HEVC' is on
Hardware Decoder to Use: Auto (Off)

fr0sty wrote on 4/25/2023, 7:02 PM

Looks like both your CPU and AMD GPU fall below the recommended specs for VEGAS, which are a 7th gen intel or greater, and a GPU with a minimum of 4GB of VRAM, with 8GB recommended for 4k.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

RogerS wrote on 4/25/2023, 9:55 PM

Vegas recommended specs include 6th generation Intel CPUs and the HD 530 iGPU is fully supported.
https://www.vegascreativesoftware.com/us/specifications/

The AMD R9 370 GPU appears to use VCE 1.0 and is not supported: https://en.wikipedia.org/wiki/Video_Coding_Engine

Post 550 if I recall VEGAS changed the way it detects graphics hardware and some users benefit from disabling autodetection, so such an option was added to preferences. Search the forum for back and forth around GPUs not being found and workarounds.

 

Wolfgang S. wrote on 4/26/2023, 1:31 AM

The HD 530 i-GPU is supported and detected. It should be available to be selected in the Preferences I/O, and should be selected.

The AMD R9 370 is outdated, also because of the 2GB ram that are not enough any more. Either, the i-GPU is used also as general GPU, what should be possible. Or it should be replaced by another GPU.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems