Displaying 20 results from an estimated 5000 matches similar to: "Re: XIPH Internet-Drafts"
2007 Jun 05
1
Re: XIPH Internet-Drafts
Peter Saint-Andre wrote:
> On Mon, Jun 04, 2007 at 03:58:17PM -0700, Ralph Giles wrote:
>> On Mon, Jun 04, 2007 at 03:20:05PM -0600, Peter Saint-Andre wrote:
>>
>>>>> Hi Luca,
>>>>>
>>>>> Thank you for working on the Theora and Vorbis drafts in the IETF's AVT
>>>>> WG. Do you also plan to work on the Speex draft?
2007 Jun 05
0
Re: XIPH Internet-Drafts
On Mon, Jun 04, 2007 at 03:58:17PM -0700, Ralph Giles wrote:
> On Mon, Jun 04, 2007 at 03:20:05PM -0600, Peter Saint-Andre wrote:
>
> > >>Hi Luca,
> > >>
> > >>Thank you for working on the Theora and Vorbis drafts in the IETF's AVT
> > >>WG. Do you also plan to work on the Speex draft?
> > >
> > >other people are working
2009 Feb 27
5
ietf discussion about draft-ietf-avt-rtp-speex
Hi Jean-Marc, Alfred and Greg,
Are you receiving the mails from IETF about draft-ietf-avt-rtp-speex
The mails are not coming from AVT mailing list, but I think we are
all 3 part of a minimal list (draft-ietf-avt-rtp-speex at tools.ietf.org)
dedicated to latest discussion about the draft.
I have answered some questions, but there are small changes and adaptation
still required to the ietf
2007 May 30
5
draft-ietf-avt-rtp-speex-01.txt
Do not forget to add the "Copying conditions" to the RFC.
Check http://wiki.debian.org/NonFreeIETFDocuments
That page contains a section titled "Template for RFC authors to
release additional rights". To follow that guideline a
section like the following should be added:
x. Copying conditions
The author(s) agree to grant third parties the irrevocable
right to
2007 May 15
4
draft-ietf-avt-rtp-speex-01.txt
Hi all
We are about to send an updated version of the internet draft
"RTP Payload Format for the Speex Codec" to the IETF AVT working group.
Before submitting we would like your input, if you have any comments
or input please send them to the mailing list.
If we don't get any comments in 1 week (by 22. May 2007) we will go ahead
and submit it to the IETF. Of course you can comment
2009 Apr 18
3
ietf discussion about draft-ietf-avt-rtp-speex
Sorry for the delay.
On 4/13/09, Alfred E. Heggestad <aeh at db.org> wrote:
> Ivo, could you also review the updated memo-status/copyright notice,
> located on page 1-2 ?
Is this a new standard for writing Internet drafts? I've never seen
it in other documents.
Specifically, this part:
"This document may not be modified, and derivative works of it may not
be created,
2009 Mar 30
2
ietf discussion about draft-ietf-avt-rtp-speex
On 3/30/09, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote:
> It seems to be related to debian, that doesn't like the fact that not
> everyone is allowed to modify these documents. If it's that much
> problem, I'd say just remove it.
Guys, both the Vorbis RTP and the Ogg media types RFCs have this
clause. It did not raise any problem. If there are problems
2007 Jun 07
1
draft-ietf-avt-rtp-speex-01.txt
Looks good to me.
Jean-Marc
Alfred E. Heggestad a ?crit :
> Hi
>
> Please find an updated version of the Speex I-D attached. The only
> change is addition of the copyright conditions in Appendix A,
> as requested by Ivo.
>
> Many thanks for your input.
>
> I will give you a few more days before submitting to AVT working group
>
>
> /alfred
>
> Ivo
2007 Aug 28
3
Speex is the default codec for Jabber's Jingle VoIP
Just a heads-up, I received confirmation that Speex is now the default
codec for the Jabber's Jingle VoIP protocol.
While not the default in Google's Jabber, Speex has been reported to
work on Google Talk as well as of last year.
This information is not news breaking, but many people aren't aware of
it yet, so spread the word.
-Ivo
2009 Mar 22
2
ietf discussion about draft-ietf-avt-rtp-speex
Jean-Marc Valin wrote:
>> Also, we need to know why there is a "license" chapter (chapter 9)
>> and we need to remove it because ietf don't like it...
>
> IIRC, the reason for the license is to make the document compatible with
> the Debian licensing guidelines or something like that.
>
I would like to know if we should keep this additional license chapter
2005 Feb 19
2
memory usage
Hi
I am currently trying to port speex v1.1.6 to a microcontroller with
very limited memory (<64Kbyte RAM).
what I found when initialising the encoder, a chunk of 32Kb was
attempted to be alloced, which failed:
src/nb_celp.c:
void *nb_encoder_init(const SpeexMode *m)
{
/* snip */
st = (EncState*)speex_alloc(sizeof(EncState)+8000*sizeof(spx_sig_t));
/* snip */
}
same goes for the
2004 May 24
6
RFC draft for Vorbis over RTP
Hi!
What happened to this document? Was it just left dying in the IETF system?
Tor
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the
2005 Feb 28
4
memory usage
On Mon, 2005-02-28 at 19:42 -0500, Jean-Marc Valin wrote:
> > jean-marc: i think we can remove spx_sig_t *orig.
> > but am not sure about exc2Buf. is it for extension?
>
> orig is already removed in SVN (which you should probably use). As for
> exc2, it can be removed, but I'm not sure if you can just use exc
> instead (maybe yes).
>
when removing "spx_sig_t
2006 Nov 15
1
[PATCH] symbian port
hi Jean-Marc,
I just updated from svn and it looks like there are some errors in the speex.mmp
file. the filters.c is duplicated, and the fft/kiss.c files are still missing..
/alfred
Jean-Marc Valin wrote:
> Applied in svn. Thanks.
>
> Jean-Marc
>
> Alfred E. Heggestad a ?crit :
>> hi,
>>
>> this patch should fix the symbian build.
>>
>>
>>
2006 Nov 15
2
[PATCH] symbian port
hi,
this patch should fix the symbian build.
/alfred
-------------- next part --------------
A non-text attachment was scrubbed...
Name: speex-symbian2.patch
Type: text/x-patch
Size: 2669 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20061115/5ac4915e/speex-symbian2.bin
2007 Aug 28
1
Speex is the default codec for Jabber's Jingle VoIP
Ivo Emanuel Gon?alves wrote:
> Just a heads-up, I received confirmation that Speex is now the default
> codec for the Jabber's Jingle VoIP protocol.
Which we hope to finalize soon for broader adoption. :)
> While not the default in Google's Jabber, Speex has been reported to
> work on Google Talk as well as of last year.
BTW, my contacts on the Google Talk team report that
2008 Jun 06
1
Stereo AEC, transition to Git
can you try git 1.5.x just in case that's the problem?
Jean-Marc
Alfred E. Heggestad a ?crit :
> Jean-Marc Valin wrote:
> <snip>
>>
>> git clone http://git.xiph.org/speex.git
>>
>
> I am getting this error:
>
> [...]
> walk 8e52b996f69c9419e3057ce0ed215fcb93a7be45
> walk 0f6a78e98ea5e7ccc4b81d1d7064a4a251d019d7
> walk
2005 Nov 05
1
speex rtp draft feedback
Jean-Marc and others,
I'm meeting informally with the AVT WG on monday, and formally
presenting our latest drafts on friday. I've been following the
vorbis/theora draft efforts, but haven't paid much attention to
the speex work. Can you brief me on what I should talk about,
what we'd like feedback on, what's new and different from other
drafts as far as the speex work goes?
2006 Jun 12
1
[PATCH] warning: missing initializer for SPEEX_STEREO_STATE_INIT
hi
this code gives me a warning:
SpeexStereoState stereo = SPEEX_STEREO_STATE_INIT;
modules/speex/mod.c: In function 'alloc':
modules/speex/mod.c:61: warning: missing initializer
modules/speex/mod.c:61: warning: (near initialization for
'stereo_init.reserved1')
would it be possible to add this patch to you svn ?
Index: include/speex/speex_stereo.h
2003 Apr 16
4
iLBC
i tried asterisk ilbc codec against kphone. when the call got
connected, i started to immediately get these kind of message to the
console:
WARNING[14350]: File codec_ilbc.c, Line 141 (ilbctolin_framein): Huh? An ilbc frame that isn't a multiple of 52 bytes long from RTP (50)?
WARNING[14350]: File codec_ilbc.c, Line 141 (ilbctolin_framein): Huh? An ilbc frame that isn't a multiple of