Re-installing V5

Mahesh wrote on 3/15/2005, 10:16 AM
OK.
I have had enough. Another long form project that would not PTT. The app freezes during rendering W64 file. The problem appears to be
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x104CBDC
some sort of conflict to my simple mind. I have posted here and there (Vegas Cow forum), sent the veg file to Sony at their request but no feedback.

The work-around, as always, is rendering the whole 100 minutes before I can Print to tape.

I shall try a re-install and if that does not work, I would have no option but to try Liquid Edition ( or go back to V4).

What is the best way for re-install? I still have V4 on the system. Only other applications on the PC are DVD Workshop and DVDA2.

Would I have to reinstall my Plug-ins and scripts?
I have
Excaliber, Wax, Plug-in Pac and Cayman Graphics Power CG.

Please, please help me to keep loyal to V5.

Thanks in advance.

Comments

jetdv wrote on 3/15/2005, 10:21 AM
What is the best way for re-install? I still have V4 on the system

Uninstall and then delete the Vegas 5 folders in the Program Files\Sony directory.

If you know what you're doing, you might also remove any Vegas 5 related registry entries.

Then reinstall using 5.0d.

Would I have to reinstall my Plug-ins and scripts?

Excalibur - Yes. Can't say for sure on all of the other ones. The DirectX ones may simply reappear.
Mahesh wrote on 3/15/2005, 10:26 AM
Thanks Edward for such a quick response.
I do hope the re-install will fix the problem.
Do I really have to install 5.0d? I am using 5.0b at the moment.
Liam_Vegas wrote on 3/15/2005, 11:13 AM
Actually you have a few options.

1) upgrade to 5.0d - as that may have some bug fixes that will help (that may be wishful thinking on my part)

2) change your workflow to always PTT from completely rendered AVI files of your entire timeline.

I generally have this workflow myself as this gives me far more control over the process. For instance.... I render the timeline as an AVI file... then maybe I decide to do some further last minute tweaking. No problem... just slam the rendered AVI file onto new tracks above all the old ones. Then just slice out the section where I need to make changes (exposing the tracks below)... then make my changes and re-render just that small segment to another track. The result is that you can still PTT without the need to render everything again (and even if you do... it will all just be straight copying - no rendering required).

*note you need to mute the audio on either the new tracks or the "old" ones otherwise the audio from the newly rendered AVI's will "ADD" to the audio already in yoru project.
Mahesh wrote on 3/15/2005, 11:24 AM
Thanks Liam_Vegas
I guess I am lazy or there is not enough HDD space for complete render or I am working to a deadline - like today.
I must admit, I never had problem with V4 in doing PTT. I would like the option to have the NLE do what it says on the box: i.e. PTT from the time line.

I have had to do what you suggest for past 3 or 4 months. I would dearly like to know why V5 suddenly stops working - the only indication being CPU activity=0.

Oh, if I reinstall, how do I save my preferences?
Liam_Vegas wrote on 3/15/2005, 11:43 AM
Although I understand your frustration... obviously this is NOT an endemic problem with Vegas (I didn't hear loads of other users saying they have the same problem)... so in the end there is SOME issue within your system that is causing this.

For me... working in the way I described gives me maximum flexibility. HD space is cheap... and for a 100 minute project you are still <only> talking about 24GB or so... so if HD is really a big issue then maybe that is a contributing factor to the problems you are experiencing.

That said... I really do hope you can find a solution to your problem... and that you get to use Vegas the way you prefer to.

Good luck.
SonyEPM wrote on 3/15/2005, 12:12 PM
Mahesh, please use 5.0d.
Mahesh wrote on 3/15/2005, 2:51 PM
OK
Just completed the project. I shall download 5.0d and do a clean install.

Another question:
Do I install 5.00 from the CD first or just go for 5.0d?

Thanks all for your help.
jetdv wrote on 3/15/2005, 6:41 PM
Straight to 5.0d. You don't need the CD.
Mahesh wrote on 3/16/2005, 6:56 AM
Uninstalled V5.0b. Cleared directories as Edward had suggested, installed 5.0d. V5 still hangs during render of W64.
I have another PC, for emergency use, with a OS partition which has clean install of Win2K SP4, Vegas 5.0b and DVDA2 only.
Same thing happens in this PC.
This means the problem is not hardware specific.
Just to give background,
Win2k was upgraded to service pack 4 in Dec 2003 so that I could use larger drives.
I ran V4 on this PC and win2k sp4 without any problem.
I strated using V5 in May 2004 and updated to V5.0a without any issues with win2k.
I updated to V5.0b at end Aug 2004 and problems started with flaky PTT which I reported here last year.
http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?ForumID=4&MessageID=343197

This may be a red herring but when I loaded the suspect project in newly installed V5.0d,
I got error message
to effect that an Audio plug-in specified was not installed
8efd2490-1362-4ee2-90f1-158ed2ea24ac
8efd2490-1362-4ee2-90f1-158ed2ea24ac
8efd2490-1362-4ee2-90f1-158ed2ea24ac
8efd2490-1362-4ee2-90f1-158ed2ea24ac

Now I have standard default track plug-ins on audio tracks and compressor on output mixer. Nothing else.

Does this mean anything to any body?
I am sincerely hoping there is a logical explanation. I am aware of a few workarounds as I have had to use them for past 6 months.
I would like to - if I can - have an option of PTT.
ken c wrote on 3/16/2005, 8:04 AM
I'd try using V4. From all the bugs I've heard plague Vegas5, I'll try it, but I'm planning on continuing to make my living w/V4 - it works.

ken
jetdv wrote on 3/16/2005, 8:12 AM
From all the bugs I've heard plague Vegas5,

Ken, I don't know what you've heard but Vegas 5 runs just as well as Vegas 4 for me. No difference. Both can crash given the right circumstances. Both have performed very well for me.
Cunhambebe wrote on 3/16/2005, 8:53 AM
Same thing here, no problems at all with Vegas 5 (I use 5b). Note: after uninstalling your software you can safely delete its entries with a software called jv16PowerTolls (called as Reg Cleaner a long time ago).
cyanidekid wrote on 3/16/2005, 8:54 AM
Wow! I thought I was the last V4 user alive! I don't understand this "when's the new version coming out?" mentality...unless you guys are working in Hollywood, or know something I don't, I'll stick with V4....
Mahesh wrote on 3/17/2005, 2:56 AM
Thanks all for your inputs. It does not solve my problem. I could go back to V4 but that would be a backward step. I like the new layout of V5. Reason for moving from V4 to V5 was because V5 offered me functionalities that V4 lacked.
There appears to be a reluctance to accept that some people are experiencing genuine software problems. The Vegas Video is 'software only' editing solution. So it should perform, as per spec, on a recommended OS platform. I have a problem which is consistent; occurs on 2 distinct PCs and menifested itself since upgrade to V5.0b.
May be a code change in 5.0b has made it flacky on Win2K platform.

I would love to know how many users of V5 are on Win2k-SP4 platform.
I would love to hear from Sony that V5 is stable on Win2K platform.


Liam_Vegas wrote on 3/17/2005, 3:17 AM
No reluctance here... I was not attempting to tell you that you were not experiencing a bug... just trying to help you find a solution is all.

Good luck with your quest.

Using XP here.
Mahesh wrote on 3/17/2005, 3:28 AM
Liam_Vegas
I did take your post in the spirit it was given. No criticism. But sometimes I get frustrated when people offer work-arounds rather than solutions. I have been round this loop 3 months ago without any conclusions.

Vegas 5 is a damn good software. I wish there was more emphasis on improving stability, reducing workarounds rather than more bells-n-whistles.

I use Vegas everyday. It earns me a living. Reliability - within reason - is essential.
For my own reasons I have to stay with win2k. V4 was stable on that platform. Hence move to V5. Perhaps it was mistake. Who knows.

DOGoodman wrote on 3/17/2005, 4:07 AM
I've been on w2k sp4 since it came out. No issues at all with V5. Sorry to hear you're having problems. I'm also running an ancient dual P3, so if anything doesn't work, you'd think I'd be the one to go in the dumper.

Dave
Mahesh wrote on 3/17/2005, 4:28 AM
Dave
Thanks for responding. That is extremely encouraging.
I presume you are on the latest version of V5.0d.
Most of my projects are 90 - 130 minutes. I experience problems when the project exceeds 100 minutes.
Would your projects be long form?
DOGoodman wrote on 3/17/2005, 4:52 PM
I'm on 5.0d. Almost all of my stuff is long form. The last one I finished was 97 minutes so I didn't push your one hour limit but I have done as much as a two hour show without problems.
Regardless, I've never had it die during the w64 process.
The only thing I have that you do is Wax but I left V3 and V4 on the system for awhile after I loaded V5.

Dave
Mahesh wrote on 3/18/2005, 1:18 AM
Thanks Dave.
Looks like I am back to were I was 3 months ago. I have now run out things to check.
Reminds me of a problem I had 3 years ago. I was having trouble installing RT Mpeg encoder (Digital Video Creator 2 by Dazzle ). I could not install drivers in win2k but it would work in win 98. Asked around forums, support lines but no solution. People either were happy with the card working in win2k or had given up and moved on to something else. After 12 months I got fed up and built another PC. On installation, same problem.
As I had tried every thing else, last thing to try was disabling Plug-nPlay in BIOS.
I looked in amazement as the drivers for this card loaded without any problems. So I tried the card in the original PC with P and P disabled and the card worked.
Next day (!!) I saw an article which dealt with conflicts occuring when Plug and Play in BIOS was enabled in Windows 2000 and pointed to a white paper by microsoft on the topic.

Sorry for the long rant but I am hoping there is something simple, may be mother board or BIOS related, that's stopping me using my V5 properly.

Zulqar-Cheema wrote on 3/18/2005, 12:35 PM
Sorry you having problems Mehesh, I have been using 4 and 5 for the last 2 years on XP (not installed the new upgrade) and it has been faultless, with it working for days with no crashes in site, if it did lock it was because a fire wire drive would hang and in turn hanging Vegas till I disconnected the FW and then Vegas would come back to life.

PTT has been the big problem, but that has been a hardware issue and would normally work,if all other processes re reduced. Going straight to DVD means hats no longer a problem.

My PC is a Medion one, so nothing special, the Laptop I have used (Targa) has also allowed Vegas to run fault free, with no problems on PTT for some odd reason.

Good luck and I hope it solves the problems.
Mahesh wrote on 3/19/2005, 4:02 AM
Hi Z
Thanks for your input and support. This problem is driving me nuts. As an engineer you know that - if it ain't broke don't fix it, but if it's broke then engineer in me wants to why.
I do not know why I am the only one having problems. It cannot be
1-Mother board because it happens on ASUS P4B and P4PE, both PCs have different makes video cards, sound cards and both have updated BIOS.

Only thing common is the hard disk which carried from onw PC to another via caddies.

Today I carried out another test on this project. The project is a 4 cam shoot of a 107 minute concert. I have 4 audio tracks with volume envelopes.
If I delete one of the audio tracks, the damn thing goes thro' its W64 ritual without any problem.
Perhaps its got nothing to do with hardware or software and everything to with the window in my room facing the wrong way.
Still the engineer in wants to know what it is. May be there is an answer.


Zulqar-Cheema wrote on 3/19/2005, 1:41 PM
I to am an engineer by trade (Radar) and like you need to know why if it is like it is.

Have you tried changing the defaults in the properties to the alternative audio render ? "Render Large Wave Files as Wave64"

What happens if you just render to WAV or MP3 is it OK
.
Could the capture be causing a glitch in the audio? so perhaps a different capture utility.

What about doing a render to AVI as opposed to PTT and then playing out via the capture utility or better still scenerlyzer, that solved mu PTT problems.

They are some of the things I would check
Mahesh wrote on 3/20/2005, 6:13 AM
I know you are an engineer Z.. I have tried some of the things you suggest. PTT from capture utility only works AVI so I have not tried that.
I think this thread has become too long and possibly one cannot see the wood for the trees.
So here's recap.
The Project:
4 camera edit of a rock concert. Duration 107 minutes. Edited on win2k sp4 operating system. After completing the edit using Excaliber, all 4 redundant camera video tracks were deleted. So the timeline consists of edited video track and 4 audio tracks. There are 2 tracks to produce lower thirds for song captions.

What happens:
The system hangs on PTT during the render of W64 file. To reduce the time for testing I have saved the pre-renders so that when I PTT, it goes straight to W64 render.
What I can do:
1-I can prerender the whole project to new tack. I can Print to Tape from this track without any problems. So I have been able to dump the edit to a DVCAM tape using the the new track avi.
2-I can render to MPEG2 from the timeline without any problems. So I have been able to author the DVD.
What have I tried:
1- In preferences toggled ( checked-unchecked) 'build 8 bit peaks', 'build large files as W64' and 'Draw video/audio waveforms..'. without any improvement.
2- Tried a clean win2k install on another PC with identical results.
3-I can print to tape if I I delete one of the audio tracks.

So, basically I am completely baffled.