Serious problem with exporting website, out of memory
I've a serious problem exporting a website, that is it won't export ! It is a heavy website (the xar file is 63,4 Mb, the web file is about 200 Mb) and contains a lot of photo galleries. I saved all photos as 75% quality jpg's, optimised them, but still Xara is telling me that it's out of memory while exporting. What can I do ? How can I increase the memory in the Tune-ups tab ?
Re: Serious problem with exporting website, out of memory
Hi,
Try rebooting your computer and disabling all no essentiall programs and run Xara before any other programs the export the site. some other programs don't release the memory the use after exiting.
Jim
Re: Serious problem with exporting website, out of memory
Hi Jim, I did all that (closed all apps and reboot) but no luck.. I even deleted two large photo gallery pages AND deleted the images in the bitmap gallery, but still Xara tells me it's out of memory. And thats strange because before I created those two pages, the website exported well. The only thing left for me to do now is split the website in two, but that means that I have to change all the links in the navigation bars to relative paths for 18 pages ! These two (now deleted) pages where the last pages I had to create before finishing the website, so I'm not in a good mood at the moment. I really hope that in the next version of XDP we're getting more memory so we can create large websites as well !
Re: Serious problem with exporting website, out of memory
Marcia
Have you optimized all JPEGs? (Utilities > Optimize All JPEGs) This changes the resolution of all JPEG images to 96dpi. If you do not do this, even though a photo is let's say, 100 x 200 pixels, if the resolution is 1200 dpi this uses memory. If you have a lot of photos that are like this, it can eat up your memory.
1 Attachment(s)
Re: Serious problem with exporting website, out of memory
Thanks Gary, but yes, I optimised the photo's, but only a few are optimised.
Look at the screenshot of the page and layer gallery, every image is 720 dpi ... The few images optimised are no longer viewable in the gallery and if I set image properties again (for these optimised images), they are very hazy. :confused:
I also would like to know if and what I can do/change under the Tune-ups tab..
Re: Serious problem with exporting website, out of memory
Hi fuad, I didn't receive your email...
Re: Serious problem with exporting website, out of memory
How many pages/images do you have?
If the photos are popups/hs they will be exported in 2 versions, the thumbnail + the popup version, which may be why it shows such high dpi even after being optimized.
No matter how much memory you have you will always be able to fill it up if you make huge sites in one step/Xara file.
When you make web sites using other tools you always work on one page at a time, and images etc are external. In Xara all pages and images have to be in memory at the same time, which seems to encourage "bad" working routines because it is so easy to use? But there will always be a limit to how much it can take, and by splitting a site into several smaller Xara files there is no limit to how big the site can be. It also makes it much faster/easier to keep it updated.
Re: Serious problem with exporting website, out of memory
Thanks Bjorn. There are 18 pages and about 650 images. I know that's a lot, but my client wants it that way. I tried to persuade her to show less (less is more) but she won't agree..
Ok, how precisely I do that ? Make different Xara webfiles and export them to the same directory (with more than one index_html_files) ? And link the links in the navigation bar to the website addresses ?
Btw I've read all the other threads about this memory issue on TG before I posted.
PS I understand now why I never had this problem while working with Dreamweaver..
Re: Serious problem with exporting website, out of memory
650 images is certainly a lot to handle in one Xara file! But it's no problem at all on a web site.
I would make a folder structure like:
web-site
...index_htm_files (made automatically by Xara)
...gallery01
......index.htm (made by Xara)
......index_htm_files (made automatically by Xara)
...gallery02
......index.htm (made by Xara)
......index_htm_files (made automatically by Xara)
...gallery03
......index.htm (made by Xara)
......index_htm_files (made automatically by Xara)
and so on...
Then you make a separate Xara file for each (gallery - or whatever) folder.
You could easily make one "template" for a gallery, complete with menus etc.
Save it with images as gallery01.
Then replace all the images and save it as gallery02 and so on.
All galleries (and other "external" pages" should have a "Home" button?
Link would simply be "../"
Link to galleries from the main pages would simply be: "gallery01/" etc.
Easy to maintain, but you won't be able to preview it all in one go.
Export locally into the correct folders, and everything should work smoothly before publishing.
Re: Serious problem with exporting website, out of memory
Ok, that's what I'll do... Thank you so much Bjorn ! (or is it Björn?)
Re: Serious problem with exporting website, out of memory
Good luck :)
(Actually it's Bjørn, which is about the same as Björn - both means "bear")
Re: Serious problem with exporting website, out of memory
Hi Marcia,
Looking at your screen grab, those jpegs are very high resolution. For web output it's best if they are all 96dpi. That's what optimising should do (and then they'd all be labelled "optimised" in the P&L gallery).
It would be worth exploring the optimisation problems first before you start breaking up your web site.
BTW: Using the Tune-ups tab would help a bit. You could reduce the sizes of the caches and buffers that Xara/Xtreme/Designer uses to help make editing fast so that more memory is available for exporting. But I think you have a more fundamental problem with the size of your jpegs that you need to solve first.
Phil
Re: Serious problem with exporting website, out of memory
Aren't you forgetting something PhilM?
Most likely those photos are thumbs with popups?
When you view bitmaps in the P&L gallery it shows the dpi of the thumbs.
And when you view them in the Bitmap gallery it shows the dpi of the actual popup photos.
And if you use 'optimize all jpegs' the text in P&L wil not show up as '(Optimized)'.
OTOH it might be useful to view/set the popup images to a lower res, which will probably save a lot of memory after 'optimizing all jpegs'.
Or am I missing something? (I noticed that you are a Xara developer...)
Anyway, with 650 photos (and more to come?) I still think it's a good idea to split the file...
Re: Serious problem with exporting website, out of memory
Yes, I might be wrong. Web publishing is not really "my area" and without seeing the web file it's hard to understand exactly what the problem is.
If the photos are popups then there's certainly no reason to store them at higher resolution than the popup will show.
Doing that might give enough headroom to continue working with just one file but if not and if the site is growing then, yes, splitting it is probably a good idea.
BTW: You can use the Document Info dialog to show you the size of the document in memory with all the jpegs and pngs unpacked ready for fast editing and rendering. Note that that's very different than the size of the file where jpgs and pngs are all packed away.
Phil
Re: Serious problem with exporting website, out of memory
Maybe i am wrong but thought i ask if you emptied your Web Cache in Xara Options? Secondly, delete the out-dated Backup Files which are created each time as these might also be taking up space. Try either of the two or the other option might be to raise your Web Cache space under Options from 10MB to something else. PLEASE BACK UP YOUR WORK PRIOR....
klamsi
Re: Serious problem with exporting website, out of memory
Quote:
Originally Posted by
PhilM
If the photos are popups then there's certainly no reason to store them at higher resolution than the popup will show.
Doing that might give enough headroom to continue working with just one file but if not and if the site is growing then, yes, splitting it is probably a good idea.
When I optimize jpegs Xara does a very good job, and keeps the dpi of the photos at 96dpi for the large versions.
That file list shows very high dpi values in the P&L, which could indicate either one of two:
- The thumbs are very small
- The large versions (popups) are shown very big?
Setting the popup size to a lower width value for all images, and then optimize them, should be able to decrease the memory needs dramatically.
But it is still nice to know that splitting a site is quite easy to do.
I would've split such a big site into sections anyway, even if I had no memory problems, just to make the files more manageable.