It's been a year, so here's another repost..

Low Memory or Out of Memory does not mean "Not enough RAM", though adding RAM can sometimes fix a "Low Memory" waning. A "Low Memory" warning means that you have exceeded your commit limit. You need either a bigger page file, more physical memory, or both.

One of the biggest sources of confusion over Windows memory usage is the whole concept of virtual memory compared to physical memory. Windows organizes memory, physical and virtual, into pages. Each page is a fixed size (typically 4 KB). To make things more confusing, there’s also a pagefile. Many Windows users still think of this as a swap file, a bit of disk storage that is only called into play when you absolutely run out of physical RAM. In versions of Windows starting with Vista, that is no longer the case. The most important thing to realize is that physical memory and the page file added together equal the commit limit, which is the total amount of virtual memory that all processes can reserve and commit. When the pool of commit memory goes low, it triggers the "Low Memory" warning from Windows. When a program needs more memory from the commit pool that is available, it halts with the "Low Memory" error. To add to the confusion, Windows also suggests that you can "close open applications" without telling you that all processes commit memory from the pool. Even if you only have one application running according to the Task Manager (which is impossible, by the way), you still have dozens of running processes in the background. For example - Windows loads MS Office applications into memory so that their applications will appear to load faster than the competition.

Your web browser program also consumes an awful lot of RAM. Try rebooting and do not run any Office or browser programs.

Thanks Steve for your explaination!

If this is the case however, that would mean that DVDA needs more RAM to render a DVD than it needs to render exactly the same Blueray?

I have tried the memory patch and I also tried rendering the project from another boot partition with a fresh windows 7 installation. This doesnt work either. So it must be a bug in DVDA or a limitation of the DVD format I think.

What DOES work is when I remove the picture slideshow from the project, I can render the DVD then.

However, the same project renders as a Blueray without any problems, which suggests there is a limitation to the DVD format? In the Blueray project (and in the DVD project as well) I do get a warning that the amount of pictures is more than the max chapter number, so the last 1/3 of the pics don't have a chapter on the Blueray, which is fine by me...

I'm gonna try to take 1/3 of the pictures out, so the chapter limit is not crossed...

Hey Dude, another thing to check is the size of those pictures, (photos?). Steve Grisetti has posted many times in the past of over-sized photos causing memory problems and other glitches. There is a optimum size for photos that you bring into your projects that seem to cause less problems.

The memory error read may have something to do with ram - maybe ?- BUT LISTEN

Here's the real error - I have no idea how the organization and authoring has been done - but indeed how you commit to the chapter sequence is very important. Note the limits of DVD and Blu-ray spec are completely different - and yes, indeed Blu-ray is more flexible but IT still has limits. MOST importantly how you author such a disc with pictures spread across multiple menus, or instead menu pages has a lot to do with what you can accomplish.

Hi guys, thanks for the input!

I used only the max of 100 pictures so that every pic has its own chapter on the DVD, this worked
On the Blueray however, 300 pictures were not a problem, 255 is the limit but the rest is there, just not accessible with the chapter buttons.

@Treetops: I made the pictures all 1920x1080, so that shouldn't be a problem I guess, I think its the chapter limit.


@VideoITguy It was just a Picture Compilation that I put in so that the wedding pictures could also be viewed on the wedding movie Blueray/DVD

Conclusion: Good software would stop and tell me that I exceeded a limit and that the DVD cannot be rendered, crappy software just starts rendering for 4 hours and then crashes with a vague memory error to tell me I used too many images in the design....

ACTUALLY the conclusion is that you would have been a whole lot more successful and pleased had you authored a multi-menu with muliti-menu pages design as you should have for the benefit of the viewer. DVD and Blu-ray would both have emminently successful outcomes.

DVDA may have its faults but in no way is it 'crappy'. Try finding another DVD/Blu-ray authoring package as good at the same price (oh that's right, it's free).
Have you tried back-pedalling to V5.2? Many users have had a lot of problems with V6.0.

Just a little update on this thread....turns out that the Bluerays that didn't crash during rendering were also faulty, so my clients came back after a month...another good impression I made thanks to this wonderful piece of software!

Turned out that although I put 300 pictures on the Blueray, and although I saw it worked in the Preview of DVDA, in a real Blueray player only the first 75 pictures are available, the rest is black. In the help file it says there is a max of a whopping 999 chapters for bluerays...

I even tried putting 5 folders of 75 pics into the project, rendered the whole project again for a whole night, but the results is that only the first compilation actually works....the rest has a black screen!

Does anyone know an alternative for DVDA? It's getting a full time job for me dealing with Sony software bugs and crashes.... :(