summaryrefslogtreecommitdiffstats
path: root/arts
diff options
context:
space:
mode:
Diffstat (limited to 'arts')
-rw-r--r--arts/modules/README.environments38
1 files changed, 19 insertions, 19 deletions
diff --git a/arts/modules/README.environments b/arts/modules/README.environments
index c3b7b985..d8ca4dde 100644
--- a/arts/modules/README.environments
+++ b/arts/modules/README.environments
@@ -25,28 +25,28 @@ for composing a song, you might require
- several audio tracks
- a mixer
-While with artscontrol, the user can setup much of this himself manually, the
-problem is that this has to be done over and over again. That is, if he saves
-the song, the settings of his effects, instruments and the mixer will not be
-saved with it.
+While with artscontrol, the users can setup much of this themselves manually,
+the problem is that this has to be done over and over again. That is, if they
+save the song, the settings of their effects, instruments and the mixer will
+not be saved with it.
The main idea of the new interfaces in Arts::Environment is that the sequencer
can save the environment required to create a song along with the the song, so
-that the user will find himself surrounded by the same effects, instruments,...
-with the same settings again, once he loads the song again.
-
-So, conceptually, we can imagine the environment as a "room", where the user
-works in to create a song. He needs to install the things inside the room he
-needs. Initially, the room will be empty. Now, the user things: oh, I am going
-to need this nice 24 channel mixer. *plop* - it appears in the room. Now he
-thinks I need some sampler which can play my piano. *plop* - it appears in
-the room.
-
-Now he starts working, and adds the "items" he needs. Finally, if he stops
-working on the song, he can pack all what is in the environment in a little
-box, and whenever he starts working on the song again, he can start where he
-left off. He can even take the environment to a friend, and continue working
-on the song there.
+that the users will find themselves surrounded by the same effects,
+instruments,... with the same settings again, once they load the song again.
+
+So, conceptually, we can imagine the environment as a "room", where a user
+works in to create a song. They needs to install the things inside the room
+they need. Initially, the room will be empty. Now, the user thinks: oh, I am
+going to need this nice 24 channel mixer. *plop* - it appears in the room.
+Now they think: I need some sampler which can play my piano. *plop* - it
+appears in the room.
+
+Now they starts working, adding the "items" they need. Finally, if they stop
+working on the song, they can pack all what is in the environment in a little
+box, and whenever they starts working on the song again, they can start where
+they left off. They can even take the environment to a friend, and continue
+working on the song there.
Note that there might be other tasks (such as creating a film, playing an
mp3 with noatun,...) which will have similar requirements of saving the