[email protected] wrote: > Tom Metro wrote: >> It's the mvpmc running out of memory, due to memory leaks and >> inefficiencies in how the program data is stored. (See discussion on >> the dev list.) > > Are there are buffer settings that might improve things?
You mean boosting the size of the audio/video buffers to ride out the slow response of the mvpmc? No. Unfortunately once the mvpmc starts hitting the memory wall, it slows down continuously from that point forward, so increasing buffers will only delay the inevitable, and take up more memory. > From the threads I read on the devel list, it looks like the problem > is for 1500 ish recordings? I've only got a few hundred .... *sigh*. Part of the problem is memory leaks, which as you'd expect get progressively worse over time. I first started seeing symptoms when I had in the hundreds of recordings. More recordings just make the symptoms noticeable sooner. It shouldn't be a substantial problem to fix. Roger Heflin posted results of research he did, which I think identified some memory leaks that could be plugged. I proposed some architecture tweaks that would filter program data based on the selected recording groups, which if you use recording groups, could substantially cut down what needs to be loaded into memory. It all just waiting for the right person with adequate time, motivation, and skills to implement it... -Tom ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
