Funny, Ain't It

[David Latta]

Dan,

Over in West Australia they have just opened a plant. Knocked it up in quick time. Here in South Oz they are looking at a closed down oil refinary at Port Stanvac to see if that can be converted. Big bucks though and the State Government here is not as progressive as those in other states. We live in hope.

David

[PeterMilliken]

My apologies, but I fall into a similar/same category to Jeff.

The item that gets up my nose is the outright denial that if you get an error when following the "burn direct to DVD" approach that it isn't a BUG - of course it is a bug. And the evidence from posts to this board and the previous version of the forum confirms that it has occured for multiple users - as I said in an earlier post, I encountered it twice before I shifted to the "recommended procedure".

As HT states, it is an acceptable work around to use the "recommended procedure" - the term "work around" is (generally) accepted terminology for "yes, the software doesn't (always) work as we advertise but you achieve the desired outcome by using this particular alternative approach".

Obviously the term "bug" causes all sorts of heartache to some people on this board - I can understand whatever his name is wanting to deny there exists a problem because his job may or may not be affected by any negative publicity.

But the facts speak for themselves - just because somebody hasn't personally experienced the bug (sorry, to use HT's terminology "issue") doesn't mean that it doesn't exist. The software industry in general is famous for a "head in the sand" approach - this is just one more occurrence - IMO

From the Wikipedia:

A software bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (e.g., producing an incorrect result).

There is plenty of evidence that people who use the "burn direct to disk" approach have experienced a failure in VS 8 - 10 producing a DVD i.e. it didn't produce the "correct result" - so by definition, there is a "bug" in VS. Some people, because they haven't personally experienced the "issue" would like to suggest that it is a failure in the users system and ULead can't be responsible for every possible system configuration problem out there in the real world - again, this is possibly an acceptable approach, although I would argue:

(a) if it was a computer system issue then it would be much more repeatable than it has been in my experience (I produced about 10 DVD's before I first "stubbed my toe" on this "issue").

(b) what have ULead done to prove that it is a system setup issue? And if so, what have they done to warn users that some aspect (ULead should be able to identify/quantify what the issue is!) of their system setup could adversely affect the operation of VS when producing a DVD. At the very least, the manual for VS 10 should include a warning acknowledging that VS doesn't always produce a disk when using the "direct burn" approach and they should document the alternative approach to save users from having to even come to this forum!!! I know several people who use VS who have never even considered looking for this forum! They mentioned their problems to me and I helped them fix it, so the user's manual should mention this "alternative procedure" as the very least in its troubleshooting section!

Personally, because you can "work around" it, I don't (normally) consider it a "serious" bug - until you look at the fact that it has existed in VS 8, 9 and 10 with no apparent effort on ULeads part to fix it - well, no evidence I have seen. So given this, I then move it from the category of "annoying" to "serious".

Peter

[daniel]

I think Belgians are culturally incapable of looking beyond clichees :lol:

Hope you don't take offence to this because non was intended. :lol:

None at all, I just see I forgot to scatter a few smileys.

All europeans indeed appreciate the climate we benefit, and understand the difficulties of dry areas especially at the end of (your) summer.

But occasionally you'll hear a belgian, briton or a french from Brittany complaining foolishly after the second month of continuous rain. Lucky us.
With what do you think we produce the millions of cubic meters of beer every year? With the water coming from the oceans around YOU, that falls on our heads.

What is more of a surprise is to read a Canberran complaining about rain.
Ken feel free to take whatever water you wish, providing it fits into a transparent, 20cc bottle or you don't get past airport control...

[sjj1805]

PeterMilliken
You are missing the point.
The 'Recommended Procedure' gave the appearance that it was written by Ulead. It was stuck at the top of the VideoStudio Forum and the title would give the impression it was something official.

In fact it was the work of a customer.

The general gist of the post was invaluable - providing new users with a work flow that they could follow in order to create a DVD from their camcorder.
If you have ever tried one of the competitors products you will soon realise the benefit of such a post.

The problem was that the customer concerned - Mr Hunter - tended to suggest that failure to follow HIS procedure WOULD result in bugs, flaws or whatever else you may care to call problems.

Whether you take the opinion or not that bugs or flaws do or do not exist is not the issue. The issue is that it became an advertisement - stuck at the very top of the VideoStudio thread which could be interpreted as
"Welcome to the World of Ulead - although this program has a bug or flaw there is no need to be concerned because we have a work round."

Whilst I sympathise with members who encounter problems when using their software, the point remains that the allegation is unproven, could not be replicated by Ulead - who if such a problem did exist would have taken steps to rectify it. The so called problem did not affect the mass majority of users but a small minority - and those users may have encountered problems for a variety of reasons - the most usual of which is a corrupt video file.

Now compare the stance taken by Mr Hunter with this extract taken from
Suggested workflow by SJJ1805 for Video Creation

Failing to follow this or any other suggested workflow will not mean that a bolt of lightening will come shooting out of the sky and fry you and your computer. Experiment and find a workflow that works for you. This work flow works for me and follows a logical set of steps and provides me with a good result. It does not imply that you cannot do things in a different manner.

[rdenny]

A classic case of a software "old wives' tale".