The peerSynth tutorial
|Welcome!||Welcome to the peerSynth tutorial. Just step thru the topics and you will
discover all details of the peerSynth concept. Have fun!
The first Sound
|You like to hear your first peerSynth Sound? OK, nothing else is that easy:
After installing peerSynth run peerSynth.exe. You see your own instrument in the left corner of the peerSynth field. Just press on the blue line in the slider at the bottom of your instrument...
(If you running peerSynth the first time you are asked to setup the Audio-Engine).
Play with OSC
|You can either play your instrument in OSC Mode or File Mode. OSC Mode uses internal Oscillators to generate a monophonic sound. Switch
to OSC Mode by pressing the <OSC> Button.
Hold the Sound
Attack and Release Time
You can control the OSC by using MIDI.
Play with Files
|You can either play your instrument in monophonic OSC Mode or polyphonic File Mode. Switch to File Mode by pressing the <File>
Choosing a Source File
Playing with the file
|After generating a Sound in OSC or File Mode it is serially processed by three independent effects.
Each effect can be controlled by X/Y controllers (The blue balls ). But it is not a normal X/Y controller: It is a physical model of a ball in a cave or a bowl. The top <S> slider beside the field controls the speed of the ball and the right <B> slider will turn the field into a bowl and then you have an auto centered system. Throw the light with the mouse. Fast movements of the mouse will make fast movements of the light. Alternative you can use midi-events to control the light. This X/Y PM-Controller is an invention of the buero </stelkens> in 2001.
To test the effects please increase Release time or switch to Hold-Mode as it is described in OSC Mode.
Scratch-Delay & Feed
Now you can generate short sequences with the Scratch-Delay: Use short source sounds by reducing release time. Then choose a ball position in the scratch delay field. Then play the first tone. After that play another tone. And so on. Hear the sequence! By moving the scratch delay you can change the speed of the sequence. Applying this, changes the stored sequence to a really crazy inferno. To clear the loop just move the Fader to the bottom.
Volume & Pan
Prepare a connection (about the Options)
|Would you like now to contact other peers and share the fun? Please read the following
step to prepare your peerSynth connection to the world!
Feel free to share the peerSynth Software!
Enter Session- and Nic-Name (required)
Go to the <Session> tab. Enter a Name of the current Session (e.g. cooljam) and press <Add date>. After that select your Nic-Name. These names are not only for identification in the network but they are also used to structure your database and log files. So please choose them with care! If you can't make up your mind now, no problem: All options can be changed during a running session. If you wish you may pick a new color for your instrument to provide better identification. Also this may be done during a running session.
Skip the other tabs now. They are discussed later in the tutorial.
Connect a peer
|Now you are prepared for your first connection! You see the Name and Session
Information at the top of your instrument. If you press <?> Button
more information,which you have entered in the options are displayed. Press <C> to pick a new color for your instrument.
Make a connection
You can login to that server by pressing the left button. After that your info that you entered in the option dialogue will be passed encrypted to the public peersynth session server. After that you will see a list of all peers that are online at the moment. Now you are able to chat and connect them. Be aware that other peers join your session during jamming!
Please read carefully the hints inside the upcoming window:
To connect to a peer that have also join the public network and is online at the moment just select him out of the first list and press <Connect> button. If you like you can leave the window open while jamming. If you like to delete your entry in the list, please use <Log Out and Close> button.
Join or create a private Network
|As soon a connection is established a new instrument representing the
new peer is born inside peerSynth. This is a so called user-representation
and this instrument will reflects all actions the peer does on its own
instrument. So each peer is eating your CPU-Power because they got an own
DSP-Thread to generate the sound. Please go to Window| Show/Hide DSP Info
to get an impression what's going on inside the audio path of your peerSynth
You got that idea? Here you see a scheme that illustrates the idea for three interconnected peers:
Each of the peerSynth network players is represented in each local peerSynth
instance as a user with his/her own interface and sound synthesis unit(module).
This means, for example, that if three users are connected via peerSynth
then 3 user interfaces and 3 sound synthesis units are produced by each
running peerSynth instance.
Using the peerSounds
More than one peer
Asymmetrical musical Networks
Chat to peers
|You have noticed that until now you can`t play the peers instruments.
So when all peers in a session allow or not allow manipulation then there is
no hierarchy in that network, but if someone allows and someone not a hierarchy
is born. Please feel free to experiment with different constellations!
What is LTSDM?
|LTSDM means Latency to Sound Distance Mapping. What the hell is that? To
understand that lets talk a bit about latency:
The latency problem
Destructive time lags or so-called latency, occur during collective music making over asynchronous networks in all real time projects. Other musical network projects sidestep this problem since they don't establish a real time connection, but only exchange data as files after they have been created. Further latency issues in real time systems arise in the use of networked live sequencers where relative time information (as opposed to absolute) is carried over the network. A local sequencer takes over the time-correct execution of musical events.
The hope for lower Internet latencies in the near future, if at all, be fulfilled only with Internet connections based within large institutions. For the independent computer musician like you, access to high-speed networks like ATM or Internet2, remains, in general, inaccessible. Considering the observations of the before mentioned approaches to musical real time collaboration, the author of peerSynth therefore considers it of little use to ignore or avoid latency problems. Rather, through the author's synthesizer concept, the existence of latency is taken into account as a given.
The author's software peerSynth's basic idea is to make a gauging of latency possible by changing the synthesized sound of a multi-user software instrument, depending on the current latency situation occurring in connections to the other users.
|The database is the heart of the peerSynths file management. It allows
you to have full and prestructured access to your and the sessions source files, log file, session recordings, live recordings and other files.
Show the database browser
The first _peersounds folder contains the peersynth sound library with hundreds of cool sounds. Just doubleclick on the names to use the sounds
Database folder: The storing place
Record a Session
|You like to record your session to a mp3 file and share that file with your peers? Then go to Synth|Record Session or press the <Session Record> button on the toolbar. The file is automatically named and inserted into the database. After recording you can send the file to your peers or use it as a sample source.
Record from Live-Input
|Parallel to your session you are able to record a mp3 file direct from the live inputs of your soundcard. This is useful to generate new sample sources during jamming or to send the peers voice messages.
Automatically use of live recordings
Adjust the Monitor Level
If you plan to use peerSynth together with sequencers or other MIDI applications that run together on the same computer you need a Loop back device driver like the freeware "HUBI'S MIDI LOOPBACK DEVICE V2.5" that you might find on the internet (see e.g. http://www.hitsquad.com/)
The MIDI Channel 1 is reserved for the local instrument. All other instruments have higher channels. For example: There are two peers connected. Your instrument receives and sends MIDI-Data on MIDI-Channel 1. peer No. 1 on MIDI-Channel 2 and peer No. 2 on MIDI-Channel 3.The peers instruments can only receive MIDI-Data if the peer allows manipulation on his instrument.
|Every action besides the pure jamming activities is stored in the session
log file. This is a simple HTML-File that you find in your database in the log folder. You can doubleclick the file to view it with your
favorite web browser.
Consider the log file as a kind of musical score of your sessions.
If you create a new session by changing the session name there will be a new creation of the log file. You can send the log file to your peers or distribute it in the internet just by uploading it to your web-site.
If you have trouble with your internet connection just take a look at the log file to find out what kind of network error occured.