Can't modify presets above 60

5 posts / 0 new
Last post
cusp
cusp's picture
Can't modify presets above 60

Hi,

I have read my presets (all) from my fcb1010 (firmware 2.5.1E). That works.

But when I try to send data to the fcb1010, all presets above 60 where not changed.

I can modify presets under 60.

What can I do? Do you have an idea?

Jörg Wrase,

Bremen (Germany)

Mark van den Berg
Mark van den Berg's picture

Hi Jörg,

Which MIDI interface did you use?

As far as I know, the FCB1010's data can only be transmitted as a huge single MIDI SysEx (System Exclusive) message of 2352 bytes.
However, many MIDI interfaces can't handle such long messages. For instance, Behringer's BCF2000 and BCR2000 MIDI controllers maim any SysEx message longer than 1019 bytes.
In the FCB1010 SysEx message, each preset takes up 16 bytes, so the first 60 presets take up 960 bytes. So if you used a BCF/BCR2000 or a similarly limited MIDI interface, this might explain why you could only change the first 60 presets.
However, this hypothesis can only be correct if the FCB1010 actually accepts the already received presets when the SysEx message gets truncated; I don't think I've ever tested this. If the FCB does not behave like this, the cause of your problem could be something else entirely.

Hope this helps,
   Mark.

cusp
cusp's picture

Hi,

thank you for the information. 

Unfortunately it doesn't work. I have used two different FCB1010 and two Computers with two Audiointerfaces (Audio Kontrol 1 by Native Instruments and Steinbergs UR242)

But infact the problem seems to be on the HardwareSide. I've also tryed the software FCB Midieditor - there is the same Problem.

Do you have a workaround for me? Maybe is it possible to "split" the data in the File in two or more chunks? 

Or is there a nother way? 

Jörg

Mark van den Berg
Mark van den Berg's picture

I have used two different FCB1010 and two Computers with two Audiointerfaces (Audio Kontrol 1 by Native Instruments and Steinbergs UR242)

Strictly speaking, the fact that your problem has occurred with two different MIDI interfaces doesn't actually prove that these MIDI interfaces process the FCB1010 SysEx message correctly.

infact the problem seems to be on the HardwareSide.

Given that you've tried two different FCB1010s, it seems unlikely (though not impossible) that their memory chips are faulty in exactly the same area.

Maybe is it possible to "split" the data in the File in two or more chunks?

As far as I know, the FCB1010 only considers a SysEx message containing the full data.

Or is there a nother way?

Perhaps you could first make absolutely certain that the problem does not lie with the sending software (FCB1010 Manager or whatever) or the MIDI interface (or its driver) or a MIDI cable, by verifying that you can loop back the SysEx message to the computer in a setup without the FCB1010.
To test this, connect a MIDI cable from the MIDI interface's MIDI Out socket directly to its MIDI In socket, then start FCB1010 Manager, press "Record" in the "MIDI input messages" window and send the FCB1010 SysEx message: the "MIDI input messages" window should record the looped-back message, with the Length column saying "2352" (bytes). If this doesn't happen, there's an error somewhere. (Since the FCB1010 SysEx message is very long, the "MIDI input messages" window doesn't display the actual bytes of the message; however, if you want to study these bytes, you can save the message via File -> "Save binary file", then open this file in any hexadecimal editor.)
As an alternative to using FCB1010 Manager for this test, you could use the MIDI Tools application: its "MIDI System messages" window allows you to create and send SysEx test messages of any desired length.

Hope this helps,
   Mark.

cusp
cusp's picture

.. and I'm on Windows 10