search for: dspic

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 fr...

I was browsing through Microchips' website and came upon their Speex library. They are charging for it and looks like it is also not open source. http://www.embeddedstar.com/press/content/2005/6/embedded18391.html scroll down to the paragraph about pricing. - farhan

...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 W...

...came upon their Speex > library. They are charging for it and looks like it is also not open > source. > http://www.embeddedstar.com/press/content/2005/6/embedded18391.html > scroll down to the paragraph about pricing. 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 impro...

All, I don't know if this is widely known, but it appears that Microchip has just released a library to perform speex compression/decompression on a dsPIC processor. The library is available under their license, so I can only assume that it is a reimplementation of the algo and not a port. Does anyone know otherwise? Cheers, David

Hello! I'm new to the list, so first I'd like to say hi to everybody! Is there somebody interested in helping with porting Speex on dsPIC series of Microchip's microcontrollers? I was looking at 30F6014A with 144 kB of flash and 8 kB of ram, fixed point DSP core and capable of 30 MIPS. If only one narrowband rate was selected and everything unnecessary stripped down, perhaps it could be ported to perform both encryption and decry...

Hi I was wondering if someone may help. We are currently using a DSPic to store speex data on a Smart Card. We have now decided to use a PC to playback the speex data. The only problem is our data does not have the Correct header. Do you know if there is an example in C++ that can take a string of speex frames and construct the correct Header so that it can be pla...

...<daconfama@gmail.com> wrote: > Have anyone works with speex in full duplex mode? To my knowledge, one can't really work with VoIP without full duplex, and Speex is used quite often for VoIP, so I'll say that people do use Speex in full duplex mode. > I?ll probably change the dspic for a ARM LPC22XX, this is a good idea? Only someone who has had experience with those platforms can give you a recommendation. I can't. -Ivo

The whole deal of using the new BSD license for libraries like Speex's is to allow companies to release commercial source-closed applications/devices. This to allow wider spread of the formats. Unless they are using the command line tools (e.g. encoder), which are not under BSD but LGPL. In that case, they should provide the source code for all changes they make to the command line tool,

Dear Sirs, I would be interested to hear your views on whether SPEEX could be made to run fast on a DSPIC33 by the following strategy: Make iir_mem16() (for example) purely 16 bit by restricting the number of bits in the signal to say 10 using SATURATE and then making the LPC co-efficients just 6 bits. At present (with standard code) the encode function is taking about 140ms which is seven times t...

...omputadores Flor Hard Soft 2058 C.A. www.florhard.com Alain wrote: > Hi, no chance to run it on anything from Microchip, theyr best > processor is 16 Mips 8 bits only. For what I have been readind on this > list for more than a year you need a lot more than that. > > Even theyr DSPic has a clck of only 25MHz, I don even understand why > they bother to make a DSP like that... > > John Villar escreveu: > >> Hello, does anyone knows how performs the fixed point version of >> Speex in "embedded" controllers? i'm referring to PIC16F84 and &gt...

On Thu, Mar 21, 2013 at 9:54 AM, Fernando Alberto Marengo Rodriguez < fmarengorodriguez at yahoo.com.ar> wrote: > I am asking this because we are studying the OGG Vorbis format and its > applications. We are very interested in constructing an audio player > hardware, based on DSP or DSPic, and the audio files are stored in an SD > card. > What is your motivation for constructing this hardware? Is your goal to learn/teach from the experience, or are you trying to build something that you cannot buy? --Ben -------------- next part -------------- An HTML attachment was scrubbe...

Hello, all! I'm trying to see if I can get stock Speex to compile for dsPIC using the current release of the gcc compiler targeted for it. I'm stuck at the very beginning of trying to get past the configure stage. Can anyone who cross-compiles give me an example of how they do that? Cheers, David

Hi Jen-Marc, this news were very interesting because of what I intedd to use speex for... Can you make some personal comments about that? Were you involved or consulted about it? Will it make it's way into the official version? I remember that you commented a long time ago that the DSPIC version was too much of a tour-de-force to make it to the official version, but this is a much nicer processor ;) It uses less then 50% cpu for encode+decode at reasonable settings for a simple phone, could the rest be used for AEC and AGC? Thanks a lot, Alain Pietro Maggi escreveu: > But...

Are there any ports of Ogg decoder to dsPIC processors ? Thanks don

Hello Cesar I'm using Speex on a PPC2002 and PPC2003 with no problems. For tune-up remember to define the FIXED_POINT macro in Project->Settings in eVC. With this setting you ought to be able to at least decode in realtime while using debug-mode. Kind regards Bjoern D. Rasmussen >From: "cesarbremer@raseac.com.br" <cesarbremer@raseac.com.br> >To: speex-dev@xiph.org

> Presuming that you are asking regarding the Ogg Vorbis audio format, the > correct answer is: there is no minimum or maximum cutoff frequency. Vorbis > can code all frequencies from DC to Nyquist. What Vorbis will actually do > is extremely complex, extremely nonlinear, and highly dependent on bitrate. > If you are in the mentality of linear time-invariant filters, you will

Hi Roberto, The PIC24 family of devices share very little commonality with PIC16 beyond the naming convention. They're a register-based 16-bit architecture, unlike the PIC16. That said, that does mean that LLVM is a much more reasonable fit to target the PIC24 (and dsPIC) than it is for PIC16. Modeling your target files after the MSP430 or Blackfin backend is likely your best bet to get up and running relatively quickly. When you run into things you need to model that aren't represented in your reference backend, then it's time to look at others to see if...

I have been analyzing the implementation for some backend (PIC16, MIPS, SPARC and MSP430) my main problem is that they are so much different, I mean obviously they are describing different architectures, but the file structure is not the same. So it is difficult to get a pattern. I have checked the available documentation files, also the video from Cardoso about how to write a backend for the

...> Hi Roberto, > > The PIC24 family of devices share very little commonality with PIC16 beyond > the naming convention. They're a register-based 16-bit architecture, unlike > the PIC16. That said, that does mean that LLVM is a much more reasonable fit > to target the PIC24 (and dsPIC) than it is for PIC16. > > Modeling your target files after the MSP430 or Blackfin backend is likely > your best bet to get up and running relatively quickly. When you run into > things you need to model that aren't represented in your reference backend, > then it's time to l...