editing/previewing performance issues, 15/built157

agatek wrote on 12/30/2018, 12:13 AM

I face some serious performance problems and I am not sure how to bite it.

The machine (main): Asus m5a97 pro / AMD FX-8350 / 16G RAM, all ssd / gtx750/2GB / Win10

The machine (secondary): Asus m5a78l-m plus/usb3 / AMD FX-8350 / 16G RAM, all ssd / gtx1050/2GB / Win10 (fresh install)

Issues: the preview (window, 2nd monitor), even with the proxy files generated is not smooth. no way to play anything better than preview (quarter). Sometime even within draft it refreshes like 1F per second, sometimes it just freezes permanently and all has to be killed.

Playing with gpu acceleration settings doesn’t seem to help.

Operation within the editor is not smooth neither. All behaves like sort of badly written web page with a lot of cpu power eating javascripts, but the actual toll taken on the cpu performance is low.

An example, I generate a text media, and start to edit it (the text) – the lag is so serious it can take 20s just to type in some few characters.

It looks like something slows down most of the editing/previewing operations.

Now, it was not like this earlier but I don’t really remember when these problems started. I think with MS 14 it was still ok. Perhaps the initial release (built) of “15” was also ok. At that time I didn’t use the proxy files at all and my gpu was some much older Nvidia with 0.5GB on board only.

What could be the problem? Suggestions what to do with it greatly appreciated.

Comments

j-v wrote on 12/30/2018, 6:10 AM

Start here, the most items are not only for Pro but also for VMS.

Playing with gpu acceleration settings doesn’t seem to help.

That options helps only for faster performance at some added effects and helps nothing for normal playback.

If you have more questions you have to give us more specific information as here under C.

agatek wrote on 1/4/2019, 5:33 AM

Thanks j-v. I tried to search the forum prior to posting but the subject is a bit difficult to define (too general). I hoped somebody recognized the issue and could provide a quick, direct work around.

In a way this recent problem helped me to make the decision of saying good bye to the Vegas family. I am with VMS since version 8. It looked very promising, it still has huge potential and functionality but all these is just killed by zillions of bugs. Over the years it's been only getting worse. Practically every video encoding freezes (ca 70% failure rate), often after few hours of encoding. 2y back it started to freeze for a few minutes during the timeline playback, now has also editing performance issues. Time to look for alternatives, perhaps less functional or/and more expensive but at least less buggy.

j-v wrote on 1/4/2019, 7:07 AM

It is sad to hear that complaining from you, because for me it is the best version of VMS ever made. I'm able to edit pretty heavy material with it on laptop and desktop from signature.
To show you that, I made a short test of material made by my DJI drone and GoPro 5 Black both with 2,7K 50p sourcefiles.
First I play it without problem in full framerate and than I render it to a 2,7K 50p Magix AVC codec, with default rendertemplate except customized dimensions to 2,7K.
The renderingpart I have speeded up in my video from the screengrab for the video with OBS that was also working during the test was running.

What is going wrong with you I don't know except that you did not give the information needed to make any suggestion.

Musicvid wrote on 1/4/2019, 7:19 PM

agatec, are you looking for a solution?

If so, provide the specific information requested.

If you want to grouse, take it to the Off Topic forum. thanks.

agatek wrote on 1/8/2019, 7:54 AM

Fair enough Musicvid/J-V. I think it is worth at least one systematic attempt before giving up.

There is one significant development since my last post. I ran some tests and indications that what I am facing are systemic issues are very strong. Basically, I installed VMS on a third machine, this time Intel cpu based and tested different scenarios for last couple of days. Here it goes.

Media info

General
  Name: 20180611_204744_hdrtd10e-00380.mts
  Folder: C:\DATA\1\Projects\S146.201805\AVPR
  Type:  MPEG-2 Transport Stream
  Size: 67.20 MB (68,812,800 bytes)
  Created: Tuesday, October 02, 2018, 8:22:36 PM
  Modified: Monday, June 11, 2018, 8:47:44 PM
  Accessed: Saturday, December 29, 2018, 10:19:25 AM
  Attributes: Archive

Streams
  Video 1: 00:00:20.800, 25.000 fps interlaced, 1920x1080x12, AVC
  Video 2: 00:00:20.800, 25.000 fps interlaced, 1920x1080x12, MVC
  Audio: 00:00:20.800, 48,000 Hz, 5.1 Surround, Dolby AC-3, Dolby AC-3

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: mvcplug.dll
  Folder: C:\Program Files\VEGAS\Movie Studio Platinum 15.0\FileIO Plug-Ins\mvcplug
  Format: MVC
  Version: Version 15.0 (Build 157)
  Company: MAGIX Computer Products Intl. Co.

The issues seem media independent. It happens with different medias from different sources. Here I used MVC/AVC files recorded with Sony HDR-TD10 camcorder

Project properties

Again, I don't see any dependence on the settings.

GPU status

Could be on or off, no difference

Machine 0

Asus m5a97 pro / AMD FX-8350 / 16G RAM, all ssd / gtx750/2GB / Win10

The system/hardware

The GPU

NVIDIA System Information report created on: 01/08/2019 18:06:14
 
[Display]
Operating System:    Windows 10 Home, 64-bit
DirectX version:    12.0  
GPU processor:        GeForce GTX 750
Driver version:        417.35
Driver Type:        Standard
Direct3D API version:    12
Direct3D feature level:    11_0
CUDA Cores:        512  
Core clock:        1019 MHz  
Memory data rate:    5.01 Gbps
Memory interface:    128-bit  
Memory bandwidth:    80.16 GB/s
Total available graphics memory:    9188 MB
Dedicated video memory:    1024 MB GDDR5
System video memory:    0 MB
Shared system memory:    8164 MB
Video BIOS version:    82.07.32.00.25
IRQ:            Not used
Bus:            PCI Express x16 Gen2
Device Id:        10DE 1381 84C81043
Part Number:        2010 0051
 
[Components]
 
nvui.dll        8.17.14.1735        NVIDIA User Experience Driver Component
nvxdplcy.dll        8.17.14.1735        NVIDIA User Experience Driver Component
nvxdbat.dll        8.17.14.1735        NVIDIA User Experience Driver Component
nvxdapix.dll        8.17.14.1735        NVIDIA User Experience Driver Component
NVCPL.DLL        8.17.14.1735        NVIDIA User Experience Driver Component
nvCplUIR.dll        8.1.940.0        NVIDIA Control Panel
nvCplUI.exe        8.1.940.0        NVIDIA Control Panel
nvWSSR.dll        25.21.14.1735        NVIDIA Workstation Server
nvWSS.dll        25.21.14.1735        NVIDIA Workstation Server
nvViTvSR.dll        25.21.14.1735        NVIDIA Video Server
nvViTvS.dll        25.21.14.1735        NVIDIA Video Server
nvLicensingS.dll        6.14.14.1735        NVIDIA Licensing Server
NVSTVIEW.EXE        7.17.14.1735        NVIDIA 3D Vision Photo Viewer
NVSTTEST.EXE        7.17.14.1735        NVIDIA 3D Vision Test Application
NVSTRES.DLL        7.17.14.1735        NVIDIA 3D Vision Module
nvDispSR.dll        25.21.14.1735        NVIDIA Display Server
NVMCTRAY.DLL        25.21.14.1735        NVIDIA Media Center Library
nvDispS.dll        25.21.14.1735        NVIDIA Display Server
PhysX        09.18.0907        NVIDIA PhysX
NVCUDA.DLL        25.21.14.1735        NVIDIA CUDA 10.0.132 driver
nvGameSR.dll        25.21.14.1735        NVIDIA 3D Settings Server
nvGameS.dll        25.21.14.1735        NVIDIA 3D Settings Server

Exactly the same set of problems happen on another machine with a lot of similarities: Asus m5a78l-m plus/usb3 / AMD FX-8350 / 16G RAM, all ssd / gtx1050/2GB / Win10 (fresh install)

Now this is the interesting development I mentioned:

Machine 1

Dell Latitude 6320 / Win 7 / 4GB

GPU

And for the Machine 1 there are no problem at all. With exactly the same project, same rendering settings (I copied a few custom templates), different encoders, no proxy files generates it just does the job with acceptable playback, no freezing and what also interesting in comparable or shorter time (for rendering/encoding). Yet another observation for running the Dell laptop, when rendering the CPU use reaches and stays at 95-100% for each and every core, while for the FX-8350 on Machine 0 it floats around 45-50% typically even with the "realtime" priority assigned.

The clear problem is that I can not decouple hardware platform from the OS. So is it the CPU or the OS and why it makes such difference in any case both the machines are within the product required spec?

Is there anything else critical that I might have failed to include and would provide some meaningful insight?