X3 - Microsoft visual c++ runtime library - error

[sging2]

I have been trailing the new x3 but in the past few days - Microsoft visual c++ runtime library - comes up on opening the programme. If I restart its ok.

Is anyone else having this problem. I was just about to the upgrade from x2 as this version seems to have fixed the AVCHD problems I was having. Annoying though I have to pay again to get a fix.

Stephen :

[Ron P.]

Try downloading and installing MS Visual C++ Redistributable Package from Microsoft's website.

[Roberto]

I got the same error message one time... I will try Ron's suggestion.
In addition, I also experienced some randomly happening "null-pointer" messages (tipical run-time bug in SW), specially when working with smartsound.
The general feeling is that VS X3 is not 100% stable.
Everytime a crash happens, a report is sent to Corel: I hope they will use and improve the product robustness.

[Ron P.]

I do think they are doing just that. Wouldn't it be nice to have a developer or two from Avid Liquid Edition or say Edius/Canopus working for Corel?

[sging2]

Hi Ron

Thanks for that info I'll let you know if it works.

I've bought Videostudio from about version 4 but the last three versions have been plagued with little niggly problems. I hope they take note and patch this one quickly and not bring out yet another version to make us pay for the fixes.
I havent long bought x2 but I just couldnt get it to behave with the AVCHD format which they seem to have fixed in this version as it is fine, but did they bring that patch out for x2!!!!!!!

Steve

[Ron P.]

I too think that the AVCHD issue should have been released in a patch for VS X2, and for all we know they may have thought that. However during that time period, if you done a little research, you would have found out that Corel was in real financial straits. All shareholders had to sell off their remaining stocks to Vector Capitol. Prior to that, Corel had Microsoft stock, that they had to sell. I think things were in limbo until the finances were settled.

Generally when they release a new version, the team starts up with the next. No problem, to write patches for the existing one, except when the above happens. I know that there were several ex-ulead personnel let-go. In those circumstances they have to be selfish, and think of the company first. So if a fix was in the works, it probably had to be tabled until the next version.

I do know that things are looking up for them now, and would not be surprised if there is a patch released within the next couple of months.