Sick of X5 corupt files and out of memory crashing

Joan,

Some use Microsoft Security Essentials and some Avast. All run as administrators, the programs used are Outlook, Draw, Firefox and Total Commander. All have the same fonts, which are checked with FontExpert and found OK. Regarding zip files, if turning off scanning of zip files and we receive a zip file containing a virus, what then? If Corel suggest this as a solution they don't take security seriously!

Corrupt fonts: Draw should not crash if a font is corrupt, period. A proper warning would be fine though.

From time to time I have installed X5 on a new computer totally patched and with no other program than X5 installed. Problem is the same.

Ariel,

I have checked color styles and views, not the problem. We have appr. 1000 corel template files we use and all are checked for these issues. I have not seen any Corel employees answering any of these questions, sorry to say, but my feeling is that users with similar problems are not getting any attention from Corel.

Some other information. This happens mostly when X5 uses a lot of RAM. I have tried opening large files to force X5 to use more than appr 1 -2GB of RAM (I have 8GB) but crashes or stops responding before 2GB. Tried to reduce the number of nodes in a vector drawing.

Some examples:

Opens a file which is 4MB and contains 14181 simple vector objects. After opening the file, Draw uses 113MB RAM, select all objects and weld, out of memory at 1302MB.... happens on all computers/installations I have tested with.

Tried opening and converting some raw files from a Canon EOS5 camera the other day, 3 or maybe 4 files opens and converts with no problem, if trying to open 5, poof and Drow disappears..... (using appr. 1GB of RAM, tested on 3 different computers).

What made me post this initially was a school yearbook I have been working on for several days. 28 A4 pages, 300 images, 2 different fonts and some simple vector illustrations, 230MB filesize. Made som corrections to 10-15 names, adjusted some images and moved some objects around,  saved the file.... corrupt. Reopening backup file and trying the same again, corrupt again. Reopen, one change at a time, save to new filename, after 4 hours I managed to finish the changes, which should have take 15 minutes.

We do a lot of print merges and if you try to edit the merged texts Draw crashes 1 out of 4-5 times. Draw also crashes often when a lot of files are opened and printed. I really can't see any problem with our computers/hardware/software. We mainly uses Dell or HP workstations. Files are stored to a fileserver, been tested with saving to local disk with no improvement.

What I want to know is if Corel Corp. acknowledges these issues as a Corel problem or not, and if we can expect a fix.

Vidar

FosterCoburn said:

Personally I would never use CorelDRAW (or Paint) as a RAW converter

All good answers but I have one question.  Does not using batch conversion of RAW files defeat the purpose of using RAW in the first place?  I would assume th eonly reason to use RAW would be to imporve quality which requires control over the conversion of each individual image and a batch conversion surly does not achieve this.

David Milisock said:

Personally I would never use CorelDRAW (or Paint) as a RAW converter

 

All good answers but I have one question.  Does not using batch conversion of RAW files defeat the purpose of using RAW in the first place?  I would assume th eonly reason to use RAW would be to imporve quality which requires control over the conversion of each individual image and a batch conversion surly does not achieve this.

[/quote]

Not always. Say you have a group of photos taken at roughly the same time and place in the same light. (Some of us are shoot happy.) You can adjust the raw settings for one and apply them to the group that is similar and then fine tune the individual results if necessary after conversion. You would not of course apply them to others.

Raw converters aren't the end all and be all. Sometimes a photo has specific needs. It could be something as simple as a shadow in one that isn't in another. But if you've got several hundred photos (remember, I said shoot happy), batch processing can cut the post down significantly.