file_id.diz
Atari POKEY Chip Emulator V2.3
==============================
by Ron Fries
19 Jan 98
The PokeySound Chip Emulator is designed to emulate the functionality of the
Atari POKEY Chip Hardware through 'C' Sourcecode. The emulator is able to
produce sounds which are essentially identical to the original POKEY chip,
including the exact distortions and pitches.
The emulator is designed to run in a 32-bit environment. Though it can be
compiled and run in a 16-bit environment, it is slow.
I would like to give special thanks to Neil Bradley. He provided excellent
testing support and was also the driving force behind the multiple POKEY
emulation.
New Features:
-------------
Version 2.3:
1) Added configurable support for signed/unsigned samples. Default is
unsigned, define SIGNED_SAMPLES if necessary.
2) Included SBDRV1.2 which adds DJGPP support and corrects the AUTO-INIT
detection problem.
Version 2.2:
1) Changed to signed 8-bit samples.
2) Increased gain range by a factor of 16. Divide gain from previous version
by sixteen to produce the same results.
3) Removed DOS dependent routines to provide cross-platform support.
4) Added conditional defines for TRUE and FALSE
5) Added support for big/little endian machines. Defaults to little endian.
Define BIG_ENDIAN if necessary.
Version 2.0:
1) Support for multiple POKEY chips. The maximum supported is configured
at compile time.
2) An adjustable gain. The previous releases had a built-in gain of 64.
3) A clipping option. Depending on the number of chips emulated and the
configured gain, it is possible for the output to exceed 8-bits.
Clipping can be enabled to prevent this, though it does increase the
processing time.
Standard Features:
------------------
The 'PokeySound' emulator supports the following functions:
1) All polynomial sound generators:
a) 4-bit poly - actual bit pattern determined from sampled sound
b) 5-bit poly - actual bit pattern determined from sampled sound
c) 17-bit poly - simulated random bit pattern
d) 9-bit poly - derived from simulated 17-bit poly
2) Full support of all 'Divide by N' counter clocks:
a) 1.79 MHz (high limited to playback sample rate)
b) 64 KHz (high limited to playback sample rate)
c) 15 KHz
3) Full support of all 'Divide by N' resolutions:
a) 8-bit - single channel
b) 16-bit - double channel
4) Full support of all distortions
a) 5-bit poly, then 17-bit poly
b) 5-bit poly only
c) 5-bit poly, then 4-bit poly
d) 17-bit poly only
e) no poly counters (pure tone)
f) 5-bit poly only
5) Full support of volume control
6) Full support of all pitches - distortions will vary exactly as the
original Atari based on different pitches
7) Accurate pitch generation
8) Support of any playback sample rate (e.g. 22050)
The 'PokeySound' emulator does not currently support the following functions:
1) High pass filters
Though I don't believe adding support for the High-Pass filters is very
complicated, I decided not to add support right now because I don't
believe this feature is used much. I'm also not sure how much impact it
would have on performance. Let me know if you find an application that
uses it.
In the 2.0 release, I've removed the non-optimized version. It was only
left in for reference. If you would still like to see the non-optimized
version, it's available in the 1.2 release.
One of the unique features of the emulator is that the processing time varies
based on the frequency. Since the routine only calculates new output values
when a change is sensed, the lower frequencies (which change less frequently)
will require less processing time.
Differences Between the Emulator and the Actual POKEY Chip:
-----------------------------------------------------------
The biggest difference between the emulator and the original hardware is
that the emulator emulates an 'ideal' POKEY chip. All output from the
emulator is a based on a precise square wave, whereas the output from the
original chip has decay. Though the output is slightly different, I
don't believe this difference is easily discernible.
Another slight difference is the 17-bit/9-bit poly. Since the polynomial
is large (2^17 bits), I choose to create the sample using a random number
generator rather than a table. I don't believe this difference is
significant.
There are also a few differences which are introduced by aliasing. This is
a direct result of using an output sampling rate which is not identical to
the original sound rate. It is most evident with high frequencies.
A final difference is the lack of support for the High-Pass Filter
functionality. I plan to add this in a future release if necessary.
Sample/Test Application:
------------------------
The test program I've distributed is a 16-bit DOS application created with
the Borland 'C' compiler. The only reason I used 16-bit was because I
already had a set of working SB drivers in 16-bit. Since the test system
is dedicated to generating sounds, the performance in 16-bit is more than
adequate.
POKEY.C
=======
The POKEY.C file is the heart of the PokeySound Emulation program.
Although the routines in the file must work together, no other files are
modules are required for operation. A header file, 'POKEY.H', has
been included for use in other modules, and provides the necessary
function prototypes. I've attempted to make the routines as portable as
possible, so the file should compile on almost any compiler with little
or no modification.
I have made some attempts at optimizing the routines, though I am sure
more optimization can be done. They are currently only available in 'C'.
I'll be happy to convert them to assembly language if desired. Please feel
free to send me e-mail at rfries@tcmail.frco.com.
The routines are easy to use. Detailed descriptions on the function calls
are listed below.
The POKEY.C module can be compiled in a 32-bit or 16-bit environment.
Since these routines are optimized for 32-bit use, the code will default
to 32-bit. To compile in 16-bits, use a command line option to define
the variable COMP16.
GENERAL OVERVIEW
----------------
On start-up of the system, a single call should be made to Pokey_sound_init.
This routine will prepare the structures for sound output. This routine
can be called again if necessary during warm-start or other reset.
Once in the main loop, there are two other functions that will be used.
Whenever the system needs to write to either the AUDC or AUDF values,
a call should be made to the Update_pokey_sound routine. This routine will
take care of updating the internal registers. It will pre-calculate several
values to help with optimization.
The only other routine that is called is the Pokey_process function. This
function will fill a audio buffer with a specified number of bytes. This
function should be called whenever a new audio buffer is required.
For best results, I recommend using at least two output buffers. Using this
scheme, the sound card can be playing one buffer while the system is filling
the other.
DETAILED FUNCTION DESCRIPTIONS
------------------------------
Pokey_sound_init(uint32 freq17, uint16 playback_freq, uint8 num_pokeys)
-----------------------------------------------------------------------
This function initializes the structures used by the PokeySound routines.
This function takes three parameters: the main clock frequency, the
playback frequency and the number of POKEY chips to emulate.
The maximum number of POKEY chips emulated is configured at compile time.
Though the maximum number of chips can be configured as one, the PokeySound
1.2 routines are recommended if only a single chip is to be emulated since
they have will provide better performance.
NOTE: The following information on the 1.79MHz clock applies only to the
Atari 800 line of home computers. Many Arcade games also use the
POKEY chip, but most use a different frequency for the POKEY clock.
Refer to the schematics for more details.
The main clock frequency is the frequency of the 1.79MHz source clock.
To provide exact results, freq17 should be set equal to 1789790 Hz. As an
alternative, freq17 can be set to an approximate frequency of 1787520 Hz.
Using this approximate frequency will reduce aliasing and thus produce a
clearer output signal.
A constant has been defined for both of these values for your convenience.
The names are FREQ_17_EXACT and FREQ_17_APPROX.
The playback frequency is the frequency of the sound playback (the frequency
used by the sound card). For best results, the playback frequency should
be an even division of the main clock frequency. Since most of the sounds
will be generated using the 64kHz clock, I also recommend making the
playback frequency an even division of the 64kHz clock.
The 64kHz clock is exactly equal to the main clock divided by 28. For
the playback frequency, I recommend one of the following values:
1) FREQ_17_APPROX / (28*1), which is equal to 63840. Of course, most sound
cards can't reproduce this frequency.
2) FREQ_17_APPROX / (28*2), which is equal to 31920. All of the newer cards
will support this frequency.
3) FREQ_17_APPROX / (28*3), which is equal to 21280. All of the SB
compatibles should support this frequency.
4) FREQ_17_APPROX / (28*4), which is equal to 15960. This may be the
best choice, as it offers good sound reproduction with good performance.
Of course, these options also assume you are using the approximate
frequency for the main clock as well. Any of these choices will offer the
best results when the main 64kHz clock is used, reasonable results when the
15kHz clock is selected, and marginal results when the 1.79MHz clock is
selected (the only way to produce good results in all cases is to set the
playback frequency to 1.79MHz!)
Feel free to experiment to find other alternatives as well.
This function has no return value (void).
Update_pokey_sound (uint16 addr, uint8 val, uint8 chip, uint8 gain)
-------------------------------------------------------------------
This function should be called each time an AUDC, AUDF or AUDCTL value
changes. This function takes four parameters: the address to change,
the new value, the chip to be updated, and the gain to be used.
The lower four bits of the address should be one of the following values:
Addr Description
------ -----------
0x00 AUDF1
0x01 AUDC1
0x02 AUDF2
0x03 AUDC2
0x04 AUDF3
0x05 AUDC3
0x06 AUDF4
0x07 AUDC4
0x08 AUDCTL
In order to support multiple POKEY chips, only the lower four bits of
the address are used. Note that this routine can no longer be called with
any address as it will affect the operation of the specified chip.
The routine pre-calculates several values that are needed by the
processing function. This is done to optimize performance.
The output will be amplified (multiplied) by the gain (note that POKEY 2.0
used gain/16). If the output exceeds the maximum value after then gain and
clipping is enabled, the output will be limited to reduce distortion.
The best value for the gain depends on the number of POKEYs emulated and
the maximum volume used. The maximum possible output for each channel is 15,
making the maximum possible output for a single chip to be 60. Assuming all
four channels on the chip are used at full volume, a gain of 4 can be used
without distortion. If 4 POKEY chips are emulated and all 16 channels are
used at full volume, the gain must be no more than one to prevent distortion.
Of course, if only a few of the 16 channels are used or not all channels are
used at full volume, a larger gain can be used.
To enable clipping, define the logical CLIP before compiling. The default
mode of operation is no clipping as this provides the best performance. If
necessary (only required if the gain is too large), remove the comments from
around the CLIP definition in the POKEY.H file.
To enable signed output, define the logical SIGNED_SAMPLES before compiling.
The default is unsigned 8-bit centered around 128. If unsigned samples are
necessary, remove the comments from around the SIGNED_SAMPLES definition in
POKEY.H.
This function has no return value (void).
Pokey_process (uint8 *buffer, uint16 n)
---------------------------------------
This function calculates and fills a buffer with signed or unsigned 8-bit
mono audio. This function takes two parameters: a pointer to the buffer to
fill and the size of the buffer (limited to 65535). This function fills the
buffer based on the requested size and returns. It automatically
updates the pointers for the next call, so subsequent calls to this function
will provide a continuous stream of data.
The size of the buffer that is needed depends on the playback frequency.
It is best to keep the buffer as small as possible to maximize response time
to changes in the sound. Of course, the minimum size is dependent on
system and emulator performance.
Selecting the correct buffer size is a careful balance. Selecting a buffer
size that is too small will produce noticeable clicks in the output, though
selecting a size that is too large will cause a poor response time and
possible delays in the system when the new buffer is filled.
This function has no return value (void).
License Information and Copyright Notice
========================================
PokeySound is Copyright(c) 1996-1998 by Ron Fries
This library is free software; you can redistribute it and/or modify it under
the terms of version 2 of the GNU Library General Public License as published
by the Free Software Foundation.
This library 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 Library General Public License for more
details.
To obtain a copy of the GNU Library General Public License, write to the Free
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Any permitted reproduction of these routines, in whole or in part, must bear
this legend.
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
RASTER Music Tracker v1.01 beta
by Radek Sterba, Raster/C.P.U., 2002-2003
http://raster.atari.org
=========================================
About:
RASTER Music Tracker (RMT) is a cross-platform tool for making 8bit Atari XE/XL music on the PC platform (OS Win9x). RMT uses new (2002) Atari XE/XL music routines of my own - I developed them for a very long time and I hope it will be small revolution for all Atari musicians and fans.
Atari sound emulation and 6502 emulation:
RMT application currently uses for producing of the Atari sound part of PokeySound emulation library by Ron Fries and part of 6502 CPU emulation from the Atari800 emulator project, homepage: http://atari800.sourceforge.net.
Credits:
Bob!k/C.P.U.
JirkaS/C.P.U.
Ron Fries (Thanks for a Atari Pokey sound emulation library)
Atari800 emulator developer team - http://atari800.sourceforge.net (Thanks for Atari800 emulator)
Greetings:
Fox/Taquart (Thanks for XASM)
Jaskier/Taquart (Thanks for TMC)
PG (Thanks for ASMA - Atari SAP Music Archive - http://asma.atari.org)
All the active "Atariarea" Polish Atarians (http://atariarea.nostalgia.pl)
...and all other 8bit Atarians all over the world! :-)
CHANGES
=======
Changes in RMT beta 1.01
------------------------
All modes
- Set the octave up-down hotkeys changed from Shift+up,down to Shift+page_up,page_down
(it works now in TrackEdit and InstrumentEdit only).
- Correction of bug with instrument copy/paste.
TrackEdit
- No more set number of the track by Control+0-9A-F keys.
- Hotkey changed: Control+I - insert new line into the song.
- Hotkey changed: Control+U - delete the current line from the song.
- Show title "EMPTY" for empty tracks.
- Shift+up,down,home,end - the block select functions.
- Control+A - select all data in the track (from the begin to the end of the track).
- Control+Insert,Control+C - copy block to clipboard.
- Shift+Insert,Control+V - paste data from clipboard.
- If the block is selected and paste function is used, then data from clipboard is placed into the block select area only.
- If the block is selected, then Delete key will delete data inside the block area.
- If the block is selected, then Control+X key will cut data inside the block area.
- New toolbar for block data modifications: menu View - Block toolbar. All this modify functions are available also by hotkeys.
- Block data modification hotkeys (the block must be selected at first):
Shift+Control+A switch between block modify mode all / current instrument only.
Shift+Control+page_up,page_down do transpose up,down notes in the block (by semitones).
Shift+Control+left,right do change of instrument numbers in the block.
Shift+Control+Num-,Num+ do change of volumes in the block.
Note transpositions, instrument changes and volume changes are indicated in window statusbar at the bottom.
- If the block is selected:
Enter key will play the lines inside the block around.
Home or End key set the cursor to the first or the last line in the block.
Control+B will restore the block data changed by modification functions from the backup (backup is created when the block is getting start to select and destroyed when the block is deselected).
Control+F4 will start cyclic playing of the part from the top to the bottom of selected block area.
Operation manual
- All this changes included to operation manual (see the rmt_en.htm, rmt_cz.htm).
RMT beta 1.00
-------------
- The first published version.