# Behringer Pro-800

**URL:** <https://forum.electra.one/t/behringer-pro-800/2378>\
**Category:** Instruments\
**Created:** [September 10, 2023, 5:38pm UTC](https://forum.electra.one/t/behringer-pro-800/2378 "2023-09-10T17:38:23Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![NewIgnis](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/newignis/32/767_2.png) [@NewIgnis](https://forum.electra.one/u/NewIgnis)\
**Post date:** [August 27, 2025, 4:31pm UTC](https://forum.electra.one/t/behringer-pro-800/2378/14 "2025-08-27T16:31:37Z")

</div>

Nice find, that Lindy HUB. what’s its price?

As said, you didn’t pick the easiest synth to parse. The good news indeed is you can parse using the standard parsing tool that is built into the E-1 .

The bad news is that Pro-800 isn’t using a 1 byte = 1 parameter approach, but is using an 8 bit approach for some parameters that can’t be placed in a single MIDI byte which lony offers 7 bit space for data.

This is typically resolved to spread 7 parameters of 8 bits over a grou p of 8 bytes, where the first byte containts the most significant bit of those 7 parameters, and the other 7 bytes then contain the 7 least significant bits. However Behringer made it extra complex, because in most cases the lowest bit didn’t even come into play, so I ignored it anyways.  
How dit I know? well be observing the traffic coming from the Pro-800 via the E1 capturing mechanism, combined with the MIDI info we get from Behringer or other sources, and then combined with the gained experience of parsing synths.

Take a look at the example below, which shows how the FINE ENV Amount CC7 paramter 89 is parsed out of a most significant bit, followed by 6 less significant bits, and skipping the 8yh lowest bit.

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/a/a8a460c8619d8bcc03d54df10848444bad5cc772.png)

I made a series of articles in this forum about parsing MIDI with a step for step approach.

> [@Adding patch parsing to a preset. Step by step](https://forum.electra.one/t/adding-patch-parsing-to-a-preset-step-by-step/2117/3):
>
> Step 2. Make the E1 aware of the SysEx response In this case, the manual details how the response’s header and payload looks like. We’re not always that lucky. But even if documentation is available, bear in my there are almost always errors in it. So while using it, be sure to check if it corresponds to the reality. In this step, we make sure the E1 is considering the SysEx response for parsing. The manual states the response looks as follows: [image] Let’s compare this with the response w…

. Might be of help to you.

I usually tag my presets as well with ‘patch parsing’, so that might help you find other examples on how to parse.

---

_[View the full topic](https://forum.electra.one/t/behringer-pro-800/2378)._