The following suggestions are offered if you experience problems downloading or using files from my pages. As other problems are identified, I will update this page.
|Problem 1: Contents of MIDI file displayed by browser during download.|
|Problem 2: Downloaded patch banks won't load into Proteus unit.|
|Problem 3: Patch bank won't transfer to Proteus unit.|
|Problem 4: Patch bank doesn't sound or is incomplete.|
|Problem 5: Patches in bank sound the same or not as its name implies.|
|Problem 6: Distorted sounds or Proteus unit lockup (Proteus Initialization Procedure).|
|Problem 7: Other things to check.|
|Problem 8: How do I setup my Proteus to play GM midi files?|
|Problem 9: Will Proteus/1 and Proteus/2 presets work on other Emu Proteus sound modules?|
Answer: Your web browser is not configured to properly handle these file types. Make changes in your web browser for .SYX and .WRK file types. Netscape has a "Helpers" tab for doing this under the "Options -> General Preferences" menu item. Define the .SYX and .WRK file types and specify the "Save To Disk" action for each.
Alternative: If you don't want to change your Netscape configurations, select the .WRK or .SYX file using the -right- mouse button. For single button mouse users, click and hold the mouse button down to popup a menu. This will give you the opportunity to "Save link as ..." and direct the links output to a disk file. Important! Make sure the "Save link as ..." format selection is set to "Source".
Answer: Check the links on my page for a standalone Sysex dump utility program.
Answer: Check the Unit ID setting on your Proteus unit. The unit ID is located by pressing the Proteus front panel Master button and scrolling with the Data knob. All patch banks on my page were saved using ID setting 00. Your Proteus must be set to ID 00 to load the patch banks. If you normally use a different unit ID in your setup, resave the patch bank using your ID setting.
Answer: Your computer based sequencer program may be sending the the Sysex data too fast for the Proteus sound module. This generally results in parts of the Sysex data being lost. Check your sequencer software configuration settings for the ability to "slow down" the transmission of Sysex data. Cakewalk, for example, allows for the insertion of a delay both between sysex bytes and/or after a specified number of bytes have been sent. Check in your sequencer program documentation.
Answer: Make sure that the patch bank is the correct one for your Proteus unit. A Proteus/2 patch bank will appear to load correctly but will not function properly on a Proteus/1. The Primary and Secondary waves specified in a patch must be available on your Proteus unit.
Answer: Most probably, a .SYX file became corrupted during download or transfer to your Proteus unit. While this is rare, it has happened to me a few times. The corrupted sysex data "scrambles" the Proteus NVRAM such that the internal processor can not properly function. A Diagnostic Mode Initialize may be the only way to correct this condition.
Answer: All of the patch banks on my page use .syx for the file type. If your bulk sysex program requires a different file type, you can safely rename the file type as appropriate. The patch bank contents are in Proteus binary format and the file name/type is not used.
If you can load the patch bank into the program, then the problem is related to the midi side. When you send the the patch bank, does the MIDI activity indicator on the Proteus light? If not, then the bulk sysex program isn't using your midi interface properly. I would check the program configuration settings for the midi port address and other parameters. Also check the midi cable connections. Midi out from computer to midi in on Proteus.
If the Proteus MIDI activity indicator does light, then the patch bank data is being sent out onto the midi cable and the problem is on the Proteus end. Double check the Proteus unit ID is set to 00. Isolate the computer midi interface and Proteus on the midi cable in question.
Answer: The stock Proteus/1, Proteus/2, and their XR versions pre-date the GM standard and do not contain all of the necessary instruments in the sound ROM's to support the standard. At one time, a "Proto Logic" upgrade was available that could add additional sound ROM's to the Proteus/1 to permit a close approximation of the GM standard. It involved creating some user presets and then using the Proteus preset map to reassign patch locations 0 through 127. Unfortunately, this upgrade is no longer manufactured.
As an alternative, the Creative Labs Sound Blaster "Live!" and "Audigy" are based upon the Proteus chip sets and provides a GM standard patch set. They also support a large selection of patch sets (SoundFonts) for additional sounds. See the SoundFont Catalog. SoundFonts are created from E-mu Emulator sampled sound libraries (like the Proteus). There's even a money back guarantee.
Problem 9: Will Proteus/1 and Proteus/2 presets work on other Emu Proteus sound modules?
Answer: You can load Proteus/1 and Proteus/2 presets into other Emu Proteus sound modules. Whether they will sound as intended depends on the fundamental sound entries contained in your Proteus wave table ROMs.
Each preset in the Proteus unit can be composed of up to 2 fundamental sounds; the primary and secondary. You can view these settings for a particular preset by pressing the "Edit" button on your Proteus and turning the "Data" knob to display the 'INSTRUMENT pri' and 'INSTRUMENT sec' settings. Your Proteus manual lists all of the fundamental sounds contained in your units sound ROMs. Lacking a manual, you can view the fundamental sound names using the Proteus front panel and the following procedure.
The Proteus units have a number of fundamental sounds in common with each other; especially the wave forms and overtone series. The newer units have some of the better fundamentals from the older units.
Experimenting could yield some unexpected and unique sounds. Who knows what you might get if you cross a woodwind preset with a bagpipe!
Use your browser's Back control to return to the previous page.