Actually, I let the program hang around a little longer and it does in fact still do MJPEG encodes - except that one encode takes 26 seconds! CE_DEBUG=3 does not provide any print-out at all, and I've made sure I have plenty of CMEM buffer pools. -- Pete
On Fri, Oct 24, 2008 at 12:34 AM, Peter Sommerfeld <[EMAIL PROTECTED]>wrote: > Yes I can run MJPEG alone or MPEG4 alone but not one after the other. > I found one source of hanging. Setting the MPEG4 instance to CBR with > bitrate results in the MJPEG hanging. Pretty wierd (although this is > obviously not a valid MPEG4 configuration). > > But the problem remains that if I run the MJPEG instance first followed by > MPEG4 it works fine, but running MPEG4 first can not be followed by MJPEG > encode. Note that I run them like this: > > VIDENC1_create() of MPEG4 > IMGENC1_create() of MJPEG > VIDENC1_process() of MPEG4 > IMGENC1_process() of MJPEG // hangs here?! > > Is there some issue of the MPEG4 holding on to DMA channels that's causing > this hanging? > > -- Pete > > On Tue, Oct 21, 2008 at 9:45 AM, Stephen Berry <[EMAIL PROTECTED]> wrote: > >> I don't think I've ever seen a CMEM allocation problem hang a codec >> before. Unless of course you feed the encoder with a bad address - but that >> is sort of self inflicted pain ;) >> >> I assume that either one of the codec's run individually - but it's the >> combination that hangs? >> >> Steve >> >> Ring, Chris wrote: >> >> Setting CE_DEBUG=2 (or 3) will provide more details. Turning on trace is >> the right way to start. >> >> CMEM provides memory for the algorithm - there are some CMEM-related >> debugging techniques documented here: >> http://wiki.davincidsp.com/index.php?title=CMEM_Overview >> >> Chris >> >> ------------------------------ >> *From:* [EMAIL PROTECTED] [ >> mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>] >> *On Behalf Of *Peter Sommerfeld >> *Sent:* Monday, October 20, 2008 8:12 PM >> *To:* [email protected] >> *Subject:* DM355: MPEG4 + MJPEG together >> >> Hi, >> Has anyone had problems running MPEG4 alongside MJPEG on the DM355? ie. >> encode the same frame in the same application with MPEG4 followed by MJPEG? >> >> For me, the MJPEG IMGENC1_process call hangs. >> >> More generally, what is the best way to debug things like this? I use >> CE_DEBUG=1 but it doesn't give me enough info. I find debugging memory >> allocation problems with the DM355 especially difficult to debug as it will >> not always tell me that it has run out of memory. If it doesn't I might get >> a SIGSEGV or no feedback at all. This really slows down debugging. I'd love >> to know how much/many pools I have remaining free at a given point. >> >> Any help is greatly appreciated. >> >> Thanks, Peter >> >> ------------------------------ >> _______________________________________________ >> Davinci-linux-open-source mailing [EMAIL PROTECTED] >> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source >> >> >
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
