THE NEW PREMIERE CANNOT HANDLE LONG FILES ANYMORE!

[dcsos]

Premiere PRO
need s WIN XP to run
besides this big drawback
I found another GOTCHA not mentioned
IF YOUR WINDOWS XP install is on a FAT 32 partition, PREMIERE PRO
will not handle large file sizes

This really sucks as VEGAS, AVID and ULEAD can all run from FAT 32 and see NTFS long files fine.

WHY WAS ADOBE unable to engineer this feat.
and am I making a mistake...
In case it matters, my Premier Pro imports and edits any dv file less than 4 gig..above that I have to use VEGAS or other becase this product is flawed it only sees 5 minutes of the file corrctly and no error message is gerated...Nobody on the ADOBE forum knows either
anyone know a work around??

[alenhard]

I can't recreate your problem since my drives are all NTFS, but I think this isn't so much an oversight by Adobe as a common-sense implementation. Most people working with video ditch FAT32 file systems because of the file size limit- an obvious limitation to serious work.

On my NTFS drives I've imported files up to 30GB into Premiere Pro.

[racer-x]

I don't know a workaround, I'm still on 6.5.

You can convert your XP partition from fat 32 to NTFS in the comandline. I can't remember the correct parameters, go to start > help, search for "Convert", it will give you the correct parameters to enter in the comandline. You'll need to reboot for the conversion to take place.

It's no workaround, but I think you're better off with NTFS anyway. Just to be safe, backup important data first.

[monoxide77]

i couldn't see why anyone would want to run FAT32 on an XP system anyway. the only reason i could think of is that you have another FAT32 computer on your network that must have access to your XP machine, and a FAT32 system cannot "see" an NTFS drive.

[dcsos]

i couldn't see why anyone would want to run FAT32 on an XP system anyway.

I use dual boot and use 98 to fix WIN XP if it crashes because they're the only things residing on my internal HDD (partitioned in 2 and holding the dual os'es)
With FAT 32 I can examine all my internal files and application files with a FAT 32 boot disc..
When you boot you can only use a CD boot and are at the mercy of the XP recovery console


Now i will have to convert to NTFS and ditch my WIN 98 OS
(i'll probably upgrade that side to 2000 to continue to dual boot)
then do the NTFS conversion

Sad cause I'd hoped Premier Pro would have more functions than
6.5 but now it doesn't appear that thay thought this out
Many systems running WINDOWS XP are installed on FAT 32 filesystem,
not only my dual boot sytem...So I'm wondering how this product got out of the package without warning you functionality is severly limited if you don't have NTFS installed under the application.

[lordsmurf]

Dual boot NTFS for OS and work files needed for NTFS.
Rest of system (other drives, partitions) left FAT32.

There, fixed. I've done that before.

[racer-x]

Here's a better idea.

I dual-boot 98se and XP Pro with NTFS. I use XP for all my video crap. Once cI got it up and running thje way I like it, I used Norton Ghost to make an image of XP partition. Then when it starts acting funny and get tired of playing with it, I restore it with the image i created. It takes about 10 min to restore the system back to normal.

[dcsos]

Well, I have to evaluate whether its worth doing all the prep work

because, in the long run I might be able to use the VEGAS application to do everything that PREMIERE PRO does....
because VEGAS, out over a year ago, certainly recognizes and edits over 4 gig files with no issues
when installed on FAT 32..when doing this you just need of course to render to NTFS if the resultant file is going to be over 3.99 GIG

[racer-x]

Oh well, if you're tired of playing with Premiere Pro, I'll take it.

[kierano]

Well I too had the 5 minute problem, but my hard drive is NTFS. The only thing I can think of is that I may have captured the files to my old (FAT32) drive, but I can't for the life of me remember whether I captured before or after I got my new drive. The only way to find out for sure is to create a new project with newly captured files. I'll let you know...

[SaSi]

Perhaps your problem is caused by Premier PRO using - by default - a temp folder on the OS partition (FAT32) in which Premier wants to hold temp info.

Perhaps, if you try and find this setting and point it to an NTFS drive, the problem will go away.

Perhaps Premier PRO isn't worth all the trouble. I went into extreme measures to re-create a new XP system for Encore, only to find out it's rubbish.