VV4 serious error / bug report

cobalt wrote on 3/15/2003, 10:15 PM

Please don't take this the wrong way. It took me a while to document it. I LOVE VV4 and this is the ONLY irritation in the program to me. I hope someone at Sonic Foundry takes note of this one ;-)

Here is the directory structure of the images.
They are 800x533 in size, and stored as jpegs...
In total there is just over 1000 photos.

V:\bc\bsci\1\FXCD0001.JPG
V:\bc\bsci\1\FXCD0002.JPG
V:\bc\bsci\1\...
V:\bc\bsci\1\FXCD0297.JPG

V:\bc\bsci\2\FXCD0001.JPG
V:\bc\bsci\2\FXCD0002.JPG
V:\bc\bsci\2\...
V:\bc\bsci\2\FXCD0420.JPG

V:\bc\bsci\3\FXCD0001.JPG
V:\bc\bsci\3\FXCD0002.JPG
V:\bc\bsci\3\...
V:\bc\bsci\3\FXCD0315.JPG

I've created 6 "media bins" in the media pool.
If I now go and grab
50 from one of the above directories and put those in bin 1
move 1 or 10 into the timeline
25 from another... and put that in bin 3
move 1 or 10 into the timeline
65 from another... and put that in bin 3
move 1 or 10 into the timeline
45 from another... and put that in bin 3
move 1 or 10 into the timeline

Somewhere in here, Vegas starts going all crazy.

It will start showing completely wrong thumbnails, which point to completely different files than I had originally dragged in.
Very soon around this time, VV4 crashes.
This happens on my...
dual celery 550Mhz 512mbytes of RAM
single athlon 1Ghz 512mbytes of RAM

P.S. Not having "thumbnails" represent media in the Media Bins is assinine. Try loading 24 3600x2400 images into a bin. How long does that take to refresh... and it needs to refresh all of them, everytime you reopen this bin.

P.S.S. The thing that really irks me when all the above will get working... is how you can't drag a list of images from outside of VV4 and drop it directly onto a sub media bin. The images always end up in the current open window. This is very counter intuitive.

Sonic Foundry Vegas 4.0
Version 4.0 (Build 115)
Exception 0xC0000005 (access violation) READ:0x1E IP:0x500C8D
In Module 'vegas40.exe' at Address 0x400000 + 0x100C8D
Thread: GUI ID=0xDAC Stack=0x12F000-0x130000
Registers:
EAX=0000000e CS=001b EIP=00500c8d EFLGS=00010202
EBX=00000001 SS=0023 ESP=0012f77c EBP=00000005
ECX=00000dac DS=0023 ESI=015163c8 FS=003b
EDX=02713370 ES=0023 EDI=00222010 GS=0000
Bytes at CS:EIP:
00500C8D: 8B 40 10 56 6A FF 6A 00 .@.Vj.j.
00500C95: 50 E8 41 6A 16 00 85 C0 P.Aj....
Stack Dump:
0012F77C: 01540FE8 014F0000 + 50FE8
0012F780: 0000000C
0012F784: 004EAA14 00400000 + EAA14 (vegas40.exe)
0012F788: 00222010 00140000 + E2010
0012F78C: 015163C8 014F0000 + 263C8
0012F790: 014F4A18 014F0000 + 4A18
0012F794: 0000000C
0012F798: 00000001
0012F79C: 004EAD59 00400000 + EAD59 (vegas40.exe)
0012F7A0: 014F4A18 014F0000 + 4A18
0012F7A4: 00000000
0012F7A8: 00000000
0012F7AC: 00000000
0012F7B0: 00000000
0012F7B4: 032B8DC0 03270000 + 48DC0
0012F7B8: 00000000
> 0012F7C8: 0054F952 00400000 + 14F952 (vegas40.exe)
0012F7CC: 00000012
0012F7D0: 01531AC0 014F0000 + 41AC0
0012F7D4: 0012FB08 00030000 + FFB08
0012F7D8: 032B8DC0 03270000 + 48DC0
> 0012F7DC: 77D4808B 77D40000 + 808B (USER32.dll)
> 0012F7E0: 005570A3 00400000 + 1570A3 (vegas40.exe)
0012F7E4: 01531AC0 014F0000 + 41AC0
0012F7E8: 0000004E
0012F7EC: 0012FB08 00030000 + FFB08
0012F7F0: 032B8DC0 03270000 + 48DC0
> 0012F810: 00557672 00400000 + 157672 (vegas40.exe)
0012F814: 00070462 00030000 + 40462
0012F818: 0000004E
0012F81C: 0000FDEA
0012F820: 0012FB08 00030000 + FFB08
> 0012F824: 00557951 00400000 + 157951 (vegas40.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 006768BA 00400000 + 2768BA (vegas40.exe)
0012FFFC: 00000000

Comments

musicvid10 wrote on 3/15/2003, 11:13 PM

It doesn't take rocket science to see that you are asking for 80 GB +/- of virtual memory (depending on your jpeg quality) to load all of these images. Perhaps that is the problem, rather than some flaw in Vegas? Try smaller projects, render each, then combine.

cobalt wrote on 3/15/2003, 11:54 PM

the 1000 images add upto 71 megabytes. I've comfortably edited several 1 hour shows with data spread across 600 gigs of RAID's, but as soon as you start piling a lot of still images into the bins VV4 crashes.

The jpegs I'm talking about are 800x500 in size. These are "chopped down" in a seperate application from the 3600x2200 originals.

Tyler.Durden wrote on 3/16/2003, 7:17 AM

Hi cobalt,

It does seem like the project is hitting Vegas' limits.

While it is not a solution, you might try using another instance of Vegas (or three)with tracks as your "bins". You could even set the timeline numbers to match the stills to find them easily.

I have not tried such large numbers of stills, but it might get you moving while the issue is explored by SoFo.

(You might send in the report on the support page)

HTH, mph

Radiation wrote on 3/16/2003, 8:40 AM

I sometimes have a problem, in that, when i try to import any type of file, it does not show in any of the bins, if i close the prog down and restart it, all my files now show, this can happen whilst to load 1 file, or several.