VP9.0c (32) on W7x64.. long nonresponsive periods?

Christian de Godzinsky wrote on 11/14/2009, 7:08 AM

Hi,

I recently uploaded and installed VP9.0c over VP9.0b (both 32 and 64 bit). This upgrade might have fixed a lot of probmes, but causes for me a new headache:

VP9.0c (32bit) goes non-responsive for long periods, and then returns back to normal operation for a while. During these "dead periods" other applications work normally. All other applications work normally. There is NO extra CPU activity during these non-responsive periods, that can last for a minute or so. This behavious is evidetn even during rendering. The render runs (remaining and elapsed time are counting) but the frame advancing has stopped. Then, after this "dead" period everyting advances again normally, for a while... This is SOOOO frustrating.

Anyone else that have experienced something similar??? This is very annoying, rendering this version totally useless. None of the earlier 9.x versions did ever show non-responsiviness like this. My only project that I have tried so far, started out in 9.0 (32bit). Im running on W7 Ultimate 64 bit. I thought that VP9.0c is now officially supported... Will continue testing, but had to ask...

Christian

Comments

xberk wrote on 11/14/2009, 7:22 AM

I did not see this condition on 9.0c 64bit under Win7 64. Haven't used 9.0c in 32 bit.
Can you repro this behavior on a newly created .veg file with no plugins going?

Christian de Godzinsky wrote on 11/14/2009, 7:25 AM

Hi xberk,

I test what you suggest, but before that I need to get one file rendered. A 50 minute AVI-->mpeg2 render that normally took about 20 minutes now has lasted for 4,5 hours.... aaarghh...

I'll be back with more results. I would have tested this project in the 64 bit VP9, but due to some video FX, it's a no-go....

Christian

GeirOtto wrote on 11/14/2009, 12:39 PM

Same happens on our 8 core xenon running vista 64bit ultimate, i supect this 64/32 bit filesystem surrogater..
but an even more serious problem with v9 is the speed which has gone significatly down and suspect that to be the new 4k resolution. Could we have a " select 2k/4k mode internal res. switch on 9.0d?

geirotto
famo
oslo, norway

Fredouillelafripouille wrote on 11/15/2009, 2:58 AM

I have similar problem from VP 8.0c to 9.0c when I open .veg with MPEG-2 files from my camcorder (Sony hdr-sr190e), and only with this files. If there are a lot of these mpg files, project could take several minutes to open...
Problem occurs too if you come back to VP from another programm when VP "close media when VP is not the current application" (see in preference ; do not know exact english translation)

farss wrote on 11/15/2009, 3:09 AM

I have a similar problem with V9.0c.I started a new 6 camera project and I found moving tracks a painful experience. The click + drag of the track headers was extremely hit and miss, I'd say at best it too 3 goes to get the header to move. Even worse the visual indication that I was moving it was almost impossible to see making it difficult to tell where the track would land.

Bob.

LoTN wrote on 11/15/2009, 6:52 AM

Same here with both 32 and 64 versions. Vegas is frozen for almost 10 seconds then back to normal if I do not let Windows kill the process.

Fletcher Kauffman wrote on 11/15/2009, 12:45 PM

I am having this very same issue.

9.0c, 64-bit Win 7.

The issue ~appears~ to be FileIOSurrogate (which is 32-bit regardless of which Vegas you're running)-- it simply stops doing what it's supposed to be doing, or it does it in a woefully inefficient manner. Task Manager (looking at processes with a bunch of columns added) shows that it's not quite in a full dead state (it will occasionally allocate/deallocate some memory).

This is infuriating-- and seems to get worse the longer I work with a project (not just in a single session, but the more times I've opened it, etc.).

Christian de Godzinsky wrote on 11/16/2009, 1:15 AM

Hi Fletcher,

Have you tried borh 32 and 64 versions of VP9.0c? Both have the same problem here. I am considering moving back to 9.0b. This is really serious. I have raised a support ticket, but have not still got any answer from SCS (not even a recognition that it is received)...

I have a feeling that a 9.0d is in the works and must be released soon. This version c runs havok my work - completely.

Christian

R0cky wrote on 11/18/2009, 8:59 AM

Yes, happens to me too. Both x32 and x64 versions. Happened in XP too. Just built a new Win7x64 machine.

I frequently have to kill Vegas in task manager when this happens. Sometimes it will recover in 15 or 20 seconds, beyond that time to kill it.

Rocky

Christian de Godzinsky wrote on 11/18/2009, 11:35 AM

I got a suggestion from SCS to completely reistall. Will try that (also because I had some problems with the install of 9.0c over 9.0b). The installation stopped prematurely... Will report back if this had any impact...

Christian

LReavis wrote on 11/18/2009, 11:44 AM

I haven't used Vegas enough yet in my 64-bit Win 7 to see this (so far, 8c, 9c-32 & 9c-64 seem OK), but I have a similar problem: when I copy huge .AVIs, or even lots of smaller .JPGs, etc., from one drive to another, I see similar long timeouts.

Based on what I've read elsewhere, I'm suspecting the Western Digital drives that I have in RAID - it appears that WD has noted similar problems with their desktop drives and does NOT recommend RAID except for their enterprise drives. I'm in the process of copying all my files from those drives to non-raid Seagate drives on an old spare 32-bit computer so that I can still work with my 64-bit system, so in a day or two I should be able to abandon the RAID drives that have WD disks - then I'll post the results here.

I notice that most who have participated in this thread are using 64-bit systems; how about WD disks? Are these problems occuring in systems that have no WD disks?

R0cky wrote on 11/18/2009, 12:27 PM

My install is brand new on a clean system. I multiboot and both versions do the same thing.

LoTN wrote on 11/18/2009, 1:27 PM

I got a suggestion from SCS to completely reistall.

Christian,

I experience this issue on a clean and fresh install of Seven 64. I've tested if the root cause could be the filesystems I/Os, this is not the case. I can copy very large files from internal disk (7200 rpm) to external ones (10000 rpm / FW800) and vice-versa without problem.

My guess is that this is induced by swapping of a large amount of faulty pages but didn't check this assumption with system tools. I have only 4Go RAM, not enough in my opinion.

Himanshu wrote on 11/18/2009, 7:07 PM

Haven't seen anyone mention this: use Process Monitor (from Microsoft/Sysinternals) to see what is happening on your system when it appears to be dead. Might yield some clues...

LReavis wrote on 11/19/2009, 1:05 AM

I was wrong - the WD drives are not the culprit in my system stumbles. Instead, I found that I consistently got the problem whenever any Seagate 1.5 TB drive was connected to the ASUS MB's controller (I'm pretty certain that these 1.5 TBs use the new firmware, not the first generation firmware that caused so many headaches). I tested 2 of these Seagates - they worked fine on a Rosewill SATA controller (Sil 3114 chip), but stumbled on the ASUS (Intel chip) controller. 750GB Seagate pair in software RAID 0 on the ASUS MB's controller also works fine.

I just ordered an 8-port SATA controller that I hope will solve my problems (http://www.newegg.com/Product/Product.aspx?Item=N82E16815121009&cm_re=sata_controller-_-15-121-009-_-Product).

Christian de Godzinsky wrote on 11/19/2009, 1:37 AM

Hi lotn,

I know that the SCS reply is more or less a standard answer, but will try anyhow, just in case. The odd thing is that if I have other programs active at the same time, everything runs completely smoothly, even HD I/O. Vegas 9.0c just sits there with no CPU acticvity (less than 1%), doing nothing... I have 8GByte of RAM...

Probably I go back to 9.0b, just need to find that download first...

Please SCS - release 9.0d soon...

Christian

JohnAsh wrote on 11/19/2009, 8:14 AM

I am experiencing a similar problem.

On my unspectacular home PC which has coped pretty well until now editing HDV material, I am finding I have to wait AGES (10 minutes plus sometimes) for the Media window to update. I don't remember this happening before I "updated" to 9.0c. Will try reverting to 9.0b to confirm I am not in the middle of some Sony-esque nightmare.

Another thought, whilst I'm waiting for 9.0c to uninstall. I've just remembered that I noticed something very odd which may be connected, with this version. When it was loading, it would appear to do nothing, until I moved the mouse about over the loading progress window, until I moved away when it would stop again, until I waved the mouse at it again. Perhaps it is a nightmare after all and I am dreaming all of this?

JohnAsh wrote on 11/19/2009, 9:07 AM

OK. It is 9.0c that's the culprit. Thank goodness. I thought my memory had gone. I'm sat there thinking "I'm sure this didn't used to take this long". As you get older, it gets worse.

Then I checked this forum and a little light of hope came on.

With 9.0b reinstalled and 9.0c cast asunder, my media window updates in a second or so instead of somewhere between 10 minutes and infinity with 9.0c.

It may be my imagination, but it seemed to take a tad longer to load my project, but mouse waving in the window was not required and, once loaded, it behaves as I'd expect it to.

Let's wait and see what 9.0d has in store for us. Over to you Sony!

John

jabloomf1230 wrote on 11/19/2009, 3:15 PM

I'm not seeing it, but I pretty much work with Vegas and one input video format (Cineform) + still images.

VanLazarus wrote on 11/24/2009, 1:17 PM

I am getting the problem on a clean install of Vegas 9.0c on a clean install of Windows 7 x64. I thought that maybe my Cineform x64 codec was the culprit because I don't get the timeouts while editing some old AVI source files.... but judging from the feedback by others, this problem must be Vegas 9.0c related. I'll have to revert back to 9.0b and hope that this problem does not exist there.... or I won't be able to get any work done. This is a major problem and renders Vegas useless to me.

I love Vegas but it gets harder and harder to argue against the Final Cut Pro Mac freaks when my PC NLE is broken most of the time due to bad software, bad drivers, or bad codecs! I spend most of my time solving workstation problems and less actually editing.

VanLazarus wrote on 11/24/2009, 4:56 PM

Unfortunately, uninstalling Vegas 9.0c x64, and reinstalling Vegas 9.0b x64 does not solve this problem. I still get long unresponsive periods while editing. Can't use Vegas right now.

VanLazarus wrote on 11/25/2009, 12:42 AM

Tried using Vegas 9.0c 32 bit.... but as others have reported, the problem still exists. This is a very repeatable problem. I've sent a bug report to Sony but have yet to receive a human response. I believe with whoever said that they think it's related to the FileIOSurrogate.exe program....

Is this problem happening to anyone else in all versions of Vegas Pro 9.0 (a through c)?

warriorking wrote on 11/25/2009, 10:09 AM

Experiencing the same issue with Vegas 9c on a fresh install of Windows 7 64Bit Ultimate, Vegas goes unresponsive for several seconds and then requires a restart of the program, plus I loose several minutes of my editing, requiring me to redo large portions of my project..this is very frustraiting to say the least....

Christian de Godzinsky wrote on 11/26/2009, 1:51 AM

This nonresponsiviness is evident only in 9.0c, earlier 9.x version (be it 32 or 64 bit) versions do not behave in this respect as 9.0c.

Both 32 and 64 bit versions of 9.0c have these very long nonresponsive periods. They come back after waiting for a minute or two - but come on - how can you do serious work with such an (pro - or was it poor) application? I love Vegas, but I would also love to be able to work with the latest bug-fix version that solves the AVCDH playback issue...

I freshly reinstalled 9.0c (as instructed by SCS) but it did not help. Just waisted time and effort. I'm now forced to revert to 9.0b to get some work done. Aaaarghh... Please SCS - release the bugfix soon. This IS pathetic.

Christian