So - where is VP9.0d ??

Christian de Godzinsky wrote on 1/11/2010, 4:41 AM
Would it not be time already for SCS to publish a new incremental fix for VP9? There are lots of letters in the alphabet... no risk of running out of them even if publishing hot fixes a litte more often...

I cannot use either 9.0c 32 or 64 bit versions (due to long non-responsive periods during editing AND redering). This on my WIN 7 Ultimate 64 bit PC. This IS a recognized problem also reported by others.

VP 8.0c works perfectly but lacks some features that exists in 9.0. It is somewhat irritating not being able to use a paid upgrade! And the version is already c!!!

Yes - I have reinistalled ---- and went through all that stuff. The PC is in mint condition. This is a sw issue. Please SCS, better earlier than later....

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Comments

Rob Franks wrote on 1/11/2010, 5:08 AM
"I cannot use either 9.0c 32 or 64 bit versions (due to long non-responsive periods during editing AND redering). This on my WIN 7 Ultimate 64 bit PC. This IS a recognized problem also reported by others."

Interesting.... I ran into one of those yesterday. (win7 64). 9c had been performing great until that point, but it actually stopped long enough so that I thought it was frozen. I was about to close the program and restart (risking losing my work) when it came back to life again. The freeze had to be at least 30 sec long

A bit irritating.

I can't go back to 8 because the avc encoder is really bad. (they did some major improvement to the avc encoder in 9)

I don't remember this happening in Vista and it just so happens I have a full disk image of Vista 64 (with full software) and I may go back.
David Laine wrote on 1/11/2010, 5:12 AM
Hi Christian

Don't hold your breath you may like me be in for a long wait and even then your problem by not be solved by V9d

I have had a problem with V9 1st version it was admitted by Sony that the problem was in the software.

It was not solved in b or c

sony cust support really sucks and so do some of the Sony fanboys in this forum for who sony can do no wrong with the over priced and buggy world of Vegas editing
Rob Franks wrote on 1/11/2010, 5:31 AM
"sony cust support really sucks and so do some of the Sony fanboys in this forum for who sony can do no wrong with the over priced and buggy world of Vegas editing"

Now was that really necessary? Does it go a long way in solving the problem.... or just make people angry? Admittedly I have not been a part of this forum for very long, but (IMO)... far too many of these unnecessary "goading-type" comments are made.
BudWzr wrote on 1/11/2010, 5:57 AM
Don't throw out the baby with the bath water.

VEGAS, Baby! YYYYeeeeeaaaaahhhhhh!!!!!!!!
David Laine wrote on 1/11/2010, 6:04 AM
Hi Rob

I hope you don't ever have to wait weeks and find sony cannot fix a problem you have with vegas

It is not nice to feel that sony have ripped me off by not fixing a problem and not offering to refund me the large cost of Vegas Pro

It is also not nice to find that another much cheaper NLE can do what Vegas cannot

Tempers do sadly get heated when Sony cust support cannot give a fix time and fanboys here go on about how great sony and Vegas is
TheHappyFriar wrote on 1/11/2010, 8:00 AM
no tech/customer support is perfect. SMS is lightyears better then most.
Christian de Godzinsky wrote on 1/11/2010, 8:16 AM
For sure I'm not holding my breath... my face would have turned from blue to white - already a long time ago ...

Mildly put - nonresponsiveness in ANY application is frustrating. It is especially bad when you use a "pro" software - professionally. Try to explain to your editing client that now we have to wait - again...and again... I have done it - now too many times - it is NOT funny at all. The next question that I get is: "why do you then edit on Vegas ?"... My answer: "Because I like it..". This is really starting to resemble a a "love-hate" affair.... I mean - working withthe VP9.0c.

I understand people's need to let out steam (I'll do it occasionally myself), but here again - the golden rule to count to ten (thousand or more), helps...

I want to use 9.0c because of the better AVCHD codces, better preview of HD on the timeline - and yes, among some other very valid reasons. One being that I have PAID for the extra features, and should assume that they already work in version c!!!

I am puzzled how many people see VP9.0c (or earlier versions of 9) hanging of freezing, without knowing what is really wrong. I hope these people all report to SCS. There seems to be onevery common nominator to this problem, that is - Vegas 9.0c, and probably WIN 7. Useless to look anywhere else, VP9.0c IS advertized to be WIN7 compatible...

I love the Vegas GUI and it's functionality. I'm not a fanboy in any sense, but I really like this program (at least all the parts of it - that works :). I don't edit on anything else - but sometimes I wonder if I should start to reconsider... Blind love is not good in the long run...

I am slowly starting to wonder about why SCS seems to neglect us users? Is it the bad economy that also causes Sony to cut on R&D resources, or reorganize the eggs in other baskets that gives a better profit? There are SO many pinpointed issues that waits to be repaired.

Take for example the HDV-capture problem. The scene detection function has been broken since at least VP7, and SCS has done NOTHING to fix it. I repeat - NOTHING!!! Is this neglectance - or what?

Anyhow - the scene detection is advertized as a feature, SCS just forgets to mention that you have manually cut from both ends from every clip, to make them usable.... Do we have to live with this - forewer? Is sadly seems so.... This is one thing that I will never accept, neither understand.

I want to keep this discussion clean, so just stick to the facts as we know it (simply report your real repeatable problems). I might already have stepped over the line with this post, since you can easily read my frustration, if not directly but at least between the lines. But I AM really frustrated.

SCS must be occasionally also be reading this forum, so our posts should here also have some kind of "impact". Even better (don't be lazy) - rise a "ticket" with the SCS support, as often you feel suitable!

I still think SCS should release bug fixes more often, since there are so many things that needs to be fixed. Some albeit small but irritating when they occur repeatedly. But you can live with them or work-around them. Some are bigger issues that are real showstoppers - as this non-responsitivity for periods up to more than one minute...

How would you feel if your text editor behaved the same? HOwever, such a thing would be easy to solve, there are many good and gratis alternatives, even with zero learning curves...

Im' fully aware of the fact that SCS releasing 9.0d is not a guarantee to bring a solution for the hangs, but I think that SCS cannot afford NOT to fix it - and ASAP!!!


Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

daryl wrote on 1/11/2010, 12:19 PM
"Software issue" or not, I am running 9c on a Win 7 ultimate system, both 32 and 64 bit, perfectly, not a problem to slow me down since building the new machine and loading it up.
Coming from a programming background, believe me, I know that no matter how "bullet-proof" you think your app is, it's NOT going to run on every machine out there.
Since 9c does seem to run very well on a LOT(if not most) of Vegas user's machines, there may be something slightly different in the configuration (hardware or system) on the ones that don't work well.
Maybe some of us that are having problems that others are not should do some trouble shooting of our own. If a solution is found, share it. If not, let SCS continue looking.
A. Grandt wrote on 1/11/2010, 12:46 PM
Interestingly I have seen the same temporary freeze in other applications on Win7 64 bit.
Most of the time (but far from all) have been when Win7 have failed in getting a sleeping HDD back on-line. It just freezes everything, and after 20+ seconds, you finally hear the HDD spin up. It is rare, but happens enough to have taken note of it.

The times I've seen it in Vegas have been because it was waiting for the HDD to spin back up.

The other times I have no idea what is going on, everything just freezes inexplicably.
dcrandall wrote on 1/11/2010, 1:47 PM
Has everybody who has experienced these intermittent freeze problems checked to see if their motherboard drivers have been updated for the version of Windows they are running under? (I believe there is another recent Discussion Thread that references this) I recently purchased a i7-860 computer loaded with Windows 7 Home Premium 64-bit. I loaded Vegas Pro 9.0c 64-bit and I soon after, experienced a freeze.... I then went to the Intel website, found and installed updated Windows 7 64-bit chipset drivers for my motherboard ..... I haven't experienced a freeze since! Maybe it's a coincidence, but it's worth checking.
-Dan
  • Velocity Micro Z55 Desktop Computer
  • ASUS Prime Z270M-Plus Motherboard
  • Intel(R) Core(TM) i7-7700K CPU @ 4.2GHz
  • Memory: 16GB DDR4-2400MHz
  • 4GB NVIDIA GeForce GTX 1050 Ti Driver Version: Studio Driver 452.06
  • Windows 10 Home 64bit v1909
  • Vegas Pro 18.0 Build 284
farss wrote on 1/11/2010, 1:58 PM
"There seems to be onevery common nominator to this problem, that is - Vegas 9.0c, and probably WIN 7. Useless to look anywhere else, VP9.0c IS advertized to be WIN7 compatible..."

I could reproduce your issues with V9.0b and they remain after switching to V9.0c, all under WinXP. I can skirt around them for most of the work that I need to do, at the moment.

Bob.
Rob Franks wrote on 1/11/2010, 1:58 PM
"I hope you don't ever have to wait weeks and find sony cannot fix a problem you have with vegas"

So what does this have to do with making other people angry?? Very sorry your having issues, but is that the forum users' fault? I just don't get people who come on here saying.... sony sucks and F-off fanboys....blah, blah blah. What have the forum members (myself included) done to deserve such ill thought???

Comments like this David in my opinion are just simply better left OFF the board because the ONLY thing they can do are bad things. There is not a single shred of good that can happen with them.
ushere wrote on 1/11/2010, 4:24 PM
Most of the time (but far from all) have been when Win7 have failed in getting a sleeping HDD back on-line. It just freezes everything, and after 20+ seconds, you finally hear the HDD spin up. It is rare, but happens enough to have taken note of it.

The times I've seen it in Vegas have been because it was waiting for the HDD to spin back up.

ditto. i went to power management and set NEVER turn off hd's. so far, no more freezes.

leslie

btw. i think it's set for 20 minutes default
Rob Franks wrote on 1/11/2010, 8:40 PM
"ditto. i went to power management and set NEVER turn off hd's."

I have 5 hard drives and have already made that adjustment. I STILL have 3 hard drives that continue to spin down (although not the win 7 drive). I wonder if there is some sort of software switch on the hard drives themselves?
CorTed wrote on 1/11/2010, 9:13 PM
USB drives are desinged to do that on their own
A. Grandt wrote on 1/11/2010, 10:14 PM
Rob Franks

There are. It is not something you can easily update though.
In Linux there is an application called hdparm (?) to manage these switches, including spin down time, however that kind of low level tampering with performance parameters could also brick the hard disk.
Rob Franks wrote on 1/12/2010, 4:42 AM
"USB drives are desinged to do that on their own "

I don't have any usb drives. They're all internal sata
Rob Franks wrote on 1/12/2010, 4:43 AM
"There are. It is not something you can easily update though."

Thanks. I think I would rather live with the spin down than risk bricking a drive!
JJKizak wrote on 1/12/2010, 4:53 AM
Judging from Sony's latest NAMM blurb they are emphasizing Acid Pro and not saying anything about Cinescore being replaced.
JJK
pavlas_petr@centrum.cz wrote on 1/12/2010, 7:26 AM
I have exactly the same problems - freezing. No one succesfull rendering into MPEG2SD. 720/50P, 1080i are OK. I also have the win7, 64 bit.
Christian de Godzinsky wrote on 1/12/2010, 9:06 AM
Same here, problems with freezing in 9.0c mainly when rendering to SD.

I have to emphasize that 8.0c works fine in this respect (no freezing) on the same PC!!!

I have additionally to emphasize that the freezing has nothing to do with hard-disk spindowns, all disks involde are internal SATA disks set to continuous operation.

Please SCS, release a fix soon!

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Wadro65 wrote on 1/13/2010, 2:33 PM
I also have internal sata drives that go to sleep no matter what I set them at. So I found a great program to fix the problem. It's called HDrive awake. I just start it before editing and it keeps all the drives awake. here is the link. It's small 1mb

http://download.cnet.com/HDrive-Awake/3000-2248_4-168361.html
Christian de Godzinsky wrote on 1/28/2010, 6:56 AM
I think that this post deserves a BUMP.

At least to inform users that the long non-responsive periods in Vegas might be caused because of an error in the external preview (via firewire). Just search the forum and you will find this post and a work-around.

And because that we need soon a release of 9.0d due to so many other recognized issues. When could that be? Personally I am not holding my breath, but I'm holding back two bigger projects in the hope to get these things fixed...

Christian

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

reberclark wrote on 1/28/2010, 7:11 AM
I am holding back a new i7 machine purchase (with windows 7) until things like this get a work-around or get resolved.