Damaged .syx file ?

This syx file isn't actually damaged, but it contains data that make working with the BCR difficult after you have uploaded this file to the BCR:

1. This syx file changes the BCR's Operating Mode to U-2, which (at least on Windows) may invalidate the current MIDI I/O devices: you'll probably have to restart any running applications (such as BC Manager) to adapt to the BCR's new MIDI I/O devices.

2. This syx file contains 32 memory presets; the preset to control Tranzistow is in memory preset 1, and memory presets 2-32 are empty. (So when you send this file to a BCR, all its existing memory presets are overwritten, which may well be undesired!) On the other hand, the syx file does not contain data for "preset 0" (the "temporary preset"), which always determines how the BCR is functioning. So after uploading this syx file to the BCR, even though the display says "P- 1", you have to press the PRESET > button (this temporarily selects preset 2), then the PRESET < button, so that the Tranzistow data in memory preset 1 is copied to preset 0.

For the reasons stated above, it's not a good idea to send this syx file to a BCR. Instead, it's much better to open this file in BC Manager (in the "B-Controls" window via File -> Open). Then in the Presets window you can copy preset 1 to preset 0, and have BC Manager send preset 0 to your BCR. (Note that BC Manager uses a bidirectional sending procedure, which is faster(!) and more informative than the unidirectional procedure used by MIDI-OX.) Another good thing to do is to have BC Manager export preset 0 to a bcr or syx file (in the Presets window: File -> "Export selected preset(s)"): this file will then only contain the "bare" preset data, rather than all those empty memory presets, and no global setup data like the operating mode.

Hope this helps,
   Mark.