IT'S HERE!!!!

Devil · Post by **Devil** » Fri May 05, 2006 12:10 pm

http://activity.ulead.com/us/events/msp8_sp1/runme.htm

Don Smith · Post by **Don Smith** » Fri May 05, 2006 12:34 pm

So if you can't uninstall the SP, can you uninstall and then reinstall MSP8? What "stays" and what do you need to "clean out" to get a good reinstall if needed?

Devil · Post by **Devil** » Fri May 05, 2006 1:00 pm

It is ulikely to be needed, but uninstalling 8.1 will allow you to re-install 8.0.

Devil · Post by **Devil** » Fri May 05, 2006 1:56 pm

As you can see, 7 new features and >30 fixes!

Don Smith · Post by **Don Smith** » Fri May 05, 2006 2:56 pm

Yes, I see. Just took the plunge. I'll check it out soon. Thanks for the reply.

rwernyei · Post by **rwernyei** » Fri May 05, 2006 6:55 pm

Yes, I see its here and it also comes with a disclaimer. As much trouble MSP7's SP2 was for instability, crashing systems, video capture module disappearing, initialization freezes, audio filters, directx, etc... I guess this was bound to happen. Nice use of CYA, Ulead. Fortunately, I still use MSP7 regularly and have a testing workstation to try SP1 on my ESD version of MSP8.

tv_news_guy · Post by **tv_news_guy** » Sat May 06, 2006 6:53 pm

HEY DEVIL AND STEVE J & THE OTHER WISER HEADS HERE,

First let me say I installed the beta update on one of my systems and all seems good. Imported a huge project. Messed around with it.. etc... so far so good.

Now let me say how stupid this update made me feel. After I installed it I read the included fixes.. and number 11 made me gag.

When you saved a project that contained mask overlay, the project would be corrupted etc.....

Just two weeks ago.. I fought with this for hours. Never figured it was a bug... kept corrupting over and over. Without ever figuring it out.. I finshed the project after changing the overlays I was using.

That brings me to my point, and I would be glad to help. Is there a way we can put a sticky up top of the web forum with know issues that have yet to be resolved. I know its not a huge problem, but I for one would read it and hopefully realize a way around a problem.

Just my 2 centavos worth.

Bill tv_news_guy
Non linear editing is half art/half brain damage

sjj1805 · Post by **sjj1805** » Sat May 06, 2006 7:52 pm

There could be some merit in having a thread of known bugs which might also be useful for ulead to check every now and again.
Before setting any up can I seek the views of the other moderators & Devil, Brian, Ken, Ron, MD etc - such a thread may also be misused and users may post what they consider to be a bug, when in fact it isn't.

Also should such a thread be a "one for all products" or seperate threads for different products. ie one for VideoStudio, another for MediaStudio another for PhotoImpact etc.

Another thought, we would seem to require a simple format:
Heading
Details of the issue goes here....

We would also need to avoid such a thread becoming a discussion otherwise I can already see several pages growing and the "Bug List" suddenly losing the purpose for which it was intended.

Thoughts please...

Post by **Ron P.** » Sat May 06, 2006 10:49 pm

Hi,

Even though my name is Ron, and even though I'm not a moderator, I thought I would try to add some input along the Bug Thread/Forum line. I think this is a great idea. It would work if Ulead would have at least one developer monitor the forum.

If anyone has or does visit Swishzone's forum, they have a Bug Forum setup. It works real well. The way they operate is based on the public being Beta testers. They will release a beta version of their software, and when you think you have found a bug, it is reported on the forum. It is monitored closely by their developers. The bug must be able to be reproduced to be considered as a fixable bug. You're also required to post a copy of the working file, to be examined. However that is much easier with that type of program, file sizes are generally less then 1 meg.

I think that the moderator(s) should have some control over the posts. If a person posts an issue that is not a bug, then the post is moved from the bug forum to the appropriate forum. For example if I would post a problem that I felt was a bug, and it turns out that I just wasn't performing a task correctly, then the post would be moved...

Anyway a long winded way of saying yes I think it is a great idea!!

Ron P.

tv_news_guy · Post by **tv_news_guy** » Sat May 06, 2006 11:03 pm

Just to respond to Steve and Ron. I agree, there would have to be someone monitoring the thread to move out reported bugs that did turn out to be operator error or (did not read the flippin manual). That said.. I want to suggest this should be for Mediastudio Pro stuff only. It would be pertinant to what we need... and if the other products like the idea... then maybe one of their mods can do the same thing in the appropriate forums. I would keep it from being full of things that would not apply and would make it a toughie to verify reports of bugs if multiple products were involved.
Again.. if I can help.. just yell.

Bill tv_news_guy
non-linear editing is half art/half brain damage

sjj1805 · Post by **sjj1805** » Sat May 06, 2006 11:08 pm

Thanks Ron, Perhaps I should have said "Vidoman" but in fact you are the "Ron" I was requesting an opinion from. In fact all of the regular 'troubleshooters' of the forum - (there are too many to name individually)

Devil · Post by **Devil** » Sun May 07, 2006 6:43 am

Good idea but it should be a sticky thread that only the moderator(s) can add to: no discussion. The input can be culled from anyone sending their submissions by either PM or publicly AND confirmed by at least one of the more knowledgeable members (most "bugs" are actually hardware/system-specific and will not qualify, unless traced to the cause). Workarounds may be included. There should be either separate lists for versions or separate threads (e.g., MSP7 and MSP8). It may also be useful to have sections for the type of bug (e.g., VE, VC, AE, etc.)

I would suggest that one for MSP8 not be started until after the release version of SP1 is available in a little less than 3 weeks.

I think it would be a good idea to have a template for reporting. I would suggest something like the non-definitive following (this is a genuine example, but it may be sorted in SP1, so should not be considered gospel until its release):

Software version: MSP8
Build: All
Symptom: Tooltips on icons display incorrectly
Known OS: WinXP SP0-2
Known hardware dependence: Matrox G-550 graphics card
Known sequence of events to provoke bug: Dual-head operation
Details: The tooltips displayed do not relate to the icons, but to another icon. This may be either a neighbouring icon or one which was last accessed.
Cause: This happens only when in dual-screen mode and is probably a function of how the layers are controlled.
Workaround: Switch to single-screen operation while this is bothersome.
Remarks: This may possibly occur with other Matrox models or with other dual-head graphics cards.

Just an idea... Feel free to modify it.

mmponline · Post by **mmponline** » Mon May 08, 2006 6:11 am

I totally agree with this. I also spent hours on crashes, etc. only now to find out it was (mostly) bugs. It would be great if wecan visit a central place to find possible problems (and workarounds) for problems. I'm sure it would take a lot of frustration from people. I have no problem with faulty software, but to wait months for the fixes is just not on. If known bugs are listed, the workarounds can save us lots of time. And yes, I agree that it should be moderated to ensure that it's kept "clean and simple".

Some more suggestions:
1. Is it not possible to split different versions as well. Eg. MSP7 & MSP8 in seperate forus. It would make it easier for people like me - and others- that would now finally (after the SP) greet MSP7.
2. Concerning the SP. Will there be a newsletter, e-mail, whatever that will go out to MSP8 users to inform them of the SP. Poor people might work forever with the bugs. So far the SP looks promising! Sure there is some database of MSP8 users out there.

Helge · Post by **Helge** » Mon May 08, 2006 5:23 pm

I also wished to have such a list of known bugs available. I first thought we could start this with our experiances of the sp. So we could also avoid reporting the same bug twice. But maybe Ulead "measures" the importance of a bug by counting how often it is reported. Such a web board needs also some organisation and preparation.

One other thing is how would we know which bugs are known? There are more forums than this and bugs can also be reported directly to Ulead. So I believe that its Ulead which had to puplish the error database. But this is a decision which must take Ulead. Very few companies puplish their error database fearing that they could loose customers if the numbers of bugs would be known.
MS puplishes the known errors of their products - you can see it at msdn.microsoft.com or order a dvd which comes quarterly. It has also a good search function (like google). I once thought I would read allways the list of knew bugs of windows and the development environments so avoiding to loose time during software development. (Looks familar - eh?) But I quickly discovered that I wouldnt be able to do anything else if I would do that.

Ok, hope Uleads products contain fewer bugs

spurrymoses · Post by **spurrymoses** » Tue May 09, 2006 3:53 am

I must admit, I'm still hoping some of the things raised in Charlie Hills' Getting Results with MediaStudio Pro book will be in SP1.

Given that Ulead are championing the book, I thought they'd be really keen to jump on some of the big criticisms.

The main thing that comes to mind is the use of multi time lines, where the time line's ruler, scale, view and position apply to all timelines (see page 360) Charlie mentions that he hopes that it would be fixed by SP1...

I didn't realise how funny this was in practice until I had a situation to actually use it in my own project.

Any chance of a 'Charlie Hill's Book Bug List'

Alludo USER to USER Web Board

IT'S HERE!!!!

IT'S HERE!!!!

Can't Uninstall??

re: Update

Thanks Steve J and Vidoman