I have done something pretty similar. I am currently encoding the video using MPEG4 and on command snapping a JPEG still. Not quite MJPEG but on the frames that I am snapping the JPEG still it is executing both algorithms on the same frame.
As previously stated, if you have one of the buffers (incoming or outgoing) pointed to a non-contiguous block of memory, the exec functions will hang. Once I corrected these pointers and made sure they were pointing to an area allocated with the CMEM allocate contig function, they worked fine. The other problem I had was trying to combine the MPEG4 codec that came with the DVSDK which is a production version but one without the complete development environment (no l64P lib files, etc) with the JPEG codec that was an evaluation version. I ultimately had to downgrade to the eval MPEG4 codecs and live with a watermark until I can get proper production versions. -mat 2008/10/21 Stephen Berry <[EMAIL PROTECTED]> > 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 > >
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
