Displaying 20 results from an estimated 133 matches for "avt".
Did you mean:
at
2018 Oct 19
2
OPUS at Texas Instruments C6418
...1
#define CONFIG_TI_C6X 1
Are there any better or further possibilities to get a speed optimized code on the TI C6418?
Code size is less relevant.
Many thanks in advance!
Best regards,
Robert
Robert Madinger
[avt_logo_signatur]
AVT Audio Video Technologies GmbH
Nordostpark 91 | D-90411 Nuernberg
T: +49 911 5271-0 | F: +49 911 5271-100
RMadinger at avt-nbg.de<mailto:%0bRMadinger at avt-nbg.de> | www.avt-nbg.de<http://www.avt-nbg.de/>
Managing Director: Wilfried Hecht
Registered Office: Nuernbe...
2018 Oct 22
1
OPUS at Texas Instruments C6418
...annot find it after enabling the TI_C6X_ASM config option.
Maybe it was only part of an early version of the Opus sources?
I looked for the file in versions V1.1, V1.1.1, V1.2alpha and V1.3 but did not found it.
Do you have an idea, where I can get the file?
Thank you and best regards,
Robert
AVT Audio Video Technologies GmbH
Nordostpark 91 | D-90411 Nuernberg
T: +49 911 5271-0 | F: +49 911 5271-100
RMadinger at avt-nbg.de | www.avt-nbg.de
Managing Director: Wilfried Hecht
Registered Office: Nuernberg, HRB 14317
AVT is now on Twitter - Follow @AVTGmbH
-----Ursprüngliche Nac...
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 i...
2018 Oct 22
0
OPUS at Texas Instruments C6418
...gt; Maybe it was only part of an early version of the Opus sources?
> I looked for the file in versions V1.1, V1.1.1, V1.2alpha and V1.3 but did not found it.
>
> Do you have an idea, where I can get the file?
>
> Thank you and best regards,
> Robert
>
>
>
>
> AVT Audio Video Technologies GmbH
> Nordostpark 91 | D-90411 Nuernberg
> T: +49 911 5271-0 | F: +49 911 5271-100
> RMadinger at avt-nbg.de | www.avt-nbg.de
> Managing Director: Wilfried Hecht
> Registered Office: Nuernberg, HRB 14317
> AVT is now on Twitter - Follow @AVTG...
2004 Aug 06
0
I-D ACTION:draft-herlein-avt-rtp-speex-00.txt (fwd)
All:
The latest draft RTP Payload Format for Speex is available via
the IETF. See below for details.
Greg
---------- Forwarded message ----------
Date: Tue, 09 Mar 2004 15:56:23 -0500
From: Internet-Drafts@ietf.org
To: IETF-Announce: ;
Subject: I-D ACTION:draft-herlein-avt-rtp-speex-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories.
<p> Title : RTP Payload Format for the Speex Codec
Author(s) : G. Herlein
Filename : draft-herlein-avt-rtp-speex-00.txt
Pages : 12
Date : 2004-3-9...
2004 Sep 13
0
[AVT] Open Speech Repository (fwd)
interesting for anyone testing out speex :)
kfish.
----- Forwarded message from Alan Clark <alan.d.clark@telchemy.com> -----
From: Alan Clark <alan.d.clark@telchemy.com>
To: avt@ietf.org
Date: Mon, 13 Sep 2004 12:57:01 -0400
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Subject: [AVT] Open Speech Repository
We've started to build a database of speech samples in multiple languages
using (roughly) phonetically balanced source material. The site currentl...
2009 Feb 27
3
ietf discussion about draft-ietf-avt-rtp-speex
...quot;license" chapter (chapter 9)
and we need to remove it because ietf don't like it...
Probably a little more...
Aymeric
> Jean-Marc
>
> Aymeric Moizard a ?crit :
>> 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...
2005 Jun 16
1
Cisco 7960 (SIP) with Asterisk: how to get # to work during a call
...incominglimit=2
mailbox=2001@default
disallow=all
allow=alaw
allow=ulaw
callgroup=2
pickupgroup=2
and in the SIPDefault.cnf for the phones I have:
# Inband DTMF Settings (0-disable, 1-enable (default))
dtmf_inband: 1
# Out of band DTMF Settings (none-disable, avt-avt enable (default), avt_always - always avt )
dtmf_outofband: avt
# DTMF dB Level Settings (1-6dB down, 2-3db down, 3-nominal (default), 4-3db up, 5-6dB up)
dtmf_db_level: 3
DTMF works for voicemail and for remote services over both analogue Zap
channels and digital (ISDN) channels....
2004 Aug 06
0
Re: [AVT] Speex: Apologies for Missed Meeting (fwd)
...mat
did not occur. Details below.
Progress continues, though, towards getting the Speex payload
format approved.
Greg
---------- Forwarded message ----------
Date: Fri, 21 Mar 2003 08:58:23 -0800 (PST)
From: Stephen Casner <casner@acm.org>
To: Greg Herlein <gherlein@herlein.com>
Cc: avt@ietf.org
Subject: Re: [AVT] Speex: Apologies for Missed Meeting
Greg,
> To those expecting my presentation yesterday on the Speex codec,
> I apologize for not being there. I was caught out in the traffic
> mess that occurred due to the anti-war protests - I could not get
> to the mee...
2005 Jul 26
2
7960 SIP Firmware Upgrade Strange Problem
...bled (default)
# Telnet Level (enable or disable the ability to telnet into this phone
telnet_level: "2" ; 0-Disabled (default), 1-Enabled, 2-Privileged
# Inband DTMF Settings (0-disable, 1-enable (default))
dtmf_inband: "1"
# Out of band DTMF Settings (none-disable, avt-avt enable (default),
avt_always - always avt )
dtmf_outofband: "avt"
# DTMF dB Level Settings (1-6dB down, 2-3db down, 3-nominal (default), 4-3db
up, 5-6dB up)
dtmf_db_level: "3"
# SIP Timers
timer_t1: "500" ; Default 500 msec
timer_t2: "400...
2008 Mar 31
0
[Fwd: Working group last call: draft-ietf-avt-rtp-speex-05.txt]
FYI,
-------------- next part --------------
An embedded message was scrubbed...
From: Colin Perkins <csp at csperkins.org>
Subject: Working group last call: draft-ietf-avt-rtp-speex-05.txt
Date: Mon, 31 Mar 2008 22:25:03 +0100
Size: 2054
Url: http://lists.xiph.org/pipermail/speex-dev/attachments/20080331/289739db/attachment.eml
2009 May 18
0
[Fwd: [AVT] Protocol Action: 'RTP Payload Format for the Speex Codec' to Proposed Standard]
Hi,
some good news from IETF :)
/alfred
-------------- next part --------------
An embedded message was scrubbed...
From: The IESG <iesg-secretary at ietf.org>
Subject: [AVT] Protocol Action: 'RTP Payload Format for the Speex Codec' to
Proposed Standard
Date: Mon, 18 May 2009 06:26:11 -0700 (PDT)
Size: 3867
Url: http://lists.xiph.org/pipermail/speex-dev/attachments/20090518/373c4928/attachment.eml
2018 Oct 19
0
OPUS at Texas Instruments C6418
...;
> Are there any better or further possibilities to get a speed optimized
> code on the TI C6418?
>
> Code size is less relevant.
>
>
>
> Many thanks in advance!
>
> Best regards,
>
> Robert
>
>
>
>
>
> Robert Madinger
>
> avt_logo_signatur
> AVT Audio Video Technologies GmbH
> Nordostpark 91 | D-90411 Nuernberg
> T:+49 911 5271-0 | F: +49 911 5271-100_
> RMadinger at avt-nbg.de <mailto:%0bRMadinger at avt-nbg.de>_| www.avt-nbg.de
> <http://www.avt-nbg.de/>
> Managing Director: Wilfried Hec...
2003 Jan 07
3
Vorbis RTP Internet Draft
Hi all,
Below is the Vorbis RTP Internet Draft as sent to the AVT working group
of the IETF.
Comments and feedback is still welcomed from the Vorbis community.
Cheers
Phil
---------------------------8<-----------------8<------------------------
Network Working Group Phil Kerr
Internet-Draft The Ogg Vorbis
January 07, 2003...
2007 Jun 04
2
Re: XIPH Internet-Drafts
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 on the speex I-D, Ralph should be able to tell
> >you which to contact ^^;
>
> Hi Ralph, let me know how I can help on the Speex I-D -- we'd like to
> make sure that our us...
2002 Dec 16
2
Updated Vorbis RTP I-D
Hi all,
Apologies in advance, this email is quite long.
I've prepared an updated Vorbis RTP Internet Draft, which is a
continuation of draft-moffitt-vorbis-rtp-00.txt which can be found
below.
If this new draft gets the ok I'd like to submit this to the AVT WG
later this week.
There are a number of changes over the original I-D, notably the
changing of the M bit function in the RTP header to match current AVT
practice, together with an initial suggestion for codebook delivery.
Other changes are the expansion of previous sections and the explicit
dec...
2007 May 31
0
draft-ietf-avt-rtp-speex-01.txt
Ivo Emanuel Gon?alves wrote:
> Do not forget to add the "Copying conditions" to the RFC.
>
> Check http://wiki.debian.org/NonFreeIETFDocuments
>
I would be happy to add this statement.
Could you let me know where to insert this statement in the xml
document? I am using xml2rfc to generate the draft. Or alternatively
point to other documents (.xml sources) that have the
2007 Jun 01
0
draft-ietf-avt-rtp-speex-01.txt
On 6/1/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:
> No, keep as is. It is definitely not public domain, since it's
> BSD-licensed and "patent-free" will open futile and unnecessary
> discussions (on what it's supposed to mean) at the IETF.
I was under the impression that Speex, like Vorbis and FLAC had its
specification under the PD, and only the
2007 Jun 01
1
draft-ietf-avt-rtp-speex-01.txt
> I was under the impression that Speex, like Vorbis and FLAC had its
> specification under the PD,
AFAIK, under US law, the only way for something to fall in the public
domain is for either 1) the author to be an employee of the US
government or 2) the author to be dead for more than X years (X being
larger than the age of Mickey Mouse). To the best of my knowledge (did I
miss
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