/[svn]/libgig/trunk/man/korg2gig.1.in
ViewVC logotype

Contents of /libgig/trunk/man/korg2gig.1.in

Parent Directory Parent Directory | Revision Log Revision Log


Revision 2543 - (show annotations) (download)
Sat May 10 02:06:58 2014 UTC (5 years, 2 months ago) by schoenebeck
File size: 3657 byte(s)
* Initial support for sample based instruments in KORG's file format (.KMP
  and .KSF files) -> Korg.h, Korg.cpp.
* Added new command line tool "korgdump" (and a man page for it).
* Added new command line tool "korg2gig" (and a man page for it), for
  converting KORG sounds to Giga format.
* riftree tool: Added more command line options for being able to also dump
  other kind of file formats similar but not equal to the RIFF format.
* gig.h/.cpp: Added new method File::GetGroup(String name) for retrieving
  group by name.
* RIFF.h/.cpp: Added support for loading RIFF-like files with a bit
  different layout than "real" RIFF files (used for KORG format support).
* RIFF.h/.cpp: Added new method Chunk::GetFile().
* RIFF.h/.cpp: Added new method Chunk::GetLayout().
* Bumped version (3.3.0.svn9).

1 .TH "korg2gig" "1" "10 May 2014" "libgig @VERSION@" "libgig tools"
2 .SH NAME
3 korg2gig \- Convert sound files from KORG to GigaStudio format.
4 .SH SYNOPSIS
5 .B korg2gig
6 [-v] [-f] [--interpret-names] FILE1 [ FILE2 ... ] NEWFILE
7 .SH DESCRIPTION
8
9 This tool takes a list of KORG sound files, used with KORG synthesizer keyboards
10 like Trinity, Triton, OASYS, M3 or Kronos, and converts them to a
11 Gigasampler/GigaStudio (.gig) file. All input KORG files are merged to a single
12 (.gig) output file.
13
14 For each KORG "multi-sample" (.KMP) file a separate GigaStudio instrument will
15 be created in the output (.gig) file. KORG Sample (.KSF) files referenced by
16 such multi-sample (.KMP) files are automatically detected, loaded and written to
17 the output (.gig) file as well. Assignemnts of samples to keyboard regions,
18 sample loops and other minor articulation informations are converted as well.
19 But note, the multi-sample (.KMP) form is very primitive. It does NOT save the
20 detailled articulation informations of your KORG keyboard like envelopes, LFO
21 and filter settings. Those informations are stored in a separate program (.PCG)
22 file.
23
24 Unfortunately there is no support for KORG's program/combinations/bank (.PCG)
25 files yet. Have a look at option
26 .B --interpret-names
27 for a workaround.
28 Because of this lack of support for .PCG files, you still have to adjust the
29 articulation settings in the output (.gig) file afterwards with an instrument
30 editor application like
31 .BR gigedit (1).
32
33 If you are explicitly passing KORG sample (.KSF) files as well, and they are not
34 referenced by any "multi-sample" (.KMP) file you might have passed, then those
35 orphaned samples are added to the output (.gig) file in a separate sample group
36 called "Not referenced". That way you can easily distinguish samples in the
37 output (.gig) file which are actually used by one of the instruments, and the
38 samples that are not used yet.
39
40 .B NOTE:
41 This tool might need quite a lot RAM at the moment. Approximately it will
42 allocate as much RAM as the expected output .gig file will be in size. So make
43 sure you have enough free RAM and/or swap space, otherwise this tool might
44 crash if it cannot allocate the required RAM space.
45
46 .SH OPTIONS
47
48 .TP
49 .B \ FILE1 [ FILE2 ... ]
50 A list of input KORG sound (.KMP or .KSF) files. You must supply at least one
51 KORG file. KORG sample (.KSF) files referenced in the so called "multi-sample"
52 (.KMP) file(s) are automatically detected and loaded. So in most cases you
53 would just pass .KMP file(s) as input file argument(s).
54
55 .TP
56 .B \ NEWFILE
57 Output file in Gigasampler/GigaStudio (.gig) format. If this output file
58 already exists,
59 .B korg2gig
60 will abort with an error message unless you specify
61 .B -f
62 as argument as well.
63
64 .TP
65 .B \ -v
66 print version and exit
67
68 .TP
69 .B \ -f
70 Overwrite output file if it already exists.
71
72 .TP
73 .B \ --interpret-names
74 Try to guess left/right sample pairs and velocity splits. This is a nasty
75 workaround for the fact that there is no support for reading KORG .PCG files
76 yet. If you manually named the multi-samples (.KMP files) on your keyboard in a
77 scheme like "PIANO 003-120 -R" it will interpret the two hints as a) velocity
78 split range (in this example from velocity 3 to 120) and b) stereo sample pairs
79 (in this case the multi-sample contains the right channel). Of course you can
80 also omit one or both hints if you don't want to have a velocity split or stereo
81 sample pair for certain instruments or regions.
82
83 .SH "SEE ALSO"
84 .BR korgdump(1),
85 .BR gigedit(1),
86 .BR rifftree(1),
87 .BR gigdump(1),
88 .BR dlsdump(1)
89
90 .SH "BUGS"
91 None. Report bugs to http://bugs.linuxsampler.org
92 .SH "Author"
93 Written by Christian Schoenebeck <cuse@users.sf.net>

  ViewVC Help
Powered by ViewVC