Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-04 Thread Frank Klemm
On Mon, Oct 02, 2000 at 04:11:57AM -0600, Mark Taylor wrote: > > 4. LAME should be converted to C++ or Java. C just is not up to > the task of distinguishing between 30 different types of integers. > * Good C programs should use the following identifier for variable names: new, delete, oper

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-04 Thread Frank Klemm
> > 2. I dont think declaring the sample rate as 'long double' is enough. We > need to add a portable, object oriented arbritrary precision floating > point library to LAME. The sample rate should be a default of > 128 digits, but the user can increase this with suitable > options. > Mathemati

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-04 Thread Frank Klemm
:: :: 3. Creating a dozen or so odd types, all synonymous with 'int' :: is a great idea. But I saw a few 'int's left. I think :: we need to replace these with more new types. :: When you were a physicist, you were a cgs advocate and a SI enemy, right? -- Mit freundlichen Grüßen Frank

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-02 Thread Takehiro Tominaga
>This is a good idea. Some comments (Frank: not all of these are serious:-) I am serious :) > 5. All developers should be required to take 200 hours of UML training > before working on any more code. 6. Learn more about CVS, especially about making your own branch. --- [EMAIL PROTECTED] // may

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-02 Thread Mark Taylor
> What about the proposal to design and discuss a well designed lame API now > without implementation? AFAICS this takes at least 3 months, if you want to > have a durable and neat API, Mark don't want to change the API until summer > 2001. May be should use this time to design all the structur

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-02 Thread Frank Klemm
On Sun, Oct 01, 2000 at 09:10:19PM +0200, Robert Hegemann wrote: > > So for backward compatibility we should make a wrapper library > with the old interface (as much as possible) and mark this as > old and outdated, to give clients the possibility for smooth > migration t

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-01 Thread Mark Taylor
Hi Robert, This just seems like a lot of work for no real gain since all 4 libraries are samll and closely related. To build LAME we would need a ./configure setup which builds 4 different libraries. so I guess I just dont see any reason to seperate them. Special applications, like embeded en

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-01 Thread Robert Hegemann
Mark Taylor schrieb am Son, 01 Okt 2000: > > > > >I think the mp3 encoding library should do what it is > > >supposed to do, encode pcm samples into mp3 frames. > > > > BTW, Robert and everyone, how should we treat with mpglib and lame_mp3_XX > > routines in frontend/get_audio.c and amiga_mpega.

Re: [MP3 ENCODER] mpglib related routines (Re: modularization)

2000-10-01 Thread Mark Taylor
> > >I think the mp3 encoding library should do what it is > >supposed to do, encode pcm samples into mp3 frames. > > BTW, Robert and everyone, how should we treat with mpglib and lame_mp3_XX > routines in frontend/get_audio.c and amiga_mpega.c ? > > I think these routine should be another li

[MP3 ENCODER] mpglib related routines (Re: modularization)

2000-09-30 Thread Takehiro Tominaga
>I think the mp3 encoding library should do what it is >supposed to do, encode pcm samples into mp3 frames. BTW, Robert and everyone, how should we treat with mpglib and lame_mp3_XX routines in frontend/get_audio.c and amiga_mpega.c ? I think these routine should be another library, and the libr