Half performence with the Radeon VII

Adi-W wrote on 6/3/2019, 3:34 PM

Since I could sell my Fury-X, I decided to buy a Radeon VII while the rest of my system will be upgraded in a few months. Now, while the "red car" test was rendered in 21 seconds with the Fury-x, it takes 45 seconds with the Radeon VII !
I understand that I'm still with my old i7 2600K@4.3Ghz, but how can I get half the performance with a Radeon VII versus Fury-x and with the same processor ?
At least I would like to be sure that my Radeon is not defective ... cinebench : 103fps novabench gpu : 838

Any thoughts ?

Thanks !

Comments

Howard-Vigorita wrote on 6/3/2019, 6:53 PM

That's similar to the time I get if I select AMD VCE to render. I usually report the XDCamEX hq 1080, however, because that's what was used back in the Vegas 11 days when Red Car was published and used it all along the way since then. The default for that codec is 60i, btw, and runs a little slower than 30p... I'm guessing most folks these days would render mp4's to 30p but you need to change it in the preset preferences to get that. Short of a mismatch in your comparisons, next thing I'd suspect is a downgrade on your x16 slot. Bios should tell you somewhere if its x16 pcie3. Sometimes plugging in a 2nd x16 device into another slot knocks both slots down to x8. Same can happen if you plugged something new like an extra m.2 on the motherboard. I assume you made sure you got the latest Radeon update for the VII.

 

petecarney wrote on 6/3/2019, 9:35 PM

I have the same issue with my x399 mobo, threadripper 1950x and Radeon VII. There is something wrong with the drivers and Vegas at this point for the Radeon VII. I had my system get to 31 seconds at one point but is now at 36 seconds on the red car render with mp4 AMD VCE

 

Most of the time when rendering Vegas Pro 16 is not using the gpu. It says it's at 76-85% gpu usage but the speed it only averaging 90 mhz out of a possible 1800 mhz available. Temps on the gpu are in the 40's

 

Vegas just isn't hitting the card at all for some reason.

 

Cheers,

Pete

Adi-W wrote on 6/4/2019, 1:28 AM

@Howard-Vigorita yes my Asus motherboard is still only pcie2 but the Radeon VII replaced the Fury-x in the same slot, Nothing else did changed in my system and I have the last amd driver/software that, by the way, seems to be really stable in Vegas. I also always use the same default template hd 1080 mp4 AMD VCE to render red car. So, as Petecarney seems to have similar problem, it looks more like that it is Vegas that don't efficiently use the Radeon VII.

Maybe it is similar issues as Neatvideo have with the card. That's the answer they gave me : "Unfortunately there are some driver issues preventing us to add support for Radeon VII at this moment. We are trying to solve the problem together with AMD. As soon as this is resolved, we will add support for these GPUs in Neat Video 5. I am not sure at this stage whether this change will be backported to Neat Video 4 or no."

 

bitman wrote on 6/4/2019, 2:36 AM

Just a question to the posters, your "red car" test was run with Vegas 15 or Vegas 16?

Just asking as V16 (26s) is slower than V15 (20s) with red car on my system.

Last changed by bitman on 6/4/2019, 2:38 AM, changed a total of 1 times.

Current system: VP16 (suite) build 424, VP15 (suite) build 416, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2019,...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - yes upgraded from 34 to 38, I can see more tracks now! Resolution: 3840x1600
  • C-drive: Samsung NVMe SSD 2TB 960 pro
  • Data storage: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z370 Aorus Gaming 7
  • PS: Corsair HX1200i, Case: Silverstone fortress 2, shuttlePROv2, Keyboard and mouse: Logitech G910 and G700s (and now Evoluent Vertical Mouse)

Before November 2018: NVIDEA Gibabyte GTX 1080ti

Before November 2017: windows 10 Pro 64, i7-4790k, mem: DDR3 16GB GTX TITAN X (Maxwell)

 

Howard-Vigorita wrote on 6/4/2019, 2:48 AM

@Adi-W Though 19.5.2 is the current driver for the VII I've found the Wattman section a little flaky with my 9900k/Raden VII combo... freezes up allot when I make more than 2 or 3 changes. Though it was rock solid with my old RX580-x99/xeon. Also solid with the Vega M built into an Intel NUC/Hades Canyon. But fwiw, the 41 sec time you're getting with the Magix AVC/AMD VCE compares favorably with the 38 sec time I get with my 9900k/VII. Sounds more like the VII may be doing some function your particular cpu is better at. If so, you might get a better time than the 61 sec that I get with gpu off.

Howard-Vigorita wrote on 6/4/2019, 2:55 AM

@bitman v16 here.

petecarney wrote on 6/4/2019, 8:40 AM

VP16 here as well

Adi-W wrote on 6/4/2019, 10:29 AM

VP16 here also... overall it is not clear what is going on with the Radeon VII. In an another thread I asked if Vegas team was working closely with AMD to improve hardware support as they do with NVIDIA. It would be great to have some feedback about that.

Howard-Vigorita wrote on 6/4/2019, 12:48 PM

Noticed something odd... this morning I was rechecking the red car times I got and the XDCam time was still 13 sec but the AMD VCE jumped up to over a minute. Checking the Radeon driver showed it somehow reset itself to auto-default with all the curves grayed out. Reloaded a profile I had saved and reran... AMD VCE down to 35 sec now. My board was delivered with the voltage profile set to M and all I did was muck with the fan curve just enough to hear a slight change on Vegas renders. Here's a screen shot of my saved profile settings...

Chief24 wrote on 6/4/2019, 2:23 PM

Here's some information concerning those of us with the Vega Cards (Vega 56, Vega 64, Radeon VII). If you use the "Wattman" portion of the AMD Ryzen Master Software, it only maintains any settings during current Usage. Once you "re-start" or Turn Off/Turn On (cold or hot boot), you will have to then go into Wattman to "Apply" your saved (hopefully you did) setting profile. The Ryzen Master is a "Software" type of Over/Under clocking/Fan curve/etc., so it is reset to default upon a "Reset" of the system.

MSI AfterBurner is similar, but there is a "checkbox" for applying your changes automatically upon loading windows.

Yep, had the same type of thing happened to me. So what I had for my "slight" overclock of the GPU core and Memory, including the slight bump in Power Limit, "Disappeared" when I rebooted my machine after using Wattman. But, I did save the profile, applied it, then wrote the settings down, rebooted again so Wattman would put the settings back to default, and upon loading Windows 10, opened AfterBurner and used the settings I wrote down, then checked the box to Automatically apply at Windows load. Yeah, much better.

I do not know if the Asus GPUTweak or EVGA Precision X do this or not, or even support AMD cards for that matter (can't remember the other companies versions either - Gigabyte, Sapphire, PowerColor, etc.). Plenty of install tutorials on YouTube, as well as the overclocking/under-clocking and such as well.

Self Build: MSI X399 Gaming Pro Carbon AC/1950X @ stock; 64GB Corsair 2666 Mhz; OS-Intel 750 800GB, Project Media-Samsung 960 EVO 1TB; (3) Samsung 850 EVO 500GB SSD for various (LightRoom & Photoshop), Render, Other Assets; Sapphire AMD Radeon VII; Vizio D43-F1 3840x2160 (TV); Windows 10 Pro 64-Bit (1809); (2) Intel 660p 2TB PCI-e on Asus Quad M.2x16; Magix Vegas Pro 15 Suite (416), Magix Movie Studio Platinum 15 Suite (157); Canon EOS 80D; GoPro Hero 5+ & 6 Black; Sony FDR AX-53 HandyCam; Sound Forge Studio 12.6; Creative SoundBlaster Zx sound card; Magix Music Maker Premium 2019

Howard-Vigorita wrote on 6/21/2019, 12:35 PM

Been getting the best Radeon VII performance on my Asus Maximus XI motherboard by getting it to team up with the onboard Intel video and using the Quick Sync option in Sony AVC or the QSV preset in Magix AVC. To get this to work I first made sure the bios setting under System Agent, Graphics Config has iGPU set to [enabled] with RC6 Render Standby also set to [enabled]. Also pays to make sure both AMD and Intel graphics drivers are properly installed. When I right click on the desktop, links to both AMD and Intel settings appear in the menu if the onboard hdmi has a monitor plugged in. My AMD driver version is v19.6.1 the Intel UHD 630 panel shows v25.20.100.6373. In Vegas, preferences, video, both Intel 630 and AMD (gfx906) are listed as options... I select AMD. Selecting Intel gave me performance so low I didn't bother to time it. To get the gpu options to appear in the Sony AVC preferences, set the Vegas general preference to 'allow legacy gpu rendering'... otherwise it hides the options and defaults to cpu only. The quick sync performance I get depends on which hdmi port I plug my monitor into. I get the best rendering performance plugging into the onboard (Intel) hdmi but their driver reports a top refresh rate of 30p hz. Plugging into the Radeon hdmi more fully supports my BenQ PD3200U monitor's ~60p hz rate so it might be smoother for editing and previewing. YouTube seems to prefer output from the Sony AVC so I'll be trying to work with the Intel hdmi but I instantly noticed the difference in refresh rate soon as I fired it up for the 1st time. But if you like the Magix AVC, it's QSV preset works with optimal performance either way. I've only explored dual connections using Windows set to display dual monitors in duplicate mode and plugging both hdmi outputs into different ports on the same monitor because I only have one 4k monitor. I did try doing this briefly with Windows set to extended display mode and it does work... sometimes... maybe depending on where you plant the Vegas shortcut before you fire it up.

matthias-krutz wrote on 6/21/2019, 2:03 PM

I use a R9 380. It's strange that render times are almost the same despite very different graphics cards.

With the last Windows Update the driver was reset to 17.1.1 (19sec). Even before the 18-driver ran fast (19-20sec). Currently I see the double rendering time with the 19.5.2 driver (38sec) in the Red Car project and MAGIX AVC 1080p29.97.
At least with my graphics card, the new driver has not brought any improvements, also in terms of other problems. I suspect that the current 19er drivers do not work well with Vegas, regardless of the Radeon VII.

petecarney wrote on 7/8/2019, 4:08 PM

New X399 chipset drivers 1.07.07.0725 and Radeon Adrenalin 2019 19.7.1 just came out over the weekend.

 

The new Radeon driver didn't change anything, but the chipset drivers solved my lower UserBenchmark scores and brought it up to 147% from the 130% my Radeon VII was running at.

The lastest Vegas 16 sample project render went from 45 to 37 seconds !!!

 

Finally feel like this thing is performing as it should.

Cheers, Pete