bin_to_cso_mp3 readme.txt updated
[picodrive.git] / tools / bin_to_cso_mp3 / readme.txt
CommitLineData
02126f5e 1\r
2bin_to_cso_mp3\r
3Originally written by Exophase as "bin_to_iso_ogg"\r
4updated for cso/mp3 by notaz\r
5\r
6\r
7About\r
8-----\r
9\r
10This is a tool to convert cue/bin CD image to cue/cso/mp3 form, useful to use\r
11with emulators. It can also create ISO instead of CSO and WAV instead of MP3.\r
12Note that input must be .cue file, along with single .bin file.\r
13\r
14\r
15Easy/Windows usage\r
16------------------\r
17\r
181. Download LAME from http://lame.sourceforge.net/links.php#Binaries\r
19 You need an archive or "LAME Bundle" with lame.exe inside. Extract lame.exe\r
20 to the same directory as bin_to_cso_mp3.exe\r
212. Find ciso.exe . It usually comes with ISO->CSO converters, for example yacc\r
22 (http://yacc.pspgen.com/). Extract ciso.exe to the directory from previous\r
23 step.\r
243. Drag the .cue file you want to convert onto bin_to_cso_mp3.exe . It should\r
25 pop up console window with some scrolling text, which should close by itself\r
26 when done. After that you should see new directory with converted files.\r
27\r
28In case it complains about missing lame.exe even after you copied it, try\r
29copying lame.exe and ciso.exe somewhere in your PATH, i.e. Windows directory.\r
30\r
31If it crashes ("this program needs to close blabla"), you probably have bad\r
32.cue or missing .bin file.\r
33\r
34\r
35Advanced usage\r
36--------------\r
37\r
38Just run bin_to_cso_mp3.exe from console terminal (or "command prompt") without\r
39any parameters to see usage.\r
40\r
41\r
42Linux\r
43-----\r
44\r
45You will need to compile bin_to_cso_mp3.c yourself using gcc:\r
46$ gcc bin_to_cso_mp3.c -o bin_to_cso_mp3\r
47\r
48You will also need to have lame and ciso binaries in PATH. Those can sometimes\r
49be installed using packet manager from the distribution, or you can compile\r
50them from sources:\r
51lame: http://lame.sourceforge.net/\r
52ciso: http://ciso.tenshu.fr/\r
53\r