Branches
Articles referencing this project
Comments
[»]
lame_enc.dll
by ko4bb - Dec 21st 2003 19:37:14
The zipped archive of the Windows distribution contains a README that
refers to an API file for info about the lame_enc.dll, but there is no API
file in the archive. A quick search on Google found the Linux API many
times, but no Windows.
Where can I get API info (and maybe a sample for use from within VB 6.0,
if I may ask?)?
Thanks
--
ko4bb
[reply]
[top]
[»]
id3 tags
by stibor - Aug 13th 2002 11:27:42
Could you make lame to first write id3 tag and than encode to
mpeg file?
Because when encoding is interrupted, file seems to know nothing about id3
tags, and someone (like me) can feel it does not work.
[reply]
[top]
[»]
Lame - appropriate name
by Shadoglare - May 1st 2002 22:06:37
OK - first off this thing was a total pain in the ass to install.
Secondly, after spending literally days tracking down & installing the
dependancies it needs, it doesn't work.
Creates bogus/empty mp3 files.
Use bladeenc instead - it actually works.
[reply]
[top]
[»]
Re: Lame - appropriate name
by brainwasher - Sep 10th 2002 05:23:46
> OK - first off this thing was a total
> pain in the ass to install.
> Secondly, after spending literally days
> tracking down & installing the
> dependancies it needs, it doesn't work.
Use one of the pre-built executables, like
notlame:
http://www.idiap.ch/~sanders/not_lame/
[reply]
[top]
[»]
./configure --with-vorbis troubles
by Neil Watson - Feb 1st 2002 12:02:33
The ./configure --with-vorbis works ok but when I do a
make:
vorbis_interface.c:15:28: codec_internal.h: No such file
or directory
vorbis_interface.c:16:22: registry.h: No such file or
directory
vorbis_interface.c:17:25: modes/modes.h: No such file
or directory
vorbis_interface.c: In function
`lame_decode_ogg_fromfile':
vorbis_interface.c:218: warning: initialization from
incompatible pointer type
make[3]: *** [vorbis_interface.lo] Error 1
I have vorbis tools and libvorbis RC3 built, installed and
running.
[reply]
[top]
[»]
Re: ./configure --with-vorbis troubles
by Arne Flones - Jun 22nd 2002 20:53:37
> The ./configure --with-vorbis works ok
> but when I do a
> make:
> vorbis_interface.c:15:28:
> codec_internal.h: No such file
> or directory
> vorbis_interface.c:16:22: registry.h: No
> such file or
> directory
> vorbis_interface.c:17:25: modes/modes.h:
> No such file
> or directory
> vorbis_interface.c: In function
> `lame_decode_ogg_fromfile':
> vorbis_interface.c:218: warning:
> initialization from
> incompatible pointer type
> make[3]: *** [vorbis_interface.lo] Error
> 1
>
> I have vorbis tools and libvorbis RC3
> built, installed and
> running.
>
>
You need to install libvorbis from source:
oggvorbis Downloads
or if you have already installed libvorbis, maybe you should include its
path: e.g.,
"--with-vorbis-prefix=/usr/local"
[reply]
[top]
[»]
Re: ./configure --with-vorbis troubles
by Arne Flones - Jun 22nd 2002 21:12:16
Nevermind about my previous post. I have been able to repeat your problem
exactly, thanks to your good error message listing.
Here's the deal. You mistakenly compiled the tarball version of libvorbis
with the sequence:
./autogen.sh
make
This only works for the CVS version, not the tarball. What you have to do
is the following.
In the libvorbis source directory:
make clean
./configure
make
make install
Then, in the lame directory:
make clean
./configure --with-vorbis
make
make install
This should fix it.
[reply]
[top]
[»]
Re: ./configure --with-vorbis troubles
by Christian Neumann - Aug 14th 2002 13:02:16
> Nevermind about my previous post. I
> have been able to repeat your problem
> exactly, thanks to your good error
> message listing.
>
> Here's the deal. You mistakenly
> compiled the tarball version of
> libvorbis with the sequence:
>
> ./autogen.sh
> make
> This only works for the CVS version, not
> the tarball. What you have to do is the
> following.
>
> In the libvorbis source directory:
> make clean
> ./configure
> make
> make install
>
>
> Then, in the lame directory:
> make clean
> ./configure --with-vorbis
> make
> make install
>
>
> This should fix it.
>
Hi,
I have the same problem and I compiled libvorbis and libogg (both release
1.0) with configure (though with --prefix=/usr) and make and still those
said files are nowhere to be found. I rechecked the Ogg-Vorbis page for the
rpm packages (normal and devel) and both don't have those files. Is it
possible that they are an older legacy that are no longer in the 1.0
release?
[reply]
[top]
[»]
Re: ./configure --with-vorbis troubles
by Holden Caufield - Sep 15th 2002 14:34:27
this is not right either.
codec_internal.h is not in the current stable source tree of libvorbis
> Nevermind about my previous post. I
> have been able to repeat your problem
> exactly, thanks to your good error
> message listing.
>
> Here's the deal. You mistakenly
> compiled the tarball version of
> libvorbis with the sequence:
>
> ./autogen.sh
> make
> This only works for the CVS version, not
> the tarball. What you have to do is the
> following.
>
> In the libvorbis source directory:
> make clean
> ./configure
> make
> make install
>
>
> Then, in the lame directory:
> make clean
> ./configure --with-vorbis
> make
> make install
>
>
> This should fix it.
>
[reply]
[top]
[»]
Re: ./configure --with-vorbis troubles
by Peter Nehrer - Mar 7th 2003 08:47:19
This may come a bit too late, seeing the date of your post... I had this
problem in RH8 w/ all the latest rpms. I simply deleted the missing
#includes from libmp3lame/vorbis_interface.c and recompiled with success.
--Peter
[reply]
[top]
[»]
VBR?
by SubPar - Aug 8th 2000 03:21:26
OK, I'll take this one up. How exactly does VBR suck? All it is is
adjusting the bitrate depending upon how many bits are need to accurately
represent a frame of audio. The upshot is that disk space isn't wasted by
a frame using more bits than it really needs, resulting in higher quality
using less disk space. What's wrong with that? If there's a downside to
VBR, I'd like to hear it because I haven't found any.
[reply]
[top]
[»]
Re: VBR?
by Raven Morris - Nov 20th 2002 02:03:19
> OK, I'll take this one up. How exactly
> does VBR suck? All it is is adjusting
> the bitrate depending upon how many bits
> are need to accurately represent a frame
> of audio. The upshot is that disk space
> isn't wasted by a frame using more bits
> than it really needs, resulting in
> higher quality using less disk space.
> What's wrong with that? If there's a
> downside to VBR, I'd like to hear it
> because I haven't found any.
I'm with you ...
The only downside to VBR MP3s are that Winamp/XMMS don't accurately read
the track lengths (or at least they didn't used to).
Now, if you want the best way ... Ogg/Vorbis VBR. Mmm-mmm, good.
--
"Time flies like an arrow. Fruit flies like a banana." -- Groucho Marx
[reply]
[top]
[»]
FUD?
by Spirilis - Jun 16th 2000 01:19:31
BladeEnc sounds better than LAME? 'Scuse me? (try lame's -k option)
And yes, VBR does suck. Lame is still at least twice faster than BladeEnc
on my machine, though.
And there's 'gogo', which took a version of lame and added x86 ASM
optimizations to it I think.
[reply]
[top]
[»]
Bitrate
by Sesse - Nov 3rd 1999 08:20:04
I'm not trying to take any sides here (I haven't even tried LAME), but I
think BladeEnc is optimized for bitrates above 128 kB. Fraunhoffer
is (according to the BladeEnc docs) optimized for lower bitrates, which
gives a negative impact on sound quality on higher bitrates.
[reply]
[top]
[»]
This cheerleading is getting LAME
by Ptolemy - Jul 3rd 1999 10:13:17
I don't know what rally cry of the oppressed went out, but the huge
increase in messages ditching on other encoders to favour LAME is getting
downright annoying.
Folks, learn that diversity is a good thing. I, personally, loathe VBE,
which is what LAME uses to get it's incredible speed. I've listened to
samples from LAME and BladeEnc, and LAME sounds worse.
If people want to try something different than what they're using, they'll
find it on their own time. Ditching on other people's hard work is not The
Freshmeat Way.
Well, maybe it is, but that doesn't mean it's right.
[reply]
[top]
|
