aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--miragextract.rst20
1 files changed, 16 insertions, 4 deletions
diff --git a/miragextract.rst b/miragextract.rst
index 37b54b6..c38bd20 100644
--- a/miragextract.rst
+++ b/miragextract.rst
@@ -52,7 +52,12 @@ OPTIONS
Choices are **wav**, **ogg**, **flac**, **cdda** (raw CD audio).
Default is **wav**.
--l Lists the tracks in the image without extracting them.
+-l Lists all tracks in the image without extracting them. Currently
+ does not combine with -t, -a, -d as expected (you can't list only
+ audio tracks with "-l -a" for instance).
+
+-L Lists all tracks in the image without extracting them, with
+ extra detail (sector sizes, counts, and exact byte sizes).
-n Set the base filename to the input filename, minus its extension.
E.g. for foo.cue, this is the same as saying "-b foo". Beware of
@@ -75,6 +80,8 @@ OPTIONS
-t <track> Takes a track number (1-99), and extracts only that one track.
Default behaviour is to extract all tracks.
+Option bundling is not supported (e.g. **-d** **-s** is OK, **-ds** is wrong).
+
Always include a space between an option and its argument (e.g. **-b foo**, not **-bfoo**).
NOTES
@@ -94,7 +101,7 @@ to convert to mp3.
Output data tracks will be named to end in '.iso' by default, or '.hfs'
if they look like Apple disk images (HFS or HFS+), or '.hfs.iso' for
"hybrid" images that can be mounted as either ISO9660 or HFS/HFS+
-(such as Blizzard's Mac/PC releases).
+(such as Blizzard's combined Mac/PC releases).
Images with multiple sessions should be supported, but have not been
tested. Track numbering just continues, so a disc with 2 sessions of
@@ -130,8 +137,13 @@ Not exactly a bug, per se, but miragextract can't deal with multi-file
images where one of the files is missing or truncated. This is because
libmirage validates the image when it's loaded, and is unlikely to change.
-Related to the above, there's no attempt to recover from
-errors. miragextract exits as soon as it encounters an error of any kind.
+Related to the above, there's no attempt to recover from errors.
+miragextract exits as soon as it encounters an error of any kind.
+
+libmirage (as of version 3.2.4) also doesn't really support "wav/cue"
+images (or ogg/cue, mp3/cue, etc). If you try to use miragextract on one,
+you'll get advised to try audiocue2bincue(1). When (if) libmirage gains
+support for these, miragextract should handle them just fine.
.. EXAMPLES
.. ========