The max locked memory and max memory size lines of my ulimit -a output are exactly the same as yours.
In Gem I can run 9 movies/streams at the same time with no problems. All my resolutions are at 160x120, both in Gem and PDP. What's causing the stream of pdp_dumps? The pdp_dumps are usually 3/sec with one v4l and one yqt at the same time. With no v4l and 2 yqt running the stream of dumps is about 2/sec. When I add another yqt to either a pair of yqt or the v4l/yqt pair, the stream of pdp_dump is constant.
For now I've switched to Gem, so I'm not in a hurry to figure this out any longer. But PDP/PiDiP has features that are much more powerful for video (as opposed to 3D), so I would like to figure this out. Running a webcam stream and a quicktime stream at the same time is something I'll probably want to do in PDP a lot.
-------- Original Message -------- Subject: Re: [PD] More pdp blues From: "Yves Degoyon" ydegoyon@free.fr Date: Tue, May 04, 2004 2:51 pm To: "Ian Smith-Heisters" heisters@0x09.com Cc: pd-list@iem.at
hi,
i think it's mainly a memory issue, i forgot about that memory limitation thing, i'm running in an unlimited mode :
ulimit -a max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited
it fairly depends on the number and the resolutions of the videos you're playing ( and of the size of the canvas too ).
meybe, should change your memory settings??
suerte, sevy
Ian Smith-Heisters wrote:
maybe be using pdp_yqt instead of pdp_qt?
this, yes, it's lighter.
I switched to pdp_yqt and the stream of pdp_dump remains.
I have pdp in its own thread, a [block~ 131072 8] which doesn't
seem
to help, and memory usage set to 100 megs
max.
it's not so much, especially for the canvas.
What would be good numbers? Is there a disadvantage to having it too
high, as long as I can spare the memory?
If I lower the memlimit, won't it just crash all that much sooner?
Problem is, instead of managing the memory as I'd hoped, it just
exits
when it goes over that limit. I am
trying to loop the video with pdp_qt
there is a 'loop' message to pdp_qt or pdp_yqt for that purpose.
Yeah, what I was saying is, that I *am* using the loop message
already, but I am *not* using any pdp_loop or
pdp_delay. I said this because the message memlimit passes when it
closes pd is
"WARNING: increase memory limit or decrease packet usage (i.e.
pdp_loop, pdp_delay)."
And, unless they're buried in the other objects I'm using, I'm not
using pdp_loop or delay.
What could be causing so many pdp_dumps? Pdp_yqt did slow the
occurence of pdp_dumps down to about 3/sec from
5/sec (guesstimating), but it still quickly eats up every available
byte of RAM. As the pdp_dumps roll in and
start eating memory, I use pdp_control's garbagecollect, but that only
frees about 3 packets and has no
noticeable effect on the amount of memory usage.
Thanks for your patience Yves -Ian
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list