VMS 11 crashing on 64-bit W7

erlingba wrote on 10/24/2011, 7:36 AM

I've ben using VMS for a couple of years, and has been qiute hapy with it.
I experienced a few crashes when opening large projects after upgrading my old pc to 64-bit W7.

I recently bought a new laptop with 8GB ram, SSD, i7 dual core and W7 64-bit, and now I can't render big projects without errors.
Got "Out of memory"-messages when only half of the memory was used.
Did the CFF-hack, but that has coused it to drop frames and clips randomly.
It is extremely frustrating to not be able to render the project that I have been working on for so long.
And it is annoying that a program I have payed for is completely useless.

Is there a fix available for VMS 11 to make it work on 64-bit systems?

Comments

ahlaj77 wrote on 10/24/2011, 8:16 AM

I am having the EXACT same problem. Bought a new PC with 12GB of RAM windows 7 64bit, 2TB hard drive, so on and so forth. When I work on or open up large VMS11 files, video studio gets upset and stops responding and I will have to close it. Its really annoying. I hope they find a solution soon.

Jack S wrote on 10/24/2011, 9:22 AM

erlingba

I don't know about the CFF hack but I applied the LAA (Large Address Aware) patch to my VMS11 executable and I've had no problems since. I'm not working on 3D but I was getting Out of Memory errors before applying the patch. Can I suggest that you apply the LAA patch before you give up on it altogether.
As far as I know, this is the only way to make it work.

D7K wrote on 10/24/2011, 2:24 PM

I think this is the LLA fix was posted:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=12&MessageID=779949

erlingba wrote on 10/26/2011, 4:03 PM

Thanks for the tip!
If this fix is so easy that everyone can do it, why hasn't Sony published an official patch?

I see there are some talk about pathcing files in that thread, but I don't understand how to do it.

I have installed build 247 on a completely new laptop.
Tried a trial Sony Vegas Pro, and that works a lot better. It renders the project with no problem, but I suddely got a chrash when it loaded mye music video project. So it might be some files there it doesn't like.
I believe five or six is transcoded to Avid DNxHD, the rest, roughly 30, is Cineform.

Wrote a message to support the other day, but haven't got any answers yet.

erlingba wrote on 10/29/2011, 7:41 AM

I located the file that coused it to crash when loading my music video project.
It was a single file, transcoded to cineform like the others, that caused the crash.
the solution is to simply rename the file before opening the project.
When Vegas has finished loading all the other files i will rename it back and everything works.
Quite strange.

Haven't fixed the "Out of memory" problem yet. Is using Vegas Pro-trial to render the files, and will probably go for Adobe Premiere for my next project as Sony don't seem able to fix their software.

ED Doc wrote on 10/30/2011, 11:39 AM

Don't give up on VMS 11 yet. I used the solution posted on this forum and it worked like a charm.

Go to http://www.ntcore.com/exsuite.php and download the Explorer Suite.

After you down load and install CFF Explorer, right click on the icon in the Start Menu and choose "Run as Administrator". Otherwise, you will not be able to save the file with the same name.

Open the file in CFFExplorer.
On the left side you'll see "NT HEADER".... "DOS HEADER"... etc
Highlight "FILE HEADER" under "NT HEADER"
On the right side you'll see a chart and in the bottom right corner you will see "CLICK HERE"
Click on that and a check box menu system will open.
Scroll down the menu list until you see "app can handle > than 2gig address space" and check that.
Save the file and close.

The files that you need to adjust for VMS 11 are as follows:
1. VegasMovieStudioPE110.exe
2. vegasmoviestudiope110k.dll
3. sonymvd2pro_xp.dll
4. sonymvd2pro_x.dll (in FileIO Plug-Ins\compoundplug directory)
5. wmfplug4.dll (in FileIO Plug-Ins\wmfplug4 directory)
6. FileIOSurrogate.exe

I was getting the "Low Memory" error when I would try to render. I have 16 Gb on my desktop. I moved from Adobe to Vegas. I am happy so far.

erlingba wrote on 11/1/2011, 2:08 PM

Thank you!

Found something about this elsewhere, but it only said it was necessary to fix the exe-file.

Applied the patch now, so I'll see if that does it.

I have tried Vegas Pro for a couple of weeks, and it works better, but i still get crashes, and the occasional black clips in the timeline.

Had trouble with both VMS and Pro chrashing when loading a music video project.
Found out which clip caused it and re-named it, when Vegas had finished loading I named it back and everything worked well.

neil down under wrote on 11/8/2011, 1:22 AM

newbie here...bravely followed yr directions, all okay until asked to save, and it wouldn't allow me to save...any further directions would be gratefully rec'd....

D7K wrote on 11/8/2011, 1:43 AM

Make sure you are signed in as administrator.

neil down under wrote on 11/8/2011, 1:44 AM

further...i didn't read yr note very well: to run as administrator: will try again and let u know (silly, silly, silly!)

neil down under wrote on 11/8/2011, 2:31 AM

...has accepted changes...will let u know result (fingers crossed) in due course...thanks all...

panzer948 wrote on 11/8/2011, 10:29 AM

Does anyone know if this workaround will work for Vista 64 bit OS as well? I believe this is for Windows 7 64.

neil down under wrote on 11/8/2011, 5:52 PM

now works like a charm....thanks for your very clear instructions...very grateful

ArtfulCodger wrote on 11/9/2011, 5:33 PM

Ack, but that's terrible. I'm running 32bit right now, but was expecting my next computer to be 64bit, and then i learn there are problems?

Computers have been using 64 bit for many years now, i thought I was one of the last not to change, apparently Sony hasn't either :-/

Martinique wrote on 12/1/2011, 2:37 PM

Thank you so much!!!!!!