I have used it from within Vegas but do not routinely do so. Vegas handles 99% of my needs on its own.

Just reduce the dpi to 72. 300 is only for printing.

Rick Diaz: Sure you have read the whole thread?

I must have a big resolution. My output will be 1280x720, and the image which I would like to use is 8000x5000 just becasue I have to pan and zoom.

The big image is like a cartoon page, where I pan and zoom, betweens the different cartoon boxes, I cant think of another word then boxes....

When using 72dpi, the big image will get pixelated mucho...

Anyway, I found out that 150dpi will do great, and render will work out without problems, also no interuppts in workflow...

Just try cutting the size down until you find one that works.
You don't have too many choices as I see it.

Slideshow Pro with video
 

I am trying to prep video files to be brought into slideshow pro and then be played on a 500 pixel wide player within a website. Does anyone out there have suggestions as to how to do this? 500 pixels wide is not standard for video, so am wondering the best way to have the video fill up the space, maintain aspect ratio, decent quality but not overload people's bandwidth. Help! I know there is a sizing option within Slideshow Pro, but want to get the clips to the optimal size first.

DPI has absolutely nothing to do with video, it is all about the image size in pixels, period. If the image size is 4000x3000, then it doesn't matter at all if the DPI is set to 72, 150, 300 or 1,000,000.

As far as really large images in Vegas are concerned, Vegas must store at least one UNCOMPRESSED copy of it in RAM. It doesn't matter if it's originally stored as JPG, PNG, TIF or BMP on disc, Vegas must uncompress it. The 32-bit Vegas v8.0 in WinXP is limited to a maximum of 2 GB of RAM address space just like every other 32-bit application. An 8000x5000 24-bit image is 120 megabytes plus whatever RAM Vegas and the OS need for other things. When Windows runs out of physical RAM, it starts using the hard drive as RAM, but this is SLOW, SLOW, SLOW. Typically, when this happens, Vegas will appear to have crashed or locked up, but it hasn't actually crashed, it's just been slowed to a snail's pace. The patient hasn't died, it's just in a coma. Regardless, it has become essentially non-responsive.

I regularly use panorama images in Vegas which are at least 10000x3000. Using the 32-bit version of Vegas in WinXP will often exhibit the out of physical RAM problem and it will take forever to render. However, the new v8.1 64-bit Vegas in Vista64 can use as much RAM as you have installed. On a typical project that would bring the 32-bit Vegas to it's knees, the 64-bit version just screams along on my quad-core machine with 8 GB of RAM.

SLIDESHOW PRO with video
 

Thanks for your reply, but I'm actually talking about a different application, just cannot figure out how to post a new topic/thread for some reason.

The application to which I'm referring is called Slideshow Pro, and the size of the player I'll be using on a website is 500 pixels wide. I would like suggestions from anyone out there regarding how to optimize video for non-typical sizes (e.g., not 320x240 or 640x480), maintain quality in terms of resolution but not overload the SLIDESHOW PRO player. Any suggestions are greatly appreciated!!!!! I'm using Final Cut and Compressor to export the original video clips.

Thanks.

Here is an example of a photo / video montage that is entirely 3D track motion. Not possible in many programs besides AE & Vegas type programs.

Still photo system limitations
 

My notes indicate 4096x4096 is max size Vegas can handle.
PNG is recommended format, but JPG (among others) is acceptable.
Optimum resolution should be between 150-300 DPI, though this spec is far less important than size.

Like I said, DPI has _absolutely_ nothing to do with video, it is ALL about the image size in pixels. Neither Vegas, nor any other NLE, pays any attention whatsoever to the DPI setting in an image file's header.

Also, 4096x4096 is the maximum project size, Vegas will import image files much larger than this assuming that you have enough RAM to handle it.

thnx for all replys u all...