1 |
.TH "wav2gig" "1" "03 Aug 2021" "libgig @VERSION@" "libgig tools" |
2 |
.SH NAME |
3 |
wav2gig \- Create GigaStudio (.gig) file from a set of WAV files. |
4 |
.SH SYNOPSIS |
5 |
.B wav2gig |
6 |
[ OPTIONS ] GIG_FILE WAV_FILE_OR_DIR_1 [ WAV_FILE_OR_DIR_2 ... ] |
7 |
.SH DESCRIPTION |
8 |
Takes a list of wave (.wav) files and / or directories containing wave files as |
9 |
argument(s) and creates one new GigaStudio / GigaSampler (.gig) file for those |
10 |
samples. |
11 |
|
12 |
The created GigaStudio (.gig) file will contain the given input samples. The |
13 |
samples' meta information like loop points are automatically extracted from the |
14 |
input wave files and applied accordingly. |
15 |
|
16 |
Additionally this tool creates exactly one instrument inside the newly created |
17 |
GigaStudio (.gig) file and tries to automatically map the samples in a |
18 |
meaningful way to that instrument. As the wave (.wav) format currently does not |
19 |
support many of the meta information required for this particular task, this |
20 |
tool tries to guess the required information from the individual sample's name |
21 |
for mapping the samples accordingly. See |
22 |
.BR SAMPLE |
23 |
.BR NAMES |
24 |
below for details on the currently supported and assumed naming scheme for the |
25 |
input sample files. |
26 |
|
27 |
.SH OPTIONS |
28 |
.TP |
29 |
.B \ GIG_FILE |
30 |
GigaStudio / GigaSampler (.gig) filename to be created |
31 |
.TP |
32 |
.B \ WAV_FILE_OR_DIR_1 |
33 |
Filename or directory containing wave (.wav) file(s) |
34 |
.TP |
35 |
.B \ WAV_FILE_OR_DIR_2 |
36 |
Filename or directory containing wave (.wav) file(s) |
37 |
.TP |
38 |
.B \ -r |
39 |
Recurse through all subdirectories of provided input WAV directories. |
40 |
.TP |
41 |
.B \ -f |
42 |
Overwrite output GigaStudio (.gig) file in case it already exists. |
43 |
.TP |
44 |
.B \ -v |
45 |
Print version and exit. |
46 |
|
47 |
.SH SAMPLE NAMES |
48 |
Right now this tool assumes the following sample naming scheme for being able to |
49 |
automatically map samples to regions on the keyboard, as well as mapping them to |
50 |
velocity splits adequately: |
51 |
|
52 |
.B NAME1 - NAME2 - VELOCITY_NR - NOTE_NR - NOTE_NAME |
53 |
|
54 |
Which are interpreted in the following way: |
55 |
|
56 |
.TP |
57 |
.B \ NAME1 |
58 |
Primary name of the sample (e.g. "Violin"). |
59 |
|
60 |
This is not interpreted for sample mapping, but it will be used to assemble the |
61 |
final sample name inside the GigaStudio (.gig) file. |
62 |
|
63 |
.TP |
64 |
.B \ NAME2 |
65 |
Secondary name of the sample (e.g. "Cresc"). |
66 |
|
67 |
This is currently ignored, but might be used in future. |
68 |
|
69 |
.TP |
70 |
.B \ VELOCITY_NR |
71 |
MIDI Velocity number of the sample (e.g. "18"). |
72 |
|
73 |
This informtion will be used to automatically create velocity splits. |
74 |
|
75 |
.TP |
76 |
.B \ NOTE_NR |
77 |
MIDI Note number of the sample (e.g. "021" for note a-1). |
78 |
|
79 |
This informtion will be used to automatically map the sample to a region on the |
80 |
keyboard. |
81 |
|
82 |
.TP |
83 |
.B \ NOTE_NAME |
84 |
Note name of the sample (e.g. "a-1"). |
85 |
|
86 |
This is not interpreted for sample mapping, but it will be used to assemble the |
87 |
final sample name inside the GigaStudio (.gig) file. |
88 |
|
89 |
.SH "SEE ALSO" |
90 |
.BR gig2mono(1), |
91 |
.BR gigextract(1), |
92 |
.BR gigdump(1), |
93 |
.BR gigmerge(1) |
94 |
.BR korg2gig(1) |
95 |
|
96 |
.SH "BUGS" |
97 |
Check and report bugs at http://bugs.linuxsampler.org |
98 |
.SH "Author" |
99 |
Application and manual page written by Christian Schoenebeck <cuse@users.sf.net> |