Hello there;
> > >
> > > I wait for someone with a bit of celt knowledge to post a patch...
> > >
> > The trouble is that there is no compatibility between versions as written on
> > the CELT web site.
> > I tried to patch but stopped.
> [Christian Hoene] We are standardizing a new codec at the IETF which is
> called Opus. It includes Celt from Xiph.org and Silk from Skype.
> I would recommend to include Opus instead of Celt - it is going to be a
> standard soon and changes in the bitstream are unlikely to happen again.
> Also, it will be royalty free.
I'm very interested in finding a way to get a prototype working with opal and
ptlib using this extension or (updated) codec into the opal compile version
3.10.1 is what I'm currently attempting.
truth is I am in japan and I happen to need a voip solution for calling home :)
I'm a product designer not a programmer, and I am looking for help with regards
as to the layout and the actual coding placment for this new codec as ether a
replacement in opal for SILK and the aforementioned faulty celt' codec.
I downloaded both the latest opal svn and the git version of the link you sent
for the <alternative> codec, My question is what directories do I replace and
how would I go about setting up a better layout? (map??)
I see that opal uses straight SILK_SDK whilest the opus codec uses many
different default directories for the silk sdk
_______________________________________________
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
