mad-dev

mad-dev@lists.mars.org

682 discussions

Crosscompiling for ARM - Zaurus
by Dave 03 Jul '03

03 Jul '03

Hi I've Successfully compiled madplay and it's libs for the Zaurus. Everything works. I used the following options for configure: CC=/usr/local/Embedix/tools/bin/arm-linux-gcc \ RANLIB=/usr/local/Embedix/tools/bin/arm-linux-ranlib \ ./configure --host=arm-linux \ --enable-speed \ --enable-fpm=arm \ --libdir=/opt/Qtopia/sharp/lib \ --includedir=/opt/Qtopia/sharp/include The playback sounds great. The only problem I've got is occasionally "skipping" which I'm assuming are some sort of buffering problem. The skips only occur when I run other apps while playing an MP3. They occur more often if the MP3 file is stored on an SD card or fetched from an SMB mounted file system. I haven't yet taken a good look at how madplay reads and buffers the data. I originally built it with mmap. After thinking about it - if my understanding of mmap is correct - it makes little sense on a device like the Zaurus. I rebuilt madplay without mmap (is the correct way to do this to edit config.h ?) and the skipping remains. So it seems that mmap had little effect. If mmap works on the Zaurus - when it's enabled madplay will request to have the full MP3 file "mapped" into memory to avoid disk reads while playing it (is this correct?). On the Zaurus, the MP3 will already be stored in memory, and mmap would just copy it from one chunk of memory to another. Perhaps this would save the time it take to execute the filesystem code but it would chew up memory on a limited device. Buffering - I don't know how the buffering in madplay works. I assume that buffering would be better for the Zaurus. Is madplay meant to be a robust generic MP3 player or is just to demonstrate how to use libmad? Finally, are there any other config options I should try? I'm not familiar with the ARM family of processors - I've noticed other posts that specify a specific arm chip in the config options. How about other options for libmad/madplay? Is there a way to get configure to tell you the full list of options? I tried --help but people here are mentioning options that aren't shown. I'm impressed with the work thats been done on MAD - it compiled and worked right out of the box and sounds great. The only trouble I had was figuring out how to cross compile it, and those questions were answered right here in other posts. Thanks in advance for any help offered. Dave ---------------------------------------------------------------- Dave Belser (mad(a)newww.com)

3 2

help for missing files !! Urgent !!
by Bhumika 23 Jun '03

23 Jun '03

Hi, We are trying to build the VLC code in WinCE. We are not able to bulid as some of the files are missing in MAD library. Following files are missing, 1. libmad.c 2. layer1.c 3. layer2.c 4. errno.h 5. math.c These 5 files are being used in VLC source code. We checked the source code available in FTP as well as in Mirror site. But we didnt fine these files there also. If we get these files it will be helpful for us to compile and build the source code. Please help us as it very urgent for us. Thanks, Bhumika

3 3

24 bit PCM output
by alok 23 Jun '03

23 Jun '03

Hi All, I am new to MAD Mpeg Decoder. I just want to know from which part of source code i can come to know that output will be 24 bit PCM. Regards,

2 1

Porting to PocketPC
by Tyler Montbriand 19 Jun '03

19 Jun '03

I've been attempting to port MAD to Windows CE running under ARM... it's tricky going, so far. I'm trying to convert the tons of macros that the FPM_ARM option uses to function calls, and having some limited success. The biggest problem is that Embedded Visual C++, quite simply, does NOT support inline assembler. Ever. Despite what their own docs say. Another problem is that the macros aren't documented well; they don't explicitly state what kind of arguments they take or what they return. Fortunately, EvC DOES support *external* assembly code; you can assemble an .asm file into an .obj file, turn it into a .lib then link it in with the rest of the C code. Even more fortunately, EvC is capable of converting C code to assembly code. This lets me write up a blank framework, compile it, and modify the resulting .asm file to do what I want. So now I'm down to deciphering just exactly what each macro does to the arguments. It looks like mad_f_mul(x,y) takes two mad_fixed_t arguments and returns a mad_fixed_t value, that's simple enough; but it's unclear how the others are using their arguments. Are the macro parameters for MAD_F_MLX, MAD_F_MLA, MAD_F_MLN, and mad_f_scale64 used ONLY as input parameters? 'cause if not, there's no way in heck to duplicate the full functionality of the macro in a function without operator overloading and hidden pointers; and MAD is a C project, not a C++ one.

2 1

help for missing files !! Urgent !!
by Bhumika 18 Jun '03

18 Jun '03

1 0

x86 speedup diff for libmad 0.15.0b uploaded
by Felix von Leitner 06 Jun '03

06 Jun '03

I ported my x86 speedup diff to libmad 0.15.0b. It is a trivial diff that only touches the x86 assembly and replaces shrd with two faster instructions. shrd is slow as hell on today's x86 implementations because of the not normally used semantics regarding the CPU flags. On my Athlon, Pentium 3 and VIA C3 it is about 30% faster. http://www.fefe.de/diffs/libmad-0.15.0b-speedup.diff.gz Felix

1 0

MAD suite 0.15.0b released
by Rob Leslie 05 Jun '03

05 Jun '03

At long last, MAD 0.15.0b is now available. This release is a bit different from previous releases: there are now independent packages for libmad, libid3tag, and madplay. There is not at this time an update to the MAD plug-in for Winamp; 0.14.2b is still the current release for the plug-in. Here is a summary of the important changes: General - Shared libraries are now built by default. - Cygwin builds have reverted to Cygwin dependency by default; MinGW builds are still possible with the --host=mingw32 option to 'configure'. libmad - Minor compatibility enhancements: 64th entry to Layer I/Layer II scalefactor table; allow reserved emphasis value in frame headers. - Bug fix for ARM mad_f_scale64() that was tickled by certain optimization options. - API additions: mad_f_div(), MAD_EMPHASIS_RESERVED. - Rewritten PPC fixed-point assembly. libid3tag - Numerous API additions: id3_tag_version(), id3_tag_options(), id3_tag_setlength(), id3_frame_field(), id3_field_getlatin1(), id3_field_getfulllatin1(), id3_genre_index(), id3_genre_number(), id3_latin1_ucs4duplicate(), id3_utf16_ucs4duplicate(), id3_utf8_ucs4duplicate(). - Fixed missing interfaces for other API routines. - Bug fix for segfault rendering ID3v1 tags. - Bug fix for reading ID3v2.2 frames. - Other miscellaneous improvements. madplay - Support for arbitrary resampling ratios (--sample-rate). - Support for RVA2 (relative volume adjustment) ID3 tag frames. - Keyboard controls for dynamic volume control (+/-). - Support for ancillary data output (--ancillary-output). - New audio_qnx, audio_alsa modules (untested). - New audio_carbon module (tested, for Mac OS X). - Other miscellaneous improvements. For complete details, see the CHANGES file in each package. Be sure also to review the README in each package for modified build/install instructions. You will find the new releases here: ftp://ftp.mars.org/pub/mpeg/ Windows developers who need zlib (no longer included with the above) can find a convenient package here: ftp://ftp.mars.org/pub/mpeg/extra/ (Note that zlib is already available as part of Cygwin, so you may only need this package if you are using MSVC++ or want to use MinGW to eliminate the Cygwin dependency.) Enjoy, -- Rob Leslie rob(a)mars.org

1 0

ID3 RVA2 support
by Bruce Fitzsimons 26 May '03

26 May '03

Hello I see some messages in the archive about adding support for ID3 RVA2 to madplay, but releases seem to have stopped. This tag is used to scale the played volume so a collection of mp3s can be normalised. (see the normalize application for more information) I'm interested in adding support for this to madplay or mpg321, but I'd hate to duplicate work thats already been done. madplay seems to be a hidden gem -- feature equivalent to mpg123 and mpg321, but with id3 support. Does anyone have any idea if madplay will be updated, or if I should work on mpg321 instead? Thanks, Bruce -- Bruce Fitzsimons <bruce(a)fitzsimons.org>

3 2

MAD ported to Texas Instuments DSP
by Tomasz Borukalo 26 May '03

26 May '03

Hello, some time ago somebody has asked if MAD was ported to Texas Instruments digital signal processors. I have not found any information on it, so I decided to do it by myself. I compiled and ran MAD on C6211 DSP - the slowest fixed-point chip in the C6000 family. MAD works very well, consumes 37% of CPU power in FPM_DEAFULT mode and 33% in FPM_DEFAULT/OPT_SPEED mode. I also tested MAD on C6711 DSP (the slowest floating point chip, pin-compatible with C6211), and again - MAD works well. For those who are familiar with TI's development tools: I ran MAD on 6211 and 6711 DSKs. Program uses DSP/BIOS for threads managment (SWI threads) and communication with audio codec and host. Decoded samples can be played on on-board AD535 codec, send back to PC using HST module or played through PCM3003 audio add-on card connected to 6711 DSK. If somebody is interested in obtaining project files for Code Comoser Studio (IDE enviroment by TI - something like Visual Studio), let me know. Now I plan to prepare TI-specific version of functions from fixed.h and then I will try to make MAD Algorithm Standard compatible. (Algorithm Standard is TI's standard for algorithms common API, memory managment, portability, etc - for information of those who are not TI programmers). Regards, Tomasz Borukalo borukalo(a)chip.pl

1 0

RE: Re: [mad-dev] ARM cross compile problem
by Steve Lee 26 May '03

26 May '03

Hello, Rob. Thank you for your kind explanation. I tried as you suggested, but the result was disappointing. Please, refer to the following console message and give me direction. ./configure --enable-speed --disable-debugging --enable-fpm=arm --enable-aso --host=arm CC=/opt/uClinux/bin/arm-elf-gcc RANLIB=/opt/uClinux/bin/arm-elf-ranlib LD=/opt/uClinux/bin/arm-elf-ld configure: warning: CC=/opt/uClinux/bin/arm-elf-gcc: invalid host type configure: warning: RANLIB=/opt/uClinux/bin/arm-elf-ranlib: invalid host type configure: error: can only configure for one host and one target at a time Steve Lee. (yslee(a)synertek.co.kr) -----Original Message----- From: mad-dev-admin(a)lists.mars.org [mailto:mad-dev- admin(a)lists.mars.org]On Behalf Of mad-dev-request(a)lists.mars.org Sent: Saturday, May 24, 2003 10:26 PM To: mad-dev(a)lists.mars.org Subject: mad-dev digest, Vol 1 #258 - 1 msg Send mad-dev mailing list submissions to mad-dev(a)lists.mars.org To subscribe or unsubscribe via the World Wide Web, visit http://www.mars.org/bin/mailman/listinfo/mad-dev or, via email, send a message with subject or body 'help' to mad-dev-request(a)lists.mars.org You can reach the person managing the list at mad-dev-admin(a)lists.mars.org When replying, please edit your Subject line so it is more specific than "Re: Contents of mad-dev digest..." Today's Topics: 1. Re: ARM cross compile problem (Rob Leslie) --__--__-- Message: 1 Date: Fri, 23 May 2003 11:02:03 -0700 Subject: Re: [mad-dev] ARM cross compile problem From: Rob Leslie <rob(a)mars.org> To: mad-dev(a)lists.mars.org On Friday, May 23, 2003, at 04:13 AM, @L?k<. wrote: > I am trying to run MAD on ARM7TDMI based machine. I use uClinux. > > When I execute ./configure as recommended in this mailing list, I > faced a followinf error message: > > [yslee@romeo mad-old]$ rm config.cache > [yslee@romeo mad-old]$ CC=/opt/uClinux/bin/arm-elf-gcc > RANLIB=/opt/uClinux/bin/arm-elf-ranlib LD=/opt/uClinux/bin/arm-elf-ld > ./configure --enable-speed --disable-debugging --enable-fpm=arm > --enable-aso --target=arm > [...] > checking for gcc... /opt/uClinux/bin/arm-elf-gcc > checking whether the C compiler (/opt/uClinux/bin/arm-elf-gcc ) > works... no > configure: error: installation or configuration problem: C compiler > cannot create executables. > > How can I solve this problem? Try invoking 'configure' like this: ./configure --enable-speed --disable-debugging --enable-fpm=arm \ --enable-aso --host=arm \ CC=/opt/uClinux/bin/arm-elf-gcc \ RANLIB=/opt/uClinux/bin/arm-elf-ranlib \ LD=/opt/uClinux/bin/arm-elf-ld The reason: 1. --target is for building cross-compilers only. Use --host to specify the system that will run the code you are compiling now. 2. The autoconf suite prefers that you pass environment variables on the command line rather than through the environment, to overcome certain problems propagating the values. -- Rob Leslie rob(a)mars.org End of mad-dev Digest --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.478 / Virus Database: 275 - Release Date: 2003-05-06

2 1

← Newer
1
...
33
34
35
36
37
38
39
...
69
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

mad-dev