this is a strange one.. (its also taken from my other post @ DVInfo
i can go into anything Vegas6 related, but as soon as i try to open a project, or import some media, or even create a new project, i get fatal exceptions with stack dump errors..
at the bottom of this message, is the crash report.
Aother thing is that with media manager, (SQL thingy) i can go through these blank template directories, but as soon as i try any other action, such as tag or import, it will also crash..
now this is a wierd one as im yet to see this happen to anyone so far apart from one guy who mentioned it crashed 5 times in as many minutes..
now im all for media management, hell this was what i was looking out for when i proclaimed i could ditch my Avid, but it seems to me that there are stil some major flaws in the program.
one thign to note (to those not in the know) is that Vegas has been totally rebuilt from the ground up. Its core code has been rebuilt and as such, from my understanding of the situration, due to security, all testing was done internally@Sony (even the distributors here in oz didnt get a chance to beta test) Hell we were all on gag order about its new features let alone get a chance to play with it..
Reason i mention the above is that teething problems like this are to be expected.. Personally though, being one of the bigger advocates and sellers of Vegas i woud have expected a little more from it. Afew more filters, afew new features within the filters themselves, (such as latch recording keyframes as seen in the surround panner, but for fitlers instead of having to draw in teh keyframes.. hell even midi suppot for XY Axis using CC messages would allow me to literally tweak a filters position as its playing back)
AAAAAAAANYWAYS>>> moving on.
IMO, sure show it at NAB, but they could have held back at least 4 weeks before distributing it. They could have said, yup, heres Vegas6, available on so and so day, instead of releasing it and gettin all this bad publicity.
First impressions last...
obviously the problems will be fixed.. hell even PC games are released months ahead before theyre ready simply due to the big guys saying that the kit must be available there and then.
needless to say, i still cant use my demo copy of Vegas and i wont be buying a full license until i learn the ins and outs of the new fetaures, but i cant do that until this crashing problem is resolved.
Even worse is taht i cant even sell the product to punters in this condition.. noone wants a buggy app.. i know PremPro has its issues, but it still works...
anywyas to the problem at hand..
some specs..
P4 2.4 non HT 533 fsb overclocked to 2.75ghz
Abit IT7max 2 mobo series2
1Gb Corsair DDR 400mhz XMS3200 ram
ATI Radeon 9550Pro (catalyst 4.1 drivers)
SBLive Audigy
Pyro firewire card as well as TI onboard (onboard for capuring and Pyro for external media drives)
2x WD 120gb HDD
2x Seagate 200gb HDD
1x Lacie external and a couple of obsure racks with WDs in them
Drives are not Raided or striped
Running XPPro SP1 (and dont ask me to update to SP2 as there are many other apps which will die coz of it.. )
now this config lets me run up to 3 instances of vegas 5 while rendering in another (4 in total)
After installing the MS databasing thingy, Vegas 6 loads up, and i can navigate through it, but any attempt at accessing anything within explorer or on any media drive and the app crashes big time
below is teh stack dump problem (by the way guys <to the Sony techs> im the same guy who had that AC3 metadata issue which was ditched after an update resovled the problem)
heres the error--------------------------------
-------------------------------------------------------------------------------------------
Sony Vegas 6.0 TRIAL
Version 6.0a (Build 99)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x587EB8
In Module 'vegas60.exe' at Address 0x400000 + 0x187EB8
Thread: GUI ID=0x884 Stack=0x10E000-0x130000
Registers:
EAX=00000000 CS=001b EIP=00587eb8 EFLGS=00010206
EBX=7c350420 SS=0023 ESP=0010e4fc EBP=00000000
ECX=00000000 DS=0023 ESI=0010f6f4 FS=003b
EDX=0010f75c ES=0023 EDI=00000034 GS=0000
Bytes at CS:EIP:
00587EB8: 8B 10 8D 4C 24 10 51 68 ...LQh
00587EC0: CC 3B 8E 00 50 FF 12 85 .;..P...
Stack Dump:
0010E4FC: 09B65320 09B20000 + 45320
0010E500: 000405F4 00030000 + 105F4
0010E504: 000E04CC 00030000 + B04CC
0010E508: 77D4546D 77D40000 + 546D (USER32.dll)
0010E50C: 00000020
0010E510: 00000000
0010E514: 00000000
0010E518: 00000000
0010E51C: 00000000
0010E520: 00000004
0010E524: 0000001A
0010E528: 000000D0
0010E52C: 0FC31C00 0FAA0000 + 191C00
0010E530: 0010E550 00030000 + DE550
0010E534: 77490D41 773D0000 + C0D41 (SHELL32.dll)
0010E538: 00011C00
> 0010E54C: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E550: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E568: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E578: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E580: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E584: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E58C: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E590: 77E760CB 77E60000 + 160CB (kernel32.dll)
> 0010E59C: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E5AC: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E5B0: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E5B8: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E5C8: 77E94809 77E60000 + 34809 (kernel32.dll)
> 0010E5CC: 77E83288 77E60000 + 23288 (kernel32.dll)
> 0010E5D4: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E5D8: 7745CF88 773D0000 + 8CF88 (SHELL32.dll)
> 0010E5E0: 774D5A77 773D0000 + 105A77 (SHELL32.dll)
> 0010E5EC: 774D5AA3 773D0000 + 105AA3 (SHELL32.dll)
> 0010E5F8: 773E476C 773D0000 + 1476C (SHELL32.dll)
> 0010E5FC: 7748138D 773D0000 + B138D (SHELL32.dll)
> 0010E664: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E668: 77F51C78 77F50000 + 1C78 (ntdll.dll)
> 0010E670: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0010E674: 771C064E 771B0000 + 1064E (ole32.dll)
> 0010E684: 771C0672 771B0000 + 10672 (ole32.dll)
> 0010E688: 772BB040 771B0000 + 10B040 (ole32.dll)
> 0010E690: 70A95D18 70A70000 + 25D18 (SHLWAPI.dll)
> 0010E6A0: 77434854 773D0000 + 64854 (SHELL32.dll)
> 0010E6AC: 77498155 773D0000 + C8155 (SHELL32.dll)
> 0010E6C4: 7197B2CA 71950000 + 2B2CA (COMCTL32.dll)
> 0010E6D4: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E710: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E714: 7747F7C4 773D0000 + AF7C4 (SHELL32.dll)
> 0010E730: 77481FD2 773D0000 + B1FD2 (SHELL32.dll)
> 0010E748: 77F944A8 77F50000 + 444A8 (ntdll.dll)
> 0010E760: 77D43B1F 77D40000 + 3B1F (USER32.dll)
> 0010E768: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E76C: 77F53870 77F50000 + 3870 (ntdll.dll)
> 0010E774: 77F944A8 77F50000 + 444A8 (ntdll.dll)
> 0010E778: 77F57D70 77F50000 + 7D70 (ntdll.dll)
> 0010E77C: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0010E798: 77D479E6 77D40000 + 79E6 (USER32.dll)
> 0010E79C: 77D47A22 77D40000 + 7A22 (USER32.dll)
> 0010E7C0: 77D47A3C 77D40000 + 7A3C (USER32.dll)
> 0010E7D4: 763B8BCE 763B0000 + 8BCE (comdlg32.dll)
> 0010E7F4: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E804: 77D454B4 77D40000 + 54B4 (USER32.dll)
> 0010E808: 0085DEF8 00400000 + 45DEF8 (vegas60.exe)
0010E80C: 0185E770 017E0000 + 7E770
0010E810: 00000000
0010E814: 00000000
0010E818: 00000000
> 0010E824: 71979A0A 71950000 + 29A0A (COMCTL32.dll)
> 0010E83C: 7197960C 71950000 + 2960C (COMCTL32.dll)
> 0010E8A0: 7197960C 71950000 + 2960C (COMCTL32.dll)
> 0010E8C4: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E8C8: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E8CC: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E8D0: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E8D8: 77D440BD 77D40000 + 40BD (USER32.dll)
-----------------------------
If need be, i can reproduce the problem and record video as i rn the steps using Camtasia. I can then get NM here in Sydney to upload it to ur ftp if u like??
i can go into anything Vegas6 related, but as soon as i try to open a project, or import some media, or even create a new project, i get fatal exceptions with stack dump errors..
at the bottom of this message, is the crash report.
Aother thing is that with media manager, (SQL thingy) i can go through these blank template directories, but as soon as i try any other action, such as tag or import, it will also crash..
now this is a wierd one as im yet to see this happen to anyone so far apart from one guy who mentioned it crashed 5 times in as many minutes..
now im all for media management, hell this was what i was looking out for when i proclaimed i could ditch my Avid, but it seems to me that there are stil some major flaws in the program.
one thign to note (to those not in the know) is that Vegas has been totally rebuilt from the ground up. Its core code has been rebuilt and as such, from my understanding of the situration, due to security, all testing was done internally@Sony (even the distributors here in oz didnt get a chance to beta test) Hell we were all on gag order about its new features let alone get a chance to play with it..
Reason i mention the above is that teething problems like this are to be expected.. Personally though, being one of the bigger advocates and sellers of Vegas i woud have expected a little more from it. Afew more filters, afew new features within the filters themselves, (such as latch recording keyframes as seen in the surround panner, but for fitlers instead of having to draw in teh keyframes.. hell even midi suppot for XY Axis using CC messages would allow me to literally tweak a filters position as its playing back)
AAAAAAAANYWAYS>>> moving on.
IMO, sure show it at NAB, but they could have held back at least 4 weeks before distributing it. They could have said, yup, heres Vegas6, available on so and so day, instead of releasing it and gettin all this bad publicity.
First impressions last...
obviously the problems will be fixed.. hell even PC games are released months ahead before theyre ready simply due to the big guys saying that the kit must be available there and then.
needless to say, i still cant use my demo copy of Vegas and i wont be buying a full license until i learn the ins and outs of the new fetaures, but i cant do that until this crashing problem is resolved.
Even worse is taht i cant even sell the product to punters in this condition.. noone wants a buggy app.. i know PremPro has its issues, but it still works...
anywyas to the problem at hand..
some specs..
P4 2.4 non HT 533 fsb overclocked to 2.75ghz
Abit IT7max 2 mobo series2
1Gb Corsair DDR 400mhz XMS3200 ram
ATI Radeon 9550Pro (catalyst 4.1 drivers)
SBLive Audigy
Pyro firewire card as well as TI onboard (onboard for capuring and Pyro for external media drives)
2x WD 120gb HDD
2x Seagate 200gb HDD
1x Lacie external and a couple of obsure racks with WDs in them
Drives are not Raided or striped
Running XPPro SP1 (and dont ask me to update to SP2 as there are many other apps which will die coz of it.. )
now this config lets me run up to 3 instances of vegas 5 while rendering in another (4 in total)
After installing the MS databasing thingy, Vegas 6 loads up, and i can navigate through it, but any attempt at accessing anything within explorer or on any media drive and the app crashes big time
below is teh stack dump problem (by the way guys <to the Sony techs> im the same guy who had that AC3 metadata issue which was ditched after an update resovled the problem)
heres the error--------------------------------
-------------------------------------------------------------------------------------------
Sony Vegas 6.0 TRIAL
Version 6.0a (Build 99)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x587EB8
In Module 'vegas60.exe' at Address 0x400000 + 0x187EB8
Thread: GUI ID=0x884 Stack=0x10E000-0x130000
Registers:
EAX=00000000 CS=001b EIP=00587eb8 EFLGS=00010206
EBX=7c350420 SS=0023 ESP=0010e4fc EBP=00000000
ECX=00000000 DS=0023 ESI=0010f6f4 FS=003b
EDX=0010f75c ES=0023 EDI=00000034 GS=0000
Bytes at CS:EIP:
00587EB8: 8B 10 8D 4C 24 10 51 68 ...LQh
00587EC0: CC 3B 8E 00 50 FF 12 85 .;..P...
Stack Dump:
0010E4FC: 09B65320 09B20000 + 45320
0010E500: 000405F4 00030000 + 105F4
0010E504: 000E04CC 00030000 + B04CC
0010E508: 77D4546D 77D40000 + 546D (USER32.dll)
0010E50C: 00000020
0010E510: 00000000
0010E514: 00000000
0010E518: 00000000
0010E51C: 00000000
0010E520: 00000004
0010E524: 0000001A
0010E528: 000000D0
0010E52C: 0FC31C00 0FAA0000 + 191C00
0010E530: 0010E550 00030000 + DE550
0010E534: 77490D41 773D0000 + C0D41 (SHELL32.dll)
0010E538: 00011C00
> 0010E54C: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E550: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E568: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E578: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E580: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E584: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E58C: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E590: 77E760CB 77E60000 + 160CB (kernel32.dll)
> 0010E59C: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E5AC: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E5B0: 77F51C88 77F50000 + 1C88 (ntdll.dll)
> 0010E5B8: 77F59037 77F50000 + 9037 (ntdll.dll)
> 0010E5C8: 77E94809 77E60000 + 34809 (kernel32.dll)
> 0010E5CC: 77E83288 77E60000 + 23288 (kernel32.dll)
> 0010E5D4: 77E760DE 77E60000 + 160DE (kernel32.dll)
> 0010E5D8: 7745CF88 773D0000 + 8CF88 (SHELL32.dll)
> 0010E5E0: 774D5A77 773D0000 + 105A77 (SHELL32.dll)
> 0010E5EC: 774D5AA3 773D0000 + 105AA3 (SHELL32.dll)
> 0010E5F8: 773E476C 773D0000 + 1476C (SHELL32.dll)
> 0010E5FC: 7748138D 773D0000 + B138D (SHELL32.dll)
> 0010E664: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E668: 77F51C78 77F50000 + 1C78 (ntdll.dll)
> 0010E670: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0010E674: 771C064E 771B0000 + 1064E (ole32.dll)
> 0010E684: 771C0672 771B0000 + 10672 (ole32.dll)
> 0010E688: 772BB040 771B0000 + 10B040 (ole32.dll)
> 0010E690: 70A95D18 70A70000 + 25D18 (SHLWAPI.dll)
> 0010E6A0: 77434854 773D0000 + 64854 (SHELL32.dll)
> 0010E6AC: 77498155 773D0000 + C8155 (SHELL32.dll)
> 0010E6C4: 7197B2CA 71950000 + 2B2CA (COMCTL32.dll)
> 0010E6D4: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E710: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E714: 7747F7C4 773D0000 + AF7C4 (SHELL32.dll)
> 0010E730: 77481FD2 773D0000 + B1FD2 (SHELL32.dll)
> 0010E748: 77F944A8 77F50000 + 444A8 (ntdll.dll)
> 0010E760: 77D43B1F 77D40000 + 3B1F (USER32.dll)
> 0010E768: 77FA88F0 77F50000 + 588F0 (ntdll.dll)
> 0010E76C: 77F53870 77F50000 + 3870 (ntdll.dll)
> 0010E774: 77F944A8 77F50000 + 444A8 (ntdll.dll)
> 0010E778: 77F57D70 77F50000 + 7D70 (ntdll.dll)
> 0010E77C: 77F58A3A 77F50000 + 8A3A (ntdll.dll)
> 0010E798: 77D479E6 77D40000 + 79E6 (USER32.dll)
> 0010E79C: 77D47A22 77D40000 + 7A22 (USER32.dll)
> 0010E7C0: 77D47A3C 77D40000 + 7A3C (USER32.dll)
> 0010E7D4: 763B8BCE 763B0000 + 8BCE (comdlg32.dll)
> 0010E7F4: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E804: 77D454B4 77D40000 + 54B4 (USER32.dll)
> 0010E808: 0085DEF8 00400000 + 45DEF8 (vegas60.exe)
0010E80C: 0185E770 017E0000 + 7E770
0010E810: 00000000
0010E814: 00000000
0010E818: 00000000
> 0010E824: 71979A0A 71950000 + 29A0A (COMCTL32.dll)
> 0010E83C: 7197960C 71950000 + 2960C (COMCTL32.dll)
> 0010E8A0: 7197960C 71950000 + 2960C (COMCTL32.dll)
> 0010E8C4: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E8C8: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E8CC: 77D44092 77D40000 + 4092 (USER32.dll)
> 0010E8D0: 7197B2B0 71950000 + 2B2B0 (COMCTL32.dll)
> 0010E8D8: 77D440BD 77D40000 + 40BD (USER32.dll)
-----------------------------
If need be, i can reproduce the problem and record video as i rn the steps using Camtasia. I can then get NM here in Sydney to upload it to ur ftp if u like??