My First Vegas Crash!

kimgr wrote on 3/20/2005, 8:53 AM
When I try to open an EDL created in PP 1.5 Vegas 5.0d crashes and gives me the following message:

[An Exception has occurred.]

Sony Vegas 5.0
Version 5.0d (Build 194)
Exception 0xC0000094 (integer divide by zero) IP:0x1090723
In Module 'vegas50k.dll' at Address 0x1000000 + 0x90723
Thread: GUI ID=0x104 Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=01090723 EFLGS=00010246
EBX=0012f4bc SS=0023 ESP=0012f498 EBP=0012f5b4
ECX=0019a0e4 DS=0023 ESI=00000000 FS=0038
EDX=00000000 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
01090723: F7 FE 52 53 E8 94 FC FF ..RS....
0109072B: FF 5F 5E 5B C2 08 00 8B ._^[....
Stack Dump:
0012F498: 0019A0E4 00140000 + 5A0E4
0012F49C: 00199FF0 00140000 + 59FF0
0012F4A0: 08F0D180
0012F4A4: 0067B6A9 00400000 + 27B6A9 (vegas50.exe)
0012F4A8: 0012F4BC 00030000 + FF4BC
0012F4AC: 0019A0E4 00140000 + 5A0E4
0012F4B0: 05020000 05020000 + 0
0012F4B4: 7C342151 7C340000 + 2151 (MSVCR71.dll)
0012F4B8: 02496030 02490000 + 6030
0012F4BC: 00000000
0012F4C0: 00000000
0012F4C4: 00000000
0012F4C8: 0000000F
0012F4CC: 00000000
0012F4D0: 00000000
0012F4D4: 00000000
> 0012F5B4: 7C35056A 7C340000 + 1056A (MSVCR71.dll)
> 0012F5B8: 0067CFA1 00400000 + 27CFA1 (vegas50.exe)
0012F5BC: 02496030 02490000 + 6030
0012F5C0: 0012F63C 00030000 + FF63C
0012F5C4: 00F48718 00F40000 + 8718
0012F5C8: 018EBFE8 018B0000 + 3BFE8
> 0012F63C: 00450053 00400000 + 50053 (vegas50.exe)
> 0012F640: 00550051 00400000 + 150051 (vegas50.exe)
> 0012F644: 004E0045 00400000 + E0045 (vegas50.exe)
> 0012F648: 00450043 00400000 + 50043 (vegas50.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0072EAA0 00400000 + 32EAA0 (vegas50.exe)
0012FFFC: 00000000

AnyOne knows what's up with that?

Comments

filmy wrote on 3/20/2005, 1:15 PM
Can't say for sure about the crash because I have not gotten this relative to EDL's - but I can say that I have done tests with the whole EDL thing and Vegas outputs something slighty different than PPro, and vice versa...this might be the issue. It is subtle to be sure. Look at this:

PPRO
TITLE: Sequence 01
FCM: DROP FRAME

001 001 B C 00:00:26:04 00:01:11:09 00:00:00:00 00:00:45:03
* FROM CLIP NAME: scene1.avi

Vegas
TITLE: Sequence 01
FCM: DROP FRAME
001 UNKNOWN V C 00:00:00;00 00:00:45;02 00:00:00;00 00:00:45;02
* FROM CLIP NAME: scene1

Ok - I have to point out a few things. First thing is that Vegas does not read TC info captured by Premiere so that is why the Vegas version shows in point of all zeros. Also Vegas does not care about "reel/tape number" thusly on EDL export all reel/tape info comes up as "unknown". Next the out points are one frame off (not a good thing!).

Now a few other things - Notice how PPro has "B" for type of edit. Because audio and video are brought over as one in this example. Vegas however breaks it down to Video edits (V) and audio edits (AA). Vegas does not seem to understand what "B" is, thusly will not bring it over to the timeline. It will find media and put it into the project but not place it on the timeline.

But there is something even more subtle...and it means when I take the Vegas EDL into PPro it can't find the media.

Take a look "side by side"



PREMIERE

001  001      B     C        00:00:26:04 00:01:11:09 00:00:00:00 00:00:45:03

* FROM CLIP NAME:  scene1.avi

VEGAS

001  UNKNOWN V      C     00:00:00;00 00:00:45;02 00:00:00;00 00:00:45;02

* FROM CLIP NAME: scene1

Now seeing things?

1> The spacing is a bit off.
2> Premiere names the file, Vegas drops the extension.

So first off - to get a Vegas file to read in PPro you need to go into the EDL and manually *add* add space after the "FROM CLIP NAME: scene1" part.

thusly:


* FROM CLIP NAME: scene1     = Wrong

* FROM CLIP NAME:  scene1    = Correct


Now PPro will still read it, however without the extension there is no real way of knowing what type of file it was. You will be asked to locate the file in both PPro and Vegas and you can assume it is an AVI but what if it isn't? And what if the audio is from, say, "scene1.wav" and not "scene1.avi"? Another bad thing the Vegas export script does (or doesn't do as it were).

But now you asked about the reverse - exporting from PPro and bringing into Vegas. More issues because, first, Vegas does not really care about time code info, this came as a pretty huge surprise to me when I found this out only a few weeks ago - Vegas goes off of the project time. Each edit you make is based on first frame of each edit in the project, not the actual time code of the media. So in this example we have the first cut happening at source time code 00:00:26:04 and project time code 00:00:00:00. But Vegas sees 00:00:00:00 as the time code of sources first frame, thusly the in point is based on 26 seconds and 4 frames *from* the first frame, which in this case Vegas thinks TC media start is 0, but Vegas is very wrong. So you will see, in this example, upon import that the audio is 45 seconds on the timeline however it is *not* correct. It starts 26 seconds into the cut and ends aprox 20 seconds after that because the shot I used here really is only 45:03 long...so if you follow me here...Vegas uses the audio it can find and when it ends it just fills in the empty space with blank audio.

Next thing you will notice is there is no video track - well there is, but it is all blank. Right clicking on the video will just show - nothing. Vegas does not bring in the video for whatever reason. Brings the clips in, loads first clip on timeline (wrong) and loads filler for everything else. Thus far no amount of editing seems to change a CMX EDL imported into Vegas - not even a CMX EDL that *comes from Vegas*.

So import from PPro to Vegas is sort of a null point.

I *wish* I could bring EDL's from Premiere into Vegas with no manual editing - but I can't, and believe me I have tried. And even more so for projects exported *from* Vegas.

As for your crash - again, it wouldn't surprise me if Vegas did crash with EDL import but trying to pinpoint why is another question as Vegas was not designed to import/export EDL's in the first place.

*EDIT* - Some formating issues and spelling.
kimgr wrote on 3/20/2005, 11:31 PM
So basically EDL import/export does not work in Vegas!?
That's to bad, as I've just accepted a job where all the material is already captured and pre-edited in Premiere...
Are there any 3rd party standalone applications that can convert Premiere projects or EDL's to Vegas?
filmy wrote on 3/21/2005, 6:34 AM
>>>Are there any 3rd party standalone applications that can convert Premiere projects or EDL's to Vegas<<<

Not directly, and not any "updated" that I am aware of.

For example - there is a Vegas EDL to After Effects plug-in available for 5 bucks. But, again, it not going from AE *to* Vegas and it has several limitations mainly because of how Vegas handles things.

Something new is called Handy Saw DS that just added Vegas EDL output. Sounds promising however right now it is just for scene detection. You bring in footage and it will detect scenes and output various formats such as Premiere or Vegas EDL. (The note here is that it only outputs to Vegas 4 EDL, Not vegas 5 - but there is a free Vegas 4 > Vegas 5 EDL convertor for download)

CuiBono makes a product called EDL Convert that had me excited because it offers CMX support as well as Vegas support. However they have kept this to an audio tool only. Video support is limited and gives almost the same results as just importing the PPro CMX export directly. For example one cut in a test EDL is aprox 12 seconds long. However source TC in at first frame is aprox 19 minutes. So in the conversion you get an error saying there are invalid TC's and they will be reset to zero (The Vegas issue I mentioned) and than you get the Vegas TXT.EDL conversion - with only one video entry that is 19 minutes long and shows up on the Vegas timeline as a 19 minute freeze frame. So this makes the product useless for what we are trying to do. Also even if it did work you have to manually locate each *video* file in the EDL, however when you get to the audio it it search an entire folder and auto update every file in the EDL that is in that folder. It would be a nightmare to use this for a feature film, or even a very fast moving music video or 30 second commercial.

There is some, now, very outdated software that could, in theory, work if you wanted to try a long work around over at ohmachi. But again, it would only be going from Vegas to Premiere...and that part sort of works anyway.

Just as a footnote this EDL issue is sort of ongoing and when Sony took over it took on another side because more people are looking at Vegas in a "pro" light. Some people have had very good results with exporting form Vegas and bringing into Avid. I tried this, sent out an EDL to someone to import on an Avid set up and, as I suspected, it was usless because Vegas does not care about source footage. Currently Vegas goes off the assumption that all project media will be in the same folder and the project and the EDL. On the other hand Vegas 5 offers support (or at least a good working relationship) with the XPRI system and the JH3. One can edit in Vegas 5 from a standard definition down convert off of a JH3, and create an EDL (edit decision list), which can be converted through XML file exchange into the Sony XPRI for conforming, or, the list can be converted to CMX style to use with another editor system of choice.

Here is an interesting little piece about EDL from 2003 in Acrobat format. Brief mention of Vegas 3 and the need for EDL support.

*EDIT* - some formating and spelling