Menu
▾
▴
jazzplusplus-updates
|
From: <pst...@us...> - 2008-05-20 04:40:07
|
Revision: 547
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=547&view=rev
Author: pstieber
Date: 2008-05-19 21:39:55 -0700 (Mon, 19 May 2008)
Log Message:
-----------
Applied a patch provided by Donald B. Moore.
1. Replaced reference to old user-list email address with current
source forge user-list address.
2. Changed some words in the opening paragraph.
3. Moved Linux/MIDI treatise out of htdocs and into the
jazz.tex file as an abstract.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-05-19 05:56:49 UTC (rev 546)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-05-20 04:39:55 UTC (rev 547)
@@ -16,9 +16,9 @@
\chapter{Introduction}\label{introduction}
-JAZZ++ is a full size 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
+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++ has two main windows; one
@@ -75,6 +75,172 @@
application allowing the sequencer/editor and the midi-driver to run on
separate computers. The native driver has better support for the MPU-401
than the JAZZ++/OSS solution (e.g. support for external timing source).
+\item *New*
+ Introduction
+
+Years ago when the Jazz++ project first came to my attention,
+using it with Linux on the PC was a much different proposition to
+what is possible today on this platform/OS. Although it would be
+entirely possible to create a MIDI score with jazz, (in the same way
+this text is being produced with a text-editor), the whole point of
+the exercise would be to compose a MIDI score you could actually hear.
+
+
+Back then with Linux, making sound via MIDI applications meant having
+MIDI *hardware*. This may have taken the form of a MIDI adapter plugged
+in the PC's serial port or soundcard gameport (in MPU-401 mode), with a real
+world MIDI instrument(s) attached to that, or else a MIDI capable soundcard
+with a hardware based MIDI sound synthesis chip to make the actual sound.
+(so called 'MIDI/synth' capable soundcards)
+In that latter case, the soundcard necessarily had to be supported
+by Linux drivers, and in that respect these drivers were more than
+likely using the now deprecated 'OSS' sound system modules.
+
+Things have changed. The x86 based hardwares have become faster and
+cheaper, Linux has grown and matured as an operating system, and
+likewise Free software has multiplied and proliferated around the world
+giving rise to the creation of a great many new software applications.
+Along the way, the venerable 'OSS' sound system drivers were replaced
+with the 'Advanced Linux Sound Architecture' (ALSA) drivers and API.
+
+The result of these many advances and changes over time, means Linux
+users are no longer constrained by the need of having actual MIDI
+capable hardware or a MIDI/synth capable soundcard, to obtain good sound
+production with MIDI applications like Jazz++. Instead of having one
+or more hardware sound synthesis chips (be they on a soundcard or
+in a MIDI musical instrument) to produce the sound(s), we can now
+use a software application to achieve the same ends, and many folks
+loosely refer to these software applications as being 'softsynths'.
+
+
+For many years now, users with Windows on their PC have had a distinct
+advantage over Linux users on the PC, because virtually every sound
+card (and/or onboard sound chip) typically ships with proprietary
+Windows drivers that enable the use of that hardware as a 'softsynth' in
+conjunction with the underlying Windows sound API supports. In
+effect, Windows users could come to the website, download Jazz++ and
+install it, and be making noise in under 2 minutes with very little
+or no effort. If only users of other platforms/OS' could have it this
+easy - hopefully this documentation will help bridge the (Linux) gap.
+
+
+
+ Hardware based sound synthesis and Linux on the x86 PC
+
+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.
+
+However, at this point documentation detailing the configuration and
+use of such soundcard hardware with Linux and Jazz++ will be the
+focus of future efforts here. Why? Simply because the majority of
+people out there on the x86 PC don't have a hardware MIDI/synth soundcard
+as part of their computer's hardware. They need to know how to setup a
+'softsynth' in Linux if they don't have this sort of soundcard or
+any 'real' MIDI hardware to hear Jazz++ with...and believe me, this
+will be 80% or more of people out there using Linux and the PC.
+
+
+I will however include a section here soon listing all the sound
+cards of this type that are currently supported under Linux, and
+later document configuration details here for use with Jazz++.
+
+
+
+ Software based sound synthesis and Linux on the x86 PC
+
+This area of the documentation will grow over time. There is a lot
+that can be documented here now with Linux, however at this early
+stage of Jazz++'s development, it's more important for potential
+users and testers of the Jazz++ code to have some form of consistant
+MIDI 'test-bed' to prove and test Jazz++ itself on linux.
+
+Although this isn't 'set in stone', the Jazz++ developers have
+been using a softsynth setup in Linux as I describe below, which
+uses JACK, FLUIDSYNTH and QSYNTH. A similar setup should also
+work on the Mac running Mac OSX.
+
+Essentially, -any- ALSA based, MIDI capable softsynth setup
+should work with Jazz++, and I've already tested a few that seem
+to work fine. However, more consistant and comparable results of
+testing, will be observed using the same softsynth 'kit' as the
+Jazz++ developers do, and this is why documentation of this
+softsynth setup comes first.
+
+
+
+ Overview of a typical Linux softsynth setup
+
+\item Abstract:
+
+Softsynth setups in Linux are comprised of a number of
+software applications which work together to form a virtual
+machine that emulates hardware based MIDI/synth devices. The
+so formed virtual machine can be easily broken down into it's
+individual parts, to better understand how the components
+'expose' themselves to the user ;
+
+\item The ALSA part -- forms virtual MIDI and real audio paths for the
+other parts of the virtual machine to communicate across. Allows
+PCM data rendered by the virtual machine to be realized as an
+analogue audio signal at the line outputs of the soundcard hardware.
+
+\item The JACK part -- a low-latency sound server. Forms both a virtual
+MIDI patch-bay and a virtual audio patch-bay to control and
+define how the virtual machine parts interconnect with and across
+the virtual and real machine paths formed by the ALSA part.
+
+\item The FLUIDSYNTH part -- the virtual MIDI synthesizer itself. It
+accepts valid MIDI data as input, and renders that data into
+PCM data output, as determined by sound/instrument data contained
+in a 'SoundFont' file.
+
+\item The QSYNTH part -- this forms the virtual control panel of the
+virtual synthesizer part. Essentially, this comprises a GUI to
+easily allow the user to change/control the virtual synthesizer
+itself, add/remove SoundFont files, define bank settings, and
+adjust other working parameters of the virtual synthesizer itself.
+
+Additionally, the QJACKCTL software provides a GUI visualization
+of the virtual MIDI/audio patch-bays formed by the JACK part,
+allowing the user a quick and easy way to 'hook it all up' as it
+were, in any particular configuration they desire.
+
+For the sake of accuracy with this overview, it is worth noting
+that Jazz++ itself is a virtual machine - it is a software emulation
+of -hardware- based MIDI sequencers that were in common use years
+ago. Jazz++ is of course much more capable than these old hardware
+sequencers I speak of, which in their day were little more than
+'drum machines' triggering sound events on a MIDI or otherwise
+connected 'tip-and-ring patch cord configured' analogue synthesizer.
+
+Also note here, the virtual machine softsynth described in the
+overview above, lacks one obvious component - the INPUT part.
+It is basically a virtual MIDI synthesizer with all the bells,
+knobs and whistles, but without a keyboard or anything else
+'driving' it. Jazz++ is that part. The MIDI data produced by Jazz++
+is that MIDI input data the FLUIDSYNTH part accepts.
+
+Jazz++ can itself accept valid MIDI data from either the virtual
+and/or 'real world' MIDI domains. This means, you can connect
+a real MIDI synthesizer keyboard to Jazz++ as a MIDI data INPUT
+part, and record notes played on that with Jazz++. Equally, you
+could connect the same external MIDI keyboard as an INPUT part
+to FLUIDSYNTH and use the virtual MIDI softsynth to replay the
+notes you are playing instead of the synthesizer's own hardware kit.
+
+Finally, there are other virtual machines in software that
+can be used as valid MIDI data INPUT parts here, such as the
+program VKEYBD, which is a virtual onscreen MIDI keyboard GUI
+with keys you click on with your mouse -- all these MIDI devices
+be they virtual machines or not, can interact and interconnect
+with each other, and thus possibly form very complex MIDI
+sound production environments that traverse and inter-operate
+across the software virtual and real hardware MIDI domains.
+
+\item Practical:
+
+Still work in progress, come back soon!!
\end{itemize}
\subsection{Windows operating systems}
@@ -104,7 +270,7 @@
You are welcome to join the JAZZ++ mailing list by sending mail to
\begin{indented}{2cm}
-{\tt jaz...@hi...}
+{\tt jaz...@li...}
\end{indented}
with subject-field containing {\tt subscribe}.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-05-22 14:12:47
|
Revision: 555
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=555&view=rev
Author: pstieber
Date: 2008-05-22 07:12:39 -0700 (Thu, 22 May 2008)
Log Message:
-----------
Applied a slightly modified version of a patch provided by Donald B. Moore.
Donald's Changes:
1. Made many corrections, some text moved/reordered.
2. Made layout alignment and formatting corrections.
3. Added general section about MIDI/time/personal computers.
4. Filled out section on MIDI/synth soundcards+linux (preliminary).
5. Cleaned up & clarified some areas regarding soft-synths + Linux.
6. Added URL references and text to help people with linux/ALSA setup.
Pete's changes:
1. Removed whit space from the ends of lines.
2. Reformatted links in the document.
3. Updated the mailing list content.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-05-22 05:42:06 UTC (rev 554)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-05-22 14:12:39 UTC (rev 555)
@@ -16,8 +16,8 @@
\chapter{Introduction}\label{introduction}
-JAZZ++ is a fully featured MIDI sequencer with audio support. In addition to
-basic sequencer functions like record and play, JAZZ++ provides many edit
+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.
@@ -49,23 +49,143 @@
\section{System requirements}\label{requirements}
\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]
+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."
+
+
+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.
+
+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.
+
+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.
+
+
+*NEW*
+
+\item MIDI, Time and the Personal Computer
+
+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.
+
+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.
+
+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.
+
+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.
+
+
+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.
+
\subsection{Linux operating systems}
+[ed: This part, down to my out mark, should probably go]
+
The device-independent part of JAZZ++ (the sequencer / editor part) is known
to run on Linux, Sun-OS4 and Solaris2 systems, but should compile and run
(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:
-\begin{itemize}
+
\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
interfacing OSS has only been tested on Linux platforms.
@@ -75,174 +195,248 @@
application allowing the sequencer/editor and the midi-driver to run on
separate computers. The native driver has better support for the MPU-401
than the JAZZ++/OSS solution (e.g. support for external timing source).
+
+[ed: and be replaced with something more current...ie; if it still
+works on Sun-OS4 and Solaris2 systems currently is unknown, USS/lite
+and voxware..?..and I thought mpu-401 was dinosaured? I'll get some
+clarity before I deal with the section above. *MARK* ]
+
+\begin{itemize}
+
\item *New*
- Introduction
-
-Years ago when the Jazz++ project first came to my attention,
-using it with Linux on the PC was a much different proposition to
-what is possible today on this platform/OS. Although it would be
-entirely possible to create a MIDI score with jazz, (in the same way
-this text is being produced with a text-editor), the whole point of
-the exercise would be to compose a MIDI score you could actually hear.
-
-
-Back then with Linux, making sound via MIDI applications meant having
-MIDI *hardware*. This may have taken the form of a MIDI adapter plugged
-in the PC's serial port or soundcard gameport (in MPU-401 mode), with a real
-world MIDI instrument(s) attached to that, or else a MIDI capable soundcard
-with a hardware based MIDI sound synthesis chip to make the actual sound.
-(so called 'MIDI/synth' capable soundcards)
-In that latter case, the soundcard necessarily had to be supported
-by Linux drivers, and in that respect these drivers were more than
-likely using the now deprecated 'OSS' sound system modules.
-
-Things have changed. The x86 based hardwares have become faster and
-cheaper, Linux has grown and matured as an operating system, and
-likewise Free software has multiplied and proliferated around the world
-giving rise to the creation of a great many new software applications.
-Along the way, the venerable 'OSS' sound system drivers were replaced
-with the 'Advanced Linux Sound Architecture' (ALSA) drivers and API.
-
-The result of these many advances and changes over time, means Linux
-users are no longer constrained by the need of having actual MIDI
-capable hardware or a MIDI/synth capable soundcard, to obtain good sound
-production with MIDI applications like Jazz++. Instead of having one
-or more hardware sound synthesis chips (be they on a soundcard or
-in a MIDI musical instrument) to produce the sound(s), we can now
-use a software application to achieve the same ends, and many folks
-loosely refer to these software applications as being 'softsynths'.
+\end{itemize}
-For many years now, users with Windows on their PC have had a distinct
-advantage over Linux users on the PC, because virtually every sound
-card (and/or onboard sound chip) typically ships with proprietary
-Windows drivers that enable the use of that hardware as a 'softsynth' in
-conjunction with the underlying Windows sound API supports. In
-effect, Windows users could come to the website, download Jazz++ and
-install it, and be making noise in under 2 minutes with very little
-or no effort. If only users of other platforms/OS' could have it this
-easy - hopefully this documentation will help bridge the (Linux) gap.
-
-
- Hardware based sound synthesis and Linux on the x86 PC
+Introduction
-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.
-
-However, at this point documentation detailing the configuration and
-use of such soundcard hardware with Linux and Jazz++ will be the
-focus of future efforts here. Why? Simply because the majority of
-people out there on the x86 PC don't have a hardware MIDI/synth soundcard
-as part of their computer's hardware. They need to know how to setup a
-'softsynth' in Linux if they don't have this sort of soundcard or
-any 'real' MIDI hardware to hear Jazz++ with...and believe me, this
-will be 80% or more of people out there using Linux and the PC.
-
+Years ago when the Jazz++ project first came to my attention,
+using it with Linux on the PC was a much different proposition to
+what is possible today on this platform/OS. Although it would be
+entirely possible to create a MIDI score with jazz, (in the same way
+this text is being produced with a text-editor), the whole point of
+the exercise would be to compose a MIDI score you could actually hear.
-I will however include a section here soon listing all the sound
-cards of this type that are currently supported under Linux, and
-later document configuration details here for use with Jazz++.
-
+Back then with Linux, making sound via MIDI applications meant having
+MIDI *hardware*. This may have taken the form of a MIDI adapter plugged
+in the PC's serial port or soundcard gameport (in MPU-401 mode), with a real
+world MIDI instrument(s) attached to that, or else a MIDI capable soundcard
+with a hardware based MIDI sound synthesis chip to make the actual sound.
+(so called 'MIDI/synth' capable soundcards) In that latter case, the
+soundcard necessarily had to be supported by Linux drivers, and in that
+respect these drivers were more than likely using the now deprecated 'OSS'
+sound system modules.
+Things have changed. The x86 based hardwares have become faster and
+cheaper, Linux has grown and matured as an operating system, and
+likewise Free software has multiplied and proliferated around the world
+giving rise to the creation of a great many new software applications.
+Along the way, the venerable 'OSS' sound system drivers were replaced
+with the 'Advanced Linux Sound Architecture' (ALSA) drivers and API.
- Software based sound synthesis and Linux on the x86 PC
-
-This area of the documentation will grow over time. There is a lot
-that can be documented here now with Linux, however at this early
-stage of Jazz++'s development, it's more important for potential
-users and testers of the Jazz++ code to have some form of consistant
-MIDI 'test-bed' to prove and test Jazz++ itself on linux.
+The result of these many advances and changes over time, means Linux
+users are no longer constrained by the need of having actual MIDI
+capable hardware or a MIDI/synth capable soundcard, to obtain good sound
+production with MIDI applications like Jazz++. Instead of having one
+or more hardware sound synthesis chips (be they on a soundcard or
+in a MIDI musical instrument) to produce the sound(s), we can now
+use a software application to achieve the same ends, and many folks
+loosely refer to these software applications as being 'softsynths'.
-Although this isn't 'set in stone', the Jazz++ developers have
-been using a softsynth setup in Linux as I describe below, which
-uses JACK, FLUIDSYNTH and QSYNTH. A similar setup should also
-work on the Mac running Mac OSX.
-
-Essentially, -any- ALSA based, MIDI capable softsynth setup
-should work with Jazz++, and I've already tested a few that seem
-to work fine. However, more consistant and comparable results of
-testing, will be observed using the same softsynth 'kit' as the
-Jazz++ developers do, and this is why documentation of this
-softsynth setup comes first.
+For many years now, users with Windows on their PC have had a distinct
+advantage over Linux users on the PC, because virtually every sound
+card (and/or 'onboard' sound chip) typically ships with proprietary
+Windows drivers that enable the use of that hardware as a 'softsynth' in
+conjunction with the underlying Windows sound API supports. In effect,
+Windows users could come to the website, download Jazz++ and install it,
+and be making noise in under 2 minutes with very little or no effort. If
+only users of other platforms/OS' could have it this easy - hopefully
+this documentation will help bridge the gap, when using Jazz++ on this
+platform with MIDI softsynth implementations.
-
- Overview of a typical Linux softsynth setup
-\item Abstract:
-
-Softsynth setups in Linux are comprised of a number of
-software applications which work together to form a virtual
-machine that emulates hardware based MIDI/synth devices. The
-so formed virtual machine can be easily broken down into it's
-individual parts, to better understand how the components
-'expose' themselves to the user ;
-
-\item The ALSA part -- forms virtual MIDI and real audio paths for the
-other parts of the virtual machine to communicate across. Allows
-PCM data rendered by the virtual machine to be realized as an
-analogue audio signal at the line outputs of the soundcard hardware.
-\item The JACK part -- a low-latency sound server. Forms both a virtual
-MIDI patch-bay and a virtual audio patch-bay to control and
-define how the virtual machine parts interconnect with and across
-the virtual and real machine paths formed by the ALSA part.
+\begin{itemize}
+\item 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.
-\item The FLUIDSYNTH part -- the virtual MIDI synthesizer itself. It
-accepts valid MIDI data as input, and renders that data into
-PCM data output, as determined by sound/instrument data contained
+One of the main benefits of using MIDI/synth based soundcards (and
+this is true for all platforms), is that it removes the system overhead
+of having a softsynth running -- the MIDI data output of Jazz++ is sent
+directly to the hardware MIDI/synth chip on the soundcard, and it takes
+care of generating the actual sound (and sound data) itself. This allows
+the kernel to be closer to 'real time' when using Jazz++, because the
+system CPU isn't having to 'play' the sound, and render that sound, all
+at the same time. A good analogy, would be to compare all this to the
+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.
+
+Adding a dedicated MIDI/synth soundcard to your system helps for
+exactly the same reasons here - it frees up your system CPU so it
+can do other tasks. In Linux, drivers for more than a few of these types of
+MIDI/synth soundcards are already available, and are a standard part
+of the linux kernel tree. Most linux distributions include so called
+'hardware detection' softwares, which should automatically discover
+your MIDI/synth soundcard (if supported), and configure your system's
+ALSA drivers accordingly. Sometimes these routines do not detect certain
+hardware cards correctly (or at all) in some situations, however it is
+beyond the scope of the Jazz++ manual to help people with problems of this
+nature.
+
+The correct place to get help with specific ALSA / soundcard related
+problems, can be found by visiting the ALSA website at ;
+
+\urlref{http://www.alsa-project.org/}{http://www.alsa-project.org/}
+
+The lastest 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 ;
+
+alsa-driver-1.0.1x/doc/SOUNDCARDS
+
+There you can see if your MIDI/synth soundcard is currently supported
+under ALSA and linux. Some MIDI/synth soundcards require firmware being
+loaded before the card will work - most all of these kinds of soundcards
+require some kind of helper application called a 'loader' to copy various
+instrument files and data (for example 'soundfont' files) into the working
+RAM of the MIDI/synth chip. Documentation regarding these things and help
+with configuring ALSA itself can be found in the same alsa-driver archive ;
+
+alsa-driver-1.0.1x/alsa-kernel/Documentation/
+
+
+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}
+
+Once you have your MIDI/synth soundcard up and running, it will appear
+in Jazz++ configuration dialogs just like any other MIDI device connected
+to the computer running Jazz++. Using a hardware based MIDI/synth soundcard,
+is very much like using a software based 'softsynth' as described below -
+you still have to decide which soundfonts to use, and which bank to load them
+into. Hardware or software, they are both MIDI instruments, and share very
+common ways of getting things done at this level.
+
+
+
+
+\begin{itemize}
+\item 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.
+
+In the early stages of the current Jazz++'s revitalization, developers,
+users and testers alike of the Jazz++ source code used softsynths. One
+of the softsynth setups used by the Jazz++ developers and testers in Linux,
+is as I describe below, which uses JACK, FLUIDSYNTH and QSYNTH. A similar
+setup should also work on the Mac running Mac OSX.
+
+Essentially, -any- ALSA based, MIDI capable softsynth setup should work
+with Jazz++ in linux. I've already tested a few that seem to work fine.
+However, it is useful to know how to setup the same softsynth kit that
+the Jazz++ developers use for testing and improving the Jazz++ code itself,
+and this is why documentation of this softsynth setup comes first.
+
+\item Overview of a typical Linux softsynth setup
+
+Abstract:
+
+Softsynth setups in Linux are comprised of a number of
+software applications which work together to form a virtual
+machine that emulates hardware based MIDI/synth devices. The
+so formed virtual machine can be easily broken down into it's
+individual parts, to better understand how the components
+'expose' themselves to the user ;
+
+\item The ALSA part -- forms virtual MIDI and real audio paths for the
+other parts of the virtual machine to communicate across. Allows
+PCM data rendered by the virtual machine to be realized as an
+analogue audio signal at the line outputs of the soundcard hardware.
+
+\item The JACK part -- a low-latency sound server. Forms both a virtual
+MIDI patch-bay and a virtual audio patch-bay to control and
+define how the virtual machine parts interconnect with and across
+the virtual and real machine paths formed by the ALSA part.
+
+\item The FLUIDSYNTH part -- the virtual MIDI synthesizer itself. It
+accepts valid MIDI data as input, and renders that data into
+PCM data output, as determined by sound/instrument data contained
in a 'SoundFont' file.
-\item The QSYNTH part -- this forms the virtual control panel of the
-virtual synthesizer part. Essentially, this comprises a GUI to
-easily allow the user to change/control the virtual synthesizer
-itself, add/remove SoundFont files, define bank settings, and
-adjust other working parameters of the virtual synthesizer itself.
-
-Additionally, the QJACKCTL software provides a GUI visualization
-of the virtual MIDI/audio patch-bays formed by the JACK part,
-allowing the user a quick and easy way to 'hook it all up' as it
-were, in any particular configuration they desire.
-
-For the sake of accuracy with this overview, it is worth noting
-that Jazz++ itself is a virtual machine - it is a software emulation
-of -hardware- based MIDI sequencers that were in common use years
-ago. Jazz++ is of course much more capable than these old hardware
-sequencers I speak of, which in their day were little more than
-'drum machines' triggering sound events on a MIDI or otherwise
-connected 'tip-and-ring patch cord configured' analogue synthesizer.
-
-Also note here, the virtual machine softsynth described in the
-overview above, lacks one obvious component - the INPUT part.
-It is basically a virtual MIDI synthesizer with all the bells,
-knobs and whistles, but without a keyboard or anything else
-'driving' it. Jazz++ is that part. The MIDI data produced by Jazz++
-is that MIDI input data the FLUIDSYNTH part accepts.
-
-Jazz++ can itself accept valid MIDI data from either the virtual
-and/or 'real world' MIDI domains. This means, you can connect
-a real MIDI synthesizer keyboard to Jazz++ as a MIDI data INPUT
-part, and record notes played on that with Jazz++. Equally, you
-could connect the same external MIDI keyboard as an INPUT part
-to FLUIDSYNTH and use the virtual MIDI softsynth to replay the
-notes you are playing instead of the synthesizer's own hardware kit.
+\item The QSYNTH part -- this forms the virtual control panel of the
+virtual synthesizer part. Essentially, this comprises a GUI to
+easily allow the user to change/control the virtual synthesizer
+itself, add/remove SoundFont files, define bank settings, and
+adjust other working parameters of the virtual synthesizer itself.
-Finally, there are other virtual machines in software that
-can be used as valid MIDI data INPUT parts here, such as the
-program VKEYBD, which is a virtual onscreen MIDI keyboard GUI
-with keys you click on with your mouse -- all these MIDI devices
-be they virtual machines or not, can interact and interconnect
-with each other, and thus possibly form very complex MIDI
-sound production environments that traverse and inter-operate
+Additionally, the QJACKCTL software provides a GUI visualization
+of the virtual MIDI/audio patch-bays formed by the JACK part,
+allowing the user a quick and easy way to 'hook it all up' as it
+were, in any particular configuration they desire.
+
+For the sake of accuracy with this overview, it is worth noting
+that Jazz++ itself is a virtual machine - it is a software emulation
+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
+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.
+
+Also note here, the virtual machine softsynth described in the
+overview above, lacks one obvious component - the INPUT part.
+It is basically a virtual MIDI synthesizer with all the bells,
+knobs and whistles, but without a keyboard or anything else
+'driving' it. Jazz++ is that part. The MIDI data produced by Jazz++
+is that MIDI input data the FLUIDSYNTH part accepts.
+
+Jazz++ can itself accept valid MIDI data from either the virtual
+and/or 'real world' MIDI domains. This means, you can connect
+a real MIDI synthesizer keyboard to Jazz++ as a MIDI data INPUT
+part, and record notes played on that with Jazz++. Equally, you
+could connect the same external MIDI keyboard as an INPUT part
+to FLUIDSYNTH and use the virtual MIDI softsynth to replay the
+notes you are playing instead of the synthesizer's own hardware
+kit. Other combinations are possible as well.
+
+Finally, there are other virtual machines in software that
+can be used as valid MIDI data INPUT parts here, such as the
+program VKEYBD, which is a virtual onscreen MIDI keyboard GUI
+with keys you click on with your mouse -- all these MIDI devices
+be they virtual machines or not, can interact and interconnect
+with each other, and thus possibly form very complex MIDI
+sound production environments that traverse and inter-operate
across the software virtual and real hardware MIDI domains.
\item Practical:
+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
+you use, (and what release version that might be), also dictates
+just how easy or difficult this process might be to complete.
+
+If you have any problems with the following instructions,
+please check the documentation Appendix for possible solutions
+relative to the Linux distribution you might be using.
+
+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.
+
Still work in progress, come back soon!!
-\end{itemize}
+
\subsection{Windows operating systems}
JAZZ++ supports the windows MIDI / audio driver interface. A driver for your
@@ -264,17 +458,32 @@
JAZZ++ homepage at
\begin{indented}{2cm}
-{\tt http://jazzplusplus.sourceforge.net}
+\urlref{http://jazzplusplus.sourceforge.net}{http://jazzplusplus.sourceforge.net}
\end{indented}
-You are welcome to join the JAZZ++ mailing list by sending mail to
+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{indented}{2cm}
-{\tt jaz...@li...}
+\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}
\end{indented}
-with subject-field containing {\tt subscribe}.
+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++ sunversion 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 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
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-05-24 18:53:43
|
Revision: 561
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=561&view=rev
Author: pstieber
Date: 2008-05-24 11:53:41 -0700 (Sat, 24 May 2008)
Log Message:
-----------
Applied a slightly modified version of a patch provided by Donald B Moore.
Donald's changes:
1. Added a soundfont section.
2. Added common system considerations (CPU, RAM, usage tips).
3. Added an appendix subsection (currently empty).
4. made some formatting corrections, text changed/rearranged in some places.
Pete's changes:
1. Removed white space at the ends of lines and wrapped some lines that
were greater than 80 columns.
2. Changed linux to Linux.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-05-24 18:43:23 UTC (rev 560)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-05-24 18:53:41 UTC (rev 561)
@@ -89,13 +89,13 @@
and/or other now affordable add-on sound/MIDI hardware options.
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.
+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.
-
*NEW*
\item MIDI, Time and the Personal Computer
@@ -167,7 +167,37 @@
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 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'.
+
+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.
+
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
@@ -175,6 +205,86 @@
hardware technologies and various 'software synthesizer' MIDI
programs available to the user today.
+\subsection{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.
+
+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,
+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 ;
+
+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.
+
+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.
+
+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 ;
+
+[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.
+
+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.
+
\subsection{Linux operating systems}
[ed: This part, down to my out mark, should probably go]
@@ -281,7 +391,7 @@
exactly the same reasons here - it frees up your system CPU so it
can do other tasks. In Linux, drivers for more than a few of these types of
MIDI/synth soundcards are already available, and are a standard part
-of the linux kernel tree. Most linux distributions include so called
+of the Linux kernel tree. Most Linux distributions include so called
'hardware detection' softwares, which should automatically discover
your MIDI/synth soundcard (if supported), and configure your system's
ALSA drivers accordingly. Sometimes these routines do not detect certain
@@ -301,7 +411,7 @@
alsa-driver-1.0.1x/doc/SOUNDCARDS
There you can see if your MIDI/synth soundcard is currently supported
-under ALSA and linux. Some MIDI/synth soundcards require firmware being
+under ALSA and Linux. Some MIDI/synth soundcards require firmware being
loaded before the card will work - most all of these kinds of soundcards
require some kind of helper application called a 'loader' to copy various
instrument files and data (for example 'soundfont' files) into the working
@@ -311,7 +421,7 @@
alsa-driver-1.0.1x/alsa-kernel/Documentation/
-Another good repository of current knowledge regarding linux sound drivers
+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}
@@ -340,7 +450,7 @@
setup should also work on the Mac running Mac OSX.
Essentially, -any- ALSA based, MIDI capable softsynth setup should work
-with Jazz++ in linux. I've already tested a few that seem to work fine.
+with Jazz++ in Linux. I've already tested a few that seem to work fine.
However, it is useful to know how to setup the same softsynth kit that
the Jazz++ developers use for testing and improving the Jazz++ code itself,
and this is why documentation of this softsynth setup comes first.
@@ -3051,5 +3161,11 @@
\helpref{Piano Window}{pianowin}. Scroll
up and down until you find the defined samples.
+\subsection{Appendix}
+\item Appendix
+
+The appendix has not been appended yet, come back soon!
+
+
\end{document}
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
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] |
|
From: <pst...@us...> - 2008-06-11 15:02:01
|
Revision: 595
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=595&view=rev
Author: pstieber
Date: 2008-06-11 08:01:58 -0700 (Wed, 11 Jun 2008)
Log Message:
-----------
1. Made Donald B. Moore the primary author.
2. Changed the date from May to June.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-10 21:55:33 UTC (rev 594)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-11 15:01:58 UTC (rev 595)
@@ -4,8 +4,9 @@
\parskip=10pt
\parindent=0pt
\title{JAZZ++ MIDI sequencer version 5.0}%
-\author{Pete Stieber $<$pst...@ve...$>$}%
-\date{May 2008}%
+\author{Donald B. Moore $<$db...@ho...$>$\\
+Pete Stieber $<$pst...@gm...$>$}%
+\date{June 2008}%
\makeindex%
\begin{document}%
\maketitle%
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-06-12 20:15:46
|
Revision: 598
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=598&view=rev
Author: pstieber
Date: 2008-06-12 13:15:36 -0700 (Thu, 12 Jun 2008)
Log Message:
-----------
Removed leading forward slash from image path.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-11 15:12:17 UTC (rev 597)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-12 20:15:36 UTC (rev 598)
@@ -919,8 +919,8 @@
server itself is not yet started.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qjack-stopped.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qjack-stopped.png}}%
+\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}%
@@ -931,8 +931,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qjack-running.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qjack-running.png}}%
+\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}%
@@ -942,8 +942,8 @@
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}}%
+\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}%
@@ -970,8 +970,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-startup.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-startup.png}}%
+\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}%
@@ -982,8 +982,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-0.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-0.png}}%
+\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}%
@@ -996,8 +996,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-1.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-1.png}}%
+\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}%
@@ -1011,8 +1011,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-2.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-2.png}}%
+\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}%
@@ -1028,8 +1028,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-3.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-3.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-3.png}}%
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-3.png}}%
\caption{The Soundfont selection GUI of QSYNTH}%
\end{figure}%
@@ -1046,8 +1046,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-4.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-4.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-4.png}}%
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-4.png}}%
\caption{The Soundfont Configuration GUI of QSYNTH}%
\end{figure}
@@ -1062,8 +1062,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qsynth-setup-5.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qsynth-setup-5.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-5.png}}%
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-5.png}}%
\caption{The Settings GUI of QSYNTH}%
\end{figure}
@@ -1076,8 +1076,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/jazz-output-sel-0.png}}%
-\htmlonly{\image{0cm;0cm}{/images/jazz-output-sel-0.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/jazz-output-sel-0.png}}%
+\htmlonly{\image{0cm;0cm}{images/jazz-output-sel-0.png}}%
\caption{The Jazz++ MIDI Output Device selection GUI}%
\end{figure}
@@ -1096,8 +1096,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qjack-connect-win-1.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qjack-connect-win-1.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-1.png}}%
+\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-1.png}}%
\caption{The Audio Connections GUI of QJACKCTL}%
\end{figure}
@@ -1109,8 +1109,8 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{/images/qjack-connect-win-3.png}}%
-\htmlonly{\image{0cm;0cm}{/images/qjack-connect-win-3.png}}%
+\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-3.png}}%
+\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-3.png}}%
\caption{The MIDI Connections GUI of QJACKCTL}%
\end{figure}
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-06-14 11:22:48
|
Revision: 601
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=601&view=rev
Author: pstieber
Date: 2008-06-14 04:22:45 -0700 (Sat, 14 Jun 2008)
Log Message:
-----------
Added backslashes ahead of an underscores so that they will be used literally.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-12 22:48:43 UTC (rev 600)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-14 11:22:45 UTC (rev 601)
@@ -101,7 +101,7 @@
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
+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]
\subsection{Software pre-requisites of JAZZ++}
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-06-14 12:20:32
|
Revision: 602
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=602&view=rev
Author: pstieber
Date: 2008-06-14 05:20:26 -0700 (Sat, 14 Jun 2008)
Log Message:
-----------
1. Removed unmatched \begin{center}.
2. Changed interFace to interface.
3. Wrapped use of \urlref with \htmlonly and added a corresponding latexonly.
4. Removed uses of \item that were missing the corresponding \begin{itemize}
\end{itemize}.
5. Preceeded _ with \ to make LaTeX happy.
6. Put \end{document} back at the end of the file.
7. Changed the includegraphics lines to please LaTeX. The graphics will
probably be poorly positioned/scaled.
The file can be processed with LaTeX.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-14 11:22:45 UTC (rev 601)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-14 12:20:26 UTC (rev 602)
@@ -16,7 +16,6 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\chapter{Introduction}\label{introduction}
-\begin{center}
JAZZ++ is a fully featured software MIDI sequencer with audio support. In
addition to basic sequencer functions like record and play, JAZZ++ provides
@@ -107,14 +106,15 @@
\subsection{Software pre-requisites of JAZZ++}
The current version of JAZZ++ uses the wxWidgets GUI library to create
-the JAZZ++ user interFace. The wxWidgets GUI library, like JAZZ++ itself,
+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 ;
\begin{indented}{2cm}
-\urlref{http://www.wxwidgets.org/}{http://www.wxwidgets.org/}
+\htmlonly{\urlref{http://www.wxwidgets.org/}{http://www.wxwidgets.org/}}
+\latexonly{http://www.wxwidgets.org/}
\end{indented}
The wxWidgets GUI library \underline{must be installed} before installing
@@ -154,8 +154,8 @@
homepage at ;
\begin{indented}{2cm}
-\urlref{http://jazzplusplus.sourceforge.net}{http://jazzplusplus.sourceforge.net
-}
+\htmlonly{\urlref{http://jazzplusplus.sourceforge.net}{http://jazzplusplus.sourceforge.net}}
+\latexonly{http://jazzplusplus.sourceforge.net}
\end{indented}
[ed: make the above link point to downloads page? ]
@@ -164,9 +164,9 @@
'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}
+\begin{indented}{2cm}
+\htmlonly{\urlref{http://jazzplusplus.sourceforge.net/subversion}{http://jazzplusplus.sourceforge.net/subversion}}
+\latexonly{http://jazzplusplus.sourceforge.net/subversion}
\end{indented}
\section{Getting Help with JAZZ++}
@@ -183,7 +183,7 @@
who join and post emails to the JAZZ++ mailing lists adhere to the following
two points of list etiquette ;
-\item{'PCYMTNQREAIYR'}
+'PCYMTNQREAIYR'
\underline{Please Configure Your Mailer To Not Quote Raw E-mail Addresses In
Your Replies.}
@@ -198,7 +198,7 @@
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'}
+'PCYMTWLL'
\underline{Please Configure Your Mailer To Wrap Long Lines.} Some email programs
don't, and
@@ -212,9 +212,9 @@
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}
+\begin{indented}{2cm}
+\htmlonly{\urlref{http://jazzplusplus.sourceforge.net/mailinglist}{http://jazzplusplus.sourceforge.net/mailinglist}}
+\latexonly{http://jazzplusplus.sourceforge.net/mailinglist}
\end{indented}
@@ -224,15 +224,15 @@
[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}
+\htmlonly{\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-user}}
+\latexonly{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}
+\htmlonly{\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}}
+\latexonly{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel}
\end{indented}
The third list contains messages generated by developers when they commit
@@ -240,8 +240,8 @@
To subscribe visit
\begin{indented}{2cm}
-\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}{
-https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}
+\htmlonly{\urlref{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}{https://lists.sourceforge.net/lists/listinfo/jazzplusplus-updates}}
+\latexonly{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
@@ -251,9 +251,9 @@
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}
+\begin{indented}{2cm}
+\htmlonly{\urlref{http://jazzplusplus.sourceforge.net/bugreports}{http://jazzplusplus.sourceforge.net/bugreports}}
+\latexonly{http://jazzplusplus.sourceforge.net/bugreports}
\end{indented}
@@ -388,7 +388,7 @@
\section{Common Considerations when using Jazz++}
-\item CPU and RAM Requirements
+\subsection{CPU and RAM Requirements}
CPU
@@ -441,7 +441,7 @@
*NEW*
-\item MIDI, Time and the Personal Computer
+\subsection{MIDI, Time and the Personal Computer}
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
@@ -499,7 +499,7 @@
achieve optimum performance when using Jazz++ and MIDI on their personal
computing machine.
-\item SoundFonts - what are they, who needs them.
+\subsection{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.
@@ -529,7 +529,7 @@
at Jazz++ think you should try.
-Jazz++ operational tricks ;
+\subsection{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
@@ -561,11 +561,6 @@
own operations.
-
-
-
-
-
\section{Windows operating systems}
@@ -617,6 +612,7 @@
The device-dependent part (midi-driver) currently supports:
+\begin{enumerate}
\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
interfacing OSS has only been tested on Linux platforms.
@@ -626,6 +622,7 @@
application allowing the sequencer/editor and the midi-driver to run on
separate computers. The native driver has better support for the MPU-401
than the JAZZ++/OSS solution (e.g. support for external timing source).
+\end{enumerate}
[ed: and be replaced with something more current...ie; if it still
works on Sun-OS4 and Solaris2 systems currently is unknown, USS/lite
@@ -702,9 +699,8 @@
\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.
@@ -737,7 +733,8 @@
The correct place to get help with specific ALSA / soundcard related
problems, can be found by visiting the ALSA website at ;
-\urlref{http://www.alsa-project.org/}{http://www.alsa-project.org/}
+\htmlonly{\urlref{http://www.alsa-project.org/}{http://www.alsa-project.org/}}
+\latexonly{http://www.alsa-project.org/}
The latest list of ALSA supported MIDI/synth soundcards, is always
available inside the current alsa-driver source tarball available from
@@ -759,8 +756,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
-}
+\htmlonly{\urlref{http://linux-sound.org/drivers.html}{http://linux-sound.org/drivers.html}}
+\latexonly{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
@@ -773,9 +770,8 @@
-\begin{itemize}
\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.
@@ -791,6 +787,8 @@
the Jazz++ developers use for testing and improving the Jazz++ code itself,
and this is why documentation of this softsynth setup comes first.
+\begin{itemize}
+
\item Overview of a typical Linux softsynth setup
Abstract:
@@ -823,6 +821,8 @@
itself, add/remove SoundFont files, define bank settings, and
adjust other working parameters of the virtual synthesizer itself.
+\end{itemize}
+
Additionally, the QJACKCTL software provides a GUI visualization
of the virtual MIDI/audio patch-bays formed by the JACK part,
allowing the user a quick and easy way to 'hook it all up' as it
@@ -863,7 +863,7 @@
sound production environments that traverse and inter-operate
across the software virtual and real hardware MIDI domains.
-\item Practical:
+Practical:
Many people have troubles getting these softsynths installed and
working properly on Linux based systems. The Jazz++ developers
@@ -880,16 +880,16 @@
packages from your Linux distribution's installation discs and/or
on line package repository. Here's how to do it ;
-\item{Setting up a Linux softsynth}
+\subsection{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 ;
-qjackctl_0.2.21-1_i386.deb
+qjackctl\_0.2.21-1\_i386.deb
-qsynth_0.2.5-2_i386.deb
+qsynth\_0.2.5-2\_i386.deb
You should find similarly named packages in your Linux distribution's
package collection. Install these packages, and if installation
@@ -919,7 +919,8 @@
server itself is not yet started.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qjack-stopped.png}}%
+%\latexonly{\includegraphics[scale=0.5]{images/qjack-stopped.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qjack-stopped.png}}%
\htmlonly{\image{0cm;0cm}{images/qjack-stopped.png}}%
\caption{Main Control GUI of QJACKCTL}%
\end{figure}%
@@ -931,7 +932,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qjack-running.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qjack-running.png}}%
\htmlonly{\image{0cm;0cm}{images/qjack-running.png}}%
\caption{Main Control GUI of QJACKCTL}%
\end{figure}%
@@ -942,7 +943,7 @@
look something like this ;
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-0.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qjack-connect-win-0.png}}%
\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-0.png}}%
\caption{Connection GUI of QJACKCTL}%
\end{figure}%
@@ -970,7 +971,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-startup.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-startup.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-startup.png}}%
\caption{Main Control GUI of QSYNTH}%
\end{figure}%
@@ -982,7 +983,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-0.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-0.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-0.png}}%
\caption{The MIDI Configuration GUI of QSYNTH}%
\end{figure}%
@@ -996,7 +997,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-1.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-1.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-1.png}}%
\caption{The Audio Configuration GUI of QSYNTH}%
\end{figure}%
@@ -1011,7 +1012,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-2.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-2.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-2.png}}%
\caption{The Soundfont Configuration GUI of QSYNTH}%
\end{figure}%
@@ -1028,7 +1029,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-3.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-3.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-3.png}}%
\caption{The Soundfont selection GUI of QSYNTH}%
\end{figure}%
@@ -1046,7 +1047,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-4.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-4.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-4.png}}%
\caption{The Soundfont Configuration GUI of QSYNTH}%
\end{figure}
@@ -1062,7 +1063,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-5.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-5.png}}%
\htmlonly{\image{0cm;0cm}{images/qsynth-setup-5.png}}%
\caption{The Settings GUI of QSYNTH}%
\end{figure}
@@ -1076,7 +1077,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/jazz-output-sel-0.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/jazz-output-sel-0.png}}%
\htmlonly{\image{0cm;0cm}{images/jazz-output-sel-0.png}}%
\caption{The Jazz++ MIDI Output Device selection GUI}%
\end{figure}
@@ -1096,7 +1097,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-1.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qjack-connect-win-1.png}}%
\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-1.png}}%
\caption{The Audio Connections GUI of QJACKCTL}%
\end{figure}
@@ -1109,7 +1110,7 @@
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-3.png}}%
+\latexonly{\includegraphics[0,0][2,2]{images/qjack-connect-win-3.png}}%
\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-3.png}}%
\caption{The MIDI Connections GUI of QJACKCTL}%
\end{figure}
@@ -1147,7 +1148,7 @@
bar codes, i.e. every event is shown as a short vertical line.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{trackwin.png}}%
+\latexonly{\includegraphics[0,0][2,2]{trackwin.png}}%
\htmlonly{\image{0cm;0cm}{trackwin.png}}%
\caption{Track window}%
\end{figure}
@@ -1178,7 +1179,11 @@
\end{enumerate}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{twtoolb.png}}%
+\latexonly{\includegraphics[0,0][2,2]{twtoolb.png}}%
+\htmlonly{\image{0cm;0cm}{twtoolb.png}}%
+\caption{Track Window Toolbar}%
+\end{figure}
+
\section{Selecting events}\label{select}
Many functions (e.g 'Delete' from the edit menu) require that you have
@@ -1198,7 +1203,7 @@
disable program-changes (patch). Finally select Delete from Edit-Menu.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{twselect.png}}%
+\latexonly{\includegraphics[0,0][2,2]{twselect.png}}%
\htmlonly{\image{0cm;0cm}{twselect.png}}%
\caption{Selecting events}%
\end{figure}
@@ -1206,7 +1211,7 @@
\section{Record and play}\label{recplay}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{recplay.png}}%
+\latexonly{\includegraphics[0,0][2,2]{recplay.png}}%
\htmlonly{\image{0cm;0cm}{recplay.png}}%
\caption{Record and play}%
\end{figure}
@@ -1246,7 +1251,7 @@
values in steps of 10 bpm.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{speed.png}}%
+\latexonly{\includegraphics[0,0][2,2]{speed.png}}%
\htmlonly{\image{0cm;0cm}{speed.png}}%
\caption{Speed adjustment}%
\end{figure}
@@ -1271,7 +1276,7 @@
display of midi channel and track number.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{trackdef.png}}%
+\latexonly{\includegraphics[0,0][2,2]{trackdef.png}}%
\htmlonly{\image{0cm;0cm}{trackdef.png}}%
\caption{Track defaults}%
\end{figure}
@@ -1286,7 +1291,7 @@
already on the track.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{tracknam.png}}%
+\latexonly{\includegraphics[0,0][2,2]{tracknam.png}}%
\htmlonly{\image{0cm;0cm}{tracknam.png}}%
\caption{Track name, midi channel etc.}%
\end{figure}
@@ -1346,7 +1351,7 @@
\subsection{Replicate}\label{replicate}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{replic.png}}%
+\latexonly{\includegraphics[0,0][2,2]{replic.png}}%
\htmlonly{\image{0cm;0cm}{replic.png}}%
\caption{Replicate dialog}%
\end{figure}
@@ -1384,7 +1389,7 @@
\subsection{Delete}\label{delete}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{delete.png}}%
+\latexonly{\includegraphics[0,0][2,2]{delete.png}}%
\htmlonly{\image{0cm;0cm}{delete.png}}%
\caption{Delete dialog}%
\end{figure}
@@ -1407,7 +1412,7 @@
nearest step-timing value). Only Note-On events are changed.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{quantize.png}}%
+\latexonly{\includegraphics[0,0][2,2]{quantize.png}}%
\htmlonly{\image{0cm;0cm}{quantize.png}}%
\caption{Quantize dialog}%
\end{figure}
@@ -1432,7 +1437,7 @@
The selected events will be set to the selected MIDI Channel.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{setchan.png}}%
+\latexonly{\includegraphics[0,0][2,2]{setchan.png}}%
\htmlonly{\image{0cm;0cm}{setchan.png}}%
\caption{Set MIDI channel dialog}%
\end{figure}
@@ -1441,7 +1446,7 @@
\subsection{Transpose}\label{transpose}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{transpos.png}}%
+\latexonly{\includegraphics[0,0][2,2]{transpos.png}}%
\htmlonly{\image{0cm;0cm}{transpos.png}}%
\caption{Transpose dialog}%
\end{figure}
@@ -1467,7 +1472,7 @@
\subsection{Velocity}\label{veloc}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{veloc.png}}%
+\latexonly{\includegraphics[0,0][2,2]{veloc.png}}%
\htmlonly{\image{0cm;0cm}{veloc.png}}%
\caption{Set velocity dialog}%
\end{figure}
@@ -1486,7 +1491,7 @@
\subsection{Shift}\label{shift}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{shift.png}}%
+\latexonly{\includegraphics[0,0][2,2]{shift.png}}%
\htmlonly{\image{0cm;0cm}{shift.png}}%
\caption{Shift dialog}%
\end{figure}
@@ -1497,7 +1502,7 @@
\subsection{Cleanup}\label{cleanup}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{cleanup.png}}%
+\latexonly{\includegraphics[0,0][2,2]{cleanup.png}}%
\htmlonly{\image{0cm;0cm}{cleanup.png}}%
\caption{Cleanup dialog}%
\end{figure}
@@ -1514,7 +1519,7 @@
\subsection{Search Replace}\label{search}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{search.png}}%
+\latexonly{\includegraphics[0,0][2,2]{search.png}}%
\htmlonly{\image{0cm;0cm}{search.png}}%
\caption{Search Replace dialog}%
\end{figure}
@@ -1556,7 +1561,7 @@
Setting of default {\em Volume}, {\em Pan}, {\em Reverb} and {\em Chorus}.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{mixer.png}}%
+\latexonly{\includegraphics[0,0][2,2]{mixer.png}}%
\htmlonly{\image{0cm;0cm}{mixer.png}}%
\caption{Mixer window}%
\end{figure}
@@ -1687,7 +1692,7 @@
e.g. 'Delete' and 'Replicate'.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{filter.png}}%
+\latexonly{\includegraphics[0,0][2,2]{filter.png}}%
\htmlonly{\image{0cm;0cm}{filter.png}}%
\caption{Event filter dialog}%
\end{figure}
@@ -1711,7 +1716,7 @@
\subsection{Song}\label{songset}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{songset.png}}%
+\latexonly{\includegraphics[0,0][2,2]{songset.png}}%
\htmlonly{\image{0cm;0cm}{songset.png}}%
\caption{Song settings dialog}%
\end{figure}
@@ -1735,7 +1740,7 @@
\subsection{Metronome Settings}\label{metroset}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{metroset.png}}%
+\latexonly{\includegraphics[0,0][2,2]{metroset.png}}%
\htmlonly{\image{0cm;0cm}{metroset.png}}%
\caption{Metronome settings dialog}%
\end{figure}
@@ -1858,7 +1863,7 @@
\subsection{Synthesizer Type Settings}\label{synthtype}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{syntype.png}}%
+\latexonly{\includegraphics[0,0][2,2]{syntype.png}}%
\htmlonly{\image{0cm;0cm}{syntype.png}}%
\caption{Setting of synthesizer type}%
\end{figure}
@@ -1947,7 +1952,7 @@
\subsection{Meterchange}\label{meterchange}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{meter.png}}%
+\latexonly{\includegraphics[0,0][2,2]{meter.png}}%
\htmlonly{\image{0cm;0cm}{meter.png}}%
\caption{Meter change dialog}%
\end{figure}
@@ -1969,13 +1974,13 @@
\subsection{Harmony browser}\label{hbrowser}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{hb.png}}%
+\latexonly{\includegraphics[0,0][2,2]{hb.png}}%
\htmlonly{\image{0cm;0cm}{hb.png}}%
\caption{Harmony browser}%
\end{figure}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{hbtoolb.png}}%
+\latexonly{\includegraphics[0,0][2,2]{hbtoolb.png}}%
\htmlonly{\image{0cm;0cm}{hbtoolb.png}}%
\caption{Harmony browser toolbar}%
\end{figure}
@@ -2123,13 +2128,13 @@
\subsection{Random rhythm generator}\label{randrhy}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{rrg.png}}%
+\latexonly{\includegraphics[0,0][2,2]{rrg.png}}%
\htmlonly{\image{0cm;0cm}{rrg.png}}%
\caption{Random rhythm generator}%
\end{figure}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{rrgtoolb.png}}%
+\latexonly{\includegraphics[0,0][2,2]{rrgtoolb.png}}%
\htmlonly{\image{0cm;0cm}{rrgtoolb.png}}%
\caption{Random rhythm generator toolbar}%
\end{figure}
@@ -2578,7 +2583,7 @@
mouse button into the trackwindow.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{pianowin.png}}%
+\latexonly{\includegraphics[0,0][2,2]{pianowin.png}}%
\htmlonly{\image{0cm;0cm}{pianowin.png}}%
\caption{Piano Window}%
\end{figure}
@@ -2588,7 +2593,7 @@
\section{Toolbar}\label{pwtoolbar}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{pwtoolb.png}}%
+\latexonly{\includegraphics[0,0][2,2]{pwtoolb.png}}%
\htmlonly{\image{0cm;0cm}{pwtoolb.png}}%
\caption{Pianowin toolbar}%
\end{figure}
@@ -2705,7 +2710,7 @@
\section{Edit/create single events}\label{pweventedit}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{eventdlg.png}}%
+\latexonly{\includegraphics[0,0][2,2]{eventdlg.png}}%
\htmlonly{\image{0cm;0cm}{eventdlg.png}}%
\caption{Example of event editing dialog}%
\end{figure}
@@ -2749,7 +2754,7 @@
\subsection{Events}\label{pwevents}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{pwevents.png}}%
+\latexonly{\includegraphics[0,0][2,2]{pwevents.png}}%
\htmlonly{\image{0cm;0cm}{pwevents.png}}%
\caption{Pianowin show-events dialog}%
\end{figure}
@@ -2786,7 +2791,7 @@
\subsection{Edit Pitch and others}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{pitched.png}}%
+\latexonly{\includegraphics[0,0][2,2]{pitched.png}}%
\htmlonly{\image{0cm;0cm}{pitched.png}}%
\caption{Graphical editing in Pianowin}%
\end{figure}
@@ -2863,7 +2868,7 @@
on the audio track corresponds to a sample you just defined.
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{audiotrk.png}}%
+\latexonly{\includegraphics[0,0][2,2]{audiotrk.png}}%
\htmlonly{\image{0cm;0cm}{audiotrk.png}}%
\caption{Audio track in pianowin}%
\end{figure}
@@ -2918,7 +2923,7 @@
\subsection{Global Settings}\label{globalsettings}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{audioset.png}}%
+\latexonly{\includegraphics[0,0][2,2]{audioset.png}}%
\htmlonly{\image{0cm;0cm}{audioset.png}}%
\caption{Global audio settings dialog}%
\end{figure}
@@ -2958,7 +2963,7 @@
\subsection{Sample Settings}\label{samplesettings}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{sampset.png}}%
+\latexonly{\includegraphics[0,0][2,2]{sampset.png}}%
\htmlonly{\image{0cm;0cm}{sampset.png}}%
\caption{Sample settings dialog}%
\end{figure}
@@ -3002,7 +3007,7 @@
\section{Sample Editor}\label{samplewin}
\begin{figure}%
-\latexonly{\includegraphics[scale=0.5]{sampedit.png}}%
+\latexonly{\includegraphics[0,0][2,2]{sampedit.png}}%
\htmlonly{\image{0cm;0cm}{sampedit.png}}%
\caption{Sample editor}%
\end{figure}
@@ -3618,13 +3623,13 @@
\chapter{Appendix}\label{appendix}
The appendix has not been appended yet, come back soon!
-\item[RoadMap]
+\chapter{RoadMap}
\section{Frequently Asked Questions}\title{FAQ}
\section{Jazz++ Specific}
-\item[How powerful does my computer need to be to run JAZZ++ properly?]
+\section{How powerful does my computer need to be to run JAZZ++ properly?}
It is best to understand here, that it's not so much a matter of how much raw
@@ -3781,7 +3786,7 @@
5. Mandriva: Have a look here ;
- http://wiki.mandriva.com/en/Docs/Howto/Mandriva_Kernels#kernel-rt
+ http://wiki.mandriva.com/en/Docs/Howto/Mandriva\_Kernels\#kernel-rt
6. Fedora: Have a look here ;
@@ -3808,3 +3813,4 @@
[ed: TBC.. ]
+\end{document}
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <pst...@us...> - 2008-06-14 12:51:01
|
Revision: 603
http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=603&view=rev
Author: pstieber
Date: 2008-06-14 05:50:56 -0700 (Sat, 14 Jun 2008)
Log Message:
-----------
Changed includegraphics statements to use scale again, now that everything else is fixed.
Modified Paths:
--------------
trunk/jazz/src/HelpFiles/jazz.tex
Modified: trunk/jazz/src/HelpFiles/jazz.tex
===================================================================
--- trunk/jazz/src/HelpFiles/jazz.tex 2008-06-14 12:20:26 UTC (rev 602)
+++ trunk/jazz/src/HelpFiles/jazz.tex 2008-06-14 12:50:56 UTC (rev 603)
@@ -3,14 +3,14 @@
%\input{psbox.tex}
\parskip=10pt
\parindent=0pt
-\title{JAZZ++ MIDI sequencer version 5.0}%
+\title{JAZZ++ MIDI sequencer version 5.0}
\author{Donald B. Moore $<$db...@ho...$>$\\
-Pete Stieber $<$pst...@gm...$>$}%
-\date{June 2008}%
+Pete Stieber $<$pst...@gm...$>$}
+\date{June 2008}
\makeindex%
-\begin{document}%
+\begin{document}
\maketitle%
-\pagestyle{fancyplain}%
+\pagestyle{fancyplain}
\tableofcontents%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -918,12 +918,11 @@
this far, QJACKCTL will present you with it's control GUI but the JACK
server itself is not yet started.
-\begin{figure}%
-%\latexonly{\includegraphics[scale=0.5]{images/qjack-stopped.png}}%
-\latexonly{\includegraphics[0,0][2,2]{images/qjack-stopped.png}}%
-\htmlonly{\image{0cm;0cm}{images/qjack-stopped.png}}%
-\caption{Main Control GUI of QJACKCTL}%
-\end{figure}%
+\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}
Next thing to do, is to click on the 'Start' button to launch the
@@ -931,22 +930,22 @@
control panel GUI should look like this ;
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qjack-running.png}}%
-\htmlonly{\image{0cm;0cm}{images/qjack-running.png}}%
-\caption{Main Control GUI of QJACKCTL}%
-\end{figure}%
+\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}
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[0,0][2,2]{images/qjack-connect-win-0.png}}%
-\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-0.png}}%
-\caption{Connection GUI of QJACKCTL}%
-\end{figure}%
+\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}
This all should have completed sucessfully and without generating any
@@ -970,11 +969,11 @@
actual softsynth itself will at this stage be unconfigured.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-startup.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-startup.png}}%
-\caption{Main Control GUI of QSYNTH}%
-\end{figure}%
+\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}
Next thing to do, is configure the softsynth itself. Click on the 'Setup'
@@ -982,11 +981,11 @@
configuration GUI. The first tab is the 'MIDI' setup page ;
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-0.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-0.png}}%
-\caption{The MIDI Configuration GUI of QSYNTH}%
-\end{figure}%
+\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}
@@ -996,11 +995,11 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-1.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-1.png}}%
-\caption{The Audio Configuration GUI of QSYNTH}%
-\end{figure}%
+\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}
@@ -1011,11 +1010,11 @@
display the Soundfont setup page - it should currently be empty ;
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-2.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-2.png}}%
-\caption{The Soundfont Configuration GUI of QSYNTH}%
-\end{figure}%
+\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}
@@ -1028,11 +1027,11 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-3.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-3.png}}%
-\caption{The Soundfont selection GUI of QSYNTH}%
-\end{figure}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-3.png}}
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-3.png}}
+\caption{The Soundfont selection GUI of QSYNTH}
+\end{figure}
Navigate to the location of the soundfont file you are going to use.
@@ -1046,10 +1045,10 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-4.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-4.png}}%
-\caption{The Soundfont Configuration GUI of QSYNTH}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-4.png}}
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-4.png}}
+\caption{The Soundfont Configuration GUI of QSYNTH}
\end{figure}
@@ -1062,10 +1061,10 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qsynth-setup-5.png}}%
-\htmlonly{\image{0cm;0cm}{images/qsynth-setup-5.png}}%
-\caption{The Settings GUI of QSYNTH}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{images/qsynth-setup-5.png}}
+\htmlonly{\image{0cm;0cm}{images/qsynth-setup-5.png}}
+\caption{The Settings GUI of QSYNTH}
\end{figure}
@@ -1076,10 +1075,10 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/jazz-output-sel-0.png}}%
-\htmlonly{\image{0cm;0cm}{images/jazz-output-sel-0.png}}%
-\caption{The Jazz++ MIDI Output Device selection GUI}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{images/jazz-output-sel-0.png}}
+\htmlonly{\image{0cm;0cm}{images/jazz-output-sel-0.png}}
+\caption{The Jazz++ MIDI Output Device selection GUI}
\end{figure}
@@ -1096,10 +1095,10 @@
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qjack-connect-win-1.png}}%
-\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-1.png}}%
-\caption{The Audio Connections GUI of QJACKCTL}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-1.png}}
+\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-1.png}}
+\caption{The Audio Connections GUI of QJACKCTL}
\end{figure}
@@ -1110,9 +1109,9 @@
\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{images/qjack-connect-win-3.png}}%
-\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-3.png}}%
-\caption{The MIDI Connections GUI of QJACKCTL}%
+\latexonly{\includegraphics[scale=0.5]{images/qjack-connect-win-3.png}}%
+\htmlonly{\image{0cm;0cm}{images/qjack-connect-win-3.png}}
+\caption{The MIDI Connections GUI of QJACKCTL}
\end{figure}
@@ -1147,10 +1146,10 @@
\helpref{pianowin}{pianowin} shows single events of one track. Events are shown like
bar codes, i.e. every event is shown as a short vertical line.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{trackwin.png}}%
-\htmlonly{\image{0cm;0cm}{trackwin.png}}%
-\caption{Track window}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{trackwin.png}}
+\htmlonly{\image{0cm;0cm}{trackwin.png}}
+\caption{Track window}
\end{figure}
@@ -1178,10 +1177,10 @@
\item \helpref{Help}{twhelp}
\end{enumerate}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{twtoolb.png}}%
-\htmlonly{\image{0cm;0cm}{twtoolb.png}}%
-\caption{Track Window Toolbar}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{twtoolb.png}}
+\htmlonly{\image{0cm;0cm}{twtoolb.png}}
+\caption{Track Window Toolbar}
\end{figure}
\section{Selecting events}\label{select}
@@ -1202,18 +1201,18 @@
mark bars and tracks by dragging a rectangle. Then select the event filter and
disable program-changes (patch). Finally select Delete from Edit-Menu.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{twselect.png}}%
-\htmlonly{\image{0cm;0cm}{twselect.png}}%
-\caption{Selecting events}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{twselect.png}}
+\htmlonly{\image{0cm;0cm}{twselect.png}}
+\caption{Selecting events}
\end{figure}
\section{Record and play}\label{recplay}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{recplay.png}}%
-\htmlonly{\image{0cm;0cm}{recplay.png}}%
-\caption{Record and play}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{recplay.png}}
+\htmlonly{\image{0cm;0cm}{recplay.png}}
+\caption{Record and play}
\end{figure}
There are 2 play modes
@@ -1250,10 +1249,10 @@
down to make bigger changes. Hold down the shift key to change
values in steps of 10 bpm.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{speed.png}}%
-\htmlonly{\image{0cm;0cm}{speed.png}}%
-\caption{Speed adjustment}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{speed.png}}
+\htmlonly{\image{0cm;0cm}{speed.png}}
+\caption{Speed adjustment}
\end{figure}
@@ -1275,10 +1274,10 @@
Clicking into the top of the leftmost column (labeled 'M') toggles
display of midi channel and track number.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{trackdef.png}}%
-\htmlonly{\image{0cm;0cm}{trackdef.png}}%
-\caption{Track defaults}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{trackdef.png}}
+\htmlonly{\image{0cm;0cm}{trackdef.png}}
+\caption{Track defaults}
\end{figure}
\section{Trackname, midi channel etc}\label{trackdlg}
@@ -1290,10 +1289,10 @@
Otherwise the midi channel will not affect events
already on the track.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{tracknam.png}}%
-\htmlonly{\image{0cm;0cm}{tracknam.png}}%
-\caption{Track name, midi channel etc.}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{tracknam.png}}
+\htmlonly{\image{0cm;0cm}{tracknam.png}}
+\caption{Track name, midi channel etc.}
\end{figure}
@@ -1350,10 +1349,10 @@
\subsection{Replicate}\label{replicate}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{replic.png}}%
-\htmlonly{\image{0cm;0cm}{replic.png}}%
-\caption{Replicate dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{replic.png}}
+\htmlonly{\image{0cm;0cm}{replic.png}}
+\caption{Replicate dialog}
\end{figure}
To replicate (copy) some events, you must first \helpref{select}{select}
@@ -1388,10 +1387,10 @@
\subsection{Delete}\label{delete}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{delete.png}}%
-\htmlonly{\image{0cm;0cm}{delete.png}}%
-\caption{Delete dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{delete.png}}
+\htmlonly{\image{0cm;0cm}{delete.png}}
+\caption{Delete dialog}
\end{figure}
To delete some events, you must first \helpref{select}{select} an area.
@@ -1411,10 +1410,10 @@
Quantize will put Note-On events in the selected area 'in time' (moved to the
nearest step-timing value). Only Note-On events are changed.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{quantize.png}}%
-\htmlonly{\image{0cm;0cm}{quantize.png}}%
-\caption{Quantize dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{quantize.png}}
+\htmlonly{\image{0cm;0cm}{quantize.png}}
+\caption{Quantize dialog}
\end{figure}
To quantize some events, you must first \helpref{select}{select} an area.
@@ -1436,19 +1435,19 @@
The selected events will be set to the selected MIDI Channel.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{setchan.png}}%
-\htmlonly{\image{0cm;0cm}{setchan.png}}%
-\caption{Set MIDI channel dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{setchan.png}}
+\htmlonly{\image{0cm;0cm}{setchan.png}}
+\caption{Set MIDI channel dialog}
\end{figure}
\subsection{Transpose}\label{transpose}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{transpos.png}}%
-\htmlonly{\image{0cm;0cm}{transpos.png}}%
-\caption{Transpose dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{transpos.png}}
+\htmlonly{\image{0cm;0cm}{transpos.png}}
+\caption{Transpose dialog}
\end{figure}
If no scale is selected, Amount is the number of semitones to transpose, e.g. an
@@ -1471,10 +1470,10 @@
\subsection{Velocity}\label{veloc}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{veloc.png}}%
-\htmlonly{\image{0cm;0cm}{veloc.png}}%
-\caption{Set velocity dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{veloc.png}}
+\htmlonly{\image{0cm;0cm}{veloc.png}}
+\caption{Set velocity dialog}
\end{figure}
Changes the velocity of Note-On events. If Stop is 0, all Note-On events will get
@@ -1490,10 +1489,10 @@
\subsection{Shift}\label{shift}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{shift.png}}%
-\htmlonly{\image{0cm;0cm}{shift.png}}%
-\caption{Shift dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{shift.png}}
+\htmlonly{\image{0cm;0cm}{shift.png}}
+\caption{Shift dialog}
\end{figure}
Moves events left or right in amounts smaller than a bar. The snap value is
@@ -1501,10 +1500,10 @@
\subsection{Cleanup}\label{cleanup}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{cleanup.png}}%
-\htmlonly{\image{0cm;0cm}{cleanup.png}}%
-\caption{Cleanup dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{cleanup.png}}
+\htmlonly{\image{0cm;0cm}{cleanup.png}}
+\caption{Cleanup dialog}
\end{figure}
Deletes note-on events that are shorter than a selected length. Optionally
@@ -1518,10 +1517,10 @@
\subsection{Search Replace}\label{search}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{search.png}}%
-\htmlonly{\image{0cm;0cm}{search.png}}%
-\caption{Search Replace dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{search.png}}
+\htmlonly{\image{0cm;0cm}{search.png}}
+\caption{Search Replace dialog}
\end{figure}
Searches for controller events and changes the controller number, eg
@@ -1560,10 +1559,10 @@
Setting of default {\em Volume}, {\em Pan}, {\em Reverb} and {\em Chorus}.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{mixer.png}}%
-\htmlonly{\image{0cm;0cm}{mixer.png}}%
-\caption{Mixer window}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{mixer.png}}
+\htmlonly{\image{0cm;0cm}{mixer.png}}
+\caption{Mixer window}
\end{figure}
\subsection{Sound, Vibrato and Envelope}
@@ -1691,10 +1690,10 @@
events that will be affected by \helpref{selection}{select} operations like
e.g. 'Delete' and 'Replicate'.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{filter.png}}%
-\htmlonly{\image{0cm;0cm}{filter.png}}%
-\caption{Event filter dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{filter.png}}
+\htmlonly{\image{0cm;0cm}{filter.png}}
+\caption{Event filter dialog}
\end{figure}
The entries {\em From Time}, {\em To Time}, {\em From Track} and
@@ -1715,10 +1714,10 @@
\subsection{Song}\label{songset}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{songset.png}}%
-\htmlonly{\image{0cm;0cm}{songset.png}}%
-\caption{Song settings dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{songset.png}}
+\htmlonly{\image{0cm;0cm}{songset.png}}
+\caption{Song settings dialog}
\end{figure}
Here you can adjust the overall resolution of the song in ticks per quarter.
@@ -1739,10 +1738,10 @@
\subsection{Metronome Settings}\label{metroset}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{metroset.png}}%
-\htmlonly{\image{0cm;0cm}{metroset.png}}%
-\caption{Metronome settings dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{metroset.png}}
+\htmlonly{\image{0cm;0cm}{metroset.png}}
+\caption{Metronome settings dialog}
\end{figure}
Adjust metronome instruments and velocity.
@@ -1862,10 +1861,10 @@
\subsection{Synthesizer Type Settings}\label{synthtype}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{syntype.png}}%
-\htmlonly{\image{0cm;0cm}{syntype.png}}%
-\caption{Setting of synthesizer type}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{syntype.png}}
+\htmlonly{\image{0cm;0cm}{syntype.png}}
+\caption{Setting of synthesizer type}
\end{figure}
Many MIDI sound generators (a synthesizer, soundmodule or soundcard) offer
@@ -1951,10 +1950,10 @@
\subsection{Meterchange}\label{meterchange}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{meter.png}}%
-\htmlonly{\image{0cm;0cm}{meter.png}}%
-\caption{Meter change dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{meter.png}}
+\htmlonly{\image{0cm;0cm}{meter.png}}
+\caption{Meter change dialog}
\end{figure}
Changes the meter (counts per bar and note-value of each count) starting
@@ -1973,16 +1972,16 @@
\subsection{Harmony browser}\label{hbrowser}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{hb.png}}%
-\htmlonly{\image{0cm;0cm}{hb.png}}%
-\caption{Harmony browser}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{hb.png}}
+\htmlonly{\image{0cm;0cm}{hb.png}}
+\caption{Harmony browser}
\end{figure}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{hbtoolb.png}}%
-\htmlonly{\image{0cm;0cm}{hbtoolb.png}}%
-\caption{Harmony browser toolbar}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{hbtoolb.png}}
+\htmlonly{\image{0cm;0cm}{hbtoolb.png}}
+\caption{Harmony browser toolbar}
\end{figure}
The harmony browser shows the 4-tuned JAZZ++ harmonies of the four scales
@@ -2127,16 +2126,16 @@
\subsection{Random rhythm generator}\label{randrhy}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{rrg.png}}%
-\htmlonly{\image{0cm;0cm}{rrg.png}}%
-\caption{Random rhythm generator}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{rrg.png}}
+\htmlonly{\image{0cm;0cm}{rrg.png}}
+\caption{Random rhythm generator}
\end{figure}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{rrgtoolb.png}}%
-\htmlonly{\image{0cm;0cm}{rrgtoolb.png}}%
-\caption{Random rhythm generator toolbar}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{rrgtoolb.png}}
+\htmlonly{\image{0cm;0cm}{rrgtoolb.png}}
+\caption{Random rhythm generator toolbar}
\end{figure}
This dialog generates rhythms from some kind of statistical specification.
@@ -2582,20 +2581,20 @@
Displayed track and bar is selected by clicking with the right
mouse button into the trackwindow.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{pianowin.png}}%
-\htmlonly{\image{0cm;0cm}{pianowin.png}}%
-\caption{Piano Window}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{pianowin.png}}
+\htmlonly{\image{0cm;0cm}{pianowin.png}}
+\caption{Piano Window}
\end{figure}
\section{Toolbar}\label{pwtoolbar}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{pwtoolb.png}}%
-\htmlonly{\image{0cm;0cm}{pwtoolb.png}}%
-\caption{Pianowin toolbar}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{pwtoolb.png}}
+\htmlonly{\image{0cm;0cm}{pwtoolb.png}}
+\caption{Pianowin toolbar}
\end{figure}
Buttons to set the mode of the left mouse-button:
@@ -2709,10 +2708,10 @@
\section{Edit/create single events}\label{pweventedit}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{eventdlg.png}}%
-\htmlonly{\image{0cm;0cm}{eventdlg.png}}%
-\caption{Example of event editing dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{eventdlg.png}}
+\htmlonly{\image{0cm;0cm}{eventdlg.png}}
+\caption{Example of event editing dialog}
\end{figure}
There are a number of dialogs that allow for detailed editing of single events.
@@ -2753,10 +2752,10 @@
\subsection{Events}\label{pwevents}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{pwevents.png}}%
-\htmlonly{\image{0cm;0cm}{pwevents.png}}%
-\caption{Pianowin show-events dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{pwevents.png}}
+\htmlonly{\image{0cm;0cm}{pwevents.png}}
+\caption{Pianowin show-events dialog}
\end{figure}
You can specify what events are to be shown in the pianowin.
@@ -2790,10 +2789,10 @@
\subsection{Edit Pitch and others}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{pitched.png}}%
-\htmlonly{\image{0cm;0cm}{pitched.png}}%
-\caption{Graphical editing in Pianowin}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{pitched.png}}
+\htmlonly{\image{0cm;0cm}{pitched.png}}
+\caption{Graphical editing in Pianowin}
\end{figure}
@@ -2867,10 +2866,10 @@
notes on the track, copy, delete or replicate bars etc. Every note
on the audio track corresponds to a sample you just defined.
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{audiotrk.png}}%
-\htmlonly{\image{0cm;0cm}{audiotrk.png}}%
-\caption{Audio track in pianowin}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{audiotrk.png}}
+\htmlonly{\image{0cm;0cm}{audiotrk.png}}
+\caption{Audio track in pianowin}
\end{figure}
Next open the piano window on that track by clicking with the right
@@ -2922,10 +2921,10 @@
\subsection{Global Settings}\label{globalsettings}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{audioset.png}}%
-\htmlonly{\image{0cm;0cm}{audioset.png}}%
-\caption{Global audio settings dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{audioset.png}}
+\htmlonly{\image{0cm;0cm}{audioset.png}}
+\caption{Global audio settings dialog}
\end{figure}
Here you specify the internal resolution for the audio processing of
@@ -2962,10 +2961,10 @@
\subsection{Sample Settings}\label{samplesettings}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{sampset.png}}%
-\htmlonly{\image{0cm;0cm}{sampset.png}}%
-\caption{Sample settings dialog}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{sampset.png}}
+\htmlonly{\image{0cm;0cm}{sampset.png}}
+\caption{Sample settings dialog}
\end{figure}
In this dialog you define the midi keys for your samples. Please read
@@ -3006,10 +3005,10 @@
\section{Sample Editor}\label{samplewin}
-\begin{figure}%
-\latexonly{\includegraphics[0,0][2,2]{sampedit.png}}%
-\htmlonly{\image{0cm;0cm}{sampedit.png}}%
-\caption{Sample editor}%
+\begin{figure}
+\latexonly{\includegraphics[scale=0.5]{sampedit.png}}
+\htmlonly{\image{0cm;0cm}{sampedit.png}}
+\caption{Sample editor}
\end{figure}
The sample editor may be invoked from the
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X