VP8/ Project Media - negative used count - why?

Christian de Godzinsky wrote on 4/14/2008, 12:30 PM

Hi,

Deleted some stuff on the timeline across all tracks, and performed a post-edit ripple (all tracks & markers & regions). Vegas crashed with the following error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x4 IP:0x743516
In Module 'vegas80.exe' at Address 0x400000 + 0x343516
Thread: GUI ID=0xEA0 Stack=0x2CF000-0x2D0000
Registers:
EAX=00000000 CS=0023 EIP=00743516 EFLGS=00210206
EBX=00000003 SS=002b ESP=002cf1e4 EBP=002cf304
ECX=00000000 DS=002b ESI=0ac10ee8 FS=0053
EDX=0ba70f50 ES=002b EDI=00000000 GS=002b
Bytes at CS:EIP:
00743516: 39 58 04 75 07 85 FF 74 9X.u...t
0074351E: 0F 83 EF 01 83 C1 01 83 ........
Stack Dump:
002CF1E4: 033D68C0 03330000 + A68C0
002CF1E8: 033D68C0 03330000 + A68C0
002CF1EC: 76010CAC
002CF1F0: 006D977D 00400000 + 2D977D (vegas80.exe)
002CF1F4: 00000003
002CF1F8: 00000000
002CF1FC: 006F3CDF 00400000 + 2F3CDF (vegas80.exe)
002CF200: 002CF304 001D0000 + FF304
002CF204: 76010CAC
002CF208: 033D68C0 03330000 + A68C0
002CF20C: 033D6C48 03330000 + A6C48
002CF210: 00000000
002CF214: 00000000
002CF218: 00000000
002CF21C: 3FF00000 3FE90000 + 70000
002CF220: 00000000
> 002CF254: 004A113D 00400000 + A113D (vegas80.exe)
002CF258: 07E36C70 07DB0000 + 86C70
002CF25C: 76010CAC
> 002CF260: 004A0F89 00400000 + A0F89 (vegas80.exe)
002CF264: 07E36C70 07DB0000 + 86C70
002CF268: 033D68C0 03330000 + A68C0
002CF26C: FFFFFFFF
002CF270: 00000000
> 002CF28C: 7D816C4D 7D800000 + 16C4D (GDI32.dll)
> 002CF2B8: 7D8149BD 7D800000 + 149BD (GDI32.dll)

After a restart the Vegas dies again if I try to re-open the project! If i open the former saved version, and THEN open the failed version, the project opens but reports an unknown error. Then some of my used stills in the Project Manager have a NEGATIVE USED COUNT!! Some of them also have disappeared from the time line, just the clip placeholder is there without the media.

This is not the first time I find that a post edit ripple runs havoc a project in Vegas 8. I just did not remember to avoid post edit ripples... :(

What can I do to rectify the problem, especially what to do with the NEGATIVE used count values? Do I dare to continue with this partially corrupted but now open project file, or should I return to my previous version, and loose about 3 hours of frenetic editing???

Has anyone else seen negative used count values? What had caused them and what was your fix? I try to repeat this proble as good as I can, to be able to open a service ticket to SCS. Just would be nice to know if anyone else has some experience on this.

My project is DV(PAL 4:3), most video on the timeline is DV (AVI), some VOB files and a handfull of stills, 3 videotracks and 5 audiotracks.

This is a serious project. And I am more than serious when I claim that since 8.0a Vegas lost it's rock stable reputation...

Please SCS, release 8c soon...

Christian

PS: BTW - where does Vegas stuff the autosave project file, and under what name ???

Thanks for your kind help!

Comments

ForumAdmin wrote on 4/15/2008, 12:41 PM

One possible workaround:

If the project uses media with file names that contain characters which sort differently depending on regional settings, it may be causing an issue.

We've had one other report of a danish regional setting causing a similiar problem because aa sorted after z. They were able to open the project by changing their OS region back to US English 1033 and then examine the media file names, tweak a few, and then restore their OS region.

Autosave files will be located in the temporary files directory that is shown in the Options > Preferences > General tab near the bottom.

Darren Powell wrote on 4/15/2008, 6:52 PM

Yeh come on Sony ... where's the working version of Vegas?? I want 8.0c NOW!!! This has been going on too long and people have paid good money and lots of users are having the same sort of stability problems ... COME ON FIX IT!

Pissed off.

Darren Powell
Sydney Australia

Christian de Godzinsky wrote on 4/16/2008, 1:00 AM

Hi,

Wow, thank's ForumAdmin (whoever you are :), I did not expect a directly reply from you. But it is always a nice surprise to see that you exist, and is ever so much appreciated when you appear. Gives the nice feeling that the big brother is watching ;)

Yes - being a scandinavian - I use regularly other than ascii characters in file names (like ä, ö, å), since Windows has been compatible with special characters already for about 100-years...

I assume that it is - for now - safer to use only the basic ASCII character set when naming media files to be used in Vegas Pro 8.

For the US users this is not an issue. But for us europeans, this can be a pain in the butt, albeit small. But as usual, you can live with things, if you now how to prevent pitfalls...

I hope you get this soon fixed in a future release. But don't hold back 8.0c for this reason ;) Thank's for your honesty and help. Appreciated!!! I will try to open the problematic file later today using your advice and see how I succeed.

regards,

Christian

PS: I opened a ticket at SCS with the same problem, and I got a very nice and constructive responce how to proceed. However, it did not reveal what you just told me?! You ForumAdmin seem to know more. We should se moore of you around here ;)

johnmeyer wrote on 4/16/2008, 8:22 AM

Ah, you pesky Scandinavians! Those "extra" letters you use have given me problems (as a developer) for decades. Å, Ä, Ð, Ø, and Þ haunted me during the five years I ran a desktop publishing company. They never seemed to fit comfortably into any space we had "left over" in the 128 character basic ASCII character set. We kept trying to keep things like numerical digits, and a few basic punctuation marks like the period and comma.

I never knew what an angry Dane sounded like (outside of Hamlet) until I asked a guy if he couldn't just get by without those "extra" letters.

Christian de Godzinsky wrote on 4/17/2008, 3:26 AM

Hi John,

Well, what should I say? Sorry for the extra trouble you have had with us pesky Scandinavians using "extra unnecessary ridiculous letters" ***big grin***.

After all, some shortsighted computer guys in US never understood (when standardizing the ASCII character set) that rest of the world uses a myriad of other symbols (other than A to Z ) to be able to express themselves. Ok, have to admit, A in ASCII stands for American, after all...

Fortunately, Unicode has finally solved the issue, every character or language set has now its local identity and special rules, including sorting. But the problem still persists of how to SORT charachters from different language sets. This is not a simple issue at all, and no wonder even SCS stumbled here!

John, the complexity and problems you had decades ago compared to what is is now with Unicode... you had an EASY time :)

I have to admit that I probably think about the asian alphabets (Chinese etc) the same way as you think about Å, Ä, Ð, Ø, and Þ.

Probably I have to find words and phrases that do not include these "special" characters, when naming files... until this is fixed.

Regards,

Christian