As many of you know, I bought VMS Plat. 10 back in June of 2010. I immediately found out that the program does NOT read Samsung High Def (or even standard def) video properly. The program leaves half second gaps every second.
I contacted Sony tech support immediately and they said they were aware of the issue and that a fix was imminent (again, back in June of 2010). Obviously "imminent" means "whenever we decide to get around to it".
Folks here at the forum have been touting Vegas Pro as the actual fix to VMS 10, so I downloaded Vegas Pro 10(c) and checked it out. Sure enough, Vegas Pro does NOT have the same problem working with the generic Samsung high def codec.
So this brings a few questions to bear:
Did Sony knowingly put out a faulty software program in the hopes that folks would put out a few hundred dollars more for the "upgrade"?
If Vegas Pro is working fine with these "problem codecs", why have they NOT released the simple fix to VMS 10?
While is Vegas Pro is at it's 4th update why is VMS 10 (which was released earlier than Vegas Pro) still awaiting it's first update?
I have supported the Vegas Movie programs as long or longer than anyone here (since Video Factory 1). With this latest version of VMS, I feel like Sony made and is continuing to make a conscience decision to put out a partially working program (works for some but not for others) just to force folks to put out even more cash for their "Premiere" software.
And before anyone responds with, "We don't work for Sony...", please understand that I have contacted Sony repeatedly about this problem with the same response each time, "We'll release an update when we get around to it".
I believe that there are folks at Sony who read these forums and it is my hope that with enough negative response to their lack of good and fair business practices, they may find that it makes sense to fix the broken software that many of us have found ourselves saddled with.
The fact is:
VMS10 does not properly read certain generic codecs while Vegas Pro does. How tough would it be to assign the same "fixes" to a program that is basically all the same code? Why are they holding back?
I contacted Sony tech support immediately and they said they were aware of the issue and that a fix was imminent (again, back in June of 2010). Obviously "imminent" means "whenever we decide to get around to it".
Folks here at the forum have been touting Vegas Pro as the actual fix to VMS 10, so I downloaded Vegas Pro 10(c) and checked it out. Sure enough, Vegas Pro does NOT have the same problem working with the generic Samsung high def codec.
So this brings a few questions to bear:
Did Sony knowingly put out a faulty software program in the hopes that folks would put out a few hundred dollars more for the "upgrade"?
If Vegas Pro is working fine with these "problem codecs", why have they NOT released the simple fix to VMS 10?
While is Vegas Pro is at it's 4th update why is VMS 10 (which was released earlier than Vegas Pro) still awaiting it's first update?
I have supported the Vegas Movie programs as long or longer than anyone here (since Video Factory 1). With this latest version of VMS, I feel like Sony made and is continuing to make a conscience decision to put out a partially working program (works for some but not for others) just to force folks to put out even more cash for their "Premiere" software.
And before anyone responds with, "We don't work for Sony...", please understand that I have contacted Sony repeatedly about this problem with the same response each time, "We'll release an update when we get around to it".
I believe that there are folks at Sony who read these forums and it is my hope that with enough negative response to their lack of good and fair business practices, they may find that it makes sense to fix the broken software that many of us have found ourselves saddled with.
The fact is:
VMS10 does not properly read certain generic codecs while Vegas Pro does. How tough would it be to assign the same "fixes" to a program that is basically all the same code? Why are they holding back?