Hi, I'm having a really hard time trying to encode ogg files. Whenever I use oggenc the whole machine completely freezes. I have tried oggenc both as a user and root with the same results. If i do something like: oggenc -q 5 track5.wav -o track5.ogg , it starts off fine, but always freezes the machine after a couple of seconds. After rebooting the machine, I have noticed that the track5.ogg output file has never been created. I have tried using the rpms off the CD, the rpms from vorbis.com and the .tar.gz files from vorbis.com, but get the same result all the time. I have also tried using oggenc via other apps, eg: Grip, abcde, ripit etc, but the same thing happens every time. Incedentaly, the other ogg tools seem to work fine, eg ogginfo The really annoying thing is that I had this working fine a couple of weeks ago, but I reinstalled SuSE and now it won't work. I have even tried changing the acpi and apm options in grub, and also using the failsafe option in grub, but no change My system: SuSE 8.1 oggenc 1.0 (CD version) /dev/hda3 9.0G 4.0G 5.1G 45% / /dev/hdb1 38G 4.3G 33G 12% /data Duron 1200, 256 MB I can't find anything on google about complete system freezes from oggenc, so if someone has even the vaguest idea about what could be wrong, I'd be very grateful. Nik
oggenc -q 5 track5.wav -o track5.ogg , it starts Hi, Try not setting the quality and see if it will create the .ogg file. like so "oggenc track5.wav". This will create a ogg file named track5 and at quality of 3. See if this works. Without the quotes that is. Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
This reply is a little belated, and you have not replied to Marshall Heartley's answer.... Have you tried compliing from source? Is that what you mean when you say you tried the "tar.gz" files? I was originally thinking that it was a architecture issue, but you state you have a Duron (i.e., i686) CPU, so it can't be that. Try compiling from source, or trying someone else's RPMs. If that doesn't fix it, post back (I have something in the back of my mind). On Thursday 21 November 2002 07:36, Nik wrote:
Hi,
I'm having a really hard time trying to encode ogg files. Whenever I use oggenc the whole machine completely freezes. I have tried oggenc both as a user and root with the same results. If i do something like: oggenc -q 5 track5.wav -o track5.ogg , it starts off fine, but always freezes the machine after a couple of seconds. After rebooting the machine, I have noticed that the track5.ogg output file has never been created. I have tried using the rpms off the CD, the rpms from vorbis.com and the .tar.gz files from vorbis.com, but get the same result all the time. I have also tried using oggenc via other apps, eg: Grip, abcde, ripit etc, but the same thing happens every time. Incedentaly, the other ogg tools seem to work fine, eg ogginfo The really annoying thing is that I had this working fine a couple of weeks ago, but I reinstalled SuSE and now it won't work. I have even tried changing the acpi and apm options in grub, and also using the failsafe option in grub, but no change My system: SuSE 8.1 oggenc 1.0 (CD version) /dev/hda3 9.0G 4.0G 5.1G 45% / /dev/hdb1 38G 4.3G 33G 12% /data Duron 1200, 256 MB
I can't find anything on google about complete system freezes from oggenc, so if someone has even the vaguest idea about what could be wrong, I'd be very grateful.
Nik
-- Karol Pietrzak <noodlez84@earthlink.net> PGP KeyID: 3A1446A0
In article <200211302148.41752.kap4020@osfmail.rit.edu>, Karol Pietrzak <kap4020@osfmail.isc.rit.edu> wrote:
This reply is a little belated, and you have not replied to Marshall Heartley's answer.... Oops, I missed the reply, sorry Marshall. I've tried oggenc with as many different options I could think of, including none at all. Have you tried compliing from source? Is that what you mean when you say you tried the "tar.gz" files?
Yep, I tried with v1.0, and I also tried with rc2 - this is the version on the SuSE 7.3 cds which I know I had it working with. Still no luck
I was originally thinking that it was a architecture issue, but you state you have a Duron (i.e., i686) CPU, so it can't be that.
I thought that that might be possibility, so I tried building with --BUILD =i386 but still have the same problem. Some times oggenc does produce a partial ogg file before the machine freezes, and this plays ok, if a little short ;-) The freezes always happen, but not at the same place, ie I can do oggenc song.wav and it can get to 20% before the freeze, and then after a reboot the same command on the same file will reach a different %.
Try compiling from source, or trying someone else's RPMs. If that doesn't fix it, post back (I have something in the back of my mind).
I'm posting back - I want to know what is at the back of your mind ;-) Many thanks, Nik
On Sunday 01 December 2002 09:31, Nik wrote:
Yep, I tried with v1.0, and I also tried with rc2 - this is the version on the SuSE 7.3 cds which I know I had it working with. Still no luck
I must say, this problem is very weird.
I thought that that might be possibility, so I tried building with --BUILD =i386 but still have the same problem. Some times oggenc does produce a partial ogg file before the machine freezes, and this plays ok, if a little short ;-)
Interesting...
Try compiling from source, or trying someone else's RPMs. If that doesn't fix it, post back (I have something in the back of my mind).
I'm posting back - I want to know what is at the back of your mind ;-)
Well, Nik, it was in the back of my mind because it's far-fetched. It could be an overheating issue. What temperature is your CPU/case/hard drive? I've had my old PC restart at the most random times because the CPU fan stopped working... If it's all cool and good, trying running something processor intensive for an extended period of time: e.g., SETI@home or Folding@home. Oh, back to oggenc. Trying logging through strace (you might have to install this from the SuSE CDs). Command to run: strace -o oggenc_log.txt oggenc some_file.wav ...if oggenc_log.txt exists after your reboot, post it back. Maybe it has something interesting. Needless to say, your experience is not typical. I have an Athlon XP and have had no problems encoding ~1.4GiB of Ogg Vorbis files over the past ten days. -- Karol Pietrzak <noodlez84@earthlink.net> PGP KeyID: 3A1446A0
In article <200212011013.04210.kap4020@osfmail.rit.edu>, Karol Pietrzak <kap4020@osfmail.isc.rit.edu> wrote:
On Sunday 01 December 2002 09:31, Nik wrote:
Yep, I tried with v1.0, and I also tried with rc2 - this is the version on the SuSE 7.3 cds which I know I had it working with. Still no luck
I must say, this problem is very weird. All my problems are weird, read on...
Well, Nik, it was in the back of my mind because it's far-fetched. It could be an overheating issue. What temperature is your CPU/case/hard drive? I've had my old PC restart at the most random times because the CPU fan stopped working...
It could well be this, although I do have another problem which could indicate (to me) a dodgy motherboard or psu Oh, back to oggenc. Trying logging through strace (you might have to
install this from the SuSE CDs). Command to run:
strace -o oggenc_log.txt oggenc some_file.wav
...if oggenc_log.txt exists after your reboot, post it back. Maybe it has something interesting.
When using oggenc via strace as above, most of the time oggenc seg faults, and only sometimes freezes the whole system. Using plain oggenc causes the system to freeze all the time. I won't post the whole log, just the last bit: gettimeofday({1038821635, 830317}, NULL) = 0 write(2, "\r", 1) = 1 write(2, "\t[ 35.8%] [ 0m26s remaining] \\", 30) = 30 read(3, "o\367@\371\324\370!\373\224\373\216\3746\373\34\373\7\371"..., 4096) = 4096 read(3, "\316\0\253\374\30\0\37\374\315\377\3\374\261\377\326\373"..., 4096) = 4096 read(3, "\215\6y\6\323\10\v\t\341\n\206\n\210\n\32\nC\t\225\ta\10"..., 4096) = 4096 read(3, "!\366\317\367\375\366*\370\4\366\217\367\376\364I\367E"..., 4096) = 4096 read(3, "\341\367\207\365v\367R\365\312\366#\3651\366I\365z\365"..., 4096) = 4096 read(3, "6\25\21\25\30\25T\25\r\23\26\24\37\21\311\23\205\21\231"..., 4096) = 4096 read(3, "3\3647\357\226\3643\357\340\364i\357+\365 \360\364\365"..., 4096) = 4096 --- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++ The problem never occurs at the same point in the encoding - indicates a hardware fault? The other problem which I am having is this: If I either rip from an audio cd or copy data off a cd, my serial ports get slow. eg If I rip the songs off a cd, the pointer has a mind of its own (this is a serial mouse btw), and my internet connection halts, although it remains up - and once the ripping has stopped, the connection picks up again. I access the internet via an external isdn TA, connected to a serial port. AFAIKT, the usb and parallel ports remain ok, its just the serial ports that are affected. So, would I be right in thinking that this indicates a very dodgy mb (elitegroup k7s5a) or a dodgy psu or something else? Many thanks Nik
On Monday 02 December 2002 08:12, Nik wrote:
Well, Nik, it was in the back of my mind because it's far-fetched. It could be an overheating issue. What temperature is your CPU/case/hard drive? I've had my old PC restart at the most random times because the CPU fan stopped working...
It could well be this, although I do have another problem which could indicate (to me) a dodgy motherboard or psu
Oh, back to oggenc. Trying logging through strace (you might have to
install this from the SuSE CDs). Command to run:
strace -o oggenc_log.txt oggenc some_file.wav
...if oggenc_log.txt exists after your reboot, post it back. Maybe it has something interesting.
When using oggenc via strace as above, most of the time oggenc seg faults, and only sometimes freezes the whole system. Using plain oggenc causes the system to freeze all the time. I won't post the whole log, just the last bit:
[snip]
--- SIGSEGV (Segmentation fault) --- +++ killed by SIGSEGV +++
The problem never occurs at the same point in the encoding - indicates a hardware fault?
Right now I'm thinking it's bad RAM. Do you have three sticks of RAM in that machine? If so, try removing one (some motherboards have problems with >2 sticks). Take out another stick as well, just to see. Move the RAM around from slot-to-slot, to see if there's a difference. BTW have you tried running some CPU intensive application over an extended period? http://www.stanford.edu/group/pandegroup/release/FAH3Console-Linux.exe ftp://ftp.cdrom.com/pub/setiathome/setiathome-3.03.i686-pc-linux-gnu-gnulibc2.1.tar
The other problem which I am having is this: If I either rip from an audio cd or copy data off a cd, my serial ports get slow. eg If I rip the songs off a cd, the pointer has a mind of its own (this is a serial mouse btw), and my internet connection halts, although it remains up - and once the ripping has stopped, the connection picks up again. I access the internet via an external isdn TA, connected to a serial port. AFAIKT, the usb and parallel ports remain ok, its just the serial ports that are affected. So, would I be right in thinking that this indicates a very dodgy mb (elitegroup k7s5a) or a dodgy psu or something else?
This I have no idea how to solve. The first thing that comes to mind is some messed-up setting in the BIOS. Sorry couldn't be of more help. -- Karol Pietrzak <noodlez84@earthlink.net> PGP KeyID: 3A1446A0
participants (3)
-
Karol Pietrzak -
Marshall Heartley -
Nik