Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: jx8p and dw8000

2011-11-10 by Mark v.d. Berg

--- In bc2000@yahoogroups.com, "nicknak110756" <neil.b.dunn@...> wrote:
> im having an issue with the JX8p for some reason.
> the one i downloaded via the file section is a midi ox file and i have sent it via that programme and i can see it loading into the BCR but the synth is not responding at all.
> do i need to convert it and send it via BC manager, if so how do i do this conversion?

I can't say straight-away what's causing this.
In any case the most fundamental question is whether your BCR accepts the preset data.
If it does, the problem lies with the preset data itself in connection with your synth - I can't help you with that.
However, if the BCR does NOT accept the preset data, here are a few tips for making it do so:

I've noticed two things about the JX8P's syx file:

1. It expects your BCR to have its global Device ID set to 1, or else your BCR won't accept the data.

2. It stores the preset data in preset 16. (So after a successful upload, the display should say "P-16".)

Concerning your questions about BC Manager:

If you wish, you can convert bc2 files to syx files and vice versa via BC Manager's File -> Convert routines (from the main window).

However, this isn't necessary:

First of all, the bc2 file also uploaded by the author of this patch already provides a straightforward conversion from the syx file (but, "obviously", without the Device ID).

Furthermore, BC Manager can work with both bc2 and syx files natively.
So you can simply open the bc2 or syx file in BC Manager (from the B-Controls window: File -> Open or Import), then send the preset to your BCR. (If BC Manager has recognized your BCR, this should automatically use the correct Device ID.)

Hope this helps,
Mark.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.