getting 'not responding' notices all the time with simple editing.

Mark-Kuzio wrote on 7/5/2020, 12:41 PM

Can anyone help with solutions to these constant 'not responding' notices that I am getting with simple editing features on Vegas Pro 17? GPU is set to 0. What should maximum rendering threads be set to? I use a GeForce GTX 1660 i9 machine. This really is getting ridiculous.

Comments

fred-w wrote on 7/5/2020, 1:21 PM

I see the community is "not responding." Also, Vegas team "not responding" to this MAJOR flaw (instability) for years now.

j-v wrote on 7/5/2020, 1:48 PM

I see the community is "not responding." Also, Vegas team "not responding" to this MAJOR flaw (instability) for years now.

If someone makes more than one double posts it's difficult to see them all.😁

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.77 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Mark-Kuzio wrote on 7/5/2020, 1:50 PM

Fred...I don't mean to be overly negative but in hindsight I wish I had started years ago with Final Cut Pro. I have been just too lazy at my age to learn a whole new editing system again. I just may have to switch after all.

Musicvid wrote on 7/5/2020, 3:02 PM

Are you guys looking for peer support? Then start here:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Otherwise, feel free to grouse.

Mark-Kuzio wrote on 7/5/2020, 3:49 PM

been there....not interested in spending hours to fix an issue that shouldn't be there in the first place. nice try.

Musicvid wrote on 7/5/2020, 3:53 PM

been there....not interested in spending hours to fix an issue that shouldn't be there in the first place. nice try.

No, you haven't "been there.".

You spent eleven minutes today posting three comments on the FAQ page, and you did not respond to the "Important Information Required to Help You" link there, either. You "might" have gotten some help here, too, but patience and accountibility seem to be two missing commodities.

We are your peers, not your target. Community rules are here, bye.

https://www.vegascreativesoftware.info/us/community-rules/

michael-harrison wrote on 7/5/2020, 6:20 PM

1. This is not a chat room. Don't expect replies immediately or even on your timetable.

2. This is a weekend for many people. Even Covid hasn't removed the desire of some people to have a Sunday off.

3. Complain to your therapist. If you want help from your peers, you're going to have to work with us, not just whinge at us.

4. Try these things. They worked for me.

Mark-Kuzio wrote on 7/5/2020, 9:02 PM

1 2 and 3 could have been skipped....thanks for 4. Thanks Dad for the advice.

fr0sty wrote on 7/5/2020, 10:29 PM

You can either stop being a dick to people trying to help you, or you can leave. If you are not willing to do the few things we've asked of you in order to be able to diagnose your problem, there is nothing we can do for you. You obviously haven't "been there", or you would have read where it requests that you post certain info with your help requests so we can know how to diagnose your problem.

You could have corrupt media, operating system corruption, driver conflicts, or a number of other external sources that could be causing issues with VEGAS, we need to rule those things out before we can start telling you what you can do inside of VEGAS to solve your issue.

To do that, we need to know your full system specs (CPU, GPU, RAM, Windows Version, GPU Driver version), a mediainfo report of the media on your timeline (one report per media type), get mediainfo here, as well as the project settings of your VEGAS project, and your settings in the video and file i/o tabs of VEGAS preferences.

Last changed by fr0sty on 7/5/2020, 10:31 PM, changed a total of 1 times.

Systems:

Desktop

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

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

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

Mark-Kuzio wrote on 7/6/2020, 10:09 AM

here goes...

Mainboard MSI MPG Z390M Gaming Edge AC, CPU= INTEL Core i7-8700K 6-core 3.7GHz (4.7Ghz Turbo, Cooler=EVO212, RAM=32gb DDR4, SSD=1TB Samsung 970 NVMe PCle M.2 Solid State Drive, Video=NVIDIA, NVIDIA Graphics Driver 441.66, GeForce GTX 1660 Ti 6GB, PSU= Corsair RM1000x, OS= Windows 10 Pro 64-bit.

Project properties= HDV 1080-60i 1440x1080 29.970, Pixel format= 8-bit,

Video= Video 1, DJI Drone Video is MP4, Format=AVC, 2704x1520x12 29.970fps

VIDEO PREFERENCES SETTINGS are: DRAM=0, Rendering Threads=32, GPU Accelaeration is OFF, Preview Device is Windows Graphics Card, display adaptor is 1920x1080 (60)

Note: I have adjusted the above video Preferences settings every which way that you can imagine... and then some. The above machine is 6 months old.

I started with Vegas 8 many years ago, then 12 and now 17. Always the same issue and sometimes others. The current and immediate issue is system crashing when doing very simple tasks. I've had many issues with the rendering process in the past over different machines and versions of Vegas. Why have I stuck with Vegas? good question...I chalk it up to my laziness in needing to start a steep learning curve all over again. Maybe Vegas runs perfectly with experts like yourself.

j-v wrote on 7/6/2020, 10:36 AM

I'm not an expert but a long time editor for pleasure and hobby.
Look at the specs for my desktop in my signature, nearly the same as yours but newer drivers I think.
I edit and render FHD 50p, 4K Hevc 50p from GoPro and 4K 50p AVC from DJI Pocket without problems.

These are my Preferences you told

Last changed by j-v on 7/6/2020, 10:37 AM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.77 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

michael-harrison wrote on 7/6/2020, 10:43 AM

Try updating to the latest studio drivers, 451.48, turning GPU rendering back on and disabling the so4 dll.

Unless you have settings in the nvidia panel you just absolutely can't live without, do a driver cleaning before installing the latest version

 

Mark-Kuzio wrote on 7/8/2020, 10:14 AM

Thanks guys, I have tweeked my settings and will see what happens. Also, will check drivers.

RogerS wrote on 7/8/2020, 9:38 PM

I haven't had freezes with the latest NVIDIA studio drivers with GPU preview on (so far) and the latest VP 17 build. Something seems to have changed for the better. I also did the clean install of NVIDIA first.