#52 ripperX crashes after ripping if cd not available at startup

[Anonymous]

put cd in drive. start ripperX. If the CD recognition process is complete before ripperX is started ripperX does not crash after ripping. If the cd recognition process has not finished when ripperX starts up, it crashes after ripping. It appears that ripping works fine.

[mapman88]

I use ubuntu, so I just wait for the cd to be mounted by the system, at which time the cd icon appears on the desktop. Then I open ripperX, and go to work. I like the program, but I have an issue with only the first nine tracks of a cd importing correctly to my music player. All tracks are ripped, those over nine included.

[Trolly]

I'm running Linux Mint and was suffering ripperX crashing and not tagging tracks > 9.
I solved them both by following this advice, 2010-08-28 16:59:35 UTC by lisond,

'When ripping CD's with track >9 ripperX will crash, because: job_control.c line 435 "char s_track_num[2];" has an wrong array size. "sprintf(s_track_num,"%d",(i+1));" needs 3 Bytes for tracks >9 "char s_track_num[3]" works.'

Just made the change in job_control.c
Also I change the program defaults in config_rw.c to my own. Especially the LAME settings. When you choose VBR and set a Rate it uses that as a minimum not a maximum.
Also changed Lame setting in config_window_handler.c from -b to -B & -v to --vbr-new for encoding to MP3.

Re-compiled and voila it hasn't crashed since.
Great tool. Thank to the original authors and lisond for the fix.

[Nobody/Anonymous]

Spoke to soon, still occasionally crashes. Not as much as before.