JPEG import crashes my system

CFong wrote on 7/5/2007, 5:01 PM
I'm new to Vegas 7, but we've used VV4 for audio production without doing video for several years.

I'm trying to import a jpeg into my timeline. I've tried selecting it in explorer, dragging it and other permutations, but each time Vegas crashes with an error "The application has encountered a fatal exception and will close".

I've tried several different jpegs and get the same results. Box is running XP.

A thumbnail of the jpg does get placed in the timeline, but the error box doesn't let me get any farther -

And the error details offered start out:
System.Data.SqlTypes.SqlTypeException: SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.

My jpeg file dates are certainly within that range, so what's really causing the crash?

Other than that, this program is way cool for cutting video - I spent years doing NLE in 16mm film and videotape and I'm just thrilled with Vegas for Video so far.

Carla

Comments

rmack350 wrote on 7/5/2007, 5:54 PM
It looks to me like it's a problem with the media manager. As a workaround you could try turning it off in the preferences.

Are you running Windows XP or is it Vista? (Vista is a problem for the Media manager, and Vegas 7 isn't supported under Vista)
Was it just one jpeg or several at a time?
Have you tried resaving one of the jpegs in some other image editor? (Preferably not the one that created it...)

Hope this is a start.

Rob Mack
CFong wrote on 7/5/2007, 7:57 PM
Rob,

Disabling the Media Manager as a workaround did the trick - thanks 1000x! Hope a software developer can reproduce my problem and fix it in the next release.

Also, re-reading my post - I haven't been doing NLE - Vegas is my first NLE experience, the rest was linear... very linear. Cutting and conforming 16mm film or assembling videotape with a Convergence editor and 3 sony U-Matics.

VegasVideo is a great improvement...

Vegas doesn't like Vista? Another good reason not to 'upgrade'.

Carla
UlfLaursen wrote on 7/5/2007, 8:09 PM
Hi Carla,

Yes, Vegas does not support Vista yet, so I would stay on XP so far.

/Ulf
rmack350 wrote on 7/5/2007, 9:45 PM
Much of Vegas 7 works in vista but the media manager requires a windows component that is superseded by something else in Vista. I'm just parroting things I've read here. No first hand experience. People do get V7 to work in Vista.

Disabling the media manager is a good short term fix but as you start to get lots of media on your computer the media manager can be really useful, so you want to fix the jpeg problem.

I can think of a few causes. Maybe jpeg images have a default handler of Photoshop6 on your system, which can actually cause a problem (explorer crashes in my case), or maybe they're coming straight from a camera that writes them in an unexpected way, or from an image editor that does something similar. I'd do some searches here and on google, especially google groups. but start here first since Vegas is the program that's exposing your JPEG problem.

Rob Mack
Spot|DSE wrote on 7/5/2007, 10:32 PM
Additionally, how large are the JPEGs you're importing to the timeline? Some systems cannot manage extremely large JPEGs imported to the Vegas timeline.
rmack350 wrote on 7/6/2007, 9:38 AM
I don't think anyone at Madison is going to fix this if it isn't a common problem.

Go find one of the jpegs in Explorer and check it's properties. You should see two date fields for Created and Modified dates. Maybe one of these is empty or illegal. Most programs wouldn't have a problem but it sounds like an SQL component of the media manager doesn't like a date in your jpeg files. The media manager get's both of these dates and tries to enter them in it's database.

Resaving the jpeg files ought to fix the date fields. If all you wanted was to reset the dates, there are freeware tools that can do that. Perhaps a port of the Unix "Touch" command.

I use a shareware file explorer called Explorer2 (www.zabkat.com) that has an attribute editor under its Actions menu. Might be more generally useful than finding a touch command utility somewhere.

Rob Mack