WE the people, in search of a more perfect V10...

i am erikd wrote on 12/28/2011, 9:48 AM
I want to start this thread by adding my name as one of the first (and encourage others too) to officially request Sony for a 10f release for the specific purpose of fixing the "replaced footage" bug. Granted we may have to wait awhile yet as we still don't know for sure that the bug was fixed in V11 but so far so good...no one has reported the problem in V11.

For those who would like for Sony to release 10f please sign below.
Please, add your name only if this matter is of high importance to you.

Erik Davis
User since 2007, Owner 2 Seats V8, V9; 1 Seat V10, V11

The list so far:

Nick Hope
Bob Moyer
Rory Cooper
Randy Brown
Alf Hanna
Radio Guy
Steve Rhoden
paul w
Don Sweger
Dan Sherman


amendegw wrote on 12/28/2011, 10:11 AM
Well, it's not of "high importance" to me as it only happened to me once on Vegas 10 and I'm now on Vegas 11, but I think a fixed 10.0f would be a good idea.


System Model: Alienware Area-51m R2
System: Windows 11 Home
Processor: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz, 3792 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Memory: 64.0 GB
Display Adapter: NVIDIA GeForce RTX 2070 Super (8GB), Nvidia Studio Driver 527.56 Dec 2022)
Overclock Off

Display: 1920x1080 144 hertz
Storage (12TB Total):
OS Drive: PM981a NVMe SAMSUNG 2048GB
Data Drive1: Samsung SSD 970 EVO Plus 2TB
Data Drive2: Samsung SSD 870 QVO 8TB

USB: Thunderbolt 3 (USB Type-C) port Supports USB 3.2 Gen 2, DisplayPort 1.2, Thunderbolt 3

Canon R5
Canon R3
Sony A9

BobMoyer wrote on 12/28/2011, 10:24 AM
I, too, would like to see the problem fixed! I am tired of Sony moving on to 'greater' improvements without fixing the old problems.

(Versions: 3,4,5,6,8,9,10)
Rory Cooper wrote on 12/28/2011, 10:38 AM
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
NickHope wrote on 12/28/2011, 11:00 AM
Hear hear! This bug is now severely affecting my work.

Nick Hope
jimsch wrote on 12/28/2011, 11:19 AM
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.
R0cky wrote on 12/28/2011, 12:18 PM
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.
Randy Brown wrote on 12/28/2011, 1:36 PM
It's happened to me too many times so count me in.
Randy Brown (versions 4,5, 8 and 10)
farss wrote on 12/28/2011, 2:20 PM
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.

winrockpost wrote on 12/28/2011, 3:22 PM
Please Sony..if you figured it out in 11...come on man!
JasonATL wrote on 12/28/2011, 3:41 PM

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.
ChristoC wrote on 12/28/2011, 3:53 PM
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!
winrockpost wrote on 12/28/2011, 6:52 PM
thats the problem, working on a new version before they have a decent current version..worse each release,
Opampman wrote on 12/28/2011, 8:08 PM
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.

ushere wrote on 12/29/2011, 12:01 AM
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).
NickHope wrote on 12/29/2011, 12:37 AM
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...
PeterDuke wrote on 12/29/2011, 2:09 AM
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?
farss wrote on 12/29/2011, 4:10 AM
"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.

Leee wrote on 12/29/2011, 4:32 AM
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
Grazie wrote on 12/29/2011, 4:36 AM
Hah ! Wrong thread . . .oops . .

- g
Grazie wrote on 12/29/2011, 4:38 AM
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

Rory Cooper wrote on 12/29/2011, 5:17 AM
This is how


Quentin Tarantino = Italian American.
NickHope wrote on 12/29/2011, 8:31 AM
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..
Hulk wrote on 12/29/2011, 9:28 AM
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.
kairosmatt wrote on 12/29/2011, 9:37 AM
+1 on fixing ten, whether its spaghetti code or not (I don't even know what that means).

As to spaghetti westerns going out of style-never! I've seen all things Leone but that list is gonna give my Netflix queue a shuffle!