Hi just some comments. I think mp3 is going obsolete pretty soon.why dno't we move on to some topics like mp3 pro or wma?
Hi All !
>
i try to use lame mp3 encoder =
>(and decoder)=20
>to create a sort of media archiver for old enough game's databases which =
>
>currently saves sounds in .wav ...
>
but when i try to encode and then =
>decode=20
>sample .wav file i.e. .wav -> .mp3 -> .wav =
>(VBR)
>
i get strange result - at the =
>output=20
>.wav the size of 'data' block exceeds the size of the 'source' =
>.wav data="20"
>at about 2..3% ... why ? can i get its sizes equal by any way ? =
>
>
i take 'data' block from my =
>game's database=20
>and have to insert exact block (in bytes) after decompressing or =
>database's=20
>format would crashes :( ... i.e. i need a way to keep the size of =
>data="20"
>samples of the same size in bytes as in the 'source' .wav =
>(database) ...=20
>
>
can anyone comment this situation =
>
>?
>
>------=_NextPart_000_0072_01C1A624.8BF690F0--
>
>
>
>--__--__--
>
>Message: 2
>Date: Fri, 25 Jan 2002 13:44:13 -0700
>From: Mark Taylor <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: [MP3 ENCODER] MS Stereo
>Reply-To: [EMAIL PROTECTED]
>
>
> >
> > Hi all,
> >
> > Just to inquire more about MS Stereo. I am confused about how the block is
> > decided between long and short blocks.
> >
> > In the previous algorithm, the blocks are decided based on LR thresholds
> > after L3psycho_anal. Is that true? Can't we use the final LR/MS thresholds ie
> > fthr for the block decision.
> >
> > One more thing on bmax(b) from 13818-7 MS Stereo section. Is that applied to
> > both short and long blocks? In lame 3.21, I notice that it is use on the
> > scalefactorbands instead of the partitions. So when the standard states to
> > calculate the LR/MS and final thresholds, it actually means the LR/MS ratios in
> > the after calculating the PE. Is that right?
> >
> > Will appreciate all assistance.
> >
> > Hann Long
> > NUS Student
> >
>
>Keep in mind that the ISO documentation is required since the format
>is going to be some kind of standard. But the companies writing
>it are surely *not* trying to make it easy for other people
>to impliment a good encoder, and I'm sure they leave out as much
>as possible. So if something in the ISO docs does (like the completely
>broken M/S stereo "sparsing") not make sense, try other strategies.
>Tonality estimation is another good example - the default tonality
>estimater in the FhG mp3 encoder is not what is given in the ISO
>docs.
>
>If you do experiment with other algorithms and find something that
>works well, I hope you'll share your experiences with this list.
>
>Mark
>
>
>
>
>
>
>
>--__--__--
>
>_______________________________________________
>mp3encoder mailing list
>[EMAIL PROTECTED]
>http://minnie.tuhs.org/mailman/listinfo/mp3encoder
>
>End of mp3encoder Digest
������� MSN Explorer��http://explorer.msn.com/lccn/intl.asp��
_______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
