Re: mp3 encoding - lame?
jurriaan wrote: > I did run memtest86 after overclocking, no problems during a 24 hrs > period. The I compiled 250 kernels, which were all identical. Still, > lame is obviously very sensitive. > The moral of the story: overclocking a 3700 San Diego to 2750 MHz works > most of the time, but not with lame. For now, 2640 works a lot better. > > >>- Check to make sure your system is being cooled adequately. > > > the cpu is never above 45 degrees C. > >>- Run memtest86 and see if it likes your RAM. > > > 24 hrs - no problems. > > This must sound lame, but I really thought I had it stable, with memtest > and compiling kernels. No, it's only LAME once you get it working right. :) Kernel compilation might not be so good a test since it's heavy in I/O -- your CPU isn't working as much while it's waiting for the hard disk and cools down somewhat. I've mostly used mencoder for stability testing in the past. Burnk7 (from the i386 cpuburn package) is very good for heating up the CPU, though, and I might start using that instead of mencoder. Bzip2 seems to work well for testing overclocked RAM, but I try to stay away from that. -Corey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
From: Corey Hickey <[EMAIL PROTECTED]> Date: Sun, Aug 21, 2005 at 11:45:44AM -0700 X-XS4All-To: > jurriaan wrote: > > > > This is with my own gcc-4.0 compiled lame. Sometimes it hangs, most of > > the time it crashes on this file. AFAIK the .wav file is OK, it plays > > and is a decompressed .flac file. It's 5.8 MiB, btw. > > Are you saying that your lame behaves differently if you run it multiple > times on the same file? If that is the case you almost certainly have > faulty or overheating hardware. > > - If you're overclocking, don't do so as much. I did run memtest86 after overclocking, no problems during a 24 hrs period. The I compiled 250 kernels, which were all identical. Still, lame is obviously very sensitive. The moral of the story: overclocking a 3700 San Diego to 2750 MHz works most of the time, but not with lame. For now, 2640 works a lot better. > - Check to make sure your system is being cooled adequately. the cpu is never above 45 degrees C. > - Run memtest86 and see if it likes your RAM. 24 hrs - no problems. This must sound lame, but I really thought I had it stable, with memtest and compiling kernels. Thanks, Jurriaan -- Corporal... get me the cassette of Spaceballs: The Movie. Debian (Unstable) GNU/Linux 2.6.13-rc4-mm1 5286 bogomips load 0.44 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
jurriaan wrote: > Script started on Sun 21 Aug 2005 02:49:45 PM CEST > INTEL :cat test.in > file /usr/local/bin/lame > r --vbr-new -V 0 "18 US Forces.wav" > bt > INTEL :rm *mp3; gdb < test.in > > Program received signal SIGSEGV, Segmentation fault. > 0x0045224b in quantize_x34 () > (gdb) #0 0x0045224b in quantize_x34 () > #1 0x00456cdb in VBR_noise_shaping () > #2 0x0044d888 in VBR_iteration_loop () > #3 0x00443abb in lame_encode_mp3_frame () > #4 0x0040f126 in lame_encode_buffer_sample_t () > #5 0x004104e7 in lame_encode_buffer_int () > #6 0x00402a6e in lame_encoder () > #7 0x00403763 in main () > > This is with my own gcc-4.0 compiled lame. Sometimes it hangs, most of > the time it crashes on this file. AFAIK the .wav file is OK, it plays > and is a decompressed .flac file. It's 5.8 MiB, btw. Are you saying that your lame behaves differently if you run it multiple times on the same file? If that is the case you almost certainly have faulty or overheating hardware. - If you're overclocking, don't do so as much. - Check to make sure your system is being cooled adequately. - Run memtest86 and see if it likes your RAM. For what it's worth, my machine has no problem with your test file and "--vbr-new -V 0". You can try my deb if you want, but I suspect your problems are hardware-related. http://fatooh.org/files/lame_3.96-0.1_amd64.deb -Corey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
are vorbis codecs a solution? Dean Corey Hickey wrote: Darnit, I forgot to send this to the list. Sorry. Azer Demir wrote: there is a package called toolame, it is nearly identical to lame, but it is a different project. in i386 (and maybe in other archs) lame package is available, but not in amd64, i don't know why. but i used toolame with grip(you can use it in command-line), it works fine.you just configure your encoder type like "other", and write encoder executable like "/usr/bin/toolame" in Config/Encode/Encoder path in tabs. tooLAME is an MPEG-1 layer 2 encoder; LAME is layer 3. I've never used tooLAME, though, so perhaps it works about as well. As far as I know, LAME isn't included in Debian for legal reasons. --- To the original poster: Unless you need to make an mp3 for a hardware player or something, you'd be better off using oggenc. I just tried the lame package from marillat; it seems to work fine for me. I fed it the audio from a two-hour movie and about an hour of /dev/urandom. No problem either for a LAME I just built myself using gcc-4.0 Can you provide a sample source audio file (perhaps cut down to a reasonable size using dd)? Also give the exact command you're using to encode. I'll see if I can reproduce your problem on my system. --- On a related note: The lame source can be easily compiled into a debian package. Whenever you see a debian directory in a source tree you can just run: $ dpkg-buildpackage -rfakeroot -uc -b If you know you have the build dependencies met you can run instead: $ fakeroot debian/rules binary (which is a little easier to type) If you decide to build yourself a debian package of LAME be sure to run `make uninstall` in the source tree first. Things can get confusing with a package installed to /usr and the same program installed to /usr/local. -Corey -- WWW: http://dean.bong.com.au LAN: http://www.bong.com.au EMAIL: [EMAIL PROTECTED] or [EMAIL PROTECTED] ICQ: 16867613 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
Darnit, I forgot to send this to the list. Sorry. Azer Demir wrote: > there is a package called toolame, it is nearly identical to lame, but > it is a different project. in i386 (and maybe in other archs) lame > package is available, but not in amd64, i don't know why. but i used > toolame with grip(you can use it in command-line), it works fine.you > just configure your encoder type like "other", and write encoder > executable like "/usr/bin/toolame" in Config/Encode/Encoder path in tabs. tooLAME is an MPEG-1 layer 2 encoder; LAME is layer 3. I've never used tooLAME, though, so perhaps it works about as well. As far as I know, LAME isn't included in Debian for legal reasons. --- To the original poster: Unless you need to make an mp3 for a hardware player or something, you'd be better off using oggenc. I just tried the lame package from marillat; it seems to work fine for me. I fed it the audio from a two-hour movie and about an hour of /dev/urandom. No problem either for a LAME I just built myself using gcc-4.0 Can you provide a sample source audio file (perhaps cut down to a reasonable size using dd)? Also give the exact command you're using to encode. I'll see if I can reproduce your problem on my system. --- On a related note: The lame source can be easily compiled into a debian package. Whenever you see a debian directory in a source tree you can just run: $ dpkg-buildpackage -rfakeroot -uc -b If you know you have the build dependencies met you can run instead: $ fakeroot debian/rules binary (which is a little easier to type) If you decide to build yourself a debian package of LAME be sure to run `make uninstall` in the source tree first. Things can get confusing with a package installed to /usr and the same program installed to /usr/local. -Corey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
On Sat August 20 2005 12:18 am, jurriaan wrote: > I want to encode some .wav files to mp3's. There's no lame in standard > debian amd64, so I downloaded a package from > > deb http://cyberspace.ucla.edu/marillat/ unstable main There are a few packages missing from the amd64 archive because they don't build (yet) or don't behave. Should be available at some point. I never noticed this one was missing because I have been using oggenc for quite a while now and it is working fine on amd64. You could use that unless you need mp3 files. > This seems to hang on some files, gdb shows a backtrace starting with > count_bits(). Then I downloaded the original source (lame-3.96.1) and > compiled that (./configure, make, make install). This even manages to > crash with a segmentation fault on some files. > > What do you people use to create mp3s ? > > Thanks, > Jurriaan > -- > Eat shit -- billions of flies can't be wrong. > Debian (Unstable) GNU/Linux 2.6.13-rc4-mm1 5505 bogomips load 0.17 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mp3 encoding - lame?
hi, there is a package called toolame, it is nearly identical to lame, but it is a different project. in i386 (and maybe in other archs) lame package is available, but not in amd64, i don't know why. but i used toolame with grip(you can use it in command-line), it works fine.you just configure your encoder type like "other", and write encoder executable like "/usr/bin/toolame" in Config/Encode/Encoder path in tabs. jurriaan yazmış: >I want to encode some .wav files to mp3's. There's no lame in standard >debian amd64, so I downloaded a package from > >deb http://cyberspace.ucla.edu/marillat/ unstable main > >This seems to hang on some files, gdb shows a backtrace starting with >count_bits(). Then I downloaded the original source (lame-3.96.1) and >compiled that (./configure, make, make install). This even manages to >crash with a segmentation fault on some files. > >What do you people use to create mp3s ? > >Thanks, >Jurriaan > > -- Azer Demir -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
mp3 encoding - lame?
I want to encode some .wav files to mp3's. There's no lame in standard debian amd64, so I downloaded a package from deb http://cyberspace.ucla.edu/marillat/ unstable main This seems to hang on some files, gdb shows a backtrace starting with count_bits(). Then I downloaded the original source (lame-3.96.1) and compiled that (./configure, make, make install). This even manages to crash with a segmentation fault on some files. What do you people use to create mp3s ? Thanks, Jurriaan -- Eat shit -- billions of flies can't be wrong. Debian (Unstable) GNU/Linux 2.6.13-rc4-mm1 5505 bogomips load 0.17 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
