All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: Saul Wold <saul.wold@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Call for help for demo UPNP media renderer
Date: Wed, 20 Oct 2010 01:04:47 +0100	[thread overview]
Message-ID: <1287533087.2283.5.camel@scimitar> (raw)
In-Reply-To: <4CBE0E4A.1050208@intel.com>

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:
> 
> Dongxiao,
> 
> Can you take a look at this since you have worked with the gstreamer?

I did a sloppy job pushing my changes when leaving the office but think
I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer elements
are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't appear
to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

Cheers,
Joshua

> 
> Thanks
>     Sau!
> 
> 
> On 10/19/2010 02:15 PM, Joshua Lock wrote:
> > Hi all,
> >
> > I've packaged Rygel, a upnp media server and renderer, to use as the
> > media renderer in the upnp demo. However I'm seeing a segfault at launch
> > and as it's getting late here I'm wondering if someone in a strategic
> > timezone can help debug while I cycle home and sleep.
> >
> > The (ugly) recipes are in the josh/demo branch of the meta-demo
> > repository.
> >
> > rygel --gst-debug-level=5
> >
> > shows plenty of output, but nothing that jumps out to a gstreamer newb
> > like me. AFAICT I have all of the plugins required but it's possible we
> > need to add more.
> >
> > If not I'll pick it up again in the morning.
> >
> > Thanks,
> > Joshua
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.pokylinux.org/listinfo/yocto

-- 
Joshua Lock
        Intel Open Source Technology Centre



  parent reply	other threads:[~2010-10-20  0:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 21:15 Call for help for demo UPNP media renderer Joshua Lock
2010-10-19 21:31 ` Saul Wold
2010-10-19 22:36   ` Joshua Lock
2010-10-19 23:56     ` Tian, Kevin
2010-10-20  0:04   ` Joshua Lock [this message]
2010-10-20  0:08     ` Tian, Kevin
2010-10-20  0:19       ` Joshua Lock
2010-10-20  0:16     ` Joshua Lock
2010-10-20  0:23       ` Darren Hart
2010-10-20  0:30         ` Tian, Kevin
2010-10-20  0:33           ` Tian, Kevin
2010-10-20  0:34           ` Darren Hart
2010-10-20  0:40       ` Xu, Dongxiao
2010-10-20  1:13         ` Tom Zanussi
2010-10-20  1:19           ` Xu, Dongxiao
2010-10-20  3:58             ` Xu, Dongxiao
2010-10-20  6:07               ` Xu, Dongxiao
2010-10-20  7:18                 ` Joshua Lock
2010-10-20  7:23                   ` Xu, Dongxiao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1287533087.2283.5.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=saul.wold@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.