Alludo USER to USER Web Board

I have used Corel VideoStudio Pro X2 on Windows XP, Windows Vista and Windows 7 (both the beta and release candidate). My older Windows Vista PC had no problems running the program, but it was 32-bit, and my current one, when I use VideoStudio Pro X2 on it, for some reason it isn't compatible with the Aero interface and must switch to the "Basic" scheme. This doesn't happen on the same PC running Windows 7 (it's a dual-boot setup). This is the 64-bit Windows Vista and Windows 7. Here are my PC's specs, both the old one and then the new one:

HP PAVILION DV9408NR (original)

1.8 GHz AMD Turion64 X2 dual-core processor
2 GB of RAM (originally 1 GB)
160 GB hard drive
Lightscribe dual-layer DVD/CD drive
NVIDIA GeForce Go 6150 graphics chip with 64 MB dedicated video RAM; shares 256 MB of system RAM
Windows Vista Home Premium with Service Pack 1 (32-bit)
(Alternate OS: Windows XP Media Center Edition 2005 with Service Pack 3)


HP PAVILION DV7-1183CL (current)
2.0 GHz Intel Core 2 Duo processor
4 GB of RAM
Two 250 GB hard drives
Blu-Ray player/dual-layer DVD burner
NVIDIA GeForce 9600M-GT graphics chip with 512 MB dedicated video RAM
Windows Vista Home Premium with SP1 (64-bit)
(Alternate OS on partition of second hard drive: Windows 7 Ultimate Release Candidtate (64-bit))


Is there a way to make VideoStudio Pro recognize the Aero interface again or something?

And this effects your editing how?

Wiley209 wrote:...... This doesn't happen on the same PC running Windows 7 .....

That is indeed good news and a sign of hope for the future. Microsoft appears to have realised the mess they have made of Vista and are taking steps to rectify it in Windows 7.

Clevo wrote:And this effects your editing how?

It doesn't much but it can sometimes screw up things in Windows

According to Corel the system specs for VS 12 are:

For general and Proxy HDV Editing

¡P Intel® Pentium® 4 3.0 GHz, AMD Athlon® XP 3000+ or higher with Hyper-Threading technology

¡P Microsoft® Windows® XP SP2 Home Edition/Professional, Windows® XP Media Center Edition, Windows® XP Professional x64 Edition, Windows® Vista By not specifying 64bit, they may mean that it is not supported

¡P 512 MB of RAM or higher (1 GB of RAM may be recommended depending on the video capture device used)

¡P 1 GB of available hard disk space for program installation

¡P Windows-compatible sound card (multi-channel sound card for surround sound support recommended)

¡P Windows-compatible DVD-ROM for installation



Non-Proxy HDV editing

¡P Intel® Pentium® 4 3.0 GHz or higher with Hyper-Threading technology

¡P Microsoft® Windows® XP (Service Pack2 for HDV camcorder support recommended)

¡P 1 GB of RAM (2GB or more recommended)

¡P 16X PCI ExpressTM display adapter

sjj1805 wrote:

Wiley209 wrote:...... This doesn't happen on the same PC running Windows 7 .....

That is indeed good news and a sign of hope for the future. Microsoft appears to have realised the mess they have made of Vista and are taking steps to rectify it in Windows 7.

I've experienced an opposite problem over here, with both the January public beta of Windows 7 and the recently released RC1. Ulead VideoStudio 11, and the trial version of Ulead VideoStudio X2, both do something to Windows Explorer once installed, at irregular intervals.

Ulead doesn't even have to run for the problem to surface. Once Ulead has been installed, at irregular intervals, both folder icons and program/file icons will begin to disappear while browsing through folders. Once this happens, both "My Computer" and "Control Panel" cannot be accessed...all that appears when clicking on them is an empty screen. Only way to restore things to normal, once this happens, is a reboot.

I've tried compatibility settings for both Ulead and its installer...have tried disabling Aero...enabling the "Classic Windows" interface that's still in Windows 7...tried the "launch folder windows in a separate process" option...have even disabled the ATI 1650 video card that came with this system and tried the motherboard graphics instead...no luck so far.

The system has plenty of RAM, 4 gigabytes, and an Intel quad core 2.4 ghz processor.

Oddly, the 32 bit version of Windows 7 seems more prone to this behavior than the 64 bit version over here...but the only way to completely eliminate the issue is to uninstall Ulead.

Ulead, itself, is unaffected. The program launches and runs in Windows 7 perfectly fine...but it certainly manages to cripple part of Windows 7, at least over here. Checking system logs for unusual error messages has turned up nothing unusual, so I don't have a clue as to why this is happening.

In a sense, I have to say that this is all a bit of whistling in the dark... The simple fact is that VS has not been written for Windows 7. I know that lots of programs also have not been but work just fine. But video editing is a demanding procedure, and VS took long enough to settle down relatively well to Vista. So I personally would not be expecting too much until Corel either bring out a Windows 7 patch, or more likely a new version which they claim is Windows 7-compliant.

Ken Berry wrote:In a sense, I have to say that this is all a bit of whistling in the dark... The simple fact is that VS has not been written for Windows 7. I know that lots of programs also have not been but work just fine. But video editing is a demanding procedure, and VS took long enough to settle down relatively well to Vista. So I personally would not be expecting too much until Corel either bring out a Windows 7 patch, or more likely a new version which they claim is Windows 7-compliant.

I knew it wouldn't be long before a response like this would surface, which is why I kept the Windows 7 issue to myself for several months, even though someone in another forum recommended that I voice the issue to Ulead...Corel...whatever.

Shortly after voicing my own concern awhile ago, a solution that I hadn't thought of trying was discovered...but I'm not going to bother sharing it here, given the attitude of the moderators.

I would think that Ulead/Corel would be grateful for any/all feedback from early adopters of an operating system...sooner or later, issues will HAVE to be addressed...but, apparently, that's not the case here.

Have you reported this to the Windows 7 Team at Microsoft?
This is the reason they release the Beta Versions and the release candidate prior to it "Going Live." - To iron out the bugs.

wh5916 wrote:.......
I knew it wouldn't be long before a response like this would surface, which is why I kept the Windows 7 issue to myself for several months, even though someone in another forum recommended that I voice the issue to Ulead...Corel...whatever.

Shortly after voicing my own concern awhile ago, a solution that I hadn't thought of trying was discovered...but I'm not going to bother sharing it here, given the attitude of the moderators.

I would think that Ulead/Corel would be grateful for any/all feedback from early adopters of an operating system...sooner or later, issues will HAVE to be addressed...but, apparently, that's not the case here.

You appear to be unaware of the fact that no one here works for Corel.
We are ALL customers and users of their software just like yourself.
Corel do not monitor these forums - though they do take a look at the "Wish List" posts I have placed at the top of the various forums.

The purpose of this USER to USER Web board is so that we users of the software can share ideas and try and help each other. When someone has a problem it is possible another member of the web board also had that problem and found a cure.

Sorry if you were misled into believing any of us are actually software engineers - we are not.

And I am sorry if I gave the impression that I am cruel and uncaring... I am not. All I was trying to convey was the thought that it is difficult for us as users to know how to fit a round peg like VS into a square hole of a new operating system for which the round peg was never designed... No more and no less than that. I was certainly not intending to put you down or cut-off discussion. If that was your impression, then I am sorry.

given the attitude of the moderators.

Sounds like you're the one with the attitude problem.

but I'm not going to bother sharing it here

I'm taking my ball and going home.