Common questions and answers about PMsndX. Q. How do I enter the registration information? A. To enter the registration information, pull down the menu from the control panel and select either the Welcome or About menu item. The display will contain a button to bring up the registration display. The information may be entered from the keyboard or from a file. Q. Where is the registration information stored? A. PMsndX stores all of the registration information in the os2.ini file. This amounts to about 20 bytes of data. Q. I have a Sun audio file that plays on my Sun machine but results in a "Unsupported style" error when PMsndX attempts to load it. A. Sun hardware supports U-Law files with and without headers. When a header is not present, the Sun hardware assumes that the sampling rate is 8012 Hz. If a Sun file results in an unsupported style error, force it to load the file in the .ul format and specify a rate of 8012 Hz. Alternately, if the "Require Header for files" is not checked (the default) in the MISC page of the Properties, any file with an extension of .au will be loaded as .ul if a valid .au header is not present. Q. What happens when I try to play a 16 bit sample on an 8 bit sound card? A. PMsndX is capable of editing and manipulating sounds of any number of bits, rate, and channels. However, audio adapters may be limited in their capabilities and may not support some of these characteristics. Therefore, PMsndX will still load and manipulate samples that cannot be played on the audio adapter but the MMPM dialog will disable all of its buttons. If you have an 8 bit audio adapter PMsndX will automatically detect that it cannot play 16 bit files and set the "Play 16 bits on 8 bit audio" box in the properties dialog box. Q. Can compressed VOC files be loaded? A. Unfortunately, I cannot find documentation on the compressed VOC formats and they are not implemented in PMsndX. A future release may have this corrected. Q. I want to load a large sample. How do I minimize the memory requirements? A. When a file is loaded it is stored as 16 bit samples regardless of the actual sample size. This takes up roughly twice the memory as would be required for 8 bit samples. The MMPM buffers make up a second copy of the data in memory. This copy is exactly the size of the data that would be written to disk. If it is an 8 bit sample file, then the samples in the buffer are 8 bits. If it is a 16 bit file, then the buffer contains 16 bit samples. During an editing operation (i.e. cut, paste, or anything in the toolbox) the data is double buffered to allow the operation to be aborted. When the UNDO capability is enabled from the settings dialog, a copy of the last sample will be maintained for the UNDO. Finally, if the faster graphical display routines are used, memory resources are used to store the bitmaps for the data. So, to reduce the memory requirements, make the following settings: Go to the PLSNDX settings page and set "Free memory after loading". Clear the "Enable Quick queueing" also. Go to the EDSNDX settings page and clear the "Enable UNDO", "Fast Full display", and "Fast Channel display" checkboxes. Go to the Editor page under EDSNDX of the properties and set the "Delay AUDIO Loading" (you can still play the sample by using the Editor menu and selecting "Load AUDIO Data Now". Q. Why doesn't the little man run when the REXX window is minimized? A. If the REXX window is minimized to the Viewer, it will still be animated. However, if it is minimized to the desktop OS/2 does not process the SETICON messages and the icon is not animated. There is nothing I can do about it. Q. When I load a file from the command line, it does not play in PlSndX. A. Check the AUDIO page of the Properties dialog and set "Play on Load" or "Play on commandline load". Without one of these options selected, files are only loaded when specified on the command line and are not immediately played. Q. EdSndX crashes when the play button is pressed when the playpos cursor is at the end of a sample. Sometimes play just stops after pressing the button and a second press starts it again. A. This is a problem I have run into with MMPM because I have to convert the returned ending position from 1/3000th seconds to indexing values. The problem is caused by roundoff error and by MMPM reporting a position that is not exactly the end of the file. To correct for this, I have added a setting that lets you specifya Zone in which I can detect the end of the file myself. The default value for the zone is 300 samples, but you may need to increase it to get better performance. When playing back a sample, this value has no effect. It only affects how I interpret the signals that come back from MMPM/2 when I go to start playback again. Q. Pressing the HELP menu item on the TOOLBOX doesn't display help? A. When the TOOLBOX is first displayed, main window has the focus and does not receive the HELP message. You must select the tool window so that the window is highlighted before pressing the HELP item. And, if your next question is "why don't you change this?", the answer is because I have written the toolbox routines to be direct replacements for the IBM notebook routines which behave this way too. Q. If I start any of the PMsndX programs from a OS/2 window, is it all right to press Ctrl-C or BREAK to exit the program? A. Generally, exiting the program through a break signal should be avoided. However, all PMsndX programs deal with this situation gracefully and close down the program correctly.