Video Studio 11 and Windows 7 - Help

[cannockyouth]

Hi,

I have VS11+ installed on Windows 7 and have run the power pack update and the latest patch from the Ulead site, I have also run the latest drivers form Nvidea. However when trying to view AVCHD files it is very jerky and when trying to edit or view them in the project with sound, subtitles etc included it is super jerky and after a few seconds freezes and the pop up with VS11 has stopped working etc etc.

I would have thought my PC spec was enough to cope - I edited standard res projects on the same system with no trouble at all.

ANy help is much appreciated.

[Ken Berry]

Welcome to the forums. I only wish it could have been under happier circumstances.

You have two things going against you. First, VS 11 was never made for Windows 7 and I am surprised it works at all. They had to bring out a special Windows 7 patch for VS X2 to make it work properly with Win 7, but they will not be bringing one out for the older VS11.

Second, you might be able to edit and play standard definition video OK on your computer, but it is at the very bottom end of what can deal with AVCHD. AVCHD is currently the most demanding video format on computer resources. And it requires even more computer resources to be able to play it smoothly than it does to edit it, believe it or not. A Core 2 Duo processor is the absolute minimum, and you have that, though it is at the very lowest end of the Core 2 Duo processors. And I think that when you also throw in the fact that you are using a program not designed to work with Win 7, you have your answer.

Video Studio X2 and X3 both have a feature called SmartProxy which can help in this situation. It creates a standard definition 'proxy' copy of your high definition original video. You edit that and when finished, apply all the edits behind the scenes to the AVCHD. But to repeat, I suspect your computer is at the bottom end of what might be able to play AVCHD smoothly. And unfortunately, as far as I can recall, SmartProxy was not included in VS 11.

[Rob717]

And unfortunately, as far as I can recall, Smart Proxy was not included in VS 11.

Smart Proxy is included in VS11 Plus

In regards to VS11 on Windows 7, don't know never tried it. But the best thing to do would be to find out what information is in the error message.

Launch the Windows Control Panel: Start | Control Panel
Go into "Administrative Tools" (if you do not see Admin Tools change the "View by" at the top right to small or large icons)
Open "Event Viewer"
Expand "Windows Logs" by double clicking or click once on the small triangle to the left
Select "Application"

Now scroll through looking for an Error under the Level categories and to the right of the Error under source it should say Application. in the information under "General" it should show Faulting Application VStudio.exe 11.0.0.0 and then the Faulting Module is what we need to determine what is causing the crash.

But we still need to keep in mind that there may be no fix for this issue because VideoStudio is not meant to be ran on Windows 7, I know one issue will be when you go to burn a disc you will not have the next button to proceed to the final burn screen. You can however use the hot keys to make your way through the burning process.

If you can post the event viewer information then I might be able to help, if not you might want to think of upgrading to X3 or installing the XP mode on Windows 7 using Microsoft Virtual PC, but even that might not help.

[Ron P.]

Yes, just to confirm that Smart Proxy is included with VS 11.5+, and was first introduced in VS10 +

[Ken Berry]

Was it really?? How quickly I forget...!!! And who are you again???

[cannockyouth]

And unfortunately, as far as I can recall, Smart Proxy was not included in VS 11.

Smart Proxy is included in VS11 Plus

In regards to VS11 on Windows 7, don't know never tried it. But the best thing to do would be to find out what information is in the error message.

Launch the Windows Control Panel: Start | Control Panel
Go into "Administrative Tools" (if you do not see Admin Tools change the "View by" at the top right to small or large icons)
Open "Event Viewer"
Expand "Windows Logs" by double clicking or click once on the small triangle to the left
Select "Application"

Now scroll through looking for an Error under the Level categories and to the right of the Error under source it should say Application. in the information under "General" it should show Faulting Application VStudio.exe 11.0.0.0 and then the Faulting Module is what we need to determine what is causing the crash.

But we still need to keep in mind that there may be no fix for this issue because VideoStudio is not meant to be ran on Windows 7, I know one issue will be when you go to burn a disc you will not have the next button to proceed to the final burn screen. You can however use the hot keys to make your way through the burning process.

If you can post the event viewer information then I might be able to help, if not you might want to think of upgrading to X3 or installing the XP mode on Windows 7 using Microsoft Virtual PC, but even that might not help.

Hi,

I have more than one by the looks of it, they are as follows, though its the first one which appears to occure the most frequently!! - thanks for the help!!:

Faulting application name: vstudio.exe, version: 11.0.0.0, time stamp: 0x4762104e
Faulting module name: H264VDecHPDll.dll, version: 1.1.1.73, time stamp: 0x46ce7b56
Exception code: 0xc0000005
Fault offset: 0x000740f3
Faulting process id: 0x1138
Faulting application start time: 0x01cb2399fb9a4281
Faulting application path: C:\Program Files (x86)\Ulead Systems\Ulead VideoStudio 11\vstudio.exe
Faulting module path: C:\Program Files (x86)\Common Files\Ulead Systems\MPEG\H264VDecHPDll.dll
Report Id: 76063625-8f8d-11df-9afc-001060d0f4fd

Faulting application name: vstudio.exe, version: 11.0.0.0, time stamp: 0x4762104e
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
Exception code: 0xe06d7363
Fault offset: 0x0000b727
Faulting process id: 0x454
Faulting application start time: 0x01cb23952ea3cb0c
Faulting application path: C:\Program Files (x86)\Ulead Systems\Ulead VideoStudio 11\vstudio.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d1552e14-8f88-11df-80e8-001060d0f4fd

[cannockyouth]

Hellooooo please - anyone????

Help me............

[Black Lab]

Ken has already given you 2 suggestions for what may be causing your problem.

[cannockyouth]

Ken has already given you 2 suggestions for what may be causing your problem.

I know, but Rob717 said to post the errors to get a specific diagnosis - thats what I was hoping someone would offer before I go and spend £££'s on a new system.

[cannockyouth]

OK Guys,

So I need to get a new PC, but budgets a bit tight, before I push the button, will the following spec be man enough to edit AVCHD with videostudio on Windows 7??

CPU: 1042 - NEW! AMD Athlon II X4 635 AM3
Operating System: 11001 - No Operating System - I will install my own
Motherboard: 4081 - Asus M4N68T-M
Memory: 5028 - 4GB DDR3 1333mhz (2x 2GB)
Hard Drives: 6004 - 500GB S-ATAII 3.0Gb/s
Optical Drive: 7006 - 22x DVD±RW DL S-ATA Lightscribe
Graphics card: 8040 - NVIDIA GeForce GTS 250 1GB
Sound card: 10001 - Onboard 7.1 Audio
Case: 17024 - Xigmatek Asgard
PSU: 18027 - 500W PSU

Many thanks guys!!

[aljimenez]

OK Guys,

So I need to get a new PC, but budgets a bit tight

Why don't you upgrade to VS X3 before you spend the money. The problem you have is that VS is not working in Win 7... Al

[Ron P.]

OK Guys,

So I need to get a new PC, but budgets a bit tight

Why don't you upgrade to VS X3 before you spend the money. The problem you have is that VS is not working in Win 7... Al

That's not his only problem. He's trying to edit AVCHD too. It's a combination of the version and the most compressed video file format. So if he does upgrade to VS X3, on his current machine, he still will have problems trying to edit AVCHD..

[cannockyouth]

So.... will the spec I posted be OK???

Cheers

[Ron P.]

Yes it should, since it is a Quad-core processor.