1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Chapter 2. Using Gimp</title>
<link rel="stylesheet" href="gimp-help-plain.css" type="text/css" />
<link rel="stylesheet" href="gimp-help-screen.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.66.1" />
<link rel="start" href="index.html" title=" " />
<link rel="up" href="index.html" title=" " />
<link rel="prev" href="ch01s04s03.html" title="4.3. What Happens to a Bug Report after you Submit it" />
<link rel="next" href="ch02s02.html" title="2. Running Gimp" />
</head>
<body>
<div xmlns="" class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center" id="chaptername">Chapter 2. Using <span xmlns="http://www.w3.org/1999/xhtml" class="acronym">Gimp</span></th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="ch01s04s03.html">Prev</a> </td>
<th width="60%" align="center" id="sectionname"> </th>
<td width="20%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title"><a id="using"></a>Chapter 2. Using <span class="acronym">Gimp</span></h2>
</div>
</div>
</div>
<div class="toc">
<p>
<b>Table of Contents</b>
</p>
<dl>
<dt>
<span class="sect1">
<a href="ch02.html#gimp-using-setup">1. Starting Gimp the first time</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="ch02s02.html">2. Running Gimp</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="ch02s03.html">3. Basic Gimp Usage</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s03.html#id3305623">3.1. Introduction</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s03s02.html">3.2. The Main Toolbox</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s03s03.html">3.3. Image Window</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s03s04.html">3.4. Dialogs and Docking</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s03s05.html">3.5. Basic Gimp Concepts</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s04.html">4. Working with Images</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s04.html#id3307365">4.1. Image types</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s02.html">4.2. QuickMask</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s03.html">4.3. Layers</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s04.html">4.4. The Selection</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s05.html">4.5. Undoing</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s06.html">4.6. Grids and Guides</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s07.html">4.7. Paths</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s08.html">4.8. Brushes</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s09.html">4.9. Gradients</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s10.html">4.10. Patterns</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s11.html">4.11. Palettes</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s12.html">4.12. Text and Fonts</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s04s13.html">4.13. Stroking a Selection or Path</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s05.html">5. Files</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="ch02s06.html">6. Working with Digital Camera Photos</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s06.html#id3314219">6.1. Introduction</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s06s02.html">6.2. Improving Composition</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s06s03.html">6.3. Improving Colors</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s06s04.html">6.4. Adjusting Sharpness</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s06s05.html">6.5. Removing Unwanted Objects from an Image</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s06s06.html">6.6. Saving Your Results</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s07.html">7. Preparing your Images for the web</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s07.html#id3315595">7.1. Squeezing Filesize a bit more</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s08.html">8. Plugins</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s08.html#id3315567">8.1. Introduction</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s08s02.html">8.2. Using Plugins</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s08s03.html">8.3. Installing New Plugins</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s08s04.html">8.4. Writing Plugins</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s09.html">9. Using Script-Fu Scripts</a>
</span>
</dt>
<dt>
<span class="sect1">
<a href="ch02s10.html">10. A Script-Fu Tutorial</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="sect2">
<a href="ch02s10.html#id3316524">10.1. Getting Acquainted With Scheme</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s10s02.html">10.2. Variables And Functions</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s10s03.html">10.3. Lists, Lists And More Lists</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s10s04.html">10.4. Your First Script-Fu Script</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s10s05.html">10.5. Giving Our Script Some Guts</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="ch02s10s06.html">10.6. Extending The Text Box Script</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="sect1">
<a href="ch02s11.html">11. Getting Unstuck</a>
</span>
</dt>
</dl>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="gimp-using-setup"></a>1. Starting Gimp the first time</h2>
</div>
</div>
</div>
<a id="id3304559" class="indexterm"></a>
<p>
The first time you run Gimp, it goes through a series of steps to
set up options and directories. This process creates a subdirectory
of your home directory called <tt class="filename">.gimp-2.0</tt>. All of the information
about the choices you make here goes into that directory. If you
later remove that directory, or rename it as something like
<tt class="filename">.gimp-2.0.bak</tt>, then the next
time you start Gimp, it will go through the whole setup sequence
again, creating a new <tt class="filename">.gimp-2.0</tt> directory. You can exploit
this if you want to explore the effect of different choices without
destroying your existing installation, or if you have screwed things
up so badly that your existing installation needs to be nuked.
</p>
<p>
For the most part, setting up Gimp is very easy, and you can just
accept the defaults at each step, and possibly adjust things later
using the <a href="ch04s18.html" title="18. Preferences">Preferences</a> dialog. The
main thing you might want to give a little thought to at the start
is the amount of memory to allocate for Gimp's tile cache.
</p>
<p>
Here is a walk-through of the setup process:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term">Welcome</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-welcome.png" />
<div class="caption">
<p>
The Welcome screen.
</p>
</div>
</div>
</div>
<p>
Since this window mentions the GNU General Public License you
know it is truly a Welcome dialog you are entering into. Also,
note the "Continue" button. The Gimp does not even ask that you
agree to it, merely whether you want to continue. Feel free to
press the continue button.
</p>
</dd>
<dt>
<span class="term">Personal Gimp Directory</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-personal.png" />
<div class="caption">
<p>
The Personal Directory screen.
</p>
</div>
</div>
</div>
</dd>
<dt>
<span class="term">User Installation Log</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-log.png" />
<div class="caption">
<p>
The User Installation Log screen.
</p>
</div>
</div>
</div>
<p>
This window shows you the files that Gimp will make. It will
have some complaints if you told it to install some place that
it didn't have permission to be. There is a scroll bar to see
all the things Gimp has created for you.
</p>
</dd>
<dt>
<span class="term">Gimp Performance Tuning</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-performance.png" />
<div class="caption">
<p>
The User Performance Tuning screen.
</p>
</div>
</div>
</div>
<p>
Setting your memory usage is not an easy thing. So much depends
on what your needs are for the gimp and what hardware you have
to work with. You have two options at this point. Go with the
default value the developers have set here, or determine the
best value. A brief <a href="ch02.html#gimp-using-setup-tile-cache" title="How to Set Your Tile Cache">tile-cache</a>
explanation. might help you
determine this value. The tile-cache information might also be
helpful to you if you are encountering memory problems when
using the gimp.
</p>
<p>
On a Unix system, <tt class="filename">/tmp</tt>
might be a good place for the swap.
</p>
</dd>
<dt>
<a id="gimp-setup-monitor-resolution"></a>
<span class="term">Monitor Resolution</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-monitor.png" />
<div class="caption">
<p>
The Monitor Resolution screen
</p>
</div>
</div>
</div>
<p>
Monitor Resolution is the ratio of pixels, horizontally and
vertically, to inches. You have three ways to proceed here:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
Get Resolution from windowing system. (easiest, probably
inaccurate).
</p>
</li>
<li>
<p>
Set Manually
</p>
</li>
<li>
<p>
Push the Calibrate Button.
</p>
</li>
</ul>
</div>
<p>
</p>
</dd>
<dt>
<span class="term">The Calibrate Dialog</span>
</dt>
<dd>
<div class="informalfigure">
<div class="mediaobject">
<img src="../images/using/ui-calibrate.png" />
<div class="caption">
<p>
The Calibration dialog
</p>
</div>
</div>
</div>
<p>
My monitor was impressively off when I tried the Calibrate
Dialog. The "Calibrate Game" is fun to play. You will need a
soft ruler.
</p>
</dd>
<dt>
<span class="term">Finally . . .</span>
</dt>
<dd>
<p>
So now you have Gimp installed and configured, and are ready to
go. Just a couple of suggestions before you start, though:
First, when you run Gimp, by default it shows a "tip" each time it
starts up. These tips tell you things that are very useful but
not easy to learn by experimenting, so they are worth paying
attention to. If you find it too distracting to look at them
each time you start, you can disable
them; but please go through them when you have the chance: for
your convenience, you can read them at any time using the menu
command
<span class="guimenu">Help</span>-><span class="guimenuitem">Tips</span>. Second,
if at some point you are trying to do something, and Gimp seems to
have suddenly stopped functioning, the section <a href="ch02s11.html" title="11. Getting Unstuck">Getting Unstuck</a> may
help you out. Happy Gimping!
</p>
</dd>
</dl>
</div>
<div class="simplesect" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="gimp-using-setup-tile-cache"></a>How to Set Your Tile Cache</h3>
</div>
</div>
</div>
<p>
Image processing can require a lot of memory. Gimp uses the
operating system services to handle memory, up to a given point,
past which it uses its own system so that it does not eat all system
memory resources. This system consists in sending old data to files
in the disk. The decision point is what the Tile Cache size
determines–the maximum amount of operating system resources to
use–and is measured in Bytes (or multiples, like MegaBytes). It does
not include Gimp's own memory, just the space required for the image
data.
</p>
<p>
A low value means that Gimp sends data vey quickly to disk, not
making real use of the available RAM, and making the disks work
without any real reason. Too high a value, and other applications
start to have less system resources, forcing them to use swap space,
which also makes the disks work; or maybe some will even get
killed or start to malfunction due lack of RAM.
</p>
<p>
How to choose a number for the Tile Cache size? Here are some
ways you could decide what value to use, as well as a few tricks:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
The easiest method is to just forget about this and hope the
default works. This was a usable method when
computers had little RAM, and most people just tried to make small
images with Gimp while running one or two other applications at
the same time. If you
want something easy and only use Gimp to make screenshots and
logos, this is probably the best solution.
</p>
</li>
<li>
<p>
If you have a modern computer with plenty of memory–say, 512 MB
or more–setting the Tile Cache to half of your RAM will probably
give good performance for Gimp in most situations without
depriving other applications. Probably even 3/4 of your RAM would
be fine.
</p>
</li>
<li>
<p>
Ask someone to do it for you, which in the case of a computer
serving multiple users at the same time can be a good idea: that
way the administrator and other users do not get mad at you for
abusing the machine, nor do you get a badly underperfoming Gimp. If
it is your machine and only serves a single user at a given time,
this could mean money, or drinks, as price for the service.
</p>
</li>
<li>
<p>
Start changing the value a bit each time and check that it goes
faster and faster with each increase, but the system does not
complain about lack of memory. Be forewarned that sometimes lack
of memory shows up suddenly with some applications being killed to
make space for the others.
</p>
</li>
<li>
<p>
Do some simple math and calculate a viable value. Maybe you will
have to tune it later, but maybe you have to tune it anyway with
the other previous methods. At least you know what is happening
and can get the best from your computer.
</p>
</li>
</ul>
</div>
<p>
Let's suppose you prefer the last option, and want to get a good value to
start with. First, you need to get some data about your
computer. This data is the amount of RAM installed in your system,
the operating system's
swap space available, and a general idea about the speed of the
disks that store the operating system's swap and the directory
used for Gimp's swap. You do not need to do disk tests, nor check
the RPM of the disks, the thing is to see which one seems clearly
faster or slower, or whether all are similar. You can
change Gimp's swap directory in the Folders page of the
Preferences dialog.
</p>
<p>
The next thing to do is to see how much resources you require for
other apps you want to run at the same time than Gimp. So start
all your tools and do some work with them, except Gimp of course,
and check the usage. You can use applications like free or top,
depending in what OS and what environment you use. The numbers you
want is the memory left, including file cache. Modern Unix keeps a
very small area free, in order to be able to keep large file and buffer
caches. Linux's <span class="emphasis"><em>free</em></span> command does the maths
for you: check the column that
says "free", and the line "-/+ buffers/cache". Note down also the
free swap
</p>
<p>
Now time for decisions and a bit of simple math. Basically the
concept is to decide if you want to base all Tile Cache in RAM, or
RAM plus operating system swap:
</p>
<div class="procedure">
<ol type="1">
<li>
<p>
Do you change applications a lot? Or keep working in Gimp for a
long time? If you spend a lot of time in Gimp, you can consider free
RAM plus free swap as available; if not, you need to go to the
following steps. (If you're feeling unsure about it,
check the following steps.) If you are sure you switch apps
every few minutes, only count the free RAM and just go to the
final decision; no more things to check.
</p>
</li>
<li>
<p>
Does the operating system swap live in the same physical disk as
Gimp swap? If so, add RAM and swap. Otherwise go to the next
step.
</p>
</li>
<li>
<p>
Is the disk that holds the OS swap faster or the same speed as the
disk that holds the Gimp swap? If slower, take only the free RAM; if
faster or similar, add free RAM and swap.
</p>
</li>
<li>
<p>
You now have a number, be it just the free RAM or the free RAM plus
the free OS swap. Reduce it a bit, to be on the safe side, and
that is the Tile Cache you could use as a good start.
</p>
</li>
</ol>
</div>
<p>
As you can see, all is about checking the free resources, and
decide if the OS swap is worth using or will cause more problems
than help.
</p>
<p>
There are some reasons you want to adjust this value, though. The
basic one is changes in your computer usage pattern, or
changing hardware. That could mean your assumptions about how you
use your computer, or the speed of it, are no longer valid. That
would require a reevaluation of the previous steps, which can
drive you to a similar value or a completly new value.
</p>
<p>
Another reason to change the value is because it seems that Gimp
runs too slowly, while changing to other applications is fast:
this means that Gimp could use more memory without impairing the
other applications. On the other hand, if you get complaints from
other applications about not having enough memory, then it may
benefit you to not let Gimp hog so much of it.
</p>
<p>
If you decided to use only RAM and Gimp runs slowly, you could try
increasing the value a bit, but never to use also all the free
swap. If the case is the contrary, using both RAM and swap, and
you have problems about lack of resources, then you should
decrease the amount of RAM available to Gimp.
</p>
<p>
Another tricks is to put the Swap Dir in a very fast disk, or in a
different disk than the one where most of your files
reside. Spreading the operating
system swap over multiple disks is also a good way to speed up
things, in general. And of course, maybe you have to buy more RAM
or stop using lots of programs at the same time: you can not
expect to edit a poster in a computer with 16MB and be fast.
</p>
<p>
You can also check what memory requirements your images have. The
larger the images, and the number of undos, the more resources you
need. This is another way to choose a number, but it is only good
if you always work with the same kind of images, and thus the real
requirements do not vary. It is also helpful to know if you will
require more RAM and/or disk space.
</p>
</div>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="ch01s04s03.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="index.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">4.3. What Happens to a Bug Report after you Submit it </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> 2. Running Gimp</td>
</tr>
</table>
</div>
</body>
</html>
|
