| 1 |
.TH "wav2gig" "1" "02 Sep 2021" "libgig @VERSION@" "libgig tools" |
.TH "wav2gig" "1" "03 Sep 2021" "libgig @VERSION@" "libgig tools" |
| 2 |
.SH NAME |
.SH NAME |
| 3 |
wav2gig \- Create GigaStudio (.gig) file from a set of WAV files. |
wav2gig \- Create GigaStudio (.gig) file from a set of WAV files. |
| 4 |
.SH SYNOPSIS |
.SH SYNOPSIS |
| 19 |
GigaStudio (.gig) file and tries to automatically map the samples in a |
GigaStudio (.gig) file and tries to automatically map the samples in a |
| 20 |
meaningful way to that instrument. As the wave (.wav) format currently does not |
meaningful way to that instrument. As the wave (.wav) format currently does not |
| 21 |
support many of the meta information required for this particular task, this |
support many of the meta information required for this particular task, this |
| 22 |
tool tries to guess the required information from the individual sample's name |
tool tries to extract the required (missing) information from the individual |
| 23 |
for mapping the samples accordingly. See |
sample's file name for being able to map the samples accordingly. See |
| 24 |
.BR SAMPLE |
.BR SAMPLE |
| 25 |
.BR NAMES |
.BR NAMES |
| 26 |
below for details on the assumed naming scheme for input sample files and how |
below for details on the assumed naming scheme for input sample files and how |
| 158 |
.BR --regex-note-name |
.BR --regex-note-name |
| 159 |
to override this part of the naming scheme. |
to override this part of the naming scheme. |
| 160 |
|
|
| 161 |
|
.PP |
| 162 |
|
This tool utilizes the |
| 163 |
|
.I regular expressions |
| 164 |
|
library provided by C++ (introduced with the C++11 standard revision). |
| 165 |
|
Each custom regular expression (abbreviated as 'RegEx' from now on below) |
| 166 |
|
passed to one of the |
| 167 |
|
.BR --regex-* |
| 168 |
|
options must contain |
| 169 |
|
.B |
| 170 |
|
exactly one |
| 171 |
|
active RegEx 'capture group' which is denoted in regular expressions by a pair |
| 172 |
|
of round brackets like: |
| 173 |
|
|
| 174 |
|
.B (PATTERN) |
| 175 |
|
|
| 176 |
|
So the 'capture group' marks the portion in the overall filename string that is |
| 177 |
|
going to be exctracted for the respective component of the filename schema. |
| 178 |
|
If additional RegEx group(s) are needed to build the overall RegEx pattern, then |
| 179 |
|
those other group(s) must be defined as 'passive groups' denoted in RegEx |
| 180 |
|
patterns by an additional question mark and colon like this: |
| 181 |
|
|
| 182 |
|
.B (?:PATTERN) |
| 183 |
|
|
| 184 |
|
Keep in mind that RegEx scanners behave 'greedy' by default, which means by |
| 185 |
|
default they try to match the longest string possible according to your defined |
| 186 |
|
RegEx pattern. If that's not desired then you may either override the required |
| 187 |
|
parts of your RegEx pattern to behave 'non-greedy' such that those parts would |
| 188 |
|
match for the shortest string possible instead, or alternatively consider using |
| 189 |
|
the RegEx 'alternation' |
| 190 |
|
operator, which is denoted in regular expressions by a vertical bar character |
| 191 |
|
like: |
| 192 |
|
|
| 193 |
|
.B PATTERN1|PATTERN2|PATTERN3 |
| 194 |
|
|
| 195 |
|
The RegEx 'alternation' operator is sometimes more intuitive, because it tries |
| 196 |
|
to match the provided patterns strictly in order from left to right. So it |
| 197 |
|
would first try to match the first pattern, and only if no match with the first |
| 198 |
|
pattern was possible (independent of string length) it would then try to match |
| 199 |
|
the second pattern, and so on. |
| 200 |
|
|
| 201 |
.SH "SEE ALSO" |
.SH "SEE ALSO" |
| 202 |
.BR gig2mono(1), |
.BR gig2mono(1), |
| 203 |
.BR gigextract(1), |
.BR gigextract(1), |
Parent Directory
| 
Revision Log
| 
Patch