I also do not have any instability issues related to using a Quad (QX6700). In fact, if a projects renders on my laptop Core 2 Duo system, it will also render with identical settings on the Quad - only exactly 2x faster.

Darren, wanting to see if there was a common denominator, I took your advise and trundled over to the COW.

I quickly scanned the first pageful - lots of interesting info, but I quickly realised I was not seeing what I wanted to see. So I put a search in on the 2 words "QUAD" and "Render". What came back was 17 threads. That's 17 over the whole of 2007, and 7 since VPro8's release in Sept 07. But within those were some rather supportive feedback on render time comparisons, stability and one example even showed the results from transferring from non-QUAD to a QUAD.

Now, Darren, I'll admit I may NOT have entered the most appropriate search words, over on the COW, so, to assist me please either supply links OR search criteria so I can read these and try and see if their is a common "theme". As we all know, common themes often provide a certainty and thence a potential cure! Then we all win! I have an investment in unearthing issues with QUADies, as I have a QUADIE too. Oh BTW, my QUADie does the JM Render Test in 2 mins. I'm editing daily and pushing the PC with many tracks and Fxs and Generated Media.

Let's see if we can discover a common denominator? Yeah?

Regards,

Grazie

Here's some:

http://forums.creativecow.net/readpost/24/874671

The second post in that thread would seem to indicate that SCS have admitted they have a problem with 24p footage from the Canon XH A1. ETA 2-5 months I think, that was in November 07

A Google using "vegas pro 8" crash quad got me a few hits on COW and DMN. One consistent complaint in multiple places is SCS's very bad tech support.

There might be some hope in something I heard about. It's somehow possible to run a single threaded app on multiple cores / CPUs by running a layer between the CPUs / cores and the OS. If anyone thinks this makes any sense I can find out more. It would for example explain how the OctoFlex can run Vegas on 8 CPUs at once. It'd probably be more stable as well.

Darren, if you're really screwed on this drop me a line and I'll see what I can do to help. There's not much room on my big Xeon system, it's all full of CS2 at the moment but I can hopefully squeeze a V8 install on there and we can try to rescue your project on that.

Bob.

I know a lot of people, running Vegas 8 Pro with Q6600 quadcore processors. Knowing and runing forums like www.vegasvideo.de, I am not aware of fundamental quadcore problems with Vegas 8 Pro. I have such a system too, and it is quite stable.

So, it would be interesting to learn some details about such problems. Sony can and will only help, if you are able to generate reproductions of the troubles. Otherwise they cannot analyse what is going on really.

I am running an Intel Quad Core 2 Duo QX6700 Extreme 2.66 Mhz overclocked to 3.24 Mhz on an Intel D975XBX2 motherboard with a BFG8800 NVidia Video card and a 650 watt Antec power supply.

I have never had a crash using Sony 8.0a Pro on this machine. It is the most stable machine I have ever used.

IMHO the stability is in great part due to using Intel's motherboard designed for the chip as well as a stable video card using the best and latest drivers they produce. Yes, yes, yes, the video card does not affect speed of render but video cards are always a major source of crashes. Best cards, best drivers are vital on video cards.

I will say, I can crash the system with no application running if I overclock higher than I am. I backed it down to be conservative.

I also have as much cooling (via fans) as I could. The motherboard cranks up the fans when needed. When rendering, the fans make it sound as if the computer is getting ready to take off! But really not that loud, just louder than normal.

David
www.EventVideoTeam.com

Hi

I have so far not have any problems with my new quad core on XP Pro, but have not used it much yet.

Could it be a combi of chipset, memory, os and GPU?

/Ulf

It'd help if people would fill in their system descriptions in their profiles. It would also help if the people having trouble would post specifics of their projects, and do this on all of their posts-not just once. Treat it like a signature at the end of your posts.

I can't count how many times I've seen a post merely saying "Vegas crashes on my project" without enough details to even think about it. It'd be good to know the project settings, length of the timeline, source of the media, types of media, etc.

Although less important, the same goes for projects that don't crash. It'd be helpful to see the differences.

Generally, it doesn't much matter how many people have crashes vs stability. It's good to know that Vegas can be stable-it's a ray of light at the end of Darren's dark tunnel. But if Vegas crashes a lot for some projects it needs to be addressed.

When Darren calls SCS he really needs to try to escalate the call to someone who can help. I've watched this same process with PPro and it takes a heck of a lot of pushiness but you can take your problems up the chain all the way to the project manager.

Rob Mack

I'm running a quad as well. I have had a few crashes but they're more memory related, as well as jpeg unfriendliness. I don't think I can trace any problems directly to the quad though.

I do however notice a lot of people running quads now so it's more likely just an issue of coincidence.

Could be coincidence, sure. Odds may favor that people with Quads have demanding projects that may expose flaws in Vegas.

I'm looking at a page on exception errors: http://www.updatexp.com/0xC0000005.html

The part that stands out to me is DEP (sometimes called XD in BIOS). Might be worthwhile to confirm that it's turned off.

Rob Mack

Question for ALL the people saying they're not having problems with Quads and Vegas. Are any of you editing 24p HDV from a Canon camera, more specifically the XH A1? Are you doing a longform project, mulitple tracks etc with that footage.

Bob.

No problems here, in fact I have just manged to capture (Scenalizer) from two separate DV devices at the same time with no lost frames. Need to find anaddtiona FW connector to try 3 captures at once

Also rendered a project from an attached USB drive on a separate PC, linking via a networked Fire wire cable,

But Darren's problem is not with DV projects.

Rob

"Question for ALL the people saying they're not having problems with Quads and Vegas. Are any of you editing 24p HDV from a Canon camera, more specifically the XH A1? Are you doing a longform project, mulitple tracks etc with that footage."
=============================================================
If you're narrowing this down to a specific format from a specific cam then can I ask how we are arriving at the conclusion that this is a quad problem?

Problems can be combinations of things. Certainly, the majority of people having this problem are on quads, but some people on quads don't have the problem, and some people on Duos have similar problems. So it'd be good to know more about the projects. Personally, I'd like to see the project details repeated on every post because after a while I don't know which post contains the info, and I can't remember stuff.

We assume it's a Quad problem because when Darren disabled 2 of the cores in BIOS Vegas' stability increased a lot.

Rob Mack

I've now followed Bob's lead and tried some search on the DVInfo site.

I tried :
1] QUAD and Vegas in the Canon A1 forum and got 8 hits - these were mostly about setup and as far as I read, not the issue under discussion here. Maybe somebody else wants to trawl through that too?

2] QUAD and Canon A1 in the Vegas Forum which brought back zero hits. Weird!

OK, what can I gather from this:

A] No apparent concern over there.

B] Those that have the 3 items - Quad + Vegas + A1 - appear to be missing from the forum as issues

C] I have the search parameters wrong!!!

Grazie

If you're looking for denominators, I would start posting how your Vegas render options are set up in the Video preferences

How many rendering threads do you have?
How much Dynamic RAM have you dedicated to to preview.

Hello everyone, and thanks again for your responses.

So, it seems there are also lots of quad core owners having zero problems which is encouraging.

Not sure why the forums aren't picking up more regarding quad core problems ... you can read lots of responses to my previous post from a week or two ago on this forum with exception errors being reported by quad core owners if you want to.

I've tried every different combination of render options including different numbers of render threads, changed the Dynamic RAM for preview (but isn't that only relevant to the amount of memory Vegas is allowed to use when building a Dynamic RAM Preview on the timeline ... that shouldn't have anything to do with how well Vegas Renders or otherwise ... ???? What the????)

I've also managed to gain a substantial increase in stability by turning off the Secondary Cores in BIOS to turn my machine into a Dual Core effectively ... but I've been over all of that a hundred times in my other posts which no-one seems to be able to find so I'm not going back there.

In the mean-time I've generated another interesting error while setting up scrolling titles in the Pro-Type Titler! (Isn't it nice to finally have a really good quality title program to work with in Vegas - great job guys ... truly ... reminds me of the Titler in Ulead Media Studio Pro from 1995! ... why has it taken so long? I have no idea ... but at least it's here now ... anyway, back to the problem ... )

Here's an error generated when re-opening a scrolling title on my virtually useless quad core Vegas Pro 8 workstation.

But guess what ... this error is an 'Unhandled Exception' reporting the type 'System.OutOfMemoryException' and the error is happening in Microsoft .NET Framework!

Very interesting considering I have 4GB of RAM and very little else running on this machine. And yes, I have filled out my system details on this forum if anyone from Sony wants to have a look - including my video card RAM etc etc etc

Maybe it's the .NET Framework on my machine and not Vegas???

What the hell's going on?

Here's the error:

--------------------------------------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.TransformBoundingBox(RectangleF rect1, Matrix2D mtx)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.CalculateBoundingBox(GraphicsState gs, Boolean applyModifiers, Boolean storeCalculatedValue, List`1 topMostNodes)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.GetBoundingBox(GraphicsState gs)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.onHittest(Int32 x, Int32 y, Boolean dragdropTest, Matrix2D mtxInitial)
at Sony.MediaSoftware.TextGen.CoreGraphics.Node.OnHittest(Int32 x, Int32 y, Boolean dragdropTest)
at Sony.MediaSoftware.TextGen.CoreUI.WidgetHost.form_Hittest(Int32 x, Int32 y, Boolean dropTest)
at Sony.MediaSoftware.TextGen.CoreUI.WidgetHost.updateHittest(Int32 x, Int32 y)
at Sony.MediaSoftware.TextGen.CoreUI.WidgetHost.form_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at Sony.MediaSoftware.TextGen.ControlLibrary.WidgetHostControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Interop
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/Interop.DLL
----------------------------------------
CoreGraphics
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreGraphics.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
CorePrimitives
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CorePrimitives.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
CoreGraphics.XmlSerializers
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreGraphics.XmlSerializers.DLL
----------------------------------------
PresentationCore
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.0 (vista_rtm_wcp.061020-1904)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/PresentationCore/3.0.0.0__31bf3856ad364e35/PresentationCore.dll
----------------------------------------
WindowsBase
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.0 (vista_rtm_wcp.061020-1904)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
WidgetLibrary
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/WidgetLibrary.DLL
----------------------------------------
CoreUI
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreUI.DLL
----------------------------------------
CoreUI.XmlSerializers
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/CoreUI.XmlSerializers.DLL
----------------------------------------
System.Data.SqlXml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Data.SqlXml/2.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
ControlLibrary
Assembly Version: 1.0.0.179
Win32 Version: 1.0.0.179
CodeBase: file:///C:/Program%20Files/Sony/Vegas%20Pro%208.0/ControlLibrary.DLL
----------------------------------------
fzghfljh
Assembly Version: 1.0.0.179
Win32 Version: 2.0.50727.832 (QFE.050727-8300)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

thanks for updating the system info.

did you ever get a chance to look into disabling DEP?

Rob Mack

"I've now followed Bob's lead and tried some search on the DVInfo site."

Searching that way is going to tell you nothing.
There's one post on COW that says SCS have said the problem relates to Canon HDV 24p footage from their A1. This could be true or could be utter BS, I haven't a clue but it's SOMETHING to start with.
Now, who here posts what camera the footage came from, heck half the people saying they don't have a problem are editing DV!
Statistically the only way to verify the theory is for people editing HDV in V8.0a from a Canon XH A1 that shot 24p to tell us if they have or haven't a problem and they have to be using a quad core CPU. If you're using a V1 and shooting 24p and are or aren't having a problem tells us nothing. It might be a different problem or not. Keep in mind that Canon cameras in 24p record a different kind of HDV, that's a significant fact.

I've just been through a similar kind of nightmare with the software i write. Suddenly 3 out of 60 sites have a problem with a fatal exception, in one line of code that's used multiple times in the app, that has run for 10 years without a glitch. Fortunately the company I contract to has a pretty decent computer room and run virtual machines with every version of Windows with every variance of service packs and every version of Office with every variant of service packs. That's a friggin lot of variants. They tracked the problem to one unique combination of all of those.

Bob.

Thanks Rob,

Yes, I did have a look at disabling DEP ... no joy, the BIOS doesn't support DEP and the software DEP in System / Advanced / Performance / Settings / blah blah ... I was given the option of turning ON DEP except for the programs listed ... so I listed Vegas Pro 8a exe and it's still bad ... here's the latest exception ... have hardly got any work done on this project.

Cheers,

Darren

------------------------------------------------

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0xFE000008 IP:0x5980E2
In Module 'vegas80.exe' at Address 0x400000 + 0x1980E2
Thread: GUI ID=0x228 Stack=0x13E000-0x140000
Registers:
EAX=00000000 CS=001b EIP=005980e2 EFLGS=00010202
EBX=00000001 SS=0023 ESP=0013efb0 EBP=0013f2d0
ECX=3ce037e8 DS=0023 ESI=fe000000 FS=003b
EDX=00000001 ES=0023 EDI=34bc4e10 GS=0000
Bytes at CS:EIP:
005980E2: 8B 5E 08 3B 5C 24 18 75 .^.; 005980EA: 0F 8B 5E 0C 3B 5C 24 1C ..^.;Stack Dump:
0013EFB0: 00000001
0013EFB4: 0013EFF8 00040000 + FEFF8
0013EFB8: 34BC4E10 347D0000 + 3F4E10
0013EFBC: 00000000
0013EFC0: 005988E5 00400000 + 1988E5 (vegas80.exe)
0013EFC4: 34BC4E10 347D0000 + 3F4E10
0013EFC8: 00000564
0013EFCC: 00000000
0013EFD0: 0013F0E0 00040000 + FF0E0
0013EFD4: 34831AA0 347D0000 + 61AA0
0013EFD8: 0000000D
0013EFDC: 0049E29B 00400000 + 9E29B (vegas80.exe)
0013EFE0: 34BC4E10 347D0000 + 3F4E10
0013EFE4: 0013EFF8 00040000 + FEFF8
0013EFE8: 0013F028 00040000 + FF028
0013EFEC: 00000000
> 0013F010: 0049FC46 00400000 + 9FC46 (vegas80.exe)
0013F014: 00000564
0013F018: 00000000
0013F01C: 0013F0C4 00040000 + FF0C4
0013F020: 0013F174 00040000 + FF174
> 0013F16C: 77F53020 77F10000 + 43020 (GDI32.dll)
> 0013F180: 00630000 00400000 + 230000 (vegas80.exe)
0013F184: 00000000
> 0013F188: 0C2D5780 0C1B0000 + 125780 (wavplug.dll)
0013F18C: 00000003
0013F190: 0DEC027F 0DE00000 + C027F
0013F194: 00000000
0013F198: 02FAF080 02DF0000 + 1BF080
> 0013F1A4: 027F64A8 02660000 + 1964A8 (CFHD.dll)
- - -
0013FFF0: 00000000
0013FFF4: 00000000
0013FFF8: 0083C9AB 00400000 + 43C9AB (vegas80.exe)
0013FFFC: 00000000

Here's another one for you ...

What the hell is going on??

Darren Powell

--------------------------------------------------------

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x42C3C8 IP:0x7C9321F1
In Module 'ntdll.dll' at Address 0x7C900000 + 0x321F1
Thread: ProgMan ID=0x1634 Stack=0x3848000-0x38F0000
Registers:
EAX=00426298 CS=001b EIP=7c9321f1 EFLGS=00010202
EBX=11f734b2 SS=0023 ESP=03848f7c EBP=03848fac
ECX=000057a8 DS=0023 ESI=11f734aa FS=003b
EDX=5250c8be ES=0023 EDI=2357db60 GS=0000
Bytes at CS:EIP:
7C9321F1: 89 B4 01 88 09 00 00 5E .......^
7C9321F9: B0 01 5B 5F C9 C3 B8 00 ..[_....
Stack Dump:
03848F7C: 2357DB68 22AE0000 + A9DB68
03848F80: 00000000
03848F84: 00140000 00140000 + 0
03848F88: 31C0FE0E 31AC0000 + 14FE0E
03848F8C: 5250C8BF 524A0000 + 6C8BF
03848F90: 705FFE0D 70540000 + BFE0D
03848F94: 5250C8BE 524A0000 + 6C8BE
03848F98: 00000000
03848F9C: 00000001
03848FA0: 77A64D59 77A20000 + 44D59 (cscui.dll)
03848FA4: 00000000
03848FA8: 0015F730 00140000 + 1F730
03848FAC: 03849070 037F0000 + 59070
03848FB0: 7C931C7C 7C900000 + 31C7C (ntdll.dll)
03848FB4: 038490B0 037F0000 + 590B0
03848FB8: 0000001D
> 03848FFC: 7C9131DC 7C900000 + 131DC (ntdll.dll)
> 03849000: 7C913212 7C900000 + 13212 (ntdll.dll)
> 03849004: 7C913281 7C900000 + 13281 (ntdll.dll)
> 03849008: 7C913288 7C900000 + 13288 (ntdll.dll)
> 03849034: 7C913288 7C900000 + 13288 (ntdll.dll)
> 03849064: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 03849068: 7C910570 7C900000 + 10570 (ntdll.dll)
> 03849074: 7C9109BC 7C900000 + 109BC (ntdll.dll)
> 03849088: 7C910992 7C900000 + 10992 (ntdll.dll)
> 03849098: 7C80B57C 7C800000 + B57C (kernel32.dll)
> 038490BC: 01203D58 01150000 + B3D58 (vegas80k.dll)
> 038490C0: 7C900000 7C900000 + 0 (ntdll.dll)
038490C4: 0384917C 037F0000 + 5917C
038490C8: 00000104
038490CC: 00000000
> 038490E4: 009910F4 00400000 + 5910F4 (vegas80.exe)
038490E8: C0000005
038490EC: 00000000
038490F0: 00000000
038490F4: 00000000
> 03849110: 7C902000 7C900000 + 2000 (ntdll.dll)
> 03849114: 7C900000 7C900000 + 0 (ntdll.dll)
> 03849128: 01000000 00400000 + C00000 (vegas80.exe)
0384912C: 00000000
03849130: 00000000
03849134: 00000000
03849138: 00000000
> 03849284: 00403027 00400000 + 3027 (vegas80.exe)
03849288: 038492A0 037F0000 + 592A0
0384928C: 00001000
> 03849290: 009910F4 00400000 + 5910F4 (vegas80.exe)
03849294: 0384C2E4 037F0000 + 5C2E4
03849298: 000000FF
0384929C: 00000000
> 038492C4: 20296E6F 20000000 + 296E6F (xpsp2res.dll)
> 0384C27C: 7C910833 7C900000 + 10833 (ntdll.dll)
> 0384C280: 0083C082 00400000 + 43C082 (vegas80.exe)
- - -
038EFFF0: 00000000
038EFFF4: 00525180 00400000 + 125180 (vegas80.exe)
038EFFF8: 00AD8658 00400000 + 6D8658 (vegas80.exe)
038EFFFC: 00000000

OK,
Darren but you still haven't answered one question. From which camera is your HDV??? And what frame rate???

Bob.