Menu
▾
▴
SF.net SVN: jazzplusplus: [594] trunk/jazz/src/HelpFiles/jazz.tex
|
From: <pst...@us...> - 2008-06-10 21:55:38
|
Revision: 594
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=594&view=rev
Author: pstieber
Date: 2008-06-10 14:55:33 -0700 (Tue, 10 Jun 2008)
Log Message:
-----------
Applied a patch provided by Donald B. Moore.
I believe Donald submitted this on May 30. Sorry for the delay. I may have modified
it a bit, but I can't remember. I trust Donald to I'm not going to go through the
effort to see if I modified the patch.
Donald's Changes:
1. Added content to 'Common Considerations' section.
2. Added own system stats and extra content to CPU - RAM section.
3. Added content to 'operational tricks' section - some text reordered.
4. Added quickstart guide for qjackctl/qsynth/jazz++ - some other corrections.
5. Added Mac section in same chapter area.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-05 23:59:58 UTC (rev 593)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-10 21:55:33 UTC (rev 594)
@@ -15,278 +15,598 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\chapter{Introduction}\label{introduction}
+\begin{center}
-JAZZ++ is a fully featured MIDI sequencer with audio support. In addition to
-basic sequencer functions like record and play, JAZZ++ provides many edit
-features like quantize, copy, transpose, graphical pitch editing, multiple
-undo/redo etc.
+JAZZ++ is a fully featured software MIDI sequencer with audio support. In
+addition to basic sequencer functions like record and play, JAZZ++ provides
+many specialized editing features like quantize, copy, transpose, graphical
+pitch editing, multiple undo/redo etc. As an extension to traditional normal
+MIDI sequencing, JAZZ++ provides audio play (*.wav files), audio recording and
+audio/midi integration. A multi function {\em audio editor} is also included.
+JAZZ++ has support for {\em GM} (General MIDI) equipment with both {\em GS}
+and {\em XG} extensions, and also offers special functions like GS/XG sound
+editing, setting of effect types, a {\em random rhythm generator} and a {\em
+harmony browser}. Windows versions of JAZZ++ can be synchronized to other sound
+equipment (e.g. a tape recorder) using MIDI Time Code (MTC) or SongPointer
+synchronization techniques. [ed: is this still only so for the Win version??]
+
+JAZZ++ is a platform/OS independant software program, and has been designed to
+work on Windows and Linux operating systems using 32bit or 64bit Intel ix86
+based computers (the 'PC'), and also for MacOSX using Mac computer systems. [ed:
+ppc? intelmac? m680x0? ;-] Being a MIDI based program, JAZZ++ can interact with
+both externally connected MIDI equipment (MIDI capable keyboards, synthesizer
+modules, drum-machines etc), internally connected MIDI equipment (soundcards
+with hardware based MIDI/synth capabilities), or with one or more MIDI capable
+software synthesizer programs ('softsynths') running on the same computer as
+JAZZ++. [ed: I'd like to add something here...is it possible ...or going to
+be...to use combinations of all of these?]
+
+
+
+[ed:..actually, this belongs in it's own chapter above trackwindow, with a
+title like 'Overview of working with jazz++'...then this bit below would
+fit.....]
+
+
JAZZ++ has two main windows; one
operating on the song as a whole, and one operating on single tracks and
single events. Among the other windows and dialogs are mixer windows for easy
adjusting of default track parameters, and all settings are saved into the
MIDI file for later use.
-JAZZ++ has support for {\em GM} (General MIDI) equipment with both {\em GS}
-and {\em XG} extensions.
-JAZZ++ offers special functions like GS/XG sound editing, setting of effect
-types, a {\em random rhythm generator} and a {\em harmony browser}. Windows
-versions of JAZZ++ can be synchronized to other sound equipment (e.g. a tape
-recorder) using MIDI Time Code (MTC) or SongPointer synchronization
-techniques.
+[ed:...and carry on with some bits removed from track/piano/audio chapters
+ below which are more to do with basic -program- operations and nothing
+to do with -tracks- (or the editing thereof) at all for instance.]
-As an extension to normal MIDI sequencing, JAZZ++ provides audio play
-(*.wav files), audio recording and audio/midi integration. A multi function
-{\em audio editor} is also included.
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{System requirements}\label{requirements}
-\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{jzwins.png}}%
-\htmlonly{\image{0cm;0cm}{jzwins.png}}%
-\caption{Main windows of JAZZ++}%
-\end{figure}
+JAZZ++ is a software MIDI sequencer that makes it possible for the JAZZ++
+user to employ everyday personal computing hardwares, and other connected MIDI
+based equipment, to potentially create a very powerful and highly featured
+Digital Audio Workstation (DAW). The performance of JAZZ++ itself when used
+is this manner, is primarily dependent on just how capable/powerful the user's
+computer system actually is This section briefly describes the various minimum
+hardware and software requirements needed for satisfactory operation using the
+JAZZ++ software MIDI sequencer.
-\section{System requirements}\label{requirements}
+The original Jazz++ documentation recorded here;
-\subsection{MIDI and audio equipment}
+"To play MIDI music your PC must be attached to a MIDI synthesizer device. The
+synthesizer can either be an integrated part of a sound-card, or an external
+device attached to the PC with a cable. To record MIDI music you will need a
+midi-capable piano-keyboard attached to the PC (as an alternative you can enter
+notes using the mouse). For audio you need an audio capable sound card."
-*NEW*
-[ed: this is an example of keeping original content]
+It is now 2008, and a lot has changed in the computing hardware and software
+arenas since the original JAZZ++ documentation was drafted some time around
+1995. While the above paragraph is more or less still correct, it was written in
+a time before modern computers had 'onboard' sound hardware like most people
+have now-a-days. Likewise, back in those days software based MIDI synthesizers
+were not as functional (nor as plentiful) as they are today, so you really
+\underline{don't} need any 'real' MIDI hardware to play MIDI music on your PC
+anymore -- you can use a software synthesizer (softsynth) instead.
-The original Jazz++ documentation recorded here;
-"To play MIDI music your PC must be attached to a MIDI synthesizer
-device. The synthesizer can either be an integrated part of a
-sound-card, or an external device attached to the PC with a cable.
-To record MIDI music you will need a midi-capable piano-keyboard
-attached to the PC (as an alternative you can enter notes using
-the mouse). For audio you need an audio capable sound card."
+\subsection{Operating Systems supported by JAZZ++}
+The current version of JAZZ++ is known to work with the Windows, Linux, and
+MacOSX operating systems. You will need to be running one of these operating
+systems on your computer hardware to use JAZZ++.
-A lot of that is still the same even today - if you're not using
-a hardware MIDI/synth soundcard or externally connected MIDI
-synthesizer, you will need an audio capable soundcard to hear
-anything. Today however, most personal computers already have
-'onboard' audio sound chipsets, so for most people it's very
-likely that you already have this requirement satisfied. Likewise,
-MIDI/synth capable addon soundcards are a -lot- cheaper today
-than when Jazz++ first started out, and you can buy MIDI/synth
-soundcards of various types for under 50 dollars these days.
-One can also buy high-end MIDI/synth soundcards for a few hundred
-dollars if you're looking for the very best quality sound ouput,
-or otherwise 'professional' features and specifications.
+\subsection{Computer Architectures supported by JAZZ++}
-Back when the original Jazz++ documentation was written, there
-weren't many 'software synthesizer' programs available for the
-personal computer, and even if they were available, the then
-computing hardware was simply too slow to run such software
-properly. A lot has changed since then and now. Today, even so
-called 'entry level' personal computers have more than enough power
-to run Jazz++ concurrently with one (or more) 'software synthesizers'
-running on the same machine, thus making it possible for Jazz++ to
-become the basis of a fully functional Digital Audio Workstation
-(DAW) using otherwise standard, low cost personal computer systems
-and/or other now affordable add-on sound/MIDI hardware options.
+The current version of JAZZ++ is known to work with most all computer
+architectures supported by the above Operating Systems. This includes the
+Intel based 'PC' hardware platforms (x86_32bit and x86_64bit), and also Mac
+computer system hardwares.[ed: bit more clarity with the Mac stuff here]
-This area of the Jazz++ documentation provides information
-explaining common concepts of working with MIDI, details of how to
-get the most out of you personal computer when using it with
-Jazz++, and also platform/OS specific information regarding setting
-up and using Jazz++ with the now available hardware technologies
-and various 'software synthesizer' MIDI programs available to the
-personal computer user today.
+\subsection{Software pre-requisites of JAZZ++}
-*NEW*
+The current version of JAZZ++ uses the wxWidgets GUI library to create
+the JAZZ++ user interFace. The wxWidgets GUI library, like JAZZ++ itself,
+is platform/OS independant, and versions of wxWidgets are available for
+all platforms/OS' currently supported by JAZZ++. If you do not have the
+wxWidgets GUI library installed, please visit the following link to download
+and install wxWidgets for your platform/OS ;
-\item MIDI, Time and the Personal Computer
+\begin{indented}{2cm}
+\urlref{http://www.wxwidgets.org/}{http://www.wxwidgets.org/}
+\end{indented}
-The MIDI protocol attempts to be a real time protocol. This is
-unsurprising -- sound generation and replay (of a song or most
-all musical compositions) happens in real time, the audience
-and/or the recording studio hear the performance in real time.
-If you are a performer on stage using MIDI equipment, that MIDI
-equipment must be operating as close to real time performance
-as it possibly can -- when the performer plays a note on a MIDI
-keyboard, that note event should be heard almost instantaneously
-not in 50 to 200 milliseconds of time after the event. Likewise,
-every note event should be acted upon - if the MIDI track is
-sequenced to produce 8 beats on a kick drum voice, you should
-hear the synthesizer produce 8 beats of that voice, not 7 beats.
+The wxWidgets GUI library \underline{must be installed} before installing
+JAZZ++ itself.
-Time (with regards to MIDI) is what we used to measure the actual
-deviation from 'real' time that the MIDI response time effectively
-is. Remember, I stated MIDI *attempts* to be a real time protocol,
-but in actual practise it very rarely is. There are latencies in
-various parts of the MIDI chain -- even the physical length of
-the MIDI patch-cords introduce latency..albeit small..into the
-interconnected MIDI device chain. The response time of the
-MIDI instrument receiving a transmitted note event is another
-place latency can be experienced, and if you are using Jazz++
-to trigger another externally connected MIDI device which itself
-is a sequencer, the timing is even more important to ensure
-everything starts, plays, and remains 'in sync'.
-The above two paragraphs are things common to the MIDI domain
-that MIDI users have always had to deal with, regardless of
-whether or not a PC was being used in the MIDI chain. As a
-matter of fact, a 'virtual' MIDI chain involving softsynths
-and Jazz++ running on a PC, is subject to exactly the same
-kinds of limitations and latency problems as 'real' MIDI
-equipment does...plus one extra layer -- the inherent amount
-of latency in the operating system and PC hardware being used
-to 'host' the virtual MIDI machines and software programs.
+\subsection{Recommended Computer Specifications for using JAZZ++}
-When using a PC in this fashion, there are possible latencies
-in a few different places of the setup overall ; how fast the
-'host' system executes (runs) Jazz++ itself, how fast the
-generated note events can be delivered to/from the computer's
-hardware ports, and/or how fast these same note events can
-be delivered to and be rendered by a softsynth running concurrently
-on the same system. Just how powerful your particular hardware is
-does matter, however there are some common methods and practises
-that can be employed to better tailor how your personal computer
-performs with Jazz++. There are also some platform/OS specific
-'tweaks' that can be employed to help make your platform of
-choice run better when using Jazz++ with timing critical
-protocols such as MIDI on the modern day PC.
+How powerful your computer system needs to be, is determined primarily by
+how you use it with JAZZ++ ....ie; if you are going to be using JAZZ++ on
+a computer system that is also running a MIDI 'softsynth' for the actual sound
+rendering and reproduction, you will need more computing power compared to
+using JAZZ++ with the same computing hardware and having MIDI/synth soundcards
+and/or external MIDI devices connected to it instead.
-Running Jazz++ should not impose any significant system load
-by itself, however it does rely on the operating system to
-deliver the MIDI data to the intended hardware/virtual ports,
-and also for delivering software data to the computer's
-graphics adapter for GUI updates..ie; track window scrolling.
+Generally speaking though, any 'modern' computer system (post-2000) with a
+1GHz or greater CPU speed and 512Mb or system ram, should easily run JAZZ++
+in normal use. Even computer systems older than this date might be perfectly
+capable or running JAZZ++ depending on what you are doing and how much system
+ram that older computer has. More details of the actual requirements needed here
+are discussed in the 'Installation and Setup' chapter of this manual, and
+various platform/OS specific informations can be found in this manual's
+Appendix section.
-No matter what PC hardware you are using, most all of this
-software data has to be processed by (or pass through) the
-operating system in use, and most modern operating systems
-allow the software programmers to use so called 'real time'
-kernel calls, and direct, immediate access to I/O ports and
-so forth to the actual computer hardware itself. On some
-platform/OS types this doesn't happen automatically, and some
-users might have change some system configurations to achieve
-optimum performance when using Jazz++ and MIDI on their
-personal computing machine.
+\subsection{MIDI devices supported by JAZZ++}
-\item SoundFonts - what are they, who needs them.
+JAZZ++ supports all standard MIDI protocols and commands, and as such should
+work with any standard MIDI capable equipment and/or musical instruments. JAZZ++
+also supports most 'virtual' MIDI devices, such as software synthesizers, other
+software MIDI sequencers and trackers, and software virtual MIDI keyboards - if
+it's MIDI, it should work with JAZZ++ 'out of the box'.
-Soundfonts are data files that both hardware MIDI/synth cards and
-MIDI softsynths may use to create (or synthesize) the actual sound
-you hear playing. Soundfont files, typically end in the .sf2 .SF2
-extensions, although you may also find .sfArk or .sfpack files, which
-are normal .sf2 packages compressed with a lossless encoding tool. A
-multitude of free soundfont packages exist on the internet, most of
-them quite good however some have decidedly better sound quality than
-others. There are also soundfont editors available for most platforms
-supported by Jazz++, which allows the user to create their own custom
-soundfont library file.
-A soundfont itself is a software library file containing both sampled
-audio data, and synthsizer parameter definitions, along with the
-table of MIDI data that describes the 'soundbank' itself. The soundbank
-presents itself to the user, as a list describing exactly what
-instruments, voices, or sounds are contained in each soundfont library
-file. Taking your time to search for 'the right' soundfont for your
-use can take a bit of trial and error, but it's well worth the trouble.
-On the other hand, you can also buy high quality soundfont libraries
-from commercial companies, sometimes referred to as sound 'foundaries'.
+\section{Where to get it}\label{wheretoget}
-Many MIDI/synth soundcards require soundfont files to work, and the
-softsynth setup described below also requires 1 (or more) soundfont
-files to actually make any pleasing sounds. Although the FLUIDSYNTH
-package includes it's own sample soundfont file, the quality is not
-the best...which you'll discover, when you download and install your
-own soundfont files. In the Appendix section of the manual, is a
-short list of soundfont resources we here at Jazz++ think you should try.
+For the latest JAZZ++ updates from {\em sourceforge}, please look at the JAZZ++
+homepage at ;
-This area of the Jazz++ documentation provides information
-detailing how to get the most out of you personal computer when
-using it with Jazz++, and also platform/OS specific information
-regarding setting up and using Jazz++ with the now available
-hardware technologies and various 'software synthesizer' MIDI
-programs available to the user today.
+\begin{indented}{2cm}
+\urlref{http://jazzplusplus.sourceforge.net}{http://jazzplusplus.sourceforge.net
+}
+\end{indented}
-\subsection{Common Considerations when using Jazz++}
+[ed: make the above link point to downloads page? ]
+If you are interested in developing JAZZ++ or want to check out the latest
+'bleeding edge' version of the JAZZ++ source code, you can always checkout the
+JAZZ++ Subversion repository at ;
+
+ \begin{indented}{2cm}
+\urlref{http://jazzplusplus.sourceforge.net/subversion}{
+http://jazzplusplus.sourceforge.net/subversion}
+\end{indented}
+
+\section{Getting Help with JAZZ++}
+
+You are welcome to join the JAZZ++ mailing lists if you require any additional
+or specific help with JAZZ+ usage and setup not covered by this manual. The
+JAZZ++ mailing lists give JAZZ++ users the facility to discuss problems they
+might be having with JAZZ++, with both other users of the software -and- the
+developers of JAZZ++ itself.
+
+The JAZZ++ developers are a faily easy going bunch of people, and they really do
+look forward from hearing from you, however, to protect both themselves and
+other subscribers to the JAZZ++ mailing lists from 'SPAM', they ask that people
+who join and post emails to the JAZZ++ mailing lists adhere to the following
+two points of list etiquette ;
+
+\item{'PCYMTNQREAIYR'}
+
+\underline{Please Configure Your Mailer To Not Quote Raw E-mail Addresses In
+Your Replies.}
+Some email programs ('Mailers') by default include the raw e-mail address in the
+"Joe <jo...@ex...> wrote:" line. The web archives for the mailing lists are
+publicly available. Let's not feed the spam harvesters! Mailing lists are
+routine targets for spam software to come looking for valid email addresses, and
+if you include raw email addresses in your email replies you may well be
+inadvertantly and innocently unaware that you're actually helping such spam
+operations in doing so. People who use their web-browser and one or another of
+the free public email servers available... like hotmail, yahoo and so on...have
+to be particularly careful with this, and you may find that you have to manually
+delete raw email addresses from you replies to comply with this etiquette.
+
+\item{'PCYMTWLL'}
+
+\underline{Please Configure Your Mailer To Wrap Long Lines.} Some email programs
+don't, and
+this is especially so when a web-browser interface is being used, and then most
+of the message ends up looking like one lo-ong line in the web archives. It's
+very annoying to have to scroll left and right as well as up and down. Please be
+considerate of this situation! All you have to do is remember to hit the return
+[enter] key at about 80 characters along each line, and start a new line. Your
+email text in an web-browser window, should appear as a column in the left of
+your web-browser window, not as a document that fills the entire window page. It
+makes it easier for everyone if you please comply with this etiquette when
+submitting emails to the lists.
+
+ \begin{indented}{2cm}
+\urlref{http://jazzplusplus.sourceforge.net/mailinglist}{
+http://jazzplusplus.sourceforge.net/mailinglist}
+\end{indented}
+
+
+There are three mailing lists. The first is a devoted to JAZZ++ users. To
+subscribe, please visit ;
+
+ [ed: double check these links below]
+
+\begin{indented}{2cm}
+\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}{
+https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}
+\end{indented}
+
+The second is devoted to developers. To subscribe visit
+
+\begin{indented}{2cm}
+\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}{
+https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}
+\end{indented}
+
+The third list contains messages generated by developers when they commit
+documentation, web content, or code to the JAZZ++ subversion repository.
+To subscribe visit
+
+\begin{indented}{2cm}
+\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}{
+https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}
+\end{indented}
+
+We'd also be happy to receive your bug reports (well, somehow). We want to find
+and fix any problems with JAZZ++, so bug reports are welcomed. Before you do
+send any email regarding a possible JAZZ++ bug, please be sure to read the
+JAZZ++ Reporting Bugs page on the JAZZ++ website, for instructions on how
+to gather the necessary informations JAZZ++ developers might need to fix the
+problem, and how to submit that bug report in a meaningful and consistant way ;
+
+ \begin{indented}{2cm}
+\urlref{http://jazzplusplus.sourceforge.net/bugreports}{
+http://jazzplusplus.sourceforge.net/bugreports}
+\end{indented}
+
+
+//...this subpara below should be melded into the above somewhere...//
+[ed: probably to get it to hit -user instead of -devel..fix l8r]
+
+ or success stories. And - of course - you are welcome to contribute to the
+JAZZ++ project by sending code, suggestions, ..., or corrections for this
+manual.
+
+\section{Acknowledgments}
+
+JAZZ++ is based on the work of countless other people who have have made
+their software freely available. Beside all the people who made Linux,
+GNU and X11 possible, we'd like to mention
+
+\begin{itemize}
+\item {\em Hannu Savolainen} for writing all these excellent midi drivers, so
+JAZZ++ can talk to nearly every midi card on Linux.
+\item {\em Julian Smart} who wrote the free, portable GUI library
+wxwin, so JAZZ++ runs with XView, Motif and MS-Windows.
+\end{itemize}
+
+We would also like to thank Henrik Seidel and Stefan Nitschke for code
+contributions.
+
+[ed: is the above complete for this section?]
+
+\section{Copyright}\label{copyright}
+
+The JAZZ++ MIDI Sequencer is copyright (C) 1994-2000 Andreas Voss and
+Per Sigmond, all rights reserved.
+
+[ed: Pete's name should be here somewhere too ]
+
+JAZZ++ program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\chapter{Installation and Setup}\label{installation}
+
+This chapter of the JAZZ++ manual, describes how to install JAZZ++ itself
+on the three platforms/OS' currently supported, and how to setup the MIDI
+and computer hardware systems for use with JAZZ++. Although most all the
+various features and functions of JAZZ++ work identically for all supported
+OS types and computer platforms, there are small inherent differences on
+how to do things relative to which platform/OS you might be using when it
+comes to installing and setting up the systems for use with JAZZ++ itself.
+
+If you are new to JAZZ++ and the MIDI domain, you are encouraged to read the
+following sections to gain some insight about how things work, and how they
+fit together to complete the final system setup for use in conjunction with
+the JAZZ++ software MIDI sequencer.
+
+On the other hand, if you're already conversant with MIDI operations and just
+want to get on with the installation and setup process, feel free to skip the
+following descriptive passages and move on to the OS specific instructions
+that appear later in this chapter.
+
+
+\section{MIDI and audio equipment}
+
+The term 'MIDI' is an acronym - it stands for (the) 'Musical Instrument Digital
+Interface'. It is an industry-standard protocol that enables electronic musical
+instruments, computers, and other MIDI capable equipment to communicate,
+control, and synchronize with each other using a common 'language'. The MIDI
+protocol does not deal with audio data itself, but instead transmits (and
+receives) MIDI data that..for example...tells the connected MIDI synthesizer
+what note to play, when to play it, and how to play it. In recent years with
+the many advances in both electronics and computer technologies, it has been
+possible to incorporate both MIDI functionality and audio editting facilities
+into the same MIDI domain, and both dedicated MIDI hardware equipment, and
+software based MIDI programs like JAZZ++, have audio (sound file) manipulation
+facilities builtin.
+
+Back when the original Jazz++ was being developed, there weren't many 'software
+synthesizer' programs available for the personal computer, and even if they were
+available, the then computing hardware was simply too slow to run such software
+properly. A lot has changed since then and now. Today, even so called 'entry
+level' personal computers have more than enough power to run Jazz++ concurrently
+with one (or more) 'software synthesizers' running on the same machine, thus
+making it possible for Jazz++ to become the basis of a fully functional Digital
+Audio Workstation (DAW) using otherwise standard, low cost personal computer
+systems and/or other now affordable add-on sound/MIDI hardware options.
+
+
+If you're not using a hardware MIDI/synth soundcard or externally connected
+MIDI synthesizer, you will need an audio capable soundcard to hear anything.
+Today however, most personal computers already have 'onboard' audio sound
+chipsets, so for most people it's very likely that you already have this
+requirement satisfied. Likewise, MIDI/synth capable addon soundcards are a -lot-
+cheaper today than when Jazz++ first started out, and you can buy MIDI/synth
+soundcards of various types for under 50 dollars these days. One can also buy
+high-end MIDI/synth soundcards for a few hundred dollars if you're looking for
+the very best quality sound ouput, or many otherwise 'professional' features
+and specifications such soundcards boast.
+
+If on the other hand you do intend to use JAZZ++ with one or another external
+MIDI devices/instruments connected to your computer, you will need to install
+and setup your OS dependant drivers to be able to communicate with whatever
+computer-to-MIDI interface and equipment you happen to be using. It is common
+practise today to use the USB computer port to connect such hardware MIDI
+interfaces, however there are examples that use the serial port, the parallel
+port, or otherwise come as an addon computer interface card instead. Whatever
+hardware is used, the OS specific drivers must be installed and configured for
+use with JAZZ++. Unfortunately, it is beyond the scope of this manual to give
+JAZZ++ users any specific help with this task, if for no other reason than the
+JAZZ++ team simply not having hands-on access to every possible MIDI interface
+type in the world today. This is further recited, in the OS specific sections
+of the manual appearing in this chapter.
+
+
+This area of the Jazz++ documentation provides information explaining common
+concepts of working with MIDI and the personal computer, and details how to
+get the most out of you personal computer when using it with Jazz++, and also
+platform/OS specific information regarding setting up and using Jazz++ with the
+now available computer hardware technologies and various 'software synthesizer'
+MIDI programs available to the personal computer user today.
+
+
+\section{Common Considerations when using Jazz++}
+
\item CPU and RAM Requirements
CPU
The original Jazz++ user manual advised -- "For MIDI-only operation
-a 486 CPU (or equivalent) is sufficient in most cases. For
-satisfactory audio operation a Pentium CPU with 32 MBytes RAM is
-recommended." That may well be true for MIDI only operations with
-no sound of any kind being needed to be produced by the computer
-hardware. Perhaps we will never know for sure how well Jazz++ ran
-on such computing powerhouses as the i486 CPU running at a then
-whopping 100mHz, because most of this hardware is now dead and gone.
+a 486 CPU (or equivalent) is sufficient in most cases. For satisfactory audio
+operation a Pentium CPU with 32 MBytes RAM is recommended." That may well be
+true for MIDI only operations with no sound of any kind being needed to be
+produced by the computer hardware. Perhaps we will never know for sure how well
+Jazz++ ran on such computing powerhouses as the i486 CPU running at a then
+whopping 100MHz, because most of this hardware is now dead and gone.
-Most modern personal computer systems now boast CPU speeds in
-excess of 2.0 gHz -- even a new low-end 'entry level' computer
-system is likely to be running at speeds greater than 1.5gHz.
-This should be more than enough computing (CPU) power to run
-and use Jazz++ effectively on a modern personal computing machine,
+Most modern personal computer systems now boast CPU speeds in excess of 1.5 GHz
+-- even a new low-end 'entry level' computer system is likely to be running at
+speeds greater than 2.0GHz. This should be more than enough computing (CPU)
+power to run and use Jazz++ effectively on a modern personal computing machine,
even with softsynths running to produce the actual sound itself.
RAM
-As mentioned earlier, Jazz++ itself should not present any
-significant system load to the personal computer it's being
-run on. Likewise, Jazz++ doesn't need a lot of system RAM to
-work correctly with modern computer hardwares. The user will
-however need enough system RAM installed to meet the following
-requirements for smooth and trouble free Jazz++ sessions ;
+As mentioned earlier, Jazz++ itself should not present any significant system
+load to the personal computer it's being run on. Likewise, Jazz++ doesn't need a
+lot of system RAM to work correctly with modern computer hardwares. The user
+will however need enough system RAM installed to meet the following requirements
+for smooth and trouble free Jazz++ sessions ;
-1. You will need enough system RAM installed to cover your computer's
-system requirements without the system needing to access the
-hard-disk based 'swap' (or 'pagefile') area of RAM whilst
-using Jazz++. Compared to real 'chip' RAM, hard-disk based
-RAM devices are incredibly slow and this can 'bottlenexk'
-other system operations. More importantly, to access hard-disk
-based RAM means generating a lot of hardware interrupts at the
-same time. Doing this is very likely to impact on MIDI playback
-and record operations in Jazz++ and introduce timing latency issues.
+1. You will need enough system RAM installed to cover your computer's system
+requirements without the system needing to access the hard-disk based 'swap' (or
+'pagefile') area of RAM whilst using Jazz++. Compared to real 'chip' RAM,
+hard-disk based RAM devices are incredibly slow and this can 'bottleneck'
+other system operations. More importantly, to access hard-disk based RAM means
+generating a lot of hardware interrupts at the same time. Doing this is very
+likely to impact on MIDI playback and record operations in Jazz++ and introduce
+timing latency issues.
-2. If you use soundfonts (and you probably will do), you need
-enough system RAM to hold these soundfile libraries, -above-
-the system RAM requirements. Soundfont libraries are loaded into
-RAM, and whilst a lot of soundfont files are small (<1mb), others
-can be quite large (100+mb), and depending on how many soundfont
-libraries you intend to use and how big they are, dictates exactly
-how much RAM you will need here.
+2. If you use soundfonts with MIDI/synth soundcards or softsynths (and you
+probably will do), you need enough system RAM to hold these soundfile libraries,
+-above- the system RAM requirements. Soundfont libraries are loaded into RAM,
+and whilst a lot of soundfont files are small (<1mb), others can be quite large
+(100+mb), and depending on how many soundfont libraries you intend to use and
+how big they are, dictates exactly how much RAM you will need here.
-It is nearly impossible to correctly and accurately predict just
-how much CPU speed and system RAM is needed in every individual's
-case -- there as just too many variables to consider. To give the
-reader some idea though, the following are results observed by
-one of the Jazz++ testing team ;
+It is nearly impossible to correctly and accurately predict just how much CPU
+speed and system RAM is needed in every individual's case -- there are just too
+many variables to consider. To give the reader some idea though, the following
+are results observed by one of the Jazz++ testing team ;
[ed: add system stats]
-Other Jazz++ operational tricks ;
-1. Try lowering your desktop resolution and/or bits-per-pixel value.
-Doing this will also lower the load on your CPU when running Jazz++, and
-enable things to run closer to real time overall. Try using the lowest
-possible resolution and screen dimension that you can -comfortably-
-work with while using Jazz++ at a color depth of 8 bits-per-pixel,
-and see if that helps real time performance.
-2. The ZOOM buttons are your friends! To avoid unnecessary system
-load when running record/replay sessions with Jazz++, always remember
-to zoom out so the track window graphics are in complete view with
-no need to paginate the window scrolling operation. Zoom in again if
-you want to edit a portion of a track. Having to paginate and scroll
-the Jazz++ track window, generates hardware interrupts which may
-impact real time performance.
+*NEW*
-3. Try to have as few software programs running in the background at
-the same when using Jazz++ on a computer system. Really serious Jazz++
-users will try to have the absolute minimum of other software programs
-running when using Jazz++, to ensure they get as close to real time
-performance as is possible using Jazz++ on their personal computer.
+\item MIDI, Time and the Personal Computer
-\subsection{Linux operating systems}
+The MIDI protocol attempts to be a real time protocol. This is unsurprising --
+sound generation and replay (of a song or most all musical compositions) happens
+in real time, the audience and/or the recording studio hear the performance in
+real time. If you are a performer on stage using MIDI equipment, that MIDI
+equipment must be operating as close to real time performance as it possibly can
+-- when the performer plays a note on a MIDI keyboard, that note event should be
+heard almost instantaneously not in 5 to 200 milliseconds of time after the
+event. Likewise, every note event should be acted upon - if the MIDI track is
+sequenced to produce 8 beats on a kick drum voice, you should hear the
+synthesizer produce 8 beats of that voice, not 7 beats.
+Time (with regards to MIDI) is what we used to measure the actual deviation from
+'real' time that the MIDI response time effectively is. Remember, I stated MIDI
+*attempts* to be a real time protocol, but in actual practice it very rarely is.
+There are latencies in various parts of the MIDI chain -- even the physical
+length of the MIDI patch-cords introduce latency..albeit small..into the
+interconnected MIDI device chain. The response time of the MIDI instrument
+receiving a transmitted note event is another place latency can be experienced,
+and if you are using Jazz++ to trigger another externally connected MIDI device
+which itself is a sequencer, the timing is even more important to help ensure
+everything starts, plays, and remains 'in sync'.
+
+The above two paragraphs are things common to the MIDI domain that MIDI users
+have always had to deal with, regardless of whether or not a PC was being used
+in the MIDI chain. As a matter of fact, a 'virtual' MIDI chain involving
+softsynths and Jazz++ running on a PC, is subject to exactly the same kinds of
+limitations and latency problems as 'real' MIDI equipment does...plus one extra
+layer -- the inherent amount of latency in the operating system and PC hardware
+being used to 'host' the virtual MIDI machines and software programs.
+
+When using a PC in this fashion, there are possible latencies in a few different
+places of the setup overall ; how fast the 'host' system executes (runs) Jazz++
+itself, how fast the generated note events can be delivered to/from the
+computer's hardware ports, and/or how fast these same note events can be
+delivered to and be rendered by a softsynth running concurrently on the same
+system. Just how powerful your particular hardware is does matter, however there
+are some common methods and practices that can be employed to better tailor how
+your personal computer performs with Jazz++. There are also some platform/OS
+specific 'tweaks' that can be employed to help make your platform of choice run
+better when using Jazz++ with timing critical protocols such as MIDI on the
+modern day PC.
+
+Running Jazz++ should not impose any significant system load by itself, however
+it does rely on the operating system to deliver the MIDI data to the intended
+hardware/virtual ports, and also for delivering software data to the computer's
+graphics adapter for GUI updates..ie; track window scrolling.
+
+No matter what PC hardware you are using, most all of this software data has to
+be processed by (or pass through) the operating system in use, and most modern
+operating systems allow the software programmers to use so called 'real time'
+kernel calls, and direct, immediate access to I/O ports and so forth to the
+actual computer hardware itself. On some platform/OS types this doesn't happen
+automatically, and some users might have change some system configurations to
+achieve optimum performance when using Jazz++ and MIDI on their personal
+computing machine.
+
+\item SoundFonts - what are they, who needs them.
+
+Soundfonts are data files that both hardware MIDI/synth cards and MIDI
+softsynths may use to create (or synthesize) the actual sound you hear playing.
+Soundfont files, typically end in the .sf2 .SF2 extensions, although you may
+also find .sfArk or .sfpack files, which are normal .sf2 packages compressed
+with a lossless encoding tool. A multitude of free soundfont packages exist on
+the internet, most of them quite good however some have decidedly better sound
+quality than others. There are also soundfont editors available for most
+platforms supported by Jazz++, which allows the user to create their own custom
+soundfont library file.
+
+A soundfont itself is a software library file containing both sampled audio
+data, and synthesizer parameter definitions, along with the table of MIDI data
+that describes the 'soundbank' itself. The soundbank presents itself to the
+user, as a list describing exactly what instruments, voices, or sounds are
+contained in each soundfont library file. Taking your time to search for 'the
+right' soundfont for your use can take a bit of trial and error, but it's well
+worth the trouble. On the other hand, you can also buy high quality soundfont
+libraries from commercial companies, if one needs first quality performance.
+
+Many MIDI/synth soundcards require soundfont files to work, and the softsynth
+setup described further on in this manual also requires 1 (or more) soundfont
+files to actually make any pleasing sounds. Although the FLUIDSYNTH package
+includes it's own sample soundfont file, the quality is not the best...which
+you'll discover, when you download and install your own soundfont files. In the
+Appendix section of the manual, is a short list of soundfont resources we here
+at Jazz++ think you should try.
+
+
+Jazz++ operational tricks ;
+
+1. Try lowering your desktop resolution and/or bits-per-pixel value. Doing this
+will also lower the load on your CPU when running Jazz++, and enable things to
+run closer to real time overall. Try using the lowest possible resolution and
+screen dimension that you can -comfortably- work with while using Jazz++ at a
+color depth of 8 bits-per-pixel, and see if that helps real time performance.
+
+2. The ZOOM buttons are your friends! To avoid unnecessary system load when
+running record/replay sessions with Jazz++, always remember to zoom out so the
+track window graphics are in complete view with no need to paginate the window
+scrolling operation. Zoom in again if you want to edit a portion of a track.
+Having to paginate and scroll the Jazz++ track window, generates hardware
+interrupts which may impact real time performance.
+
+3. Try to have as few software programs running in the background at the same
+when using Jazz++ on a computer system. Really serious Jazz++ users will try to
+have the absolute minimum of other software programs running when using Jazz++,
+to ensure they get as close to real time performance as is possible using Jazz++
+on their personal computer.
+
+4. If you are using other MIDI softwares or MIDI softsynths in conjunction with
+JAZZ++, if possible (and where applicable), use the relevant user GUI interface
+to set these 'virtual' MIDI entities up, but when actually playing or recording
+MIDI compositions, launch these programs from the commandline instead. Use the
+'--quiet' commandline switch if it's available. Having to render the GUI
+interfaces for such MIDI programs...especially when that GUI contains elements
+such as blinking transport running lights or 'RT' (real time) meters...steals
+valuable CPU cycles JAZZ++ (or any softsynth) might have otherwise used for it's
+own operations.
+
+
+
+
+
+
+
+
+\section{Windows operating systems}
+
+For Windows there is an install utility (run {\tt setup.exe}) which
+mostly automates the installation process.
+
+JAZZ++ supports the windows MIDI / audio driver interface. A driver for your
+MIDI interface card or sound card must be installed before JAZZ++ can play /
+record MIDI or audio.
+
+Provided such a MIDI driver is installed in your system, JAZZ++ currently
+supports 32-bit platforms.
+
+\section{Linux operating systems}
+
+For Linux there is a shell script {\tt install-jazz} in the
+distribution. You must be logged in as root when running the installation
+script. As a default JAZZ++ will be installed to {\tt /usr/local/jazz},
+this may be changed by editing {\tt install-jazz}. Also you
+must set the environment variable JAZZ to point the jazz directory by
+adding the line:
+
+{\tt export JAZZ=/usr/local/home}
+
+to your .profile or .bashrc. Please refer to the file
+{\tt install.txt} which contains up-to-date instructions.
+
+On startup JAZZ++ looks for its configuration files
+\begin{enumerate}
+\item in the current directory
+\item in the home directory (where the environment variable HOME points to)
+\item in the directory where the environment variable JAZZ points to
+\item in the directory from where JAZZ++ itself was started.
+\end{enumerate}
+The main configuration file is named {\tt jazz.cfg}.
+This file also contains pointers to other configuration files {\tt (*.jzi)}
+present in the same directory.
+Then JAZZ++ searches for a song named {\tt jazz.mid} in the current directory
+and loads it - if found. This song may contain default settings for your
+midi equipment.
+
+
[ed: This part, down to my out mark, should probably go]
The device-independent part of JAZZ++ (the sequencer / editor part) is known
@@ -294,7 +614,7 @@
(with some minor hacking) on any system supporting Linux/X11. To compile you
will need the wxWidgets GUI package together with GTK.
-The device-dependant part (midi-driver) currently supports:
+The device-dependent part (midi-driver) currently supports:
\item OSS/Free (OSS/Linux) midi driver API (formerly known as USS/Lite and
VoxWare). This API is included in later Linux kernels. The JAZZ++ code
@@ -366,10 +686,24 @@
+\subsection{Command line options (Unix only)}
+Command line options (in any order):
+
\begin{itemize}
-\item Hardware based sound synthesis and Linux on the x86 PC
+\item {\tt jazz -h} -- Print help text
+\item {\tt jazz -v} -- Print help text
+\item {\tt jazz -f filename} -- Input midi file
+\item {\tt jazz -trackwin xpos ypos [width height]} -- Position/size of main
+window
+\item {\tt jazz -pianowin xpos ypos [width height]} -- Position/size of piano
+roll window
\end{itemize}
+
+
+\begin{itemize}
+\subsection{Hardware based sound synthesis and Linux on the x86 PC}
+\end{itemize}
Thanks to all the great work done by the ALSA team over the years, Linux
now has much better driver supports for the various soundcards on the market
today that have hardware based MIDI/synth chips as part of their design.
@@ -385,7 +719,7 @@
difference it makes to system -graphics- performance, when you add
a dedicated 3D graphics-card with it's own onboard processor unit. Not
only are the graphics greatly improved, the system responsiveness is
-greatly improved.
+greatly improved as well.
Adding a dedicated MIDI/synth soundcard to your system helps for
exactly the same reasons here - it frees up your system CPU so it
@@ -404,7 +738,7 @@
\urlref{http://www.alsa-project.org/}{http://www.alsa-project.org/}
-The lastest list of ALSA supported MIDI/synth soundcards, is always
+The latest list of ALSA supported MIDI/synth soundcards, is always
available inside the current alsa-driver source tarball available from
the above website. Once you unpack that archive, read the file ;
@@ -424,7 +758,8 @@
Another good repository of current knowledge regarding Linux sound drivers
overall (not just the ALSA sound drivers) can be found at ;
-\urlref{http://linux-sound.org/drivers.html}{http://linux-sound.org/drivers.html}
+\urlref{http://linux-sound.org/drivers.html}{http://linux-sound.org/drivers.html
+}
Once you have your MIDI/synth soundcard up and running, it will appear
in Jazz++ configuration dialogs just like any other MIDI device connected
@@ -438,7 +773,7 @@
\begin{itemize}
-\item Software based sound synthesis and Linux on the x86 PC
+\subsection{Software based sound synthesis and Linux on the x86 PC}
\end{itemize}
This area of the documentation will grow over time. There is a lot
that can be documented here now with Linux.
@@ -497,7 +832,7 @@
of -hardware- based MIDI sequencers that were in common use years
ago, so called 'step sequencers'. Jazz++ is of course much more
capable than these old hardware sequencers I speak of, and more
-closely resembles a modern day Digial Audio Workstation. In their
+closely resembles a modern day Digital Audio Workstation. In their
day, old MIDI sequencers were little more than 'drum machines'
triggering sound events on a MIDI or otherwise connected 'tip-and
-ring patch cord configured' analogue synthesizer.
@@ -531,7 +866,7 @@
Many people have troubles getting these softsynths installed and
working properly on Linux based systems. The Jazz++ developers
-have also noted, that dependant on just which Linux distribution
+have also noted, that dependent on just which Linux distribution
you use, (and what release version that might be), also dictates
just how easy or difficult this process might be to complete.
@@ -542,150 +877,268 @@
For some Linux distributions, the whole process can be as
straight forward and simple as installing the needed software
packages from your Linux distribution's installation discs and/or
-online package repository.
+on line package repository. Here's how to do it ;
-Still work in progress, come back soon!!
+\item{Setting up a Linux softsynth}
+Step 1. Assuming you have already built/installed Jazz++, startup
+your Linux distribution's package manager application, and search
+for the package names 'qjackctl' and 'qsynth'. On a Debian 4.0 'Etch'
+linux system, these packages are named ;
-\subsection{Windows operating systems}
+qjackctl_0.2.21-1_i386.deb
-JAZZ++ supports the windows MIDI / audio driver interface. A driver for your
-MIDI interface card or sound card must be installed before JAZZ++ can play /
-record MIDI or audio.
+qsynth_0.2.5-2_i386.deb
-Provided such a MIDI driver is installed in your system, JAZZ++ currently
-supports 32-bit platforms.
+You should find similarly named packages in your Linux distribution's
+package collection. Install these packages, and if installation
+completes without error (it should), continue on to the next step.
-\subsection{CPU and memory}
-For MIDI-only operation a 486 CPU (or equivalent) is sufficient in most
-cases. For satisfactory audio operation a Pentium CPU with 32 MBytes
-RAM is recommended.
+[ed: if this flunks out?....]
-\section{Where to get it}\label{wheretoget}
+Step 2. You may want to download a soundfont file and have it handy
+for when we start QSYNTH. Although the FLUIDSYNTH package includes a
+soundfont library file, it isn't particularly suited for the replay of
+the MIDI composition 'jazz.mid' mentioned below. Check the resources
+section in the Appendix of this manual for places to download soundfont
+library files. You will also ultimately need a MIDI file to load into Jazz++
+so there's something to play, or else move on to creating your own MIDI
+composition, but for the purposes of this Quickstart guide you can use
+the 'jazz.mid' file contained in the Jazz++ source distribution. A general
+purpose GM/GS soundfont library file is probably best suited for replaying
+the jazz.mid file.
-For latest updates on software from {\em sourceforge}, please look at the
-JAZZ++ homepage at
-\begin{indented}{2cm}
-\urlref{http://jazzplusplus.sourceforge.net}{http://jazzplusplus.sourceforge.net}
-\end{indented}
+Step 3. The first stage of 'turning your softsynth on', is to start the
+JACK sound server using the QJACKCTL frontend GUI you installed in the
+beginning stages here. Look in your system's Multimedia or Sound menu
+areas for the QJACKCTL link and launch the program. If all has gone well
+this far, QJACKCTL will present you with it's control GUI but the JACK
+server itself is not yet started.
-You are welcome to join the JAZZ++ mailing lists. In order to cut down on the
-amount of spam on the list, you must subscribe to post to any of the lists.
-There are three mailing lists. The first is a devoted to JAZZ++ users. To
-subscribe, visit
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qjack-stopped.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qjack-stopped.png}}%
+\caption{Main Control GUI of QJACKCTL}%
+\end{figure}%
-\begin{indented}{2cm}
-\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}
-\end{indented}
-The second is devoted to developers. To subscribe visit
+Next thing to do, is to click on the 'Start' button to launch the
+(background) JACK sound server, and after a moment or two the QJACKCTL
+control panel GUI should look like this ;
-\begin{indented}{2cm}
-\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}
-\end{indented}
-The third list contains messages generated by developers when they commit
-documentation, web content, or code to the JAZZ++ sunversion repository.
-To subscribe visit
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qjack-running.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qjack-running.png}}%
+\caption{Main Control GUI of QJACKCTL}%
+\end{figure}%
-\begin{indented}{2cm}
-\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}
-\end{indented}
-We'd be happy to receive your bug reports (well, somehow) or success
-stories. And - of course - you are welcome to contribute to the JAZZ++
-project by sending code, suggestions, ..., or corrections for this
-manual.
+Now click on the 'Connect' button - this should open the connections
+panel GUI. Click on the 'MIDI' connection tab - it should currently
+look something like this ;
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qjack-connect-win-0.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qjack-connect-win-0.png}}%
+\caption{Connection GUI of QJACKCTL}%
+\end{figure}%
-\section{Copyright}\label{copyright}
+This all should have completed sucessfully and without generating any
+errors or warnings. If this is the case, move onto the next step.
-The JAZZ++ MIDI Sequencer is copyright (C) 1994-2000 Andreas Voss and
-Per Sigmond, all rights reserved.
-JAZZ++ program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or
-(at your option) any later version.
+If however you have encountered errors or problems here, you will have to
+fix them first before continuing -- JACK is an essential part of the
+entire setup, and must be up and running properly before anything else
+will work here. Look in the FAQ area of the manual Appendix for help with
+common JACK/QJACKCTL errors and warnings. Once you get it all fixed, come
+back and continue on here.
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-GNU General Public License for more details.
-You should have received a copy of the GNU General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+Step 4. The next step, is to start the actual synthesizer part itself.
+In this example we are using the FLUIDSYNTH software synthesizer, which
+we control and configure using the QSYNTH frontend GUI you installed in
+the beginning stages here. Look in your system's Multimedia or Sound menu
+areas for the QSYNTH link and launch the program. If all has gone well this
+far, QSYNTH will start and present you with it's main control GUI but the
+actual softsynth itself will at this stage be unconfigured.
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qsynth-startup.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qsynth-startup.png}}%
+\caption{Main Control GUI of QSYNTH}%
+\end{figure}%
-\section{Installation and Startup}\label{installation}
+Next thing to do, is configure the softsynth itself. Click on the 'Setup'
+button in the main QSYNTH control GUI -- this will display the QSYNTH
+configuration GUI. The first tab is the 'MIDI' setup page ;
-For Windows there is an install utility (run {\tt setup.exe}) which
-mostly automates the installation process.
-For Linux there is a shell script {\tt install-jazz} in the
-distribution. You must be logged in as root when running the installation
-script. As a default JAZZ++ will be installed to {\tt /usr/local/jazz},
-this may be changed by editing {\tt install-jazz}. Also you
-must set the environment variable JAZZ to point the jazz directory by
-adding the line:
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-0.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-0.png}}%
+\caption{The MIDI Configuration GUI of QSYNTH}%
+\end{figure}%
-{\tt export JAZZ=/usr/local/home}
-to your .profile or .bashrc. Please refer to the file
-{\tt install.txt} which contains up-to-date instructions.
-On startup JAZZ++ looks for its configuration files
-\begin{enumerate}
-\item in the current directory
-\item in the home directory (where the environment variable HOME points to)
-\item in the directory where the environment variable JAZZ points to
-\item in the directory from where JAZZ++ itself was started.
-\end{enumerate}
-The main configuration file is named {\tt jazz.cfg}.
-This file also contains pointers to other configuration files {\tt (*.jzi)}
-present in the same directory.
-Then JAZZ++ searches for a song named {\tt jazz.mid} in the current directory
-and loads it - if found. This song may contain default settings for your
-midi equipment.
+Your setup should look something closely akin to the above for using
+a softsynth on Linux. Once you are happy with the settings, click on
+the 'Audio' tab to display the Audio setup page ;
-\subsection{Command line options (Unix only)}
-Command line options (in any order):
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-1.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-1.png}}%
+\caption{The Audio Configuration GUI of QSYNTH}%
+\end{figure}%
-\begin{itemize}
-\item {\tt jazz -h} -- Print help text
-\item {\tt jazz -v} -- Print help text
-\item {\tt jazz -f filename} -- Input midi file
-\item {\tt jazz -trackwin xpos ypos [width height]} -- Position/size of main window
-\item {\tt jazz -pianowin xpos ypos [width height]} -- Position/size of piano roll window
-\end{itemize}
-\section{Acknowledgements}
+Your setup should look something closely akin to the above for using
+a softsynth on Linux using JACK as your audio output driver. This is
+the most basic setup example - more complex environments are possible.
+Once you are happy with the settings, click on the 'Soundfonts' tab to
+display the Soundfont setup page - it should currently be empty ;
-JAZZ++ is based on the work of countless other people who have have made
-their software freely available. Beside all the people who made Linux,
-GNU and X11 possible, we'd like to mention
-\begin{itemize}
-\item {\em Hannu Savolainen} for writing all these excellent midi drivers, so
-JAZZ++ can talk to nearly every midi card on Linux.
-\item {\em Julian Smart} who wrote the free, portable GUI library
-wxwin, so JAZZ++ runs with XView, Motif and MS-Windows.
-\end{itemize}
+\begin{figure}%
+\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-2.png}}%
+\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-2.png}}%
+\caption{The Soundfont Configuration GUI of QSYNTH}%
+\end{figure}%
-We would also like to thank Henrik Seidel and Stefan Nitschke for code
-contributions.
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+This is a most important part of the softsynth setup - it is here you
+define exactly what sounds (musical instruments, drum kits, sound FX,
+synthesizer sound presets, etc, etc) your softsynth will be able to produce,
+and how you do that is by loading (one or more) soundfont library files
+into the softsynth itself, using this setup page. Click on the 'Open'
+button, and a familiar looking 'open files' dialog window will appear ;
+
+
+
+\begin{figure}%
+\latexonl...
[truncated message content] |
