DVD Architect memory limit problems

AlanMintaka wrote on 10/18/2019, 9:17 AM

Hello,

I'm running into some sort of memory limit problem in DVDA 7 build 100. The platform is Windows 10 1903 x64 (latest update according to Windows Update). System is a Dell XPS 8700 with 8GB physical RAM.

If I try to add more than 6 or 7 titles to a project, DVDA either hangs or the existing titles get corrupted (A/V frame drops, or blank A/V tracks). When this happens, task manager shows that DVDA is using ~800 MB of memory. Through trial and error I've found that ~800 MB is as large as the usage can get before problems start happening.

However if I use Vegas Pro 17 to render all the titles into one large title, I can import it into DVDA without problems. So it seems the memory limit depends more on the number of titles rather than the total size of all the titles when they're merged.

Merging the titles in Vegas is an OK workaround as far as my current project is concerned. But it forces me to always use Vegas to merge multiple titles first. Isn't there any way to avoid this extra step? For large projects, Vegas can use a lot of time (4+ hours on this system) that would be saved if I could just import all the titles into DVDA.

Thanks for your time,

Alan Mintaka

Comments

EricLNZ wrote on 10/18/2019, 6:16 PM

I wonder if this thread relates https://www.vegascreativesoftware.info/us/forum/vegas-dvd-architect-memory-problem--111285/#ca687678

Unfortunately it doesn't provide an answer.

AlanMintaka wrote on 10/18/2019, 6:55 PM

I wonder if this thread relates https://www.vegascreativesoftware.info/us/forum/vegas-dvd-architect-memory-problem--111285/#ca687678
Unfortunately it doesn't provide an answer.

Hi EricLNZ,

Yes, I first posted my message at the end of that thread. However the thread was started over a year ago and I didn't get any hits after a week, so I thought I'd try for increased visibility by starting my own topic.

Besides, you're right about that thread - none of the suggestions worked. Still it was worthwhile to rule out all of those possibilities and keep trying to sniff out something different.

I take it that you haven't had any luck with this problem?

 

 

 

 

EricLNZ wrote on 10/18/2019, 8:05 PM

I've yet to encounter the problem. But then I've only burnt two full BR discs both with DVDA Studio5. My next will be with DVDA7 but it takes me ages to have enough home movies to fill a BR!

One of my previous burns was on a Vista machine with 2gb system RAM so I don't think available RAM is the problem. That burn had 20 individual videos on it so the number of files also doesn't appear to be the problem. At least not with DVDAS5.

It appears to be an issue for only a few so presumably there's something unique with your system that causes it. This of course makes it difficult for developers when a problem cannot be replicated. Did you try the 4gb patch?

vkmast wrote on 10/19/2019, 4:17 AM

The forum has several reports of the 4gb patch not working re VEGAS DVD Architect (aka DVD A 7). Generally, "DVD Architect software supports many file types and can convert your media to the formats required for DVD or Blu-ray Disc as needed. However, for best performance (decreased disc preparation time and recompression), use existing rendered files."

 

AlanMintaka wrote on 10/19/2019, 9:00 AM

The forum has several reports of the 4gb patch not working re VEGAS DVD Architect (aka DVD A 7). Generally, "DVD Architect software supports many file types and can convert your media to the formats required for DVD or Blu-ray Disc as needed. However, for best performance (decreased disc preparation time and recompression), use existing rendered files."

 

Hi vkmast,

Thanks for that info. OK then, it looks like always rendering the source media in Vegas before using DVDA is the way to go, regardless of memory issues. The latter can be taken care of by merging multiple titles during that Vegas render.

I'll shift my priorities to shortening Vegas render times, and sideline the memory issues for now.

I'm already on the rendering times issue - am experimenting with disabling resampling. In my case the render almost always has to change frame rate from 29p to 24p, so disabling resampling may help shorten the renders. Nick Host has gotten me started with all of that via his FAQ page.

I'm going to tag your post as a solution. Pre-rendering multiple titles really is only a workaround for the memory issue, but does seem the best way to solve the problem until DVDA is available in x64. Think this will ever happen?

Thanks again,

Alan Mintaka

vkmast wrote on 10/19/2019, 10:19 AM

Think this will ever happen?

Don't remember if there's been any news since this comment.

@AlanMintaka

brian-kolbasky wrote on 11/11/2019, 4:44 PM

I have to say i have had a lot of issues with this program, That is had to revert back to dvda 6 and it works perfect.

Why is it you Guy's are not focused to even save this program? It needs a massive overhaul!

EricLNZ wrote on 11/11/2019, 7:22 PM

Why is it you Guy's are not focused to even save this program? It needs a massive overhaul!

Hi Brian, this is a user to user forum and as such we aren't the ones you need to address this to. Suggest you contact the Vegas developers with your inquiry. Whilst they do visit this forum there's no guarantee they will notice your post.