Memory usage requirement for DVDA is very minimal...the lightest of PC builds will burn just fine. A CPU that is hefty on processing speed can help burn Blu-ray a bit faster, not much.

I guess it might help if we knew what problems you're having that you think would be solved by memory usage.

If you created compliant media files in Vegas, then the most time consuming part will be burning to optical discs. Faster media can be burnt faster, but apart from that you are limited by the discs, not your computer.

Is it a case of having a cure (lots of memory) and looking for a disease to use it on?

Not having Low Memory warnings.

Not looking for a cure for a disease.

What I am seeing in in the Task Manager is that even under stress: Creating Menus; Encoding Audio files to AC3; getting all them pesky animation thumbnails rendered (?) I see that my CPUs and Mem are poodling along at about 10% of what they could be using. So, my woolly-headed thought process was that I might derive some insights into tweaking what I've got to give DVDA to do its thing faster. Nothing more, nothing less than that.

Now, are you all saying that I've got enough to give DVDA what it needs? And that every option is now available to improve preparation time. Sure, "Burning", being an electromechanical process is kinda limited by the speed of the media.

Grazie

Those menu preparation tasks may not be written for multi-threaded processing (or for only say two at most) so all your other CPU cores won't be used.

If that's all the memory that DVDA is using, then that's all it needs to use. Be happy that it's so memory efficient.

I'm reminded of the olden days in the Sound Forge forum where folks were constantly complaining that Sound Forge operations were using 99-100% CPU. What's the problem? Don't you want the program to run as fast as possible? Then a year later when much improved multi-threaded CPUs and OSes came out the same folks were complaining, "why isn't Sound Forge using all my available CPU power?" Weren't they happy that they now had a PC that could run Sound Forge full speed and still have some guts left over for other tasks?

Generally this software works as well as it can. If it's not using more memory or CPU then it's very well likely that the task being performed is already running in an optimal state with all the other system components taken into account and won't benefit from using more resources.

Lovely.
G

CPU usage is a very poor metric of PC efficiency. In fact, I would worry if my CPU usage was at 100% because that means it's time to buy another PC with a faster processor.

Although the original post is old, I feel compelled to comment because I am irritated. I wish there was a way to prevent people from posting irrelevant garbage.

I had a similar problem to what was originally posted here and is how I found in this thread. All this talk here about how efficient DVDA is with memory or low memory requirement is such BS... not to mention the talk about speed. OP didn't ask anything about speed.

A simple observation of Windows Task manager shows how memory is exponentially consumed, depending on the number of titles in the project.

In my case, my project was made up of a *large* number of titles (roughly 30 or so). Firstly, DVDA could not render more than a few titles without bumping up against the 32bit 2GB memory limit and crashing. DVDA uses an alarming amount of memory as more titles are added.

The solution was to simply patch the DVDA.exe with the brilliant utility from "ntcore.com", allowing DVDA to take advantage of 4GB on a 64bit platform. After this, DVDA was able to render all titles in a single 1.5hr operation, consuming roughly 2GB or RAM by itself. (I would post the screenshot that showed the memory consumption, but don't see a way to post it)

I hope this information is helpful, sorry for the little rant, but am just tired of trolling thru irrelevant BS to find meaningful info.

Peace.

Thank you so much mmediaman ! You have fixed my bug.

Thanks a lot mmediaman.
the utility from ntcore.com solved my memory problem on my 64 bits seven machine.

As mentionned here:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=872497&Replies=7

I also get crashes if I do not reduce the number of "logical cores" from 12 to 4 (even 2 with many titles in the project.
They are different from the memory problem.
But patching the exe AND reducing the number of cores : it seems I have no more limit now .Rendering complex films is now possible for me.
I alos stopped unnecessary services, reduced starting program upon boot.

With those settings DvdA 6 does the job you want !
Kind regards.

I don't know, here the post from, mmediaman, etc is a bit at odds with what should be rational thinking. I don't see the science in this tweak and I certainly don't see a post from anyone here on what problems this solved.
It would really be helpful to know what problems were encountered before the under-the-hood tweak - lets post that in details please - then share with everyone what was accomplished. From what little is posted I would say this tweak actually did nothing. Let's have some clear thinking that can be shared for the good of all users.

Answer to videoITguy
The patch solves a memory problem with Seven 64 bits only.
If you prepare a simple project, you will never need it.
Prepare saying 12 videos from 5 to 35 minutes long.
Add them one per one, add submenus.
Your software will complain about memory OR crash.
This patch solves the memory problem.

As explained by mmediaman, DvDA uses A LOT OF MEMORY if you add many (heavy) files and because it's a 32 bits program, 24 Gb memory does not help.
Everybody running seven 64 bits can check - and solve - this problem with the patch.

I have another problem, related also to complexity : if I do not reduce the number of logical cores (threads ?) , I cannot open my complex projects.
What happens : its starts loading 5- 10 60 % then the program freezes.
I should not be alone.
I would really prefer not to have to reduce the number of threads !!!

Again, the patch DOES help me - thanks again to mmediaman.

videoITguy, just try what we are trying to explain in English, a foreign language for us. It's easyer not to share !
Kind regards.

Thanks DiDequ for your comments.

I would just like to restate the point that I have here to fore held to and will probably continue to do so. I know for a fact, as much as I can state, that I author far more complex projects in Blu-ray environs than you state, and I know that many others using DVDAPro do as well.
As an example, a Blu-ray title divided into 22+ chapters for one video asset, additional videos in an extras group, access to on-screen buttoning for unique custom navigation, looped menus with 3 levels of submenus, and a section of the disc title reserved for assets on a Bd_ROM base. This is authored within the 32bit app run on a garden variety Windows 32bit OS and total run time of Blu-ray title will run over 1 hour. Not a problem. Been doing this five plus years.
My thought is that the tweak expanded on in this thread may be doing something, but I don't see it expanding on what the app is already very capable of.

Yes, videoITguy, I think you have no problems just because you are running
"authored within the 32bit app run on a garden variety Windows 32bit OS"
Memory problem appear with 64 bit OS.

Before patching the exe, I had understood I had a memory problem, this is why I had stopped some services, managing the OS. I could add more titles /submenus.
But that was not enough.
As I have 24 Gb memory, "DvDA+Seven" NEVER use pagefile.sys.
Other software (blender) do use it
I suppose"DvDA+Seven"do use pagefile.sys on 32 bit OS.

For example, I start Seven.
1.8gb memory (just seven)
I use DvdA (patched) with a complex project ->4 GB (no other software was used)
I leave DvdA -> 1.2Gb ram used !!!

Without the patch.
1.8gb memory (just seven)
I use DvdA (patched) with a simple project ->3.2 GB (no other software was used)
I leave DvdA -> 1.8Gb ram used !!!

The patch uses memory were it is available (do not understand why Seven uses so much memory - on same machine, arch linux uses only 520 Mb Ram).

With the standard configuration (Ms services), it uses 2Gb Ram on my PC.
With the patch, I've been able to produce a blueray containing 22.7 Gb data (only 400 Mb free space, because 25Gb is an unformatted value) showing 2 X 12 titles (3D and Anaglyph versions of same films).
That was not possible without the patch.
I was limited to 2 X 7 films without stopping unnecessary services.
I was limited to 2 X 10 films without the patch.

At last, I tried (without the patch) to add 99 pictures as menus, and that was OK (each of them containing 3 very small films)
Strange : it's probably a problem related to the number of files AND their sizes ( that fake project was around 4Gb on the ISO )

I do hope Sony will realease a 64 bit version for DVDA !
If they do not, I can work. I enjoy this software.

On my Pc, you will just find DVDA + Vegas pro, libre office, Gimp, Stereo photo maker, Ccleaner DvdLab (virtual blueray player) and audacity. Just Sp1 - no internet connexion (reserved to Linux or hackintosh)