1 |
.TH "gig2stereo" "1" "06 Jan 2015" "libgig @VERSION@" "libgig tools" |
2 |
.SH NAME |
3 |
gig2stereo \- Converts Gigasampler (.gig) files from mono pairs to true stereo. |
4 |
.SH SYNOPSIS |
5 |
.B gig2stereo |
6 |
[ OPTIONS ] FILE_OR_DIR1 [ FILE_OR_DIR2 ... ] |
7 |
.SH DESCRIPTION |
8 |
Takes a list of Gigasampler (.gig) files and / or directories as argument(s) and |
9 |
converts the individual Gigasampler files from two separate mono sample pairs to |
10 |
true stereo interleaved format. Given directories are scanned for .gig files. |
11 |
The Gigasampler files are directly modified, not copied. Since at this point the |
12 |
Gigasampler format only defines mono and stereo samples, this program currently |
13 |
also assumes all samples in the .gig files provided to be either mono or stereo. |
14 |
|
15 |
Background: The Gigasampler/GigaStudio format allows one to create stereo |
16 |
instruments in two ways: either by referencing true stereo (interleaved) samples |
17 |
in the instruments, or by referencing a pair of (two) mono samples. Unfortunately |
18 |
LinuxSampler does not support the latter at the moment, thus if a gig instrument |
19 |
uses mono sample pairs, you will still hear it in mono. This tool was created to |
20 |
circumvent this issue by allowing to convert gig files to using real stereo |
21 |
(interlaved) samples instead. And even if LinuxSampler would add support for |
22 |
mono sample pairs, it would be less efficient than using real stereo samples, |
23 |
both concerning disk streaming as well as DSP processing after streaming input. |
24 |
|
25 |
After conversion, you will find all newly created true stereo samples in |
26 |
separate new sample group(s), which will be postfixed with " STEREO" in their |
27 |
group names. So you should easily be able to distinguish the newly created true |
28 |
stereo samples (i.e. when editing the .gig file with |
29 |
.BR gigedit (1) |
30 |
) from old samples. Also, if the original (now replaced) mono samples were |
31 |
postfixed with a channel indicator in their sample names |
32 |
(i.e. "Spiccato D3 -L"), the new stereo samples will have a similar sample name, |
33 |
but without such an audio channel indicator at the end of their names. Thus in |
34 |
the mentioned example, the newly created stereo sample would be named |
35 |
"Spiccato D3" instead. |
36 |
.SH OPTIONS |
37 |
.TP |
38 |
.B \ FILE_OR_DIR1 |
39 |
Gigasampler (.gig) filename or directory |
40 |
.TP |
41 |
.B \ FILE_OR_DIR2 |
42 |
Gigasampler (.gig) filename or directory |
43 |
.TP |
44 |
.B \ --force-replace |
45 |
Force replacing any found old mono sample reference by the new true stereo |
46 |
samples. By default certain references of the old mono samples are not replaced |
47 |
by new true stereo samples, usually because the respective old mono reference is |
48 |
been used in an instrument context that seems to be entirely a mono use case, |
49 |
not stereo, and thus replacing the mono sample reference by stereo ones might |
50 |
not be intended for the respective instrument. Because there might indeed be |
51 |
instruments in the same .gig file which are designed as explicit mono variant |
52 |
(i.e. to allow the musician to save resources while playing, or for live |
53 |
mix-down reasons, which are usually mono on live venues). By using |
54 |
--force-replace all those old mono sample references in question will also be |
55 |
replaced by the new stereo sample references. |
56 |
.TP |
57 |
.B \ --incompatible |
58 |
Also match incompatible mono samples as pairs. By default, when searching for |
59 |
potential mono samples that could be combined to true stereo samples, some |
60 |
sanity checks are performed. Thus if two mono samples have completely different |
61 |
characterstics (i.e. different fine tune setting, different loop types) then |
62 |
they are by default considered to be incompatible and will not be merged to a |
63 |
true stereo sample to avoid undesired audible errors in the modified file. Under |
64 |
certain circumstances you might want to circumvent this sanity check, for |
65 |
instance when you think that few cents fine tuning difference in the mono |
66 |
samples are no reason for you to not merge them into a stereo sample. In this |
67 |
case you can use this option to force the conversion. However certain |
68 |
fundamental incompatibilities are still not ignored, even if you use |
69 |
--incompatible, for example if the two mono samples have different bit depth, |
70 |
sample rate or loop start and loop end points, in such cases those mono samples |
71 |
will still not be merged to stereo samples, because the actual result of the |
72 |
merge under that condition will certainly not be desired. |
73 |
.TP |
74 |
.B \ --keep |
75 |
Keep old mono samples. By default old converted mono samples, if they are not |
76 |
referenced by any instrument anymore, will automatically be deleted after |
77 |
conversion. By using this argument it will preserve all of the old mono samples. |
78 |
.TP |
79 |
.B \ -r |
80 |
Recurse through subdirectories. |
81 |
.TP |
82 |
.B \ -v |
83 |
Print version and exit. |
84 |
.TP |
85 |
.B \ --verbose [LEVEL] |
86 |
Be verbose and print additional information while converting. The additional |
87 |
numeric argument is optional, it allows one to define the verbosity level |
88 |
(1 .. 2, default: 1). |
89 |
|
90 |
.SH "SEE ALSO" |
91 |
.BR gig2mono(1), |
92 |
.BR gigextract(1), |
93 |
.BR gigdump(1), |
94 |
.BR gigmerge(1), |
95 |
.BR wav2gig(1) |
96 |
|
97 |
.SH "BUGS" |
98 |
Check and report bugs at http://bugs.linuxsampler.org |
99 |
.SH "Author" |
100 |
Application and manual page written by Christian Schoenebeck <cuse@users.sf.net> |