PC2 SERIES OS v4.00 UPDATE

Version 4.00 Release Notes

- v4.00 is required to use the new Classic Keys (ROM2) optional ROM Block

*Please read the Version History section below for a complete OS revision history.

System Requirements

- any PC2
- v2.00 or greater of the system Boot Loader

Note: The PC2 receives its system updates through MIDI sys-ex (i.e. playing a specified MIDI file containing system exclusive data into its MIDI in port).

We normally recommend doing a Hard Reset after installing a new file. Therefore, if you have any user created Programs or Setups, you should do a system exclusive back up dump of the memory before updating. Please read "Dumping Objects" on page 4-4 or 4-5 (depending on model) of your Musician's Guide for more info.

Details on how to update your PC2 using the Boot Block can be found in your manual, starting on page A-3 or A-4 of your manual (depending on model), however, for convenience sake, we have also detailed the upgrade procedure below.

Tools Required to Perform the Update

- computer (Mac or PC)
- software sequencer / MIDI File Player
- MIDI Interface
- (1) MIDI Cable
- .MID OS file to be installed (the file included in this download)

Please Note: We have tested the following software applications and know that they work correctly for sending sysex to the PC2. We have also tested many software applications that do not handle sysex correctly, so for this reason we strongly recommend using one of the software programs that we have listed:

PC PLATFORM:

Shareware/Freeware:

• Windows Media Player. You need to have version 5 or later of Media Player - older versions will not work correctly. Windows Media Player can be downloaded at http://www.microsoft.com/windows/windowsmedia/en/Download/default.asp

  If you have not used Media Player before to control an external MIDI device, you may need to configure it. Go to the Control Panel (Start - Settings - Control Panel). From Control Panel, select Multimedia, then Midi. Now you can choose your midi output instrument.

  Please note that Alesis Freeloader, which we recommend for the Mac, is buggy in the PC version and will NOT work correctly.

Commercial software:

• Logic (from EMAGIC)

MACINTOSH PLATFORM:

Shareware/Freeware:

-OS X

• There are currently no native OS X freeware/shareware apps that we have tested that handle this sys-ex dump correctly. OS X users will have to boot under OS 9 (if possible) and use shareware below OR use a commercial application (see below). We are currently searching for a free/shareware app in OSX that will work properly.

-OS 9

• MIDIGraphy 1.4.3 (older versions tend to crash w/OS 8 and 9), can be downloaded at http://member.nifty.ne.jp/mmaeda/e/macos.html
• Alesis Freeloader can be downloaded at http://www.alesis.com/downloads/software/freeloader

As of this writing, Freeloader appears to work only with older Macs with a serial port - it does not support USB MIDI interfaces. If you have a USB MIDI interface, you should use MIDIGraphy. If you are using Freeloader, you need to select "Any File Type" in the Edit Menu, instead of "MIDI Files" (For some reason, Freeloader does not recognize our .MID files when the "MIDI Files" option is selected.)

MIDIGraphy also normally supports only serial ports. But if you use OMS and have it configured for a USB interface, you can select OMS as the control with MIDI Port parameter in the MIDI menu of MIDIGraphy and it will use the USB interface.

You may need to increase the memory allocation for MIDIGraphy in order to open and play the file. Click on the MIDIGraphy icon, then hold the command (apple) key and press "I", and then select Memory from the pull down menu in the window. We suggest setting the minimum size to 8 meg (8192k).

In addition, you need to hold down the Option button when selecting Open from the File menu, or MIDIGraphy may not see the .MID file.

Please note that Windows Media Player, which we recommend for the PC, is buggy in the Mac version and does NOT work.

Commercial software: (OS9 or OSX)

• Performer (from Mark of the Unicorn)
• Logic (from EMAGIC)

Installation Procedure

Boot Block

The PC2 boot block lets you install new software and factory setups into Flash ROM. The boot block also provides hard reset and diagnostic options. Execution of any function in the boot block may cause or require a hard reset causing erasure of the setups that you have created. To save them, back them up using a MIDI Sysex dump as described on page 4-4 thru 4-7 of your Musician's Guide.

1. Connect a MIDI cable from the MIDI Out of the computer's MIDI port or interface to the MIDI In of the PC2.

2. Launch the sequencer application.

3. Start up the PC2 in Boot Block mode:

Power up the PC2, it displays "Waiting for scanner" then displays "Please wait" after a couple of seconds. When you see "Please wait" press and release the 'Panic' button (EDIT button on RACK models).

The Boot Block version number will be briefly displayed. If the version is less than v2.00, you will need to update the Boot Block before proceeding. Need be, please download the latest Boot Block revision from our PC2 Boot Loader page and install it, then continue here. If you have v2.00 or greater of the Boot Block already, proceed.

After the boot block message banner and version number is displayed, you will see:

Main menu Install engine_    

4. Press Enter/Yes, you will see:

Install engine       via MIDI_

5. Press Enter/Yes again, you will see:

Waiting for MIDI    _

6. Open the PC2xxxxx400.MID file using the sequencer program. Start playing the MIDI file from the sequencer. While loading, the bottom line of the PC2's display will show:

SYS3-0 file 1 of 1  segment X of Y_

...where X starts at 1 and increments with each segment up to Y segments. If the display continues to show "Waiting for MIDI" after starting the sequencer, stop and restart the sequence.

7. It will take approximately 20 minutes to completely load at which point the bottom line of the display will show "Done".

8. After you have completed loading the file, press the Cancel button twice to get back to the main boot block menu. With the cursor buttons beneath the display scroll to the Hard RESET menu item:

Main menu Hard RESET_        

...and select it by pressing Enter. As mentioned at the beginning of this document, this will erase all user created Setups, so you should have backed them up previous to installing the new files.

You will see:

Erase RAM objects? ___No____Yes___

9. Press the right cursor button (>) to execute a hard reset; the PC2 will restart with the new operating system and setups.

10. If you also have the Polyphony Expansion Board (PCX-1), you will need to update it to v4.00 as well. If so, repeat all of the above steps using the appropriate v4.00 Polyphony software .MID file.

Done.

Troubleshooting Tips For Updating Problems

Because a number of people have reported having problems when trying to update their unit, we've done quite a bit of testing, and studying PC2 upgrading process. Because of the wide variety of MIDI interfaces, MIDI software, and computer configurations, it is impossible for us to test all possibilities. However, in virtually all cases where we have found problems, they were tied to software problems, interface/driver issues, or configuration (within the computer) problems.

PC2 ISSUES

¤ The PC2 itself is very tolerant of timing. You can throw almost anything at it, and it will come through. It's got enough processing power to receive MIDI and use it to control a 64-voice synth in real time while managing the user interface at the same time. When the boot block is receiving data, all this processing power is available to handle the data being received. Needless to say, there is horsepower to spare.

¤ The PC2 does need several seconds between segments, which it uses to program the Flash ROM. The PC2 boot block will ignore any MIDI it receives during that period. If you send a file without sufficient space between segments, some segments will be missed. After the entire file has been transmitted, the PC2 display will still say "Segment M of N;" it will never read "done." This might occur, for example, if you crank up the playback tempo too high. It could also happen if the MIDI interface is sending the data too slowly. However, if you send the file repeatedly, after two or three attempts all segments will get programmed, and the display will read "done."

INTERFACE AND SOFTWARE ISSUES

¤ A variety of interfaces, including the newer USB interfaces work without problems. However, many of the early drivers for USB interfaces did not handle sysex messages correctly. You should make sure you have the most current driver/extension for your interface, especially in the case of USB interfaces.

¤ A variety of interfaces and software don't work. In each case we've examined, the data was getting corrupted before it even got to the PC2. Certain interfaces work with some software but not with other software. Sometimes the interface or software needs to be configured a certain way before it will work.

¤ In our MIDI files, each segment of data is split up into smaller packets. Without these packets, Media Player wouldn't work. However, the packets confuse some software, such as Cakewalk Pro Audio 8.0. Note that, with or without packets, the MIDI file itself is in full compliance with the Standard MIDI File specification.

RESOLVING VARIOUS INSTALLATION PROBLEMS

¤ Firstly, using the recommended sequencer software (listed above) can solve many installation problems. Unfortunately, we have observed that many popular sequencers corrupt certain sysex events in Standard MIDI Files.

¤ If the file begins transmitting, but the display still reads "Waiting for MIDI," none of the MIDI data is making it to the PC2. Check your cables and connectors. Also check any configuration software you might have which controls whether or not MIDI data is being sent out the MIDI Out port.

¤ If the display reads "segment 1 of N," and continues with this display for more than about a minute, data is being dropped. If the display reads "data error [ED0] checksum error," the data is being corrupted in transmission. In either of these cases:

* Use one of the recommended sequencers. Be sure to read the specific notes above that apply to the different shareware programs.

* Bypass any MIDI mergers in the data path. MIDI mergers can corrupt sysex data.

* Bypass any other MIDI gear in the data path that might be corrupting the data.

* Some MIDI interfaces can merge the MIDI outputs of multiple applications. Disable any such features on the MIDI interface.

* Some MIDI interfaces allow you to patch MIDI input channels directly to output channels. Disable any such patches.

* Under Windows, make sure the latest drivers are installed. On the Mac, make sure the latest extensions are installed for your MIDI hardware and software.

* Use a different MIDI interface. We have seen reports that some USB interfaces still do not handle sysex messages correctly, even with their current drivers.

¤ If the entire file transmits, but the display on PC2 still displays "segment M of N," some segments are being received but others are being dropped. Most likely, the sequencer is sending the segments without pausing long enough between each one. In this case:

* Do everything noted above.

* If using a sequencer that allows you to adjust the tempo, reduce the tempo. 120 BPM is nominal.

* If using a sequencer that requires you to transmit the sysex manually, make sure you send the sysex messages one at a time. (Note that none of our recommended sequencers require this.) Each sysex message contains the data for one segment. After the PC2 receives each one, it will say "Programming M of N at XXXXXXXX" for up to 10 seconds (or as little as 0 seconds). Make sure the display returns to "segment M of N," where M is now one larger than it was before. At this point, the PC2 is ready to receive the next segment.

* Resend the file from the beginning. After several attempts, the PC2 will eventually get all the segments, and the display will read "done."

Version History

• Version 3.10

  This version contains a few minor bug fixes and improvements to the diagnostics.

• Version 3.00

  Most of the changes in this version apply to the Orchestral ROM block option. But even if you do not have this option, there are a few new features, a few bug fixes, and changes to some of the preset objects. These features and fixes are documented in the Version 3 Supplement Manual.

  Please note that the ROM Demos have changed, since version 2. There are still only two demos, as opposed to the original four, but they are now Fandango & The Girl With The Flaxen Hair (Fandango replaces Elements). If you install the Orchestral ROM Block option, an additional demo for the ROM block will appear.

• Version 2.10

  This version adds an additional 128 preset Programs. (The version 2.0 Setups file must be installed along with the version 2.10 Operating System in order to have access to these new presets.) In addition, several new features have been added.

  The Version 2 Supplement Manual contains information on all new features, plus documentation on the new presets. Also included is a list of controller assignments for all the preset Setups, which was never included in the original PC2 keyboard manual. In addition, a list of changes and bug fixes added since version1.0 is documented. The manual is in .PDF format and can be viewed with Adobe Acrobat. You can download a free copy of the Adobe Acrobat Reader from the Adobe web site: http://www.adobe.com.

  Please note that the number of ROM Demos in the instrument has been reduced to two (Elements & The Girl With The Flaxen Hair), in order to make room for the new preset programs.

• Version 1.50

  The following new editing parameters/features have been added:

  1. Capture MIDI Values. This parameter has been added to the series of Init Value parameters, found in the Timbre Menu when editing a regular (non-KB3) program. This parameter allows you to capture the current values of the controllers that correspond to the controller numbers that are used for setting a program function to a specific amount when that program is called up.

  For example, In program 90 Meteor Strings, Slider D is assigned to the Lo Pass Filter Resonance. The Init Value is 66 (approximately halfway up). So when you first call up the program a value of 66 for controller 13 (the default assignment for Slider D) is sent. If you would like to change this to a different setting, you can simply move the slider till you find the amount of Resonance you want, then go into the Timbre Menu, scroll to the Capture MIDI Values parameter, and then press Yes (Enter). Your new setting will be retained as the Init Value for controller #13.

  2. Several parameters have been added to the KB3 edit menus. All of the functions previously accessed by pushing the front panel buttons now have edit displays. Pressing the buttons will still change the values but they can also be changed by scrolling to the parameter and changing it in the display.

  In the Timbre Menu: Chor/Vib Switch: (Off/On) & Rotary Speed: (Slow/Fast)

  In the Envelope Menu: Perc Switch: (Off/On), Perc Volume: (Soft/Loud), Perc Decay: (Slow/Fast), & Perc Pitch: (Low/High)

  The following bugs have been fixed:

  1. Previous to this version, you might encounter a "Low Battery" message when powering up the instrument. In fact, the battery was fine but the battery voltage was misread on power up. This has been fixed, and you should no longer see a Low Battery message unless the battery is actually low.

  2. Treble EQ. The old values of +11dB and +12dB values were not correct and have been fixed.

  3. Compare mode is no longer allowed if there is not enough memory available. Also fixed a problem with the wet/dry mix display for Setups when using compare.

  3. Fixed a problem in which sysex dumps were not allowed due to the reserved memory being used. Now sysex dumps are never disabled.

  4. Fixed a bug where the cancel button would not work properly while in numeric entry on some menus.

  5. Fixed a mono mode problem in the "Vox Lead" program, when layer 4 was enabled.

• Version 1.07b (beta release)

  1. Previously, when editing effects and changing parameters only (not algorithms), the changes would remain even after you left the editor. The proper effects would not be re-loaded until you reselected the program change (either from the front panel or via program change message). If you just left the editor and re-entered the editor without a program change, the values in the display would not match what you heard.

  Now the effects will always reload when leaving program or setup edit.

  2. Previously, the FXA and FXB routing display would not update when changing zones in the Setup editor unless you were on one of the FX edit pages. This problem has been fixed.

  3. Previously, changing between Panel and Auto mode could cause the effects display for Panel mode to be out of synch with what was actually heard. You can try this before you update by making a new panel effect, switching back to auto, change the program, go back and re-select panel mode, then look at the effects edit.

  Now when you switch from "Auto" to "Panel", the effects now change immediately instead of waiting for the program/setup change.

  4. Previously, the Setup effect wet/dry and routing values were incorrect when creating an auto split/layer from an internal voice or KB3 program.

  Now they all default to the programs wet/dry for each zone. The routing for zone 1 is kept, while zones 2-4 are set to FXB only.

  5) Previously, the "Cancel" from MIDI receive mode would not always bring you back to the last program before entering MIDI Receive mode, but would sometimes change back to the last remembered before a mode change.

  Now, if you change programs on the internal setup zone 1 channel while in MIDI Receive mode, then Cancel, the PC2 will keep new zone 1 channel program. If you change to a KB3 program on the KB3 channel while in MIDI Receive mode, it will keep the new KB3 program. Both of these only happen if there is a valid program at those locations. If you select a valid KB3 program at any point and then select an internal voice program, both of these programs will be the first program to appear when you switch to their modes. All operations on other MIDI channels will not change the reverted programs.

  6. Previously, the Global FXA->B from internal voice edit could change it's value even when not on an effects channel.

  Now the Global FXA->B from internal voice edit will no longer work if you are not on the effects channel. Instead, it will display Ch#, with # being the effects channel.

  7. Previously, entering and exiting an internal voice edit would load the effect associated with the effects channel even if the current channel was not the effects channel and the current effect was not what belonged to the program on the effects channel.

  Now when changing effects channels, the effects associated with the current program on that channel will be loaded.

  8. Previously, controllers 68,93, and 95 would sometimes get cleared when hitting the panic button, inadvertently changing the wet/dry values and programs that use controller 68.

  Now these controllers are only cleared for KB3 programs, so wet/dry values should be maintained even after pressing panic.

  9. Previously, the sustain pedal "catch" did not work properly for certain sounds. This has been fixed.

  10.Previously, that use "System" tempo would sync to the internal clock but not to an external clock.

  Now, these effects will also sync to an external clock. However, on some delay based effects, syncing to an external clock may cause clicks.

  11. The PC2 will no longer paste effects that do not exist. (In v1.0, the way to cause this to happen is to paste effects without copying them first.) This puts an empty effect in the program or setup. In addition, if you somehow manage to get empty effects in, the system will no longer crash when trying to display the values.

  12. Compare now works when you are creating a setup from an internal voice.

  13. The PC2 now starts with program 0 Stereo Grand at power-up.

-END-