New User - Vegas Movie Studio - Repeated Crashes.

cg7aa wrote on 6/27/2010, 3:46 PM

I bought Vegas Studio 9 recently and have had a dismal experience so far, I just cannot get it to run for anything length of time, usually during normal editing or more commonly when importing media, it simply crashes and shuts down: an error occured during the current operation, an exception occured.

I'm new to all of this and I'm finding it quite trying, I've reinstalled as advised and even tried older versions of quicktime without any luck

Here is the error message I get, I would be grateful for any advise or help experienced users can offer me. Thanks.

Vegas Movie Studio 9.0
Version 9.0b (Build 66)
Exception 0xC0000005 (access violation) READ:0xA054000 IP:0x6691DDEA
In Module 'QuickTime.qts' at Address 0x66800000 + 0x11DDEA
Thread: ProgMan ID=0x808 Stack=0x254E000-0x2550000
Registers:
EAX=0a0566bc CS=001b EIP=6691ddea EFLGS=00210206
EBX=00000000 SS=0023 ESP=0254e708 EBP=0254e710
ECX=000009af DS=0023 ESI=0a054000 FS=003b
EDX=00000000 ES=0023 EDI=04e52664 GS=0000
Bytes at CS:EIP:
6691DDEA: F3 A5 FF 24 95 04 DF 91 ...: 66 90 8B C7 BA 03 00 00 f.......
Stack Dump:
0254E708: 0254E760 02450000 + FE760
0254E70C: 0254E734 02450000 + FE734
0254E710: 0254E74C 02450000 + FE74C
0254E714: 66869FF4 66800000 + 69FF4 (QuickTime.qts)
0254E718: 04E51AF0 04B10000 + 341AF0
0254E71C: 0A05348C 09FF0000 + 6348C
0254E720: 00003230
0254E724: 6689856F 66800000 + 9856F (QuickTime.qts)
0254E728: 0A05348C 09FF0000 + 6348C
0254E72C: 04E51AF0 04B10000 + 341AF0
0254E730: 00003230
0254E734: 0A0405EA 09FF0000 + 505EA
0254E738: 00003230
0254E73C: 0000000C
0254E740: 6686A000 66800000 + 6A000 (QuickTime.qts)
0254E744: 669F0E25 66800000 + 1F0E25 (QuickTime.qts)
> 0254E750: 669F0E56 66800000 + 1F0E56 (QuickTime.qts)
> 0254E770: 669C1E06 66800000 + 1C1E06 (QuickTime.qts)
> 0254E7AC: 669C2458 66800000 + 1C2458 (QuickTime.qts)
> 0254E7EC: 669C3B9D 66800000 + 1C3B9D (QuickTime.qts)
> 0254E800: 76616C75 76600000 + 16C75 (CSCDLL.dll)
> 0254E828: 669C3C3A 66800000 + 1C3C3A (QuickTime.qts)
> 0254E83C: 76616C75 76600000 + 16C75 (CSCDLL.dll)
> 0254E84C: 668981E6 66800000 + 981E6 (QuickTime.qts)
> 0254E874: 76616C75 76600000 + 16C75 (CSCDLL.dll)
> 0254E88C: 669C3C00 66800000 + 1C3C00 (QuickTime.qts)
> 0254E8A4: 6691C3C0 66800000 + 11C3C0 (QuickTime.qts)
> 0254E8A8: 77B049EA 77A80000 + 849EA (CRYPT32.dll)
> 0254E8B4: 34FCDCBE 34EA0000 + 12DCBE (qt7plug.dll)
> 0254E8DC: 34EBB7DD 34EA0000 + 1B7DD (qt7plug.dll)
> 0254E8F0: 76616C75 76600000 + 16C75 (CSCDLL.dll)
> 0254E914: 34EBC9C0 34EA0000 + 1C9C0 (qt7plug.dll)
> 0254E958: 34EC35A4 34EA0000 + 235A4 (qt7plug.dll)
> 0254E96C: 34EBD36C 34EA0000 + 1D36C (qt7plug.dll)
> 0254E9A8: 7C42E090 7C420000 + E090 (MSVCP80.dll)
> 0254EA50: 00A9005B 00400000 + 69005B (VegasMovieStudio90.exe)
> 0254EA54: 00720075 00400000 + 320075 (VegasMovieStudio90.exe)
> 0254EA58: 005D006C 00400000 + 1D006C (VegasMovieStudio90.exe)
> 0254EA5C: 34EB0000 34EA0000 + 10000 (qt7plug.dll)
0254EA60: 00000000
0254EA64: 00000000
0254EA68: 0024BEE8 00150000 + FBEE8
> 0254EA7C: 34EBD689 34EA0000 + 1D689 (qt7plug.dll)
> 0254EA98: 35019630 34EA0000 + 179630 (qt7plug.dll)
> 0254EAA0: 003A0043 00350000 + 50043 (sfwbdmux.dll)
> 0254EAA4: 0044005C 00400000 + 4005C (VegasMovieStudio90.exe)
> 0254EAA8: 0063006F 00400000 + 23006F (VegasMovieStudio90.exe)
- - -
0254FFF0: 00000000
0254FFF4: 005282F0 00400000 + 1282F0 (VegasMovieStudio90.exe)
0254FFF8: 00AF3D58 00400000 + 6F3D58 (VegasMovieStudio90.exe)
0254FFFC: 00000000

Comments

MSmart wrote on 6/27/2010, 10:33 PM

Hi, welcome to the forum. What are your PC specs and what type of video (format) are you working with?

Eugenia wrote on 6/28/2010, 9:15 AM

cg7aa wrote on 6/28/2010, 1:01 PM

Hi MSmart,

My PC specs are as follows:

XP Professional
AMD Athlon XP 3200+ ~2.2gHZ
2048Mb RAM.

I appreciate that it's an old machine but having said that, should any software be crashing like that? I would expect it to run quite slowly but not implode everytime I tried to use it.

The video format I'm working with is .mp4. The files come off my Aiptek camcorder in .MOV form but to get Vegas 9.0 to import the clips with sound, I have to rename the files to .mp4 manually before import.

cg7aa wrote on 6/28/2010, 1:03 PM

Why is Quicktime such an almighty pain then? It's been nothing but that in my experience I'm afraid.

cg7aa wrote on 6/28/2010, 1:04 PM

"Which is why we have to transcode to another format before we can edit such files... "

Could you please educate this idiot on how to do such 'transcodes'?

drw wrote on 6/28/2010, 2:06 PM

Quicktime and pre-Vegas 10 is not a good mix. If you're using a camera that shoots in h.264 MOV format, and therefore the Quicktime decoder is used for these, you will get crashes after putting a few too many clips in the timeline or the media bin.

Hi, I'm new here and have been editing small clips from a Canon S90 that produces .MOV files and haven't seen any problems yet. By "a few too many clips" how many do you mean? My normal process is to edit the clips individually, or in very small groups of 2 or 3, then render to mpg and eventually assemble the mpgs into a DVD later. I'm using 9.0b, have I just been lucky, or is the fact that I never have more than 3 files in the timeline at any one time the reason I haven't run into this problem already.

Edit: Last night I brought 20-25 .MOV files into the timeline, made random edits, transitions, etc. and rendered to MPEG-2 without any problems at all. The clips were all fairly short, the rendered file was about 1.2GB. So I'm just not seeing the problems claimed with VMS9 and H.264 format, are those of you having troubles doing larger projects, or using the Platinum version with AVCHD files (mine are not HD, maybe that's the difference)

cg7aa wrote on 6/30/2010, 1:49 AM

dwalby, I've been getting my crashes usually when I'm importing the third or fourth clip into the project area or the trimmer area. The files I've been importing are all fairly small (on average 30Mb each) and they are not HD either. I'm running standard 9.0b too.

Have you tried importing .mp4 files rather than .MOV files?

drw wrote on 6/30/2010, 4:16 PM

I'm importing the .mov files directly without any problems. I saw you are renaming them to .mp4 because of an audio problem with .mov format, I don't have to do that. I'm not sure if .mov and mp4 are interchangable, they are slightly different file formats, but I don't know enough about the small details to say if you can just change the extension and bring them in. That may be what's causing the crash. I'd try to figure out why the native .mov format files don't have audio, perhaps you need to download a later version of Quicktime.

I guess all I can say at this point is I am able to bring in any number of .mov files, assemble them on the timeline, and render them to another output format without any problems. I've done it numerous times, and never had any problems at all. I'm also running on a low-spec platform with 2G of RAM, but I'm on Vista instead of XP. I don't think the OS should make any difference, but mention it because I seem to recall seeing something else about XP only supporting up to a certain release of a particular driver or something (sorry it wasn't important at the time so I didn't pay much attention to it, just remember reading it). My only suggestion is to try to fix the .mov audio problem rather than change the extensions to .mp4 and try to fix the crashing problem.

I'll also check my Quicktime version and reply back with an edit to this post later, you can compare your version to the one I'm running to see if they're the same or not.

Edit: Quicktime version is 7.6.4. Also, when I select one of the .MOV files here are the format specifics: video 640x480x24 30.000 fps progressive H.264, audio 44,100Hz, 16bit, mono, 16-bit little endian.

MSmart wrote on 6/30/2010, 4:45 PM

@cq7aa, you'll find this thread interesting as it mentions video from Aiptek camcorders:

LINK

It's all about what "flavor" .MOV file is created by the camera and whether or not the editing app supports it. dwalby's Canon S90 creates a .MOV file that VMS likes.

Try downloading the trial version ov VMS 10 to see if it likes your Aiptek .mov files better.

cg7aa wrote on 7/1/2010, 3:09 AM

MSmart,

This may sound a bit daft but when you say "Try downloading the trial version ov VMS 10" do you mean Vegas Movie Studio HD Platinum 10? I wanna make sure we are talking about the same thing.

Thanks.

drw wrote on 7/1/2010, 9:58 AM

Which Aiptek camcorder model are you using? I looked at one of them online and the video format it used was a bit weird, like 11 fps in VGA resolution. It may be that the problem is not with the compression standard being used, it may be the video/audio formats are odd to begin with. If that's the case you may be able to convert it to something more common before importing it into VMS. This has already been recommended in a prior post, but before doing that you need to figure out what format you have to begin with.

MSmart wrote on 7/1/2010, 10:07 AM

do you mean Vegas Movie Studio HD Platinum 10?

Yes.

cg7aa wrote on 7/1/2010, 3:10 PM

dwalby,

I'm using the Aiptek AHD300 High Definition (1080P) Camcorder. See here for details:

http://www.aiptek.com.tw/c0_1.php?bid=2&cid=5&pid=1

MSmart wrote on 7/1/2010, 3:29 PM

Which resolution setting are your files?

HD 1080p (1440x1080)
HD 60f (1280x720)
HD 30f (1280x720)
D1 60f (720x480)

I think it's safe to say that regardless of setting, the .mov files your cam produces won't play in v9 VMS unless you transcode as Eugenia suggested. Try the v10 trial as I suggest before you have to go down that road.

However, according to THIS thread, you may be out of luck with v10 with your flavor of H.264/AVC files.

drw wrote on 7/4/2010, 9:16 AM

This is a combination of an editorial rant, and request for clarification from experts if my understanding is incorrect.

What appears to be happening here is the H.264 standard has so many possible variations, Sony has implemented many, but not all of them in VMS. I spent a little time researching H.264 and from what I can gather it groups various processing algorithms into 17 different "profiles" defined by the spec. Add to that the different video resolutions available in both HD and non-HD, plus the many different audio settings allowed by AAC, and the permutations number in the thousands.

Its my understanding that the primary purpose of standards is to ensure that all manufacturers can comply to a common requirement when implementing products, thus promoting interoperability between various products and manufacturers. It appears that the authors of H.264 lost sight of this goal and allowed far too many options within a single standard. I assume the manufacturers decided it would be too expensive and time consuming to fully cover all the possible H.264 video/audio combinations, so they each decide which permutations to implement, and leave some out that they feel will be less commonly encountered. But they all put the same H.264 compliant sticker on the product. So now the consumer can't tell which subset of H.264 modes are being implemented by any manufacturer, but the products still get labeled as H.264 compliant so they think they're buying products that are compatible and interoperable when in fact they are not. This seems like the whole point of the standard got missed.

It would also seem that the simple solution to this problem would be to divide the H.264 standard into sub-groupings, which could then be designated with additional letters or numbers to indicate the sub-group. Then manufacturers could decide which sub-groups they support, and label their products accordingly. This might make it easier for the consumer to figure out which products will actually work together and which will not.

Again, if my understanding of the H.264 standard is incorrect, please feel free to correct me, I'm interested in learning more about the implementation details.

musicvid10 wrote on 7/4/2010, 9:58 AM

cg7aa,
You said "Vegas Movie Studio 9." I hope you mean the Platinum version, otherwise HD editing is not officially supported afaik.

I don't see where you said what version of Quicktime you are using.
You need 7.6.2 or earlier, because later version all have compatibility problems with VMS 9.

You are already doing the right thing by renaming the file extension from .mov to .mp4. More detail here:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=12&MessageID=687896

drw wrote on 7/4/2010, 2:14 PM

I don't see where you said what version of Quicktime you are using. You need 7.6.2 or earlier, because later version all have compatibility problems with VMS 9.

FWIW, I'm using version 7.6.4 with VMS9.0b, and its working just fine with the .MOV files my Canon P&S spits out. I have read about the later QT versions having compatibility problems, but maybe that's with HD formats, I don't know. I've edited dozens of non-HD .MOV files with 7.6.4 installed and haven't seen any problems at all.

Also, the original poster was having problems with non-HD files IIRC.

musicvid10 wrote on 7/4/2010, 5:04 PM

That's excellent that 7.6.4 is working for you on VMS 9. I can assure you that is not a typical experience, although it is not unheard of either. The issues with 7.6.4 (and later) QT libs with all Windows NLE's (not just Vegas) are well documented here on these forums, and on the internet. The problems range from loss of audio to exceptions to BSOD. So you're either lucky or living right.

The OP is using an HD capable camera, although whether the files are HD or SD in itself makes absolutely no difference where there is a QT / Vegas version conflict. It does make a difference if one is looking to edit HD video on a Vegas version that does not support it.

The issues of QT 7.6.4 with VMS 9 was important enough to Sony for them to construct a Knowledgebase article, and also to issue a driver patch (which they rarely do), that incidentally did not work so well either.

http://www.custcenter.com/cgi-bin/sonypictures.cfg/php/enduser/std_adp.php?p_faqid=4787&p_created=1254146741&p_sid=S4l3y54k&p_accessibility=0&p_redirect=&p_lva=4787&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9OCw4JnBfcHJvZHM9MTcsNjU5JnBfY2F0cz0mcF9wdj0yLjY1OSZwX2N2PSZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PW1wNA**&p_li=&p_topview=1

That article is also linked to in the thread I referenced two posts up. Makes for interesting reading.

cg7aa wrote on 7/5/2010, 6:12 AM

First off, let me say I appreciate all the help I am being given. Thanks very much to everyone.

MSmart - you were spot on with your conclusion that "it's safe to say that regardless of setting, the .mov files your cam produces won't play in v9 VMS".

I reassured myself that my VMS 9 installation was not suspect by successfully importing several .MOD clips from another camcorder without a single crash. I tried my .MOV files again and hey presto, VMS gave up the ghost as it has been doing.

I then got Vegas Movie Studio HD Platinum 10 (trial version) as you suggested and although it froze on me once (but not crashed like VMS 9), I was able to import the .MOV files (albeit renamed to .mp4) and manipulate them for several hours without any problems at all.

dwalby - I think you have a point in your 'rant'.

musicvid - I'm not using the platinum version of VMS 9 just the standard version, the clips I've been working with are not HD either. Although the camcorder is HD capable, my old PC really struggles with the format so I'm sticking with the 'D1 60f (720x480)' res for now till I get a new machine sometime this year.

Incidentally, tech support got me to try QT 7.6.2 and earlier with VMS 9, standard all to no avail. Then they suggested, it was something to do with QT access permissions, at which point I gave up listening to them. They ought to read the forums for user knowledge.

Now, can I upgrade VMS 9 to 10 or is that not advisable? I suspect I would have to accept that VMS 9 (if want to use my camcorder) is a non-starter and I will have to spend again and get VMS 10.