As I see that ripperX development is not active anymore, I did a fork in Gitlab and implemented some big new features and fixed some more bugs.
If the developers/maintainers have interest on that, feel free to contact me or merge it.
Here it is, for users that have interest to take a look in the Changelog and build it :
RipperX now support multiple encoders configuration and multiple encodings in
the same encoding process:
* Enhanced encoders configuration with new options supporting more than
* one encoder and specific options to each encoder. You don't need to change
* anymore your extra options every time you change your encoder!
* Enhanced the jobs controller to process all enabled encoders in the
* encodings queue.
* ".ripperxrc" file renamed to ".ripperx3rc".
* The config file ".ripperx3rc" was heavyly updated. There're new options
* for each codec and most encoder global options were removed.
* Updated the encoding status dialog and the finished dialog.
Add Opus encoder support (needs opusenc installed).
Add Musepack encoder SV8 (mpcenc) support. Uses the same SV7 (mppenc) plugin.
Add Twolame MP2 encoder support. Added a new plugin, ripperX_plugin-twolame.
Add "Eject disk when finished" configuration option to general tab:
If enabled the disk is ejected when some track ripping is done. It's
not ejected if it's done only existing wav encoding.
Add "split title" configuration option to configuration files tab.
Add "General.LastConfigPage" configuration key to remember the last
accessed configuration page to auto-select it on configuration dialog open.
Add portuguese brazilian translation.
Enhancements
Lots of code converted to C++ (Thanks to Ralf Ulrich @rulrich).
The build has changed to compile without debug symbols by default.
Added the "--enable-debug" argument to "configure".
To enable the debug symbols and the DEBUG define in the code you should run:
make clean && ./configure --enable-debug=yes
From now on, the DEBUG definition will be enable without the need to
add/uncomment the "#define DEBUG" in the code (all defines were removed).
* Some terminologies changes on screen and in source code:
* Change some "Mp3" references to "Encoder":
* Configuration "Mp3" tab title to "Encoder";
* "make mp3 from existing wav" to "encode from existing wav".
* Changelog converted to markdown.
* Translations updates.
* Some code cleanup and refactoring.
Bugfixes
For not installed encoders, activation is disabled in configuration.
Encoding doesn't run for a specific encoder if it's not installed (even
if it's enabled in the config file).
Fix encode priority configuration not set in the config file.
Fix UTF-8/locale encoded titles and files.
Fix unexpect application close if "encode from existing wav" is enabled
and all selected tracks have existing wav files.
Change the default cddb server (freedb) to gnudb.
Fix the debug symbols for GDB debugging.
Fix spanish translation encoding issue.
Lots of small bugfixes.
Last edit: Tiago Barrionuevo 2026-01-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Happy to see someone working on ripperX again. I've got a couple of small patches for the Gitlab 3.0 release:
The changelog states: Change the default cddb server (freedb) to gnudb.
config_rw.c still contains:
// CDDB
insert_pair("CDDBConfig::Server", &config.cddb_config.server,"freedb.freedb.org/~cddb/cddb.cgi");
Also, when ripperX was originally written, encoding was much slower than ripping. Now the opposite is true. The default value for config.mp3_ratio needs to be reduced to account for this. I changed my default Mp3Ratio to 0.0008 in .ripperX3rc and am getting much better elapsed time estimates.
In config_rw.c the default is currently:
insert_pair("General::Mp3Ratio", &config.mp3_ratio, 0.08f);
Something much smaller works better:
insert_pair("General::Mp3Ratio", &config.mp3_ratio, 0.0008f);
0.0008 is an estimate that works for me. There is probably a better default.
Both items are posted in the ripperX Gitlab/issues as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The changes are already in the 3_0_1_release branch in Gitlab.
I have no additional changes to commit right now so I should merge it in master next week.
Last edit: Tiago Barrionuevo 2025-12-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I stated here, we don't have any responses here from the maintainers or someone else.
There're some valuable merge requests that are ignored without any comment.
So I decided to fix some bug I got and finishing implementing a lot of enhancements.
I didn't try yet a contact by email with the guys in the readme so I'll try it soon. I think they have no interest to merge this so I forked it in Gitlab.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Status: open Group: ripperX 2.8.1 Created: Sat Oct 11, 2025 07:07 PM UTC by Tiago Barrionuevo Last Updated: Wed Dec 03, 2025 10:58 PM UTC Owner: nobody
If we enable the "make mp3 from existing wav" and all selected tracks have
existing wav files, ripperx close unexpectedly.
Hi @thothix - Thank you for continuing development of ripperX. I have not had time to participate in active development of this project for quite a while.
Codeberg looks like a good home going forward. Please let me know how I can help with the migration. At a minimum, I would like to update the project description on the landing page to refer to the Codeberg repo as the new home. (You might also consider editing the review you left that refers to the gitlab fork.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry to not be able to talk to you before make the fork.
As ripperX development was inactive and I had made a lot of changes to my own use, I thought it was a good thing to share with other users.
I don't know if I'll get time to be always in active development as well.
You and the former developers feel free to request access to new repo or get the code to update yours for future developments if you want. My intention is to join efforts to keep the project alive and not own it.
I forgot about my review. It's updated now.
Last edit: Tiago Barrionuevo 2026-01-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I see that ripperX development is not active anymore, I did a fork in Gitlab and implemented some big new features and fixed some more bugs.
If the developers/maintainers have interest on that, feel free to contact me or merge it.
Here it is, for users that have interest to take a look in the Changelog and build it :
https://codeberg.org/thothix/ripperx
I'm going to create binary .deb files for Debian and Ubuntu/Mint soon.
Last edit: Tiago Barrionuevo 2026-01-02
Changelog for the 3.0 release:
Features
the same encoding process:
* Enhanced encoders configuration with new options supporting more than
* one encoder and specific options to each encoder. You don't need to change
* anymore your extra options every time you change your encoder!
* Enhanced the jobs controller to process all enabled encoders in the
* encodings queue.
* ".ripperxrc" file renamed to ".ripperx3rc".
* The config file ".ripperx3rc" was heavyly updated. There're new options
* for each codec and most encoder global options were removed.
* Updated the encoding status dialog and the finished dialog.
not ejected if it's done only existing wav encoding.
accessed configuration page to auto-select it on configuration dialog open.
Enhancements
Added the "--enable-debug" argument to "configure".
To enable the debug symbols and the DEBUG define in the code you should run:
make clean && ./configure --enable-debug=yesFrom now on, the DEBUG definition will be enable without the need to
add/uncomment the "#define DEBUG" in the code (all defines were removed).
* Some terminologies changes on screen and in source code:
* Change some "Mp3" references to "Encoder":
* Configuration "Mp3" tab title to "Encoder";
* "make mp3 from existing wav" to "encode from existing wav".
* Changelog converted to markdown.
* Translations updates.
* Some code cleanup and refactoring.
Bugfixes
if it's enabled in the config file).
and all selected tracks have existing wav files.
Last edit: Tiago Barrionuevo 2026-01-07
Happy to see someone working on ripperX again. I've got a couple of small patches for the Gitlab 3.0 release:
The changelog states: Change the default cddb server (freedb) to gnudb.
config_rw.c still contains:
// CDDB
insert_pair("CDDBConfig::Server", &config.cddb_config.server,"freedb.freedb.org/~cddb/cddb.cgi");
Also, when ripperX was originally written, encoding was much slower than ripping. Now the opposite is true. The default value for config.mp3_ratio needs to be reduced to account for this. I changed my default Mp3Ratio to 0.0008 in .ripperX3rc and am getting much better elapsed time estimates.
In config_rw.c the default is currently:
insert_pair("General::Mp3Ratio", &config.mp3_ratio, 0.08f);
Something much smaller works better:
insert_pair("General::Mp3Ratio", &config.mp3_ratio, 0.0008f);
0.0008 is an estimate that works for me. There is probably a better default.
Both items are posted in the ripperX Gitlab/issues as well.
The changes are already in the 3_0_1_release branch in Gitlab.
I have no additional changes to commit right now so I should merge it in master next week.
Last edit: Tiago Barrionuevo 2025-12-03
Hi @circlotron
Thanks for report these issues.
As I stated here, we don't have any responses here from the maintainers or someone else.
There're some valuable merge requests that are ignored without any comment.
So I decided to fix some bug I got and finishing implementing a lot of enhancements.
I didn't try yet a contact by email with the guys in the readme so I'll try it soon. I think they have no interest to merge this so I forked it in Gitlab.
Gitlab repository was archived and migrated to Codeberg at:
https://codeberg.org/thothix/ripperx
Hey Guys,
cool that ripperX project is still continuing :-D.
I've been working off and on on this: https://github.com/joske/ripperx4
In my experience it's much faster to rip than the C/C++ version.
Any thoughts?
Cheers!
jos
On Fri, 2 Jan 2026 at 04:23, Tiago Barrionuevo thothix@users.sourceforge.net wrote:
Related
Bugs: #69
Hi @thothix - Thank you for continuing development of ripperX. I have not had time to participate in active development of this project for quite a while.
Codeberg looks like a good home going forward. Please let me know how I can help with the migration. At a minimum, I would like to update the project description on the landing page to refer to the Codeberg repo as the new home. (You might also consider editing the review you left that refers to the gitlab fork.)
Hi @tmancill! Thanks for your reply.
I'm sorry to not be able to talk to you before make the fork.
As ripperX development was inactive and I had made a lot of changes to my own use, I thought it was a good thing to share with other users.
I don't know if I'll get time to be always in active development as well.
You and the former developers feel free to request access to new repo or get the code to update yours for future developments if you want. My intention is to join efforts to keep the project alive and not own it.
I forgot about my review. It's updated now.
Last edit: Tiago Barrionuevo 2026-01-06