Hi,
I am running speex wideband for speech. While doing that I am getting
Hissing sound during silence. If you want I can give you input and
output files.
Thanks,
Shridhar
-----Original Message-----
From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On
Behalf Of speex-dev-request@xiph.org
Sent: Tuesday, October 09, 2007 12:30 AM
To: speex-dev@xiph.org
Subject: Speex-dev Digest, Vol 41, Issue 6
Send Speex-dev mailing list submissions to
speex-dev@xiph.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xiph.org/mailman/listinfo/speex-dev
or, via email, send a message with subject or body 'help' to
speex-dev-request@xiph.org
You can reach the person managing the list at
speex-dev-owner@xiph.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Speex-dev digest..."
Today's Topics:
1. Re: Speex on DSPic, violation of license? (David Willmore)
2. Re: Speex on DSPic, violation of license? (Jean-Marc Valin)
3. Floating point implementation (Matt Bucknall)
----------------------------------------------------------------------
Message: 1
Date: Sun, 7 Oct 2007 15:30:40 -0400
From: "David Willmore" <davidwillmore@gmail.com>
Subject: Re: [Speex-dev] Speex on DSPic, violation of license?
To: "Jean-Marc Valin" <jean-marc.valin@usherbrooke.ca>
Cc: speex-dev@xiph.org
Message-ID:
<1cddf4cc0710071230r2620f413o583b776e0cb3a2db@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 10/1/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
wrote:> I'm aware of Microchip's closed-source port of Speex to the dsPIC.
As
> far as I know (haven't checked the details), this is perfectly legal,
> even though I think it's a dumb decision for a company that's in
the
> business of selling chips. I say it's dumb because by not contributing
> the changes back, they ended up not benefiting from significant
> improvements I made to Speex since their forked. Had they done so, the
> memory requirement for Speex on dsPIC would be smaller than what they
> have now and the quality would likely be better. In case there are any
> dsPIC developers around, you should know that the current Speex
svn/git> version (or 1.2beta2) now has small enough RAM requirement to fit on
the> dsPIC, so it probably wouldn't be too hard to create an open-source
port> that's actually better (and of course cheaper) than what Microchip
sells.
There are a couple of us working on it. We're both also radio amateurs,
so
we hope to keep our work completly free--so it can be used in open
standard
software for amateur radio--as well as whatever else people feel like
using
it in. Our code will make its way back into the main tree.
Jean-Marc, all of your hard work in reducing memory footprint and CPU
usage
is wonderful. Thank you, very much.
Cheers,
David n0ymv
------------------------------
Message: 2
Date: Mon, 08 Oct 2007 09:31:18 +1000
From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
Subject: Re: [Speex-dev] Speex on DSPic, violation of license?
To: David Willmore <davidwillmore@gmail.com>
Cc: speex-dev@xiph.org
Message-ID: <47096C46.1010804@usherbrooke.ca>
Content-Type: text/plain; charset=ISO-8859-1
Hi David,
Glad to know you're working on this? What's the status of that? Does it
run on a dsPIC yet? Do you have any code yet that is worth merging? It's
good when things can be merged early; otherwise it takes much more
effort as the codebases diverge. In some cases, I actually don't even
mind merging code that doesn't work/compile -- as long as it's
platform-specific code that doesn't break things that worked before.
Jean-Marc
David Willmore wrote:> On 10/1/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote:
>> I'm aware of Microchip's closed-source port of Speex to the
dsPIC. As
>> far as I know (haven't checked the details), this is perfectly
legal,
>> even though I think it's a dumb decision for a company that's
in the
>> business of selling chips. I say it's dumb because by not
contributing>> the changes back, they ended up not benefiting from significant
>> improvements I made to Speex since their forked. Had they done so,
the>> memory requirement for Speex on dsPIC would be smaller than what they
>> have now and the quality would likely be better. In case there are
any>> dsPIC developers around, you should know that the current Speex
svn/git>> version (or 1.2beta2) now has small enough RAM requirement to fit on
the>> dsPIC, so it probably wouldn't be too hard to create an open-source
port>> that's actually better (and of course cheaper) than what Microchip
sells.>
> There are a couple of us working on it. We're both also radio
amateurs, so> we hope to keep our work completly free--so it can be used in open
standard> software for amateur radio--as well as whatever else people feel like
using> it in. Our code will make its way back into the main tree.
>
> Jean-Marc, all of your hard work in reducing memory footprint and CPU
usage> is wonderful. Thank you, very much.
>
> Cheers,
> David n0ymv
>
>
------------------------------
Message: 3
Date: Mon, 08 Oct 2007 17:38:34 +0100
From: Matt Bucknall <matt@mattbucknall.com>
Subject: [Speex-dev] Floating point implementation
To: speex-dev@xiph.org
Message-ID: <470A5D0A.30701@mattbucknall.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
I'm fairly new to Speex, so please forgive me if this question has an
obvious answer. I'm currently studying the source code to understand how
Speex works and wondered, is there still a floating-point implementation
I could look at as the fixed-point stuff makes it a little difficult to
see what the code is doing.
Regards,
Matt.
------------------------------
_______________________________________________
Speex-dev mailing list
Speex-dev@xiph.org
http://lists.xiph.org/mailman/listinfo/speex-dev
End of Speex-dev Digest, Vol 41, Issue 6
****************************************
