Comments

fr0sty wrote on 8/19/2019, 7:17 PM

I don't know the direct contact number to give it to you, however you'd probably find them much faster by telling us a few things about what you're dealing with. Chances are we've already solved your issue here on the forums.

1. Your system specs

2. Your GPU driver version

3. The project settings of the project you are trying to load

We may need to know a few other things, but this will get us started with isolating your issue. Many times it's something simple like a GPU driver issue or a setting that needs to be changed.

 

Last changed by fr0sty on 8/19/2019, 7:17 PM, changed a total of 1 times.

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)

Xorcist wrote on 8/19/2019, 8:19 PM

Thanks fr0sty,

Project settings: 1920x1080 / 59.940 double NTSC - Pixel aspect 1.0

I'm going to collect more data - Current issue is v15 is locking up just playing or when I hit STOP via playback with the spacebar. I thought I solved the issue making sure there were no HEVC files (just AVC) and I turn the so4 setting for AVC from TRUE to FALSE but it still crashes. If GPU acceleration is on, it crashes within 40 seconds. If off, 2-3 minutes and when it started to fail, sometimes the preview window turns red.

The system is W10 Enterprise Ed - i7-2600K @ 3.40 w/nvidia latest drivers (studio drivers) GTX 1060 6GB. SSD drives. Vegas V15 with suspect .veg project and GPU acceleration on never goes over 80%. GPU hardly anything. With GPU acceleration OFF: CPU still the same. GPU also same. No change really so it's not an issue there. I've sent in a few dumps to the Magix support email with no response. Had to get the dumps from the system manager against the locked up Vegas process.

Then I was able to obtain Vegas POST today, install it on same system, loaded same working .veg and then not only did it crash just while playing (with for the first time a crash screen of which I sent 3 reports now), it also locked up just like before upon hitting stop. I changed the so4 option again but then it failed to load .MOV files altogether so I had to change it back. It locks up both using GPU or not (acceleration) - I've been told that the GPU acceleration only effects rendering but I also read it effects playback in the preview window and considering how much faster it locks up when GPU acceleration is on, that seems to be the case?

I did notice when running 17 POST, with CPU only, the CPU can peg at 100% (GPU 25%) much more often than with V.15. In fact it's odd that the CPU is mostly way up there with V17 POST. With GPU acceleration on, the numbers are CPU: 100% much more than CPU only, GPU: 3% so it's almost like it's backwards. These are all with preview set to DRAFT: AUTO

New laptop:

In an attempt to see if it was my system, I installed V.17 POST to an ASUS ROG. i7-8750H @ 2.20GHz. 16GB RAM, SSD drive. Nvidia GTX1070 w/16GB (8 dedicated/8 shared)

GPU Acceleration on: CPU 80% / GPU 12% - Playing and it locked up just like with the other system. I never get a crash window. Happened within 45 seconds1

GPU Acceleration off: CPU 70%-80% (!!) / GPU 24%-30% - Didn't lock up for a minute but those numbers? They seem backwards from above acceleration on!

So in the end, the faster laptop doesn't make a lick of difference.

Any ideas would be welcomed at this point.

PS

Kinvermark wrote on 8/19/2019, 9:38 PM

How about some details (preferably from MEDIAINFO program ) of your source files? (.MOV is not enough info)

fr0sty wrote on 8/19/2019, 9:46 PM

Also, when you say GPU acceleration, do you just have timeline acceleration on, or have you gone into the file i/o tab and enabled GPU decoding as well for your nvidia cards?

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)

Xorcist wrote on 8/19/2019, 10:05 PM

Also, when you say GPU acceleration, do you just have timeline acceleration on, or have you gone into the file i/o tab and enabled GPU decoding as well for your nvidia cards?

Just the options -> Prefs -> Video -> GPU Acceleration of video processing

Not aware the was another place.
I noticed that File I/O was set to Intel QSV instead of NVIDIA. Will change that to NVIDIA.

 

Xorcist wrote on 8/19/2019, 10:21 PM

Well that change from Intel QSV to NVIDIA did a lot. CPU down to 40-60% from pegged. GPU only up to 20-60%. The Preview windows on draft half still chugs once in a while but I'll let this run for a while and see if it locks up like usual.

Xorcist wrote on 8/19/2019, 10:32 PM

How about some details (preferably from MEDIAINFO program ) of your source files? (.MOV is not enough info)

iPhone footage .mov

H.264 mpeg4 AVC so it's really odd that Vegas with that so4 option off would fail to load it but maybe it would if I just changed the name extension from .mov to .mp4 - but now with the change I just made to the I/o decode, if that worked, then I'm golden.

Kinvermark wrote on 8/19/2019, 10:36 PM

Really not a great idea to mess with the hidden "internal" settings IMO. They are hidden for a reason. :) Best to reset.

Run MEDIAINFO (google it and download) on the iPhone footage. Variable frame rate?

.MOV and .mp4 are often interchangeable/ renamable. That said, you shouldn't need to do this with so4 at default.

Xorcist wrote on 8/19/2019, 11:32 PM

It was suggested by someone else but in the end, I am NOT using it. What has so far seemed to fix everything was switching from the Intel to the Nvidia encoder in the other File I/O settings. Thank you fr0sty. It's been running for almost an hour with no issues. CPU/GPU low. Still some chugging on the Draft/Half setting but to be expected given the fades.