
             FREQUENLY ASKED QUESTIONS ABOUT DES-TRACKER LIBRARY
             ===================================================

   The following questions are (for the most part) listed in order by the
frequency they are asked, with the most frequently asked questions first.



Q: Why did you write the LScope program to run in PAL mode?

A: I didn't.  LScope simply defines a custom screen that is slightly taller
   than a normal NTSC screen.  If your Workbench screen is set low enough in
   your preferences, then the bottom of the LScope display will be clipped
   off.



Q: When I run the LScope program, the bottom of the display is clipped off.
   Why is that, and what's down there?

A: The reason that LScope may be clipped off at the bottom is because LScope
   creates a screen that is slightly taller than a standard screen.  Since I
   use an interlaced WorkBench screen with overscan on my Amiga, I have my
   preferences set so that the top of the display is slightly higher than
   normal.  As such, LScope always ran fine for me.  However, on a standard
   preferences setup, the top of the display is lower, so LScope is pushed
   down slightly, causing the bottom of the LScope display to be clipped.  The
   information that you may not be able to see down there consists of the name
   of the song module loaded and the elapsed play time in minutes and seconds.



Q: Can you write a version of DTC that uses Intuition and has a window with
   buttons for all the commands, plus a built-in jukebox and scope display?

A: Why, of course you can.  DES-Tracker is fully programmable, allowing you
   to write programs just such as the one you described. :)



Q: The Loop Intent flag doesn't seem to work.  I clear it for a song and then
   save the song to disk, but when I reload it and play it from DTC, it still
   loops.  What's the prob?

A: There is no prob.  DTC is simply a program that allows you to invoke the
   functions of the DES-Tracker library from the command line.  DTC itself
   performs no analysis of the song once it is loaded.  Since the DES-Tracker
   library doesn't use the Loop Intent flag for itself, the flag has no effect
   when the song is loaded and played from DTC.  The purpose of the Loop Intent
   flag is so that *your* programs that *you* write that use DES-Tracker can
   load a song module and then examine the Loop Intent bit *yourself*, so 
   that *you* can decide how you will play the song based on the Loop Intent
   flag.  The Jukebox.rexx program, if it sees the Loop Intent flag set when
   it loads a song, will play the song for 2 iterations instead of 1, and fade
   the song out on the second iteration.  But that's not necessarily how you
   *have* to interpret the flag.

                            --- End of QA.TXT ---
