toolame-devel Mailing List for toolame
Status: Alpha
Brought to you by:
mikecheng
Menu
▾
▴
toolame-devel — Development of toolame (layer 2 audio encoder)
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
(2) |
Mar
(8) |
Apr
|
May
(25) |
Jun
(1) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2004 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
(4) |
Dec
(3) |
| 2005 |
Jan
|
Feb
(6) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: GILBERTO S. <gl...@em...> - 2006-04-28 16:57:41
|
Hello, I had trying to download the toolame package and all link's said=20 ___________________________________________________________________________= ___ High security alert!!! You are not permitted to download the file "toolame-02l.tgz". URL =3D http://internap.dl.sourceforge.net/sourceforge/toolame/toolame-02l.= tgz =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ |
|
From: Stephen S. <lp...@pa...> - 2005-04-15 23:20:20
|
Hi, Thanks for the information, I've been wondering what was happening with the development. I have the new site bookmarked, and hopefully someone will look into it for inclusion into MPlayer, also. Take care, Steve On Fri, 15 Apr 2005, Nicholas J Humfrey wrote: > > Hi, > > > I decided to go ahead with the fork of toolame, and called it TwoLAME. > > > I started a new SourceForge project: > > http://twolame.sourceforge.net/ > > > Features added: > > - Fully thread-safe > - Static and shared library (libtwolame) > - API very similar to LAME's (for easy porting) > - Frontend supports wider range of input files (using libsndfile) > - automake/libtool/pkgconfig based build system > > A lot of other internal changes have been made too. > > > Mike Cheng's homepage seems to have disappeared completely now. If anyone has > any other patches/improvements to toolame, I would be happy to look at > incorporating them into TwoLAME. > > Thanks to Christophe Massiot, VLC will soon use TwoLAME. > > > > nick. > |
|
From: Nicholas J H. <nj...@ec...> - 2005-04-15 21:54:09
|
Hi, I decided to go ahead with the fork of toolame, and called it TwoLAME. I started a new SourceForge project: http://twolame.sourceforge.net/ Features added: - Fully thread-safe - Static and shared library (libtwolame) - API very similar to LAME's (for easy porting) - Frontend supports wider range of input files (using libsndfile) - automake/libtool/pkgconfig based build system A lot of other internal changes have been made too. Mike Cheng's homepage seems to have disappeared completely now. If anyone has any other patches/improvements to toolame, I would be happy to look at incorporating them into TwoLAME. Thanks to Christophe Massiot, VLC will soon use TwoLAME. nick. |
|
From: Christofer B. <tos...@ho...> - 2005-04-06 11:04:30
|
Greetings! My name is Christofer Bustad and I'm currently doing my 5 months master's thesis project at Swedish Radio (www.sr.se) in MPEG Audio Layer 2 coding. I'm trying to optimize the encoding algorithm for different types of material. My first aim is to write a command promt encoder where as many of the internal settings as possible can be altered. This is to be done by passing the name of a text file with settings as an argument to the encoder. I am going to base this code on the TooLame code. When this project is finnished I plan to publish the code and the report on my website (www.bustad.com). I have read most of the LGPL lisence, and as I understand the license this is legal to do. Have I interpreted the license correctly...? Thanks in advance! Best regards, Christofer Bustad _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ |
|
From: Ibro <ib...@ya...> - 2005-02-26 13:42:31
|
well, i don't mean to break a development chain. and by making another fork, ..... don't we have enough forked project to deal with ? i think it's nice to make it able to process more formats but users don't want to make things worse with dependencies. i think nic's improvements is quite nice. regards. -- Ibro __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail |
|
From: Nicholas J H. <nj...@ec...> - 2005-02-24 14:42:34
|
Hello, Mike Cheng contacted me asking me to rename/version my unofficial toolame release. I should have made it clearer in the first place. He wants to keep the toolame code simple, and doesn't want to have a dependency on libsndfile. I personally think it is very handy being able to encode other audio file formats, and supporting more variants of the WAV file format. So I think I am going to start a separate fork, based on the changes I made. Thinking of calling it twolame. Not quite as good a pun but hey! Sufficiently different ? Any other suggestions ? I look at renaming symbols, so that it compiles alongside LAME for the next release. nick. - changed build system to use automake/libtool - now builds shared library - restructured lots of code - Removed some dead code and unused files - should now be close to being thread safe - removed memory leaks / static variables - changed library API so that it is almost the same as LAMEs - hopefully not too many people have been using the old API - not too many big differences - will hopefully add resampling support to next release - API is ready for resampling support to be added - ready for downmixing to be added to libtoolame - Added libsndfile support to toolame frontend (if you have it) - moved set/get functions into get_set.c - I have broken energy levels support (sorry !) - will try and fix - Added LGPL header to the top of all the files - Added toolame_encode_buffer_interleaved - other stuff I have forgotten - Frontend displays information about the input file format - Fixed bug with audio_get_samples reading more than buffer size - Added asciidoc documentation - Added doxygen documentation |
|
From: Stephen S. <lp...@pa...> - 2005-02-23 06:35:50
|
OK, thanks for the link. I had that bookmarked once, I thought. As for the official development, I'm not sure what's happened with it. Maybe somebody will pop in here with some news. Take care, Steve On Tue, 22 Feb 2005, Ibro wrote: > well, i know that this is not an official release, but if it will .. > then i'll cry because of header conflicts with LAME. > > i got it from: > http://www.ecs.soton.ac.uk/~njh/toolame/toolame-02n-beta2.tar.gz > > maybe i should mail the responsible person, Nicholas Humfrey instead. > > > --- Stephen Stocker <lp...@pa...> wrote: > >> Hi, >> >> I must have an old link or something. Where's the 02n beta version? >> Thanks! >> >> Steve >> >> >> On Mon, 21 Feb 2005, Ibro wrote: >> >>> i like the improvements made so far, but the API that resembles LAME leads to clashes when i >> use >>> Toolame and LAME. >>> maybe you could change it into some unique structs and/or functions that will not clash with >> other >>> library/software ? >>> >>> thank you. > |
|
From: Ibro <ib...@ya...> - 2005-02-23 04:33:25
|
well, i know that this is not an official release, but if it will .. then i'll cry because of header conflicts with LAME. i got it from: http://www.ecs.soton.ac.uk/~njh/toolame/toolame-02n-beta2.tar.gz maybe i should mail the responsible person, Nicholas Humfrey instead. --- Stephen Stocker <lp...@pa...> wrote: > Hi, > > I must have an old link or something. Where's the 02n beta version? > Thanks! > > Steve > > > On Mon, 21 Feb 2005, Ibro wrote: > > > i like the improvements made so far, but the API that resembles LAME leads to clashes when i > use > > Toolame and LAME. > > maybe you could change it into some unique structs and/or functions that will not clash with > other > > library/software ? > > > > thank you. __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/ |
|
From: Stephen S. <lp...@pa...> - 2005-02-22 06:48:40
|
Hi, I must have an old link or something. Where's the 02n beta version? Thanks! Steve On Mon, 21 Feb 2005, Ibro wrote: > i like the improvements made so far, but the API that resembles LAME leads to clashes when i use > Toolame and LAME. > maybe you could change it into some unique structs and/or functions that will not clash with other > library/software ? > > thank you. > > > |
|
From: Ibro <ib...@ya...> - 2005-02-22 05:35:04
|
i like the improvements made so far, but the API that resembles LAME leads to clashes when i use Toolame and LAME. maybe you could change it into some unique structs and/or functions that will not clash with other library/software ? thank you. __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 |
|
From: Steve S. <st...@pr...> - 2004-12-02 17:25:50
|
Mike, That sounds great! It would be nice to get Nicholas' documentation onto the main Toolame site, assuming his stuff gets merged in. His documentation is here: http://www.ecs.soton.ac.uk/~njh/toolame/html/ His changelog is here: http://www.ecs.soton.ac.uk/~njh/toolame/html/changes.txt If you can get Win32 exe, DLL, and OS X compiling working right out of the source tree it seems like there's some hope encourage others including the BeSweet, CDex and Awave folks to use the main DLL and contribute back to the main source tree instead of their particular branches that are based on old Toolame code. Thanks for all your work on this. It's a great tool. Cheers, Steve On Dec 1, 2004, at 8:29 PM, mike wrote: > Hi all, > I'm still alive, but life matters have taken precedent over the past > year. > Christmas break should give me some time to catch up with fixes and > emails. > > A sort of list of things todo: > * squish any bugs: VBR bug is still there. > * finish the *nix library + assorted makefiles > * an official windows DLL (need some help here as I don't do windows) > > Any work you would like to see done, now is the time to ask it. > Mike. > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Toolame-devel mailing list > Too...@li... > https://lists.sourceforge.net/lists/listinfo/toolame-devel > > - - Steve Schultze Technical Manager, The Public Radio Exchange http://www.prx.org |
|
From: mike <mik...@pl...> - 2004-12-02 01:30:10
|
Hi all, I'm still alive, but life matters have taken precedent over the past year. Christmas break should give me some time to catch up with fixes and emails. A sort of list of things todo: * squish any bugs: VBR bug is still there. * finish the *nix library + assorted makefiles * an official windows DLL (need some help here as I don't do windows) Any work you would like to see done, now is the time to ask it. Mike. |
|
From: Steve S. <st...@pr...> - 2004-12-02 00:26:59
|
Nicholas, I'll hook you up with Markus Jonsson and try to get him to join this list. He created ToolameF.dll based on Toolame 0.2l for his program Awave Audio and posted about it here: http://www.hydrogenaudio.org/forums/index.php?showtopic=29634 What are your thoughts on getting your source tree merged with the main Toolame tree? Is it just that Mike has disappeared? It'd be great to have a reliable contact for the main tree. I wish I could give hands-on help, but I'm not much of a c programmer. MP2 is an important format for my nonprofit and others in radio. It's increasingly used for exchanging audio for broadcast and is much favored over MP3. Cheers, Steve On Nov 25, 2004, at 3:50 PM, Nicholas J Humfrey wrote: > Sorry, I don't run Windows and have never made a DLL. > > But I would suspect that now there is a toolame library / API, then > making a DLL would be much easier and probably more standard. > > If someone were to produce instructions / a Visual C/whatever project, > then I would be happy to include it in my source code release. > > > nick. > > > On 24 Nov 2004, at 21:05, Steve Schultze wrote: > >> I just posted a topic on the Hydrogen Audio forums asking questions >> about the various Toolame DLLs that exist. If anyone has any >> insights, please post a response there. The biggest question is >> whether or not it's possible to generate a single DLL and windows >> executable straight out of the Toolame source tree in order to avoid >> the multiple confusing and incompatible forks that now exist. Has >> the librification effort made this a more likely possibility? >> >> http://www.hydrogenaudio.org/forums/index.php?showtopic=29634 >> >> - - >> Steve Schultze >> Technical Manager, The Public Radio Exchange >> http://www.prx.org >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://productguide.itmanagersjournal.com/ >> _______________________________________________ >> Toolame-devel mailing list >> Too...@li... >> https://lists.sourceforge.net/lists/listinfo/toolame-devel > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Toolame-devel mailing list > Too...@li... > https://lists.sourceforge.net/lists/listinfo/toolame-devel > - - Steve Schultze Technical Manager, The Public Radio Exchange http://www.prx.org - - Steve Schultze Technical Manager, The Public Radio Exchange http://www.prx.org |
|
From: Nicholas J H. <nj...@ec...> - 2004-11-25 20:51:12
|
Sorry, I don't run Windows and have never made a DLL. But I would suspect that now there is a toolame library / API, then making a DLL would be much easier and probably more standard. If someone were to produce instructions / a Visual C/whatever project, then I would be happy to include it in my source code release. nick. On 24 Nov 2004, at 21:05, Steve Schultze wrote: > I just posted a topic on the Hydrogen Audio forums asking questions > about the various Toolame DLLs that exist. If anyone has any > insights, please post a response there. The biggest question is > whether or not it's possible to generate a single DLL and windows > executable straight out of the Toolame source tree in order to avoid > the multiple confusing and incompatible forks that now exist. Has the > librification effort made this a more likely possibility? > > http://www.hydrogenaudio.org/forums/index.php?showtopic=29634 > > - - > Steve Schultze > Technical Manager, The Public Radio Exchange > http://www.prx.org > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Toolame-devel mailing list > Too...@li... > https://lists.sourceforge.net/lists/listinfo/toolame-devel |
|
From: Steve S. <st...@pr...> - 2004-11-24 21:02:28
|
I just posted a topic on the Hydrogen Audio forums asking questions about the various Toolame DLLs that exist. If anyone has any insights, please post a response there. The biggest question is whether or not it's possible to generate a single DLL and windows executable straight out of the Toolame source tree in order to avoid the multiple confusing and incompatible forks that now exist. Has the librification effort made this a more likely possibility? http://www.hydrogenaudio.org/forums/index.php?showtopic=29634 - - Steve Schultze Technical Manager, The Public Radio Exchange http://www.prx.org |
|
From: Nicholas H. <nj...@ec...> - 2004-11-15 15:03:46
|
I'm afraid I don't know the answer to this one, but would be interested if you found the result. nick. At 11:36 pm +1100 15/11/04, Tom Mander wrote: >Hi, > >Does anyone know how much the toolame encoder introduces when creating a >MPEG 1 Layer II audio file. My experiments using the mpg321 decoder >indicate a 10ms total delay is introduced using 48kHz material on >the complete encode/decode cycle. For proper A/V sync in a muxed >Program Stream file I'm presuming the PTS offset should only include >the delay from the encoder. I know frame lengh, filterbank delay, >look-ahead block switching delay and possibly also bit reservoir >all contribute, but does anyone know the total amount for this encoder? > >Thanks, > >Tom > > >------------------------------------------------------- >This SF.Net email is sponsored by: InterSystems CACHE >FREE OODBMS DOWNLOAD - A multidimensional database that combines >robust object and relational technologies, making it a perfect match >for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 >_______________________________________________ >Toolame-devel mailing list >Too...@li... >https://lists.sourceforge.net/lists/listinfo/toolame-devel |
|
From: Tom M. <to...@pr...> - 2004-11-15 12:37:28
|
Hi, Does anyone know how much the toolame encoder introduces when creating a MPEG 1 Layer II audio file. My experiments using the mpg321 decoder indicate a 10ms total delay is introduced using 48kHz material on the complete encode/decode cycle. For proper A/V sync in a muxed Program Stream file I'm presuming the PTS offset should only include the delay from the encoder. I know frame lengh, filterbank delay, look-ahead block switching delay and possibly also bit reservoir all contribute, but does anyone know the total amount for this encoder? Thanks, Tom |
|
From: Stephen S. <lp...@pa...> - 2004-09-23 00:51:36
|
Hi, Well, I'm supposed to be subbed to this list, but I might not have set my spam filter correctly to let it through. Anyway, thanks for the work you're putting into this! It builds fine on Slackware (still with gcc 2.95.3, which seems to be the best overall). I'm going to see if MEncoder's newly-added TooLame encoding support will work OK with this version. If you use MPlayer/MEncoder, it's a real improvement, I think. Take care, Steve |
|
From: Nicholas H. <nj...@ec...> - 2004-09-17 18:40:16
|
Fixed the problem I was having under Linux - it was a silly buffer overflow mistake ! Here is my next release: http://www.ecs.soton.ac.uk/~njh/toolame/toolame-02n-beta2.tar.gz I have done some documenting. Documentation is generated using asciidoc and doxygen: http://www.ecs.soton.ac.uk/~njh/toolame/html/ I have decided to not use libsamplerate because it is GPL. And gone for libresample instead, which like toolame is LGPL. To make compiling simpler, I have included the library in the toolame source code (in its own directory). I will try and get resampling and downmixing all working for my next release. I would be interested in peoples feedback - I haven't done a huge amount of testing of the various toolame parameters with the new code - I hope I haven't broken too much. Cheers, nick. |
|
From: Nicholas H. <nj...@ec...> - 2004-09-14 20:23:36
|
Hi, I have been doing some work on toolame and decided to show you all the work I have done so far: http://www.ecs.soton.ac.uk/~njh/toolame/toolame-02n-beta1.tar.gz I developed it on my Mac (10.3.5) but just tried it on an i686 Linux box and it compiled fine, but had stupid runtime problem. I have been working quite hard on this without any feedback, so I decided not delay the release. Here is a summary of the work I have done: - changed build system to use automake/libtool - now builds shared library - restructured lots of code - Removed some dead code and unused files - should now be close to being thread safe - removed memory leaks / static variables - changed library API so that it is almost the same as LAMEs - hopefully not too many people have been using the old API - not too many big differences - will hopefully add resampling support to next release - API is ready for resampling support to be added - ready for downmixing to be added to libtoolame - Added libsndfile support to toolame frontend (if you have it) - moved set/get functions into get_set.c - I have broken energy levels support (sorry !) - will try and fix - Added LGPL header to the top of all the files - Added toolame_encode_buffer_interleaved - other stuff I have forgotten I will try and get the Linux problem worked out and solved ASAP ! Although I have made some major chances, I am not trying to fork the code - let me know what you think Mike - I hope I haven't trampled all over your code too much or offended you in any way ! I really think that MPEG Layer 2 has some real advantages (licensing being a major one !) and hope my changes will allow people to integrate a industry standard audio encoder into their Open Source product more easily. Cheers, nick. |
|
From: Stephen S. <lp...@pa...> - 2004-09-02 06:53:58
|
> Hi, > > I have done some work on the toolame build system and converted it to > use automake and libtool. > libtool builds a shared library, which seems to work fine :) > > I have reorganised and renamed a few files to make them more standard > and keep automake happy. > > > I am still doing some work on it, but here is what I have so far: > > http://www.ecs.soton.ac.uk/~njh/toolame-02m-beta8_automake.tar.gz > > > > I have successfully built this on a Debian Linux box and on Mac OS X > 10.3.5. > > Included is a script called bootstrap, which is for developers to > update automake after changing configure.in or any of the Makefile.am > files. > > > One thought I had, was to remove the custom libwave and libaiff and use > the commonly available libaudiofile instead. Is this a good idea ? or > do you aim to be non-dependent on any libraries ? This would add proper > WAVE header parsing and be able to decode many more audio files. > > > Cheers, > > nick. Hi Nick, Thanks, and I just wanted to let you know that it builds perfectly on Slackware, too. :) I don't know where the guy went who maintains TooLame, but my 2 cents worth is that the libaudiofile idea sounds good to me. This is a really great piece of software, I hope development continues! Take care, Steve |
|
From: Nicholas H. <nj...@ec...> - 2004-08-20 10:03:47
|
Hi, I have done some work on the toolame build system and converted it to use automake and libtool. libtool builds a shared library, which seems to work fine :) I have reorganised and renamed a few files to make them more standard and keep automake happy. I am still doing some work on it, but here is what I have so far: http://www.ecs.soton.ac.uk/~njh/ toolame-02m-beta8_automake.tar.gz I have successfully built this on a Debian Linux box and on Mac OS X 10.3.5. Included is a script called bootstrap, which is for developers to update automake after changing configure.in or any of the Makefile.am files. One thought I had, was to remove the custom libwave and libaiff and use the commonly available libaudiofile instead. Is this a good idea ? or do you aim to be non-dependent on any libraries ? This would add proper WAVE header parsing and be able to decode many more audio files. Cheers, nick. |
|
From: Jesse S. <sc...@gm...> - 2004-07-31 03:26:32
|
Update, turns out after much banging of my head into a brick wall, I finaly figured out that even though the test.aiff file sounded like it was ok, other encoders produced the same noise after converting. Now my question is simply what is the best way to convert *input* to PCM, I may have Prophet Systems formated .wav files, .mp3, or .wav in pcm format. On Fri, 30 Jul 2004 12:14:41 -0400, Jesse Schoch <sc...@gm...> wrote: > I've been having lots of problems with noise in my output. see below. > > Snip, snip > > > > > > Batch converting is trivially simple on Linux -- it just takes a little shell > > scripting. Something like: > > > > #!/bin/bash > > for i in /some_dir/*.wav; > > do toolame -m s -b 256 "$i"; > > done > > I did quite a bit of expirimentation last night (I actualy got past > research and started building ) but I could not output an acceptable > quality file. > > I grabbed libmad (a high quality decoder ???) and libmad-dev with my > friendly apt-get, I also grabbed madllb which should output pcm from > a .wav file. The problem was that though I could create an acceptable > sounding .aiff file with madlld and sox, I could not do the same with > toolame and your patch (didnt' try without your patch). > > Generating the .aiff file with madlld > ./madlld < This_land_is_your_land.mp2 |sox -r 44100 -t cdr - test.aiff > madlld: 256000 kb/s audio MPEG layer II stream without CRC, normal LR > stereo with no emphasis at 44100 Hz sample rate > madlld: end of input stream > madlld: 7299 frames decoded (3:10.667). > > Various toolame attempts > > ./madlld <This_land_is_your_land.mp2| toolame -t 2 -p 2 -v 10 -s 44.1 > -e -b 256 -W - out.mp2 > -------------------------------------------- > Input File : 'stdin' 44.1 kHz > Output File: 'out.mp2' > 256 kbps MPEG-1 Layer II stereo Psycho model=2 (Mode_Extension=0) > [De-emph:Off Copyright:No Original:No CRC:On] > [Padding:Off Byte-swap:Off Chanswap:Off DAB:Off] > VBR Enabled. Using MNR boost of 10.000000 > ATH adjustment 0.000000 > -------------------------------------------- > encode_init: using tablenum 1 with sblimit 30 > madlld: 256000 kb/s audio MPEG layer II stream without CRC, normal LR > stereo with no emphasis at 44100 Hz sample rate > absthr[][] sampling frequency index: 1 > madlld: end of input stream > madlld: 7299 frames decoded (3:10.667). > Hit end of audio data > VBR stats: > 32 48 56 64 80 96 112 128 160 192 224 256 320 384 > 0 0 0 0 0 0 0 0 0 52 116 67 7064 0 > Avg slots/frame = 1034.129; b/smp = 7.18; bitrate = 316.702 kbps > > Done > > toolame -b 256 test.aiff outMP2.mp2 > >>> Using Audio IFF sound file headers > Parsing AIFF audio file > >>> 44100.000000 Hz sampling frequency selected > -------------------------------------------- > Input File : 'test.aiff' 44.1 kHz > Output File: 'outMP2.mp2' > 256 kbps MPEG-1 Layer II j-stereo Psy model 1 > [De-emph:Off Copyright:No Original:No CRC:Off] > [Padding:Normal Byte-swap:Off Chanswap:Off DAB:Off] > ATH adjustment 0.000000 > -------------------------------------------- > encode_init: using tablenum 1 with sblimit 30 > [2200]] > Hit end of audio data > Avg slots/frame = 835.918; b/smp = 5.80; bitrate = 256.000 kbps > > Done > |
|
From: Jesse S. <sc...@gm...> - 2004-07-31 02:32:17
|
I'm using madplayer which works great for BWF and raw MP2 encoding, but the mp3 encoding with lame is not working. I would imagine that it would be fairly easy to write both BWF and MP2 output at the same time as the frame data is the same. Is that assumption correct? On Fri, 30 Jul 2004 17:39:11 -0400, Fred Gleason <fr...@sa...> wrote: > On Friday 30 July 2004 16:19, you wrote: > > Update, turns out after much banging of my head into a brick wall, I > > finaly figured out that even though the test.aiff file sounded like it > > was ok, other encoders produced the same noise after converting. Now > > my question is simply what is the best way to convert *input* to PCM, > > I may have Prophet Systems formated .wav files, .mp3, or .wav in pcm > > format. > > Have you tried mpg321? > > Cheers! > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Director of Broadcast Software Development | > | | Salem Radio Labs | > |-------------------------------------------------------------------------| > | All progress is based upon a universal innate desire of every organism | > | to live beyond its income. | > | -- Samuel Butler | > | "Notebooks" | > |-------------------------------------------------------------------------| > > |
|
From: Fred G. <fr...@sa...> - 2004-07-30 21:43:43
|
On Friday 30 July 2004 16:19, you wrote: > Update, turns out after much banging of my head into a brick wall, I > finaly figured out that even though the test.aiff file sounded like it > was ok, other encoders produced the same noise after converting. Now > my question is simply what is the best way to convert *input* to PCM, > I may have Prophet Systems formated .wav files, .mp3, or .wav in pcm > format. Have you tried mpg321? Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Director of Broadcast Software Development | | | Salem Radio Labs | |-------------------------------------------------------------------------| | All progress is based upon a universal innate desire of every organism | | to live beyond its income. | | -- Samuel Butler | | "Notebooks" | |-------------------------------------------------------------------------| |
1 message has been excluded from this view by a project administrator.
