Opening a project simply destroys my ssd disc space. What should i do?

konstantinos-sokolas wrote on 9/23/2016, 6:42 AM

I installed VEGAS 14.0 (build 161) in my Windows 128 gb SSD and tried to open a VEGAS 13 (build 453) 2 hour project from an 2 TB HDD. The project wouldn't load because all of my SDD space was consumed, something i was never had experienced with previous sony vegas editors... Also when i start a new project and import files to VEGAS 14, it just keeps eating space from my SDD.

Any solutions please?

Comments

Quitter wrote on 9/23/2016, 9:43 AM

Vegas 14 is using up to 10 GB memory sometimes, if your virtual ram (paging file) is managed by the system.
if you decrease the paging file, vegas runs out of memory.

The intermediate solution: set the Pagefile up to 15.000 MB on another disk. (not pretty but it works)


i have the same problem and stay in contact with MAGIX
[Ticket#2016092117003023]

Last changed by Quitter on 9/23/2016, 9:55 AM, changed a total of 2 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

NickHope wrote on 9/23/2016, 10:39 AM
The intermediate solution: set the Pagefile up to 15.000 MB on another disk. (not pretty but it works)

I just tried this to see if it would help my out-of-memory problem opening big projects containing HDV. I have 32GB RAM and I set a static pagefile of a further 16GB on my C: drive (SSD, whereas my others are HDD). It didn't help. Previously it was a system-managed size of 4864 MB.

Quitter wrote on 9/23/2016, 10:50 AM

i have 8 GB physical
2.048 MB static pagefile on C (SSD)
15.000 NB static pagefile on D (HDD)
Have you looked at the recourcemonitor how many committed memory Vegas take?

Here i have set the pagefile on 20.000 and Vegas don't crash

Last changed by Quitter on 9/23/2016, 10:55 AM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

NickHope wrote on 9/23/2016, 11:10 AM

This is opening a big VP12/13 project with lots of HDV and MagicYUV clips in it. Machine has 32GB RAM, 16GB pagefile. When "Commit Charge" got to it's peak first time round it stayed there for a while and I had a modern day equivalent of a BSOD crash. The 2nd test that this was captured from I got a Windows message to close the program when it reached the peak. I'm not expert at interpreting this stuff but I don't think it's pretty.

Quitter wrote on 9/23/2016, 11:16 AM

Try 50.000 pagefile (i know this is nuts)
This is only for testing i have it mailed to Magix

they can't recover this problem, i sent them my files now on DVD

Last changed by Quitter on 9/23/2016, 11:20 AM, changed a total of 2 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

NickHope wrote on 9/23/2016, 11:31 AM

Try 50.000 pagefile (i know this is nuts)

Result = Same ramp of "Commit Charge" then BSOD.

My poor C: drive that has been trundling along happily for 2 years suddenly doesn't know what's hit it.

But before the crash the "Opening Project" bar at the bottom left was at 9% and still creeping up.

I've heard people more technical than me refer to "memory leaks". Sounds like this might be one.

For kicks I'm thinking of putting a 1TB page file on my 8TB media RAID and trying it again, but I really can't afford to trash it. What do you think?

Quitter wrote on 9/23/2016, 11:35 AM

This can't be a problem of our PC configuration, VP13 works well with the same files

The Magix employee says:
I have imported up to 50 clips and then produced therefrom by cutting even more events. The program has never occupied more than 1.4GB memory.

Don't know what system they use

Last changed by Quitter on 9/23/2016, 11:39 AM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

NickHope wrote on 9/23/2016, 12:15 PM

I'm going to have to recreate my problem project bit by bit and see where it goes wrong.

konstantinos-sokolas wrote on 9/26/2016, 2:17 PM

Ok so i got a response from MAGIX:

Windows comes with a hidden administrator account which must first be enabled.  To do so:

Press the Windows Key + Q to bring up the search bar. Enter Command Prompt and right-click on the Command Prompt result that should appear.

This opens a list of options at the bottom of the screen.

Select Run as administrator and accept the UAC prompt.

Enter the following command to enable the hidden administrator account: net user administrator /active:yes

Double check to make sure the command is entered correctly and hit Enter on your keyboard.

After running this command, the prompt will respond with:  command completed successfully

This will enable the hidden admin profile in Windows. Go back to the Metro (Windows key at desktop) click your user name in the upper right hand corner and select Administrator from the drop down options.

Install and activate your former Sony Creative Software applications onto this profile.

 

Does that mean that i have to install VEGAS 13 as Administrator and then install VEGAS 14 in my profile?

NickHope wrote on 9/27/2016, 8:38 AM

Ok so i got a response from MAGIX:...

That sounds like a solution to an entirely different problem.

There is ongoing discussion on a more general thread about the out-of-memory issue here: https://www.vegascreativesoftware.info/us/forum/vp-14-win10-out-of-memory-problem--103767/?page=last#ca640682