I, too, would like to see the problem fixed! I am tired of Sony moving on to 'greater' improvements without fixing the old problems.

Bob
(Versions: 3,4,5,6,8,9,10)

Sticking with 10. I loaded 11 and it fired up like a dud skyrocket. this shouldn’t be rocket science? point the top toward the sky and light the bottom end.

I wish they would add sync to cursor in Pro Type Titler. In pro 10 but that isn’t happening.

please guys fix 10

Hear hear! This bug is now severely affecting my work.

Nick Hope

Absolutely count me in!!

While I am using V11-511 some, I don't like the way you have to go about stabilization in V11.
It was so much easier to work with in V10 that I will definitely be working in V10 quite a bit and don't want to get bit by the nasty replacement bug.

I'm not using 11, it is just too buggy. 10 is not much better if you want to use an external monitor.

I want the media replace and external monitor crashes fixed in 10.

If I never turn on ext mon to my Black Magic Intensity Shuttle, 10 doesn't crash too often, you can actually get some work done. If you turn it on even once, the next time you save to a new file it will crash. And don't think about using magic bullet with the external monitor. Vegas will crash as soon as you close Magic Bullet and save the vegas file.

It's happened to me too many times so count me in.
Randy Brown (versions 4,5, 8 and 10)

Count me in although I'd prefer it be fixed in V9 as V10 introduced another set of bugs that were never fixed either as noted by someone above.

Bob,
V4,5,6,7,8,9,10.11.

Please Sony..if you figured it out in 11...come on man!

+1

A known bug should be fixed. By fixing this bug, Sony would help to restore some goodwill that was lost to those of us who paid for v11 and have reverted to v10 out of necessity and perhaps help keep some from jumping ship altogether.

1 vote here too.
Although I already own VegasPro11 (to take advantage of earlybird discount.....) I am not moving to Win7 for some time yet as there are not Win7 drivers for some of my existing hardware; must stay with WinXPpro; therefore imperative that VegasPro10 works correctly as advertised - that's what I paid for!

thats the problem, working on a new version before they have a decent current version..worse each release,

I agree with ChristoC...and others. I have been a fan of Vegas since my first use in Version 3. However, it seems that every new version comes with its own set of issues, some are fixed and some not. The ones that are not, are perpetuated on version after version. I have never had any big show stopping issues with Vegas but it is getting to the point where the bugs that are carried over from one release to the other are beginning to add up and diminish the appeal of the product.

But, be honest...Sony is never going to spend one minute on an older version no matter how many complain. I too bought V11 to take advantage of the discount and actually have it on my XP machine (but Sony made sure I couldn't update it when they found out it could be installed on XP), so I'm afraid it may just be my last trip to Vegas. The slot machines are not being good to me anymore.

Kent

sort of strange reading this thread - i loved windows 2000, so could m$ please update it so the few bugs that were there get sorted out? i think not...

frankly i reckon scs should just simply buckle down and clean up 11 before even dreaming of doing anything else, and by that i mean clean up the KNOWN bugs, along with sorting out the ram preview anomalies.

the truth is i've found 11 perfectly adequate for my purposes, but with it's rocky start i'm not likely to think about buying again unless scs sorts 11 out.

frankly i'm tiring of extra features when existing ones don't function as they should, or are changed for some reason to quite illogical purposes, eg, stabilisation. i'm sure there's a few people using 3d, but to be honest i think it was a complete waste of resources relative to the vast majority of users who NEED a reliable, robust and dependable nle for their businesses.

btw. i'm not knocking the 3d aspect, just that it seems more a marketing gimmick rather than a money earner for professional editors like myself (by pro i mean i make my living from video production).

The point is, if Sony have really fixed this in V11, then it's a pretty good bet that the changes in the code they have made could be fairly easily ported back to V10, and a 10.0f version released without taking up much time or resources.

If we're talking about a fairly minor bug then fair enough, don't bother, but in this case we're talking about an absolute nightmare of a bug. Leaving this in the wild, even on an old version, can only do Sony's reputation harm, especially as it's an old version that many people are forced to keep using because of instability in the new version.

There's also a potential litigation issue that Sony might want to protect themselves against. Let's say someone loses a $$$ contract because their presentation contains clips of their kids opening their Christmas presents instead of whatever...

Making a perfect version 11 is not going to help those who choose to stay with Win XP for whatever reasons.

When Adobe brought out Premiere CS5, which only worked on 64 bit Windows, they also bundled CS4 32 bit. Perhaps Sony should bundle version 10 with version 11 for the same reason, and if they are bundling it, why not keep it up to date?

"Software flows through a diode. It can only go in one direction and that direction is forward!"

I'd suggest you learn something about how software is written today, spaghetti code went out along with Spaghetti Westerns.


Bob.

Money (and resources) is the bottom line. Customer satisfaction only comes into play when that satisfaction (or lack of) interferes with the bottom line. This is especially true with larger companies.

I totally agree that this bug should be fixed, but unfortunately from Sony's POV it just wouldn't be cost effective. And not fixing it in version 10 probably won't adversely effect their bottom line. In fact, by fixing the bug ONLY in V11, will probably greatly increase their overall profits. Eventually.

Leee - the realest

Hah ! Wrong thread . . .oops . .

- g

Just jossing . .


" . . . went out along with Spaghetti Westerns"

And wrong again, Bob!

Oo-wee Oowee oooo,
Dang Dang Dang
Oo-wee Oowee oooo,
Dang Dang Dung

Oo-wee Oowee oooo,
Dang Dang Ding
Oo-wee Oowee oooo,
Dang Dung-along
Oo-wee Oowee oooo,
Dang Ding


Now, how on Earth could THAT be ever passe?? Teh, the cheek of it.

- g

This is how

http://www.spaghetti-western.net/index.php/Quentin_Tarantino's_Top_20_favorite_Spaghetti_Westerns

Quentin Tarantino = Italian American.

Vidmus said: "Since much of the code for Vegas 11 was re-written for GPU usage, it is highly unlikely that the code could easily be ported back to V10."

You might be right. Or it might be that the fix is in a single line of code that is completely unrelated to the new GPU stuff. Only the programmers can know that.

Releasing updates to old versions of software is common. Microsoft are still supplying me with updates to Windows XP, which is 2 major releases old now. Mozilla is still supplying me with updates to Firefox 3, which is 6 major releases old. Acronis released updates to old versions of True Image, because there were serious bugs, even though newer versions were already out. GP Sortware release updates to old versions of Directory Opus etc..

I am in as well.

In addition I'd like to see the timeline sync issue fixed for which I submitted a bug report about a year ago. Basically when zoomed in the timeline will not accurately represent the audio being played. I do quite a bit of musical event moving around and that's when this issue occurs. It happens in 9 and 10 but not 8. It happens after a few minutes of editing.

- Mark
Vegas user since Version 3.