Is this a minor bug in Vegas?

organism_seven wrote on 6/22/2003, 10:38 AM
Hi,

I think I have found a really annoying (but minor) bug in Vegas 4.0.
Can you guys confirm if it happens on your machines?
I am using Windows XP Pro.

Step 1: Open up the plain Text option from Media Generator.
Step 2: Type in some text.
Step 3: Now select some or all of the text, and use the key combination "Crtl X" to cut to the clipboard.
As soon as I do this, Vegas bombs.

I can't remember the last time I saw Vegas crash.
So I'm curious. Is this a bug?

Regards
Organism Seven.

Comments

BillyBoy wrote on 6/22/2003, 11:42 AM
Tried, doesn't crash for me. Were you the guy that posted a similar post about it using 100% CPU resources? I was going to respond to that, then got busy building my latest system and didn't.
philfort wrote on 6/22/2003, 1:33 PM
I've had this happen once or twice in the most recent version of vegas, but I can not repro consistently.

I've also had it crash when ctrl-x'ing some keyframes in an event.

Only times Vegas has ever crashed for me.
Trichome wrote on 6/22/2003, 3:10 PM
I can say that this does happen for me too, not everytime, but usually when I don't want it to, and often does not auto save to the most recent edits.
Would be my only dislike about the great and powerful NLE.
24Peter wrote on 6/22/2003, 11:09 PM
Cutting/pasting keyframes has killed my Vegas 4.0c several times. A bit disconcerting to say the least. Now I always save before copying keyframes. (I should say event video effect keyframes)
organism_seven wrote on 6/23/2003, 4:46 PM
Hi,

No, I wasn't the guy posting about CPU resources.
Glad to see (sorry, guys!) that I'm not the only one who has this "Crtl X" problem.
Obviously some kind of minor bug that needs correcting by SOFO.
But I still find it amazing that this is about the worst problem I have ever had with Vegas.
Stll the best NLE program by light years!

Regards

Organism Seven
jaegersing wrote on 6/26/2003, 6:54 AM
I've had Vegas crash a few times in the text media setup window. Same thing, cutting and pasting text, but not consistent (I've had projects with >200 text events and no problems).

I also get crashes when trying to copy keyframes sometimes, again it is not consistent.

I think this is the only thing I've seen so far that causes Vegas to crash, usually it is really solid.

Richard Hunter
edit_suite wrote on 6/26/2003, 7:21 PM
I occasionally have a similar problem with VV3. When splitting, copying and pasting clips and editing text, an error message sometimes appears, and Vegas closes after clicking "OK".
It doesn't always happen, but when it does, it happens several times in a row.
Maverick wrote on 6/26/2003, 7:34 PM
Me, too.

It happened in both Vv£ & V4. I am bnow very careful, like a previous poster, to ensure I save the project before cutting/pasting/deleting text.

As for keyframes I tend to select all the ones I want to copy and CTRL drag them to copy. Of course, this doesn't work when copying to a new event.

Cheers
edit_suite wrote on 6/26/2003, 7:42 PM
I referred my similar problem (Vegas crashing while text editing, copying, pasting, etc.) to e-mail support. The person who replied asked, among other things, if I had recently installed any new software or hardware (I hadn't) and what type of editing I was doing when this occurred. She also asked for the STACK DUMP values listed under "Details" in the error message window. I sent to her all necessary information. If I recieve any helpful info, I'll be sure to post the 411.
philfort wrote on 6/27/2003, 12:27 AM
SF, listen up,
This is very easy to repro for me. Here are the steps:

1) Open vegas to a blank project
2) Go to the media generators tab, and drag the first text generator onto the timeline (the one with transparent background, although it probably doesn't matter)
3) Click on the generated clip, and press ctrl-c to copy it to the clipboard
4) Click somewhere else on the timeline, presse ctrl-v to paste it there
5) Choose "Create a new copy of generated media" from the dialog that pops up
6) Click on the icon on the copied clip that will bring up the Text Generator window
7) Highlight some of the text in the editbox, and press ctrl-x

Boom!

I'm running XP SP1, Vegas 4.0c

This won't mean much to most of you, but might be of help to SF: I put it under a debugger, and the first pointer of a vtable of an object in riched20.dll had been corrupted, and we jumped 0 when calling a method.

Memory corruption bugs can be hard to find/fix.


Haven't been able to repro the keyframe problem though.
Grazie wrote on 6/27/2003, 1:24 AM
Just done it in WimE - guess what? - No BOOM! - THAT'S gotta be a first! Laptop didn't fall over - V4.0c still on screen!

P3
1 ghtz
256 ram

Repeated same and put a another Copy between original and 1st copy - BIG BOOM!

Here's the report - "Error Exception" thing:

Sonic Foundry Vegas 4.0
Version 4.0c (Build 184)
Exception 0xC000001D (illegal instruction) IP:0x2
In Module 'VEGAS40.EXE' at Address 0x0 + 0x2
Thread: GUI ID=0xFFF6710F Stack=0xDFF000-0xE00000
Registers:
EAX=a3675bb9 CS=01a7 EIP=00000002 EFLGS=00210282
EBX=0000001e SS=01af ESP=00dff05c EBP=00dff0ac
ECX=039cb40c DS=01af ESI=039cb40c FS=6597
EDX=819d0000 ES=01af EDI=00000000 GS=0000
Bytes at CS:EIP:
00000002: .. .. .. .. .. .. .. .. ........
0000000A: .. .. .. .. .. .. .. .. ........
Stack Dump:
00DFF05C: 4803279C 48000000 + 3279C (RICHED20.DLL)
00DFF060: 00000000
00DFF064: 00000000
00DFF068: 00DFF200 00CF0000 + 10F200
00DFF06C: 00000001
00DFF070: 00000000
00DFF074: 00000000
00DFF078: 00000000
00DFF07C: 00DFF200 00CF0000 + 10F200
00DFF080: 0000001E
00DFF084: 48028959 48000000 + 28959 (RICHED20.DLL)
00DFF088: 00DFF200 00CF0000 + 10F200
00DFF08C: 00000001
00DFF090: 039CB40C 035D0000 + 3FB40C
00DFF094: 03698010 035D0000 + C8010
00DFF098: 48017B9C 48000000 + 17B9C (RICHED20.DLL)
> 00DFF0B0: 48017954 48000000 + 17954 (RICHED20.DLL)
> 00DFF0D0: BFF4252A BFF40000 + 252A (USER32.DLL)
> 00DFF0E8: 004200FD 00400000 + 200FD (VEGAS40.EXE)
00DFF0EC: 03698010 035D0000 + C8010
> 00DFF0F0: BFF424EF BFF40000 + 24EF (USER32.DLL)
00DFF0F4: 00DFF120 00CF0000 + 10F120
> 00DFF0F8: 4801718D 48000000 + 1718D (RICHED20.DLL)
> 00DFF108: 4802B099 48000000 + 2B099 (RICHED20.DLL)
> 00DFF128: 48048319 48000000 + 48319 (RICHED20.DLL)
> 00DFF14C: 4804223E 48000000 + 4223E (RICHED20.DLL)
> 00DFF15C: BFF42DA9 BFF40000 + 2DA9 (USER32.DLL)
> 00DFF168: 48042253 48000000 + 42253 (RICHED20.DLL)
> 00DFF184: 4801FE16 48000000 + 1FE16 (RICHED20.DLL)
> 00DFF18C: 48049BC5 48000000 + 49BC5 (RICHED20.DLL)
> 00DFF194: 48049BEA 48000000 + 49BEA (RICHED20.DLL)
> 00DFF198: 02000001 01F20000 + E0001 (AVIPLUG.DLL)
00DFF19C: 00000001
00DFF1A0: 065EFFA4 061F0000 + 3FFFA4
00DFF1A4: 00000000
00DFF1A8: 00000000
> 00DFF1C0: 02000001 01F20000 + E0001 (AVIPLUG.DLL)
00DFF1C4: 00000000
00DFF1C8: C66E0002
00DFF1CC: 00000000
00DFF1D0: 00000000
> 00DFF200: 480028C0 48000000 + 28C0 (RICHED20.DLL)
> 00DFF204: 480028B8 48000000 + 28B8 (RICHED20.DLL)
> 00DFF240: BFF641CF BFF60000 + 41CF (KERNEL32.DLL)
> 00DFF248: BFF66963 BFF60000 + 6963 (KERNEL32.DLL)
> 00DFF24C: BFFBB4C0 BFF60000 + 5B4C0 (KERNEL32.DLL)
> 00DFF254: BFF6152E BFF60000 + 152E (KERNEL32.DLL)
> 00DFF258: BFF61547 BFF60000 + 1547 (KERNEL32.DLL)
> 00DFF26C: 48056844 48000000 + 56844 (RICHED20.DLL)
> 00DFF278: 48020010 48000000 + 20010 (RICHED20.DLL)
> 00DFF2AC: 4801EB5C 48000000 + 1EB5C (RICHED20.DLL)
> 00DFF2D4: BFF614D9 BFF60000 + 14D9 (KERNEL32.DLL)
> 00DFF2E4: BFF61547 BFF60000 + 1547 (KERNEL32.DLL)
> 00DFF2F0: 7C003E1F 7C000000 + 3E1F (MSVCR70.DLL)
> 00DFF304: 7C04E054 7C000000 + 4E054 (MSVCR70.DLL)
> 00DFF308: 7C003ED5 7C000000 + 3ED5 (MSVCR70.DLL)
> 00DFF324: 7C04E05A 7C000000 + 4E05A (MSVCR70.DLL)
> 00DFF338: 7C002F91 7C000000 + 2F91 (MSVCR70.DLL)
> 00DFF348: 7C00293C 7C000000 + 293C (MSVCR70.DLL)
> 00DFF35C: 7C031CA5 7C000000 + 31CA5 (MSVCR70.DLL)
> 00DFF380: BFF76234 BFF60000 + 16234 (KERNEL32.DLL)
> 00DFF414: BFF76574 BFF60000 + 16574 (KERNEL32.DLL)
> 00DFF4D0: BFEE623D BFE80000 + 6623D (COMCTL32.DLL)
> 00DFF4D4: BFE83598 BFE80000 + 3598 (COMCTL32.DLL)
> 00DFF4E0: BFF63613 BFF60000 + 3613 (KERNEL32.DLL)
> 00DFF4F0: 02000001 01F20000 + E0001 (AVIPLUG.DLL)
00DFF4F4: 852C6B07 840CE000 + 11F8B07
00DFF4F8: 000002A2
00DFF4FC: 000003B5
00DFF500: C57A45DF
> 00DFF548: BFF76234 BFF60000 + 16234 (KERNEL32.DLL)
> 00DFF550: 0295030E 027D0000 + 18030E (VIDPCORE.DLL)
> 00DFF554: 02A203B5 02A00000 + 203B5 (COLORCORRECTOR.DLL)
- - -
00DFFFF0: 70B76CBE 70040000 + B36CBE
00DFFFF4: 89BF1FEC 89BE4000 + DFEC
00DFFFF8: BFF7A24F BFF60000 + 1A24F (KERNEL32.DLL)
00DFFFFC: 00000000

Any ideas SoFo?

Grazie
Grazie wrote on 6/27/2003, 1:34 AM
Just repeated same - same crash out. Repeated, using mouse - works fine - it appears to be only the keystrokes - rodent control works fine. I'm no programmer - wondering if these Ctrl-C-V-X combinations are somehow duplicated somewhere else within the V4 prog/system? Dunno . . .

Grazie
Grazie wrote on 6/27/2003, 1:36 AM
Correction mouse control don't work either . . hmmmmm....

Here's the report SoFo:

Sonic Foundry Vegas 4.0
Version 4.0c (Build 184)
Exception 0xC0000005 (access violation) READ:0xFFFFFFFF IP:0x48032782
In Module 'RICHED20.DLL' at Address 0x48000000 + 0x32782
Thread: GUI ID=0xD4C09A47 Stack=0xDFD000-0xE00000
Registers:
EAX=00000000 CS=01a7 EIP=48032782 EFLGS=00210286
EBX=00000000 SS=01af ESP=00dfdb38 EBP=00dfdb6c
ECX=0395429c DS=01af ESI=0395429c FS=1827
EDX=aaab0000 ES=01af EDI=00000000 GS=0000
Bytes at CS:EIP:
48032782: F6 40 6C 01 75 16 57 8B .@l.u.W.
4803278A: 06 57 FF 74 24 1C FF 74 .W.t.t
Stack Dump:
00DFDB38: 00000000
00DFDB3C: 00DFDC4C 00CF0000 + 10DC4C
00DFDB40: 00000000
00DFDB44: 48028959 48000000 + 28959 (RICHED20.DLL)
00DFDB48: 00DFDC4C 00CF0000 + 10DC4C
00DFDB4C: 00000001
00DFDB50: 0395429C 036F0000 + 26429C
00DFDB54: 039552C4 036F0000 + 2652C4
00DFDB58: 48017B9C 48000000 + 17B9C (RICHED20.DLL)
00DFDB5C: 0395429C 036F0000 + 26429C
00DFDB60: 00DFDC4C 00CF0000 + 10DC4C
00DFDB64: 00000001
00DFDB68: 039552C4 036F0000 + 2652C4
00DFDB6C: 00DFDCF4 00CF0000 + 10DCF4
00DFDB70: 480487A9 48000000 + 487A9 (RICHED20.DLL)
00DFDB74: 00000300
> 00DFDC20: BFF76574 BFF60000 + 16574 (KERNEL32.DLL)
> 00DFDC4C: 480028C0 48000000 + 28C0 (RICHED20.DLL)
> 00DFDC50: 480028B8 48000000 + 28B8 (RICHED20.DLL)
> 00DFDCB8: BFF61547 BFF60000 + 1547 (KERNEL32.DLL)
> 00DFDCC8: BFF641CF BFF60000 + 41CF (KERNEL32.DLL)
> 00DFDCD0: BFF44F8C BFF40000 + 4F8C (USER32.DLL)
> 00DFDCDC: BFF45749 BFF40000 + 5749 (USER32.DLL)
> 00DFDCE0: 48056844 48000000 + 56844 (RICHED20.DLL)
> 00DFDCF8: 4801EB5C 48000000 + 1EB5C (RICHED20.DLL)
> 00DFDD54: BFF76234 BFF60000 + 16234 (KERNEL32.DLL)
> 00DFDD5C: 029F01F2 027D0000 + 2201F2 (VIDPCORE.DLL)
> 00DFDD60: 02AC0337 02A00000 + C0337 (COLORCORRECTOR.DLL)
00DFDD64: 00DFE0D8 00CF0000 + 10E0D8
00DFDD68: 00DFE090 00CF0000 + 10E090
00DFDD6C: 00DFE13F 00CF0000 + 10E13F
00DFDD70: 73CC94F8 73730000 + 5994F8
> 00DFDD9C: 0042063F 00400000 + 2063F (VEGAS40.EXE)
00DFDDA0: 000A14EE
00DFDDA4: 724F0000 70040000 + 24B0000
00DFDDA8: 71D7ADDC 70040000 + 1D3ADDC
> 00DFDDAC: 01F202AA 01F20000 + 2AA (AVIPLUG.DLL)
00DFDDB0: 4DBE0000 48070000 + 5B70000
00DFDDB4: AE6E063F AAEA7000 + 383963F
00DFDDB8: 000095BE
00DFDDBC: 00000000
> 00DFDDC4: 029F01F2 027D0000 + 2201F2 (VIDPCORE.DLL)
> 00DFDDC8: 02AC0337 02A00000 + C0337 (COLORCORRECTOR.DLL)
- - -
00DFFFF0: 77675836 771A0000 + 4D5836
00DFFFF4: 8ED59FEC 8ED3A000 + 1FFEC
00DFFFF8: BFF7A24F BFF60000 + 1A24F (KERNEL32.DLL)
00DFFFFC: 00000000


It's beyond me,

Grazie
Grazie wrote on 6/27/2003, 1:42 AM
Both ways in copying "Create a new copy of source media " and "Create a reference . . " both crash out V4. Placing Fresh Text media doesn't.
SonyEPM wrote on 6/27/2003, 9:43 AM
Thanks for the info- the exact repro is what we needed.
Grazie wrote on 6/27/2003, 9:49 AM
EPM - you mean you understand that stuff???!!! " . . the exact repro ..." Hats off to you all at SoFO! - I'm not worthy . .. . I'm not worthy . . . .

Best regards from London UK,

Grazie
philfort wrote on 6/27/2003, 10:38 AM
Ok, the keyframe crash is easy to repro too. Just add some keyframes in the media generator before copying it. Then right after you've copied the event, ctrl-x one of the keyframes in it. Boom.

So it seems like it's related to having something on the clipboard.
philfort wrote on 6/27/2003, 10:47 AM
It seems related to making a copy of *any* generated media, and then attempting to ctrl-x something.