[Nigel O’neill]

If you are certain your files are under the DVD size limit and DVDA reports it is too large, select make DVD and ignore the warnings and then select Prepare. Complete all the steps so that DVDA creates the image to a folder. If you go into Make DVD again, you should notice DVDA reports the correct disc size. You can choose to Prepare the DVD again.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Are you using the latest version of 9 pro? Is there an associated error message with the shutdown? Have you tried reporting the issue to Sony?

[Nigel O’neill]

Shirley

There is no Sony conspiracy to phase out DV as you suggested. You could give this a go. Info provided by Mike in another post:

There have been several reports about firewire issues with Windows 7.

•Go to Device Manager and click on IEEE 1394 Bus host controllers
•Click on the device listed underneath this heading. In my case it was NEC 1394 OHCI Compliant Host Controller
•Right click this device and select ‘update driver software’ from the shortcut menu
•Then select the option ‘browse my computer for driver software’
•Then select the option ‘let me pick from a list of device drivers on my computer’
•This then gave me three drivers to pick from (make sure the’show compatible hardware’ checkbox is ticked
•Select the driver named ‘1394 OHCI Compliant Host Controller (Legacy)’
•Install driver.

If you don’t want to do that, try hooking up your camera to another computer that has firewire. If you have a DV line protector, make sure you use it. If not, you risk blowing up the firewire board in the camera, not the PC. If it is already blown, chances are the other computer will not detect it. A camera repair is most likely necessary.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

If your other computer has a firewire port, you could try plugging it in and seeing if it is detecting the camera. If not, a blown firewire board in the camera could be the issue. That caused a lot of grief for Sony FX1 users back in 2005, which made me go out and buy a Kramer DV line protector.

If you have blown the firewire board in the camera, and it is still under warranty, you could try and get it repaired for free, otherwise a new internal board for the camera could be on the cards. They are not cheap because of the labour that is involved in replacing them.

I don’t believe your firewire port on the laptop is damaged, and neither is Vegas. You can check the status of the firewire port in Windows device manager.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

I don’t use Cineform and regularly edit HDV, MXF and AVCHD in a multi-cam situation using Vasst Ultimate S Quadcam. Even on my i7 970, I cannot set the preview higher than Preview Auto. I can set it to best/good Auto, but the preview chokes up and transitions/FX are hard to preview. Interestingly, adding an external monitor has had some negative effect on the preview, but I put up with it as at least I can see what I am doing!

I was expecting more when I upgraded from an i7 920 to an 17 970, as the raw specs seemed to suggest double the grunt, but I only see about a 20% improvement. Well, at least the render times are much shorter.

I have to admit I had no preview issues with SVP V8, and only noticed them in V9 and even more so in V10. Having a 64-bit system has not helped one iota IMHO when it comes to preview lag. I no longer get out of memory errors with Vegas x64 though.

Alf, if you really want to test your system, you can try loading 4,000 small jpg images of a time lapse sequence of a duration of 1 frame 🙂 Even in a single track project with no FX, it brought my entire system to its knees. Preview was laggy. About 20 seconds between each adjustment on the timeline.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Great explanation, Dave! Are you suggesting a fire store drive be used?

[Nigel O’neill]

Can’t believe I missed that one, despite looking at the specs which I now realize were presented in quite a misleading way. However, further down the page is a screen shot taken from the Nero Info tool. Yup, your drive is only a reader:

https://www.cdrlabs.com/Reviews/lite-on-ihes208-8x-blu-ray-combo-drive/Features.html

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

What version of DVD Architect are you using?

Personally, I have had 100% success with BD-RE discs. I get nothing but coasters with BD-R. Strange but true.

Just as a test, can you burn Blu-ray from Nero, Roxio or similar third party burning tools?

Nigel

[Nigel O’neill]

Steve

At a minimum you need the XpressCard slot. Mike is correct in that the USB -> Firewire is a waste of time. I’ve been down that path. Good high-end laptops support XpressCard.

[Nigel O’neill]

If you can capture in DV but not HDV, your down convertor on the camera may be set to HDV->DV.

On the XHA1, unplug firewire cable. In signal settings, make sure playback is set to auto, and also make sure down convert is not set to on if you’re trying to capture HDV.

Switch off A1 and connect firewire cable, switch on the A1