VEGAS Pro 15 Update 3 (build 311) - General Discussion

Comments

fr0sty wrote on 3/5/2018, 12:57 AM

Those having crashing problems with 311, disable so4compoundplug.dll for AVC, disable your GPU for timeline rendering, do not use NVENC to encode. It sucks, but it will at least get your project out the door... albeit slowly. Even then, it still crashes some, but it got me to the point of rendering at least. I also had to disable neat video, for those that use it. Pretty much anything that uses the GPU or so4compoundplug.dll will make it unstable. This is especially true with projects that have large amounts of media in them (like when loading dozens to hundreds of clips from 4-5 cameras for a 2 day wedding video shoot), which makes me think memory management is the root cause of all of these issues... that and the fact that neat video was complaining about running out of VRAM even though it was set to only use 25% of 4GB.

Last changed by fr0sty on 3/5/2018, 12:59 AM, changed a total of 2 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)

AVsupport wrote on 3/5/2018, 4:00 AM

Re. Crashes / Instability:

I'm just in the process of testing a different approach to @fr0sty [thanks for sharing and testing!!] , since it looked like VP doesn't like the use of 'modern' integrated intel GPU's;

I have turned my CPU-internal intel GPU OFF (Bios), to avoid handover confusion, and a simple test bed, and loaded a 4K project with 4K XAVC-S clips using so4compound.dll [**no timecode**], applying system wide GPU support (GTX1060/6GB), and applying Filmconvert (GPU rendering selected within) on approx 12 consecutive clips;

I have changed my VP preset memory usage in the System>[shift]Preferences>Internal which seemed to help stabilize the system by making more resources available (early tests):

  • 'Memory needed by Vegas 64-bit' value = [2,048] default: 1,024
  • 'OpenCL Memory Size Filter' = [1,024] default: 384
  • 'Autocalc Video Memory (64-bit) : I cannot set to TRUE even though default = true. Value = False. >>>???<<<
  1. 'Rendering to New Track' a 10 minute section to 4K/25 NVidia gives me GPU 50%, ~1:1 10'44". acceptable. but not better than realtime. [11'30" on HQ]
  2. Rendering via Intel HEVC is awfully slow, GPU 5%, est ~7.7:1, 1 hr 17",
  3. Rendering using Sony XAVC-S Long: ~9% avg GPU use, rendering time ~25' giving a slow ratio of 2.5:1

in all cases, CPU is 100% flat out, 6 cores @ 4GHz. And there's plenty fast RAM spare, Disk speed not an issue, nor busses..

...but in all cases, No Crashes, so far so good.

-----The other little ?Lame code warning? I detected whilst doing so: When you redo a 'render to new track' essentially overwriting an existing rendered file, you get prompted: 'do you really want to overwrite?' On confirmation, it then says It can't do it because it's in use, forcing you to delete the file from the timeline, and then the project list...

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

david-ruby wrote on 3/5/2018, 10:53 AM

For what it is worth.I just applied 2 text boxes to a track and one xacv or avc clip as vegas is saying in properties. Everything previews fine. Then I add a simple shadow to the text. Major lag on preview. My task monitor shows 5% and no excess memory being used. cpu holds at 12% all upon playback. Can't edit unless you go to preview and work with blurry footage. My client would not sit through this.l Hope some of this helps guys.

 

david-ruby wrote on 3/5/2018, 10:54 AM

For what it is worth.I just applied 2 text boxes to a track and one xacv or avc clip as vegas is saying in properties. Everything previews fine. Then I add a simple shadow to the text. Major lag on preview. My task monitor shows 5% and no excess memory being used. cpu holds at 12% all upon playback. Can't edit unless you go to preview and work with blurry footage. My client would not sit through this.l Hope some of this helps guys.

 

Footage is shot with a Sony A7s camera.

david-ruby wrote on 3/5/2018, 5:59 PM

I must also add here as I was trying to see how color correcting did with the color wheels? They flash on and off as you move the wheels to adjust color. Very unusable at this point. The video does react to the adjustment correctly but you cannot use the color wheels or the lumetri screen to get this correct.

david-ruby wrote on 3/5/2018, 6:11 PM

I must also add here as I was trying to see how color correcting did with the color wheels? They flash on and off as you move the wheels to adjust color. Very unusable at this point. The video does react to the adjustment correctly but you cannot use the color wheels or the lumetri screen to get this correct.

I must add that the lumetri vectorscope and rgb parade do not update at all while stuttering when wheel moved.

John Lewis wrote on 3/5/2018, 8:04 PM

Finally got VP15 311 edit working but it wont open VP13 Projects, i get message that it was created in earlier version. will this be a new feature of Magix Vegas when 16 is released will i be able to open Vp15 projects or will i get the same message. If yes then that sucks

fifonik wrote on 3/5/2018, 8:06 PM

That's strange. I am able to open in VP15 projects that were created in VP11 and VP13 (have not checked other versions).

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

John Lewis wrote on 3/5/2018, 8:17 PM

Thanks I will uninstall and re install tomorrow and re try,.

NickHope wrote on 3/5/2018, 9:37 PM

Finally got VP15 311 edit working but it wont open VP13 Projects, i get message that it was created in earlier version. will this be a new feature of Magix Vegas when 16 is released will i be able to open Vp15 projects or will i get the same message. If yes then that sucks

@John Lewis Are you sure you didn't just get this?:

Vegas Pro projects are always forwards-compatible by design. One problem you might have is if the project contains an FX that is not supported in the later version.

AVsupport wrote on 3/5/2018, 10:05 PM

Just done another couple of test with my above setup, rendering 1 hour XAVC-S 4K down to 1080/25 using Magix AVC NVENC.

Clips had Filmconvert (GPU) on it, plus Event Pan/Crop 200% for fun, plus overlay bouncing Text (Vegas) with a shadow.

Besides the fact that Vegas Text is CPU intensive (no GPU acceleration here..) it seemed to render fine, albeit a little slow: est 5hrs for a 1 hr timeline [5:1]; aborted after 2 hrs 30', at 50%. I recon it would have done the full lot allright.

Just using Filmconvert & 2xZoom applied does it in 38' [0.63:1].

I have tried to disable the 'shared GPU memory' but I cannot do this (ideas, anyone??), neither possible in the BIOS. On googling the issue here and here , it seems Win10 Creators update now pushes / manages the Vram and doesn't like to push graphics cards further than 50% standard load so that other tasks can be unaffected. Yes, in our case this is counter productive. And maybe the 'fixes' for the lack of internal CPU/GPU memory may adversely affect a high power application like a Vegas rendering process.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Cielspacing wrote on 3/5/2018, 10:29 PM

(ideas, anyone??), neither possible in the BIOS. On googling the issue here and here , it seems Win10 Creators update now pushes / manages the Vram and doesn't like to push graphics cards further than 50% standard load so that other tasks can be unaffected. Yes, in our case this is counter productive. And maybe the 'fixes' for the lack of internal CPU/GPU memory may adversely affect a high power application like a Vegas rendering process.

A rather unrelated idea (to shared GPU memory) but since all solutions there point to BIOS modification, found a singular settings mod you might like to try out:

"Faking the Increase

Because most integrated graphics solutions automatically adjust to use the amount of system RAM they need, the details reported in the Adapter Properties window don’t really matter. In fact, for integrated graphics, the Dedicated Video Memory value is completely fictitious. The system reports that dummy value simply so games see something when they check how much VRAM you have.

Thus, you can modify a Registry value to change the amount VRAM your system reports to games. This doesn’t actually increase your VRAM, it just modifies that dummy value. If a game refuses to start because you “don’t have enough VRAM,” upping this value might fix that.

Open a Registry Editor window by typing regedit into the Start Menu. Remember that you can mess up your system in the Registry, so take care while in here. How Not to Accidentally Mess Up the Windows Registry How Not to Accidentally Mess Up the Windows Registry Working with the Windows registry? Take note of these tips, and you'll be much less likely to do lasting damage to your PC. Read More

Head to the following location:

HKEY_LOCAL_MACHINE\Software\Intel

Right-click the Intel folder on the left sidebar and choose New > Key. Name this key GMM. Once you’ve made it, select the new GMM folder on the left and right-click inside the right side. Select New > DWORD (32-bit) Value. Name this DedicatedSegmentSize and give it a value, making sure to select the Decimal option. In MB, the minimum value is 0 (disabling the entry) and the maximum is 512. Set this value, restart your computer, and see if it helps a game run."


https://www.makeuseof.com/tag/video-ram-windows-10/

AVsupport wrote on 3/5/2018, 10:44 PM

interesting read @Cielspacing ,perhaps I wasn't clear:

I want to disable the 'shared GPU memory' to see if VP runs better that way. I have a GTK1060/6GB and under 'full load', the best VRam usage I get is 1.8/6.0 GB, but using 0.6/8.0GB Shared GPU memory..That's with allocating 4GB for VP64 and 2GB for OpenCL in preferences...Why?? GPU is only under ~20% load at most..I can't get it to work harder..!

 

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

John Lewis wrote on 3/6/2018, 1:29 AM

Finally got VP15 311 edit working but it wont open VP13 Projects, i get message that it was created in earlier version. will this be a new feature of Magix Vegas when 16 is released will i be able to open Vp15 projects or will i get the same message. If yes then that sucks

@John Lewis Are you sure you didn't just get this?:

Vegas Pro projects are always forwards-compatible by design. One problem you might have is if the project contains and FX that is not supported in the later version.

 

John Lewis wrote on 3/6/2018, 1:33 AM

Thanks Nick I did see that for 1 project but i saved it with VP15 added to filename

I will check to see if any fx are on but the pc will also have VP13 on it and the fx would be the same ones

John Lewis wrote on 3/7/2018, 12:02 AM

Totally weird but it is working now Thanks

walter-i. wrote on 3/7/2018, 3:26 AM

I observe in Build 311, that media-effect Vegas-stabilizer works much worse than in Build 261.
It also works satisfactorily in VP14.
In Build 311, I can't notice a single zoom-in after stabilize, even with strongest stabilization (1,00).
The effect in VP15 B311 with strongest stabilization (1,00) is worse than light stabilization (0,25) in VP 14 B270.

Can anybody confirm this?

Last changed by walter-i. on 3/7/2018, 3:27 AM, changed a total of 1 times.

CPU: Intel i9-9900KS 4GHz, (UHD Graphics 630, driver: 27.20.100.8581)
MB: ASUS TUF Z390-PLUS Gaming,
MEM.: 32 GB Ram, DDR4-3200
GPU: Nvidia GTX 1660 SUPER, (driver 451.77)
Storage: SSD 970 EVO Plus 500GB M.2, SSD 860 EVO Series 1TB, Toshiba 3TB SATA,
OS: WIN 10 Pro, 1909
Monitor: HP243i 1920x1200 / BenQ G2200W 1680x1050
NLE: Vegas Pro11-15+17,18 Heroglyph4, RespeedR
Camcorder: Pana HDC SD909, Sony FDR-AX53

paul-priestley wrote on 3/7/2018, 8:07 AM

Hi Everyone

I have a strange issue. I upgraded to version 311 (also happened in build 261) a few days ago and since then, if I click on an fx button on an object in the timeline, a single white bar appears across the screen with the words 'Plugin Chooser - video event FX' but no plugins are shown.  It also launches the Event Pan /crop box at the same time which displays normally. I can't do anything on the screen until I close the bar. When I close the white bar the Event Pan /Crop box remains, the bar disappears. The only way I have found of applying an fx is to drag and drop onto the time line which is a bit more long winded. Anyone else have the same problem and anyone know a solution? I am using a dell machine I7 4770 with GTX 750TI

Thanks Paul

NickHope wrote on 3/7/2018, 8:23 AM

@paul-priestley If you hover over the bottom of that white bar, can you drag the bottom of it down? Does it have a ? and X at the right end of it?

paul-priestley wrote on 3/7/2018, 9:04 AM

Hi Nick I can hover over the bar and pull to it to the bottom of the screen and it does have an ? and X at the end. However, the program just bleeps until the x is clicked to close the bar - I'm not able to do anything until the bar is closed. Weirdly, if I drop a FX onto an object in the timeline, that will work, and from then on clicking the fx button on that object will work normally.

vkmast wrote on 3/7/2018, 9:11 AM

So you don't get anything like this hovering? Maybe try resetting?

paul-priestley wrote on 3/7/2018, 9:34 AM

Hi Vmast No, it is simply a white bar that stretches across two thirds across the screen, there is nothing below or attached to it. Tried resetting but holding down shift and control and double clicking just brings up a box saying 'do you want this app to make changes to your device - Vegas Pro 15' clicking yes simply loads the program.

paul-priestley wrote on 3/7/2018, 9:45 AM

Hi Vmast Finally read the instructions for resetting properly and have reset the program. It's solved the problem. Many thanks, much appreciated. Paul

vkmast wrote on 3/7/2018, 10:56 AM

Great. Yes, it's important to take note of the asterisked amendment in the factory default reset FAQ.