Is VS10 such a good product?

[LV_426]

As a newcomer to VS10 and a programmer, I am puzzled by the readiness of users to accept excuses such as corrupt files etc. Any well designed program should detect and gracefully handle such situations. Just letting the program crash is indicative of either carelessness or incompetence on the programmers part. Yes it takes extra effort to design a quality program, but my experience has been it pays off in sales. Just take a look at the reviews of VS 10 on Amazon.

Hear Hear! Sadly, I find VS10+ to be - by a LONG stretch - the least stable program I've ever had the misfortune to encounter. I experience crashes, lip-sync errors (of up to a second/25 frames) audio errors on both preview and rendering, failure to render, glitches in chapter indeces on programmes over 1 hour.......the list goes on. And, sadly, it's far, far too easy to "blame" the user's system environment and so on. A well-designed, robust, program will cope. This one doesn't. I have no hesitation in recommending anybody thinking of entering video editing to look elsewhere. ULead doesn't deserve your money.

[Black Lab]

As a newcomer to VS10 and a programmer, I am puzzled by the readiness of users to accept excuses such as corrupt files etc. Any well designed program should detect and gracefully handle such situations. Just letting the program crash is indicative of either carelessness or incompetence on the programmers part. Yes it takes extra effort to design a quality program, but my experience has been it pays off in sales. Just take a look at the reviews of VS 10 on Amazon.

Hear Hear! Sadly, I find VS10+ to be - by a LONG stretch - the least stable program I've ever had the misfortune to encounter. I experience crashes, lip-sync errors (of up to a second/25 frames) audio errors on both preview and rendering, failure to render, glitches in chapter indeces on programmes over 1 hour.......the list goes on. And, sadly, it's far, far too easy to "blame" the user's system environment and so on. A well-designed, robust, program will cope. This one doesn't. I have no hesitation in recommending anybody thinking of entering video editing to look elsewhere. ULead doesn't deserve your money.

I agree with HT. I have none of those problems you mention. We have the same VS10+, but obviously different system environments. So what must be the problem? Hmmm.

[sjj1805]

Hi, H.T.
I agree with you that bugs will always creep in and can be hard to find. My point was that the video editing community seems to accept that frequent crashes just go with the territory. Worse, there is no expectation that the software will check capture device or file compatibility before attempting to use it and then fail gracefully. This culture seems to extend to the ULead folks. I keep finding "workarounds" that warn against using the software in an intuitive way rather than fixing a known problem. If the problem is well enough characterized to post a workaround then it should be repeatable and fixable.
As for the environment, I am running a clean install of Win2000 SP4 on an Intel mother board. I use a removeable hard drive drawer to be able to keep the video/audio editing off the internet with no security software installed. The computer shows no signs of problem using the alternate HD where I run realtime data acquistion software (mine) so the hardware seems reliable.

best,
frank

I too use removable hard drive drawers. Video Editing is very demanding on the computer and as a result can detect a problem that does not show up when using less demanding software. The act of removing and inserting the hard drive drawer can cause the IDE cable to work loose at the back of the caddy.

Visualy the connection appears intact. If you give the connectors a good push with your thumbs you may be surprised to find that suddenly your problems are resolved. This has happened to me a few times and until you discover this 'fault' it can be very frustrating investigating a number of other possible causes.

It's worth giving it a try as you have everything to gain and nothing to lose.

[LV_426]

I agree with HT. I have none of those problems you mention. We have the same VS10+, but obviously different system environments. So what must be the problem? Hmmm.

What must be the problem?

I have used ULead VS v9.
I have used Adobe Premiere Elements 2.0.
I have used an editing program from Serif (doesn't handle DD).
I have used Windows Movie Maker, functionally limited
I have used CyberLink Power Producer also functionally limited.

None of these programs exhibit serious problems - with the same source file types and the same environment. So, what must be the problem?

I say again. In my view vs10+ is not, by a long stretch, a well-written program. A well-written program would cope with whatever it is you believe is "wrong" with my environment - as do all these others.

[Ron P.]

I'll have to agree with H.T. and Blacklab.. and it seems you are missing the point.

If group A and group B all have the same program, Group A has no problems with the program, however group B has been having some problems. The only differences between group A and group B are their systems. Then you are saying that it is the program???? That's ridiculous, because that is identical for both groups. If the program was the cause, then why is it that group A does not have those problems? Remember they have the same identical program as group B.

[sjj1805]

Ron
Very well put and I do not have any problems with my well maintained Windows XP Professional Operating system complete with Service Pack 2.

So how do I keep a well maintained system?
Mostly by use of scheduled tasks that run overnight.
All of my hard drives are in removable hard drive carriers. There are 3 physical hard drives in my computer. At 0400 hrs. The defragmentation programs starts it work.
Monday & Thursday - Drive 1
Tuesday & Friday - Drive 2
Wednesday & Saturday - drive 3

At 0500 hrs each day Spybot Search and Destroy commences its work.
I always have running (24/7) Lavasoft Ad-Watch.

I prevent anything messing with my Windows Registry RUN sections by making them read only

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

Although I have written an article Create a VideoEditing Profile you can also use these same methods to rid your computer of other unwanted start up processes and programs.

The other thing to do is prevent an attack by the worlds most prolific computer virus - the Human Being sitting at the keyboard in front of it.
Create Separate XP user accounts for any members of your family likely to use your computer. Implement any necessary restrictions to their accounts to prevent them messing up your machine.

I can hear lots of people now gasping in horror - other people let loose on Steve's computer!
I would of course prefer it if no one else touched my machine but unfortunately it is located where it acts like a magnet with the most comfortable swivel style armchair in the house. My wife has to do her banking on it plus that crazy bingo game she plays when I am at work.

I can't prevent them from using it so I manage their use.
A question often asked by a number of friends & family is
"Should I turn off my computer at night time?"
The answer to that is simple NO computers are designed to be left turned on at all times. More damage is caused to the computer circuity by powering it up.

Think of it like this - I work for the Police Force. Our many thousands of computers are left turned on permanently (You can of course turn the monitor off). Now supposing someone telephones the Police "Someone is breaking into my house - help" - the Police reply "Sorry chum we can't come tonight we've had to turn all our computers off!"

[CycleWriter]

I prevent anything messing with my Windows Registry RUN sections by making them read only.

Steve, more info on this, please.

The answer to that is simple NO computers are designed to be left turned on at all times. More damage is caused to the computer circuity by powering it up.

I try to tell my family and friends this, but they can't understand. I explain that when a light bulb goes bad, it is rarely after its been on awhile and most often when you turn it on. The electrical surge on startup is often the cause. An already weakened filament can no longer handle the momentary current surge (often more than what the bulb sees while on), and cold electronics respond poorly to sudden voltage spikes. Transistors and ICs are much the same. Over time, they become unstable. Repeated cold off-on cycles weaken them more than if they remained on all the time. And today's energy saving modes that put the computer into sleep while keeping certain electronic components alive draw very little power so it makes more sense to just leave the thing on.

[sjj1805]

The following is an extract from the tutorial:
Create a video editing profile

Step 5. If you have Xp Pro alter the security setting of the [all user run section] to read only.

This is one of the simplest changes you will make to your computer that will also prevent many virus attacks. If you intend to install new software you must however remember to temporarily revert this setting back to read/write.

Navigate to the All User run Section. Then Edit | Permissions



and now simply click each user in the list in turn and set permissions to read only.



Repeat this procedure for the current user run section.

[CycleWriter]

Steve, I already knew how to do that. What I was interested in was your statement that made it appear as though you could make just those two specific registry keys read-only. That would have been a neat trick. Thanks anyway.

[sjj1805]

Doing the above makes them read only.

[PeterMilliken]

Hi Peter,

What I strongly suspect is that ULead don't want to "waste" money on VS fixing "problems" that are long standing and well recognised (such as burning from the timeline). <snip>

<snip>

Whereas fixing a problem such as burning from the timeline (which obviously hasn't affected sales BTW!) would probably require considerable programmer effort and then test effort as well.

ULead obviously follow the same philosophy as Microsoft - if it doesn't affect sales then leave it be.

This is also not true. Ulead welcomes any bug or issue reports and will look forward to get them solved in the update pack (or the next version). However, if Ulead cannot get the response or cannot reproduce the issue then it's hard to solve the issue because you might not know where the problem is.

Again I would say, Ulead welcomes any report about problems and issues and will try to solve them if they can be reproduced in the lab.

Hi H.T.

No wish to start a "war" here , I don't wish to cast aspersions on you or your opinions and I certainly have no doubts that ULead do make best effort at addressing (reproducable) bugs.

But please excuse my scepticism regarding ULead's desire to fix problems when it comes to the "timeline burning" problem. This is a well recognised problem with VS and has (to my knowledge) been present since VS 8 - I assume from postings on this board that it is still present in VS 10.

Now I can easily understand many of the more "one-off" problems that appear on this board not being something that ULead can address - I am a 20+ year programmer after all, so I fully understand the issues involved.

But I will not accept the stance that ULead can't reproduce the "timeline burning" problem if they really tried - this is not a "once off, some weird problem that a single user encountered and nobody has ever seen or heard of again problem", this happens with sufficient frequency that people on this board have been forced to make it a permanent notice and direct all users to it as a first port of call when they have problems.

It is my opinion (:-)) that if ULead really wanted to fix this problem then they could reproduce it and then work out what the problem is - the fact that we have been living with this for 3 versions now leads me to my opinion that "if it doesn't affect sales, then ULead don't care".

I would be extremely happy if you could prove me wrong by ULead fixing this problem!

But in the meantime I won't hold my breath and will maintain the above expressed opinions - your protestations to the contrary, the "evidence" clearly supports my view

Peter

[CycleWriter]

Doing the above makes them read only.

Your steps make the entire registry read-only. That means any program that needs to write to the registry upon shutdown will not be able to save necessary data. While this keeps your system from changing, it is cumbersome, particularly for users who often test trial software like myself. The Run keys are of interest to me mainly because programs like QuickTime and RealPlayer are constantly placing commands there for update apps to run in the background despite repeatedly turning them off using MSCONFIG.EXE or editing the registry directly. The best way I've found to prevent this is to find the actual command file and rename it, i.e., realsched.exe to realsched.ex_. This way, even if the command gets reborn in the Run key, it will be harmless as the program can't run without its proper extension.

[sjj1805]

I think you may have misread my registry tweak. (Not Windows Explorers regedit.exe)
it is only the RUN key that is made read only, not the entire registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

The only times you will notice any difference are

1. when you are on the internet and something tries to hijack your computer and update the RUN section - which of course it can no longer do
2. When you install new software and that software wants to alter the RUN section. It stops and complains - no problem you can open up the registry, temporarily restore the write permissions and continue on with the installation.

I've used this method a few years now.

[CycleWriter]

I think you may have misread my registry tweak. (Not Windows Explorers regedit.exe)
it is only the RUN key that is made read only, not the entire registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

The only times you will notice any difference are

1. when you are on the internet and something tries to hijack your computer and update the RUN section - which of course it can no longer do
2. When you install new software and that software wants to alter the RUN section. It stops and complains - no problem you can open up the registry, temporarily restore the write permissions and continue on with the installation.

I've used this method a few years now.

I don't use XP Pro, so I don't have the option to make just the user Run keys read only. Thanks.

[LV_426]

...it seems you are missing the point.

If group A and group B all have the same program, Group A has no problems with the program, however group B has been having some problems. The only differences between group A and group B are their systems. Then you are saying that it is the program???? That's ridiculous, because that is identical for both groups. If the program was the cause, then why is it that group A does not have those problems? Remember they have the same identical program as group B.

I AM saying it's the program - yes indeed. I don't think I am missing your point at all. I'm just less prepared to "blame" something else when UVS10+ is the only thing I have that misbehaves as it does.

Using your analogy, the program is failing to cope properly with something that's present in Group B's system. I blame the program because, in my case at least, it's the only program that misbehaves to the degree it does.

I mean, for all I know, it could be something like my Epson Printer driver that's conflicting. Suppose for the sake of debate that it is a conflict with Epson. Where, then does the "problem" lie?

If nothing else ever conflicts with Epson, is it Epson's fault - my fault for using Epson - or a bug in UVS? That's my point.

In any case - you can't excuse the number of workrounds that are publised on this very board.........