i had installed the rpm version of Blade Enc, which installs the binary named BladeEnc into /usr/local/bin or wherever it should according to the rpm command.
on a hunch, i downloaded the source for Blade Enc, compiled and installed it (standard ./configure && make && make install). this installs a binary named bladeenc into /usr/local/bin or wherever you specify as --prefix to ./configure.
Then, like magic, my mp3s have non-zero size and actually contains music data.
i haven't dabbled in the source for the blade enc plugin, but we should probably tell people in a faq that they should use bladeenc and not BladeEnc as the binary name. (or even better, have the plugin detect which is there, and produce an appropriate error message if necessary.)
dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same problem, however the solution didn't work for me - bladeend are installed and lame, and work OK standalone, but still 0-sized mp3's and no messages what so ever,
-- anyone up for help, please ??
/@arsten
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if you're having this problem with lame, it's probably due to a mis-initialized array in config_window_handler.c
abythell has submitted a patch for this which is in the patch manager
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-10-27
I have the same problem with 128 bit files. They are 0 seconds long. No encoding seems to happen just ripping and then ripperX says it's done.
Q1 What do the plugins do on v2.2 do they encode or do you still need the encoder software
Q2 If you do need encoders installed what do they need to be called and which version can be used
Q3 If you need a bit of help writing this up I can do the donkey work, my html skill ain't brill though!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried with ripperX 2.0 and 2.2 gogo 231f, 236 and 239b and none have worked. I am not sure what the issue is. On another system I have ripperX 2.0 and gogo 231f always work. I have tried gogo at a command prompt and it works. Any ideas would be great.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I tried to set a ID tag of would get a file fo just 128 bytes if I did not I would get a file of no size. I have tried both gogo and lame now. Lame works at a command prompt but not in ripperX.
Josh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not sure if anyone reads this forum any more, but I just wanted to give an update on my install. I have found that all gogo encode compile fine for ne, but when I try and run gogo is core dumps. SO I am now using lame. One thing I have noticed about lame is that only version 3.70 works for my. I am not sure what the deal is, but the betas do not work. As of right now I can encode a cd and it takes about 25 minutes. It takes over a minute to rip each track and around a minute to encode with VBR, high quality, and error correction. If you check my other posts you can see my config which is not slow. I just hope I can get faster perfomance as time goes on.
Josh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using ripperx 2.3 and lame 3.92-1 and i can`t rip from audiocd to mp3files. The files are sized 0 byte. I don`t know how to configure ripperx or lame. thanks thomash19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it seems that i rip a cd fine...but then when they are converted from wav to mp3, the resultant mp3 file has 0 size....
is this a common problem? if so, then shouldn't this be included in a readme or faq or something?
also, what is the solution?
dave
Dave, are you sure that the supported encoders are installed? Check your system to make sure.
I've found the reason...
i had installed the rpm version of Blade Enc, which installs the binary named BladeEnc into /usr/local/bin or wherever it should according to the rpm command.
on a hunch, i downloaded the source for Blade Enc, compiled and installed it (standard ./configure && make && make install). this installs a binary named bladeenc into /usr/local/bin or wherever you specify as --prefix to ./configure.
Then, like magic, my mp3s have non-zero size and actually contains music data.
i haven't dabbled in the source for the blade enc plugin, but we should probably tell people in a faq that they should use bladeenc and not BladeEnc as the binary name. (or even better, have the plugin detect which is there, and produce an appropriate error message if necessary.)
dave
I have the same problem, however the solution didn't work for me - bladeend are installed and lame, and work OK standalone, but still 0-sized mp3's and no messages what so ever,
-- anyone up for help, please ??
/@arsten
if you're having this problem with lame, it's probably due to a mis-initialized array in config_window_handler.c
abythell has submitted a patch for this which is in the patch manager
I have the same problem with 128 bit files. They are 0 seconds long. No encoding seems to happen just ripping and then ripperX says it's done.
Q1 What do the plugins do on v2.2 do they encode or do you still need the encoder software
Q2 If you do need encoders installed what do they need to be called and which version can be used
Q3 If you need a bit of help writing this up I can do the donkey work, my html skill ain't brill though!
I have tried with ripperX 2.0 and 2.2 gogo 231f, 236 and 239b and none have worked. I am not sure what the issue is. On another system I have ripperX 2.0 and gogo 231f always work. I have tried gogo at a command prompt and it works. Any ideas would be great.
When I tried to set a ID tag of would get a file fo just 128 bytes if I did not I would get a file of no size. I have tried both gogo and lame now. Lame works at a command prompt but not in ripperX.
Josh
I am not sure if anyone reads this forum any more, but I just wanted to give an update on my install. I have found that all gogo encode compile fine for ne, but when I try and run gogo is core dumps. SO I am now using lame. One thing I have noticed about lame is that only version 3.70 works for my. I am not sure what the deal is, but the betas do not work. As of right now I can encode a cd and it takes about 25 minutes. It takes over a minute to rip each track and around a minute to encode with VBR, high quality, and error correction. If you check my other posts you can see my config which is not slow. I just hope I can get faster perfomance as time goes on.
Josh
I'm using ripperx 2.3 and lame 3.92-1 and i can`t rip from audiocd to mp3files. The files are sized 0 byte. I don`t know how to configure ripperx or lame. thanks thomash19