Date
1 - 15 of 15
MIDI MERGE issue with UnO2 FCB1010
|
bongoism@...
Hello,
yet another newbie with a potentially dumb question, I apologize if this has been already answered somewhere else, I was unable to find it. I have a M-Audio Oxygen49 controller connected to the MIDi In port of my FCB1010 with UnO2 chip, the FCB is then connected to the MIDI in port of a Roland Octa-Capture that goes into my computer. The FCB works fine, zero issues there but the controller is a disaster. NoteOff messages are only sent if I hit the keys with certain force (otherwise they stay on) and all the faders and knobs are very unresponsive. I checked the MIDI Monitor and fader and knob movement only send the initial and, sometimes, the final position's value. Since there are partial messages going through I am assuming the MIDI MERGE function on the FCB is on. If I am wrong and I need to enable it, how is this done? I can't find it anywhere! If the MIDI MERGE is indeed on then, what is the problem? I read on the UnO2 manual that one of the bug fixes was "the MIDI MERGE problem" but it doesn't say anything else. Any help will be much appreciated, Thank you. Michel. |
|
|
|
Confirm it works fine directly? If so, could be cable. On Sep 30, 2022, at 3:42 PM, bongoism via groups.io <bongoism@...> wrote:
|
|
|
|
ossandust
you might confuse UnO and UnO2 firmware. The original Behringer firmware had a bug in the MIDI merge functionality, which caused hanging notes and other errors. This bug was solved in the UnO firmware upgrade.
The UnO2 firmware was based on the code of the TinyBox, which never had a MIDI merge issue. |
|
|
|
Nick Wall
Where does one by an UNO2
toggle quoted message
Show quoted text
With in the US? I only found 1 site in England.
Thank You kindly,
Nick On Oct 2, 2022, at 1:14 AM, ossandust <ossan.dust@...> wrote:
|
|
|
|
toggle quoted message
Show quoted text
On Sun, Oct 2, 2022 at 6:39 AM Nick Wall <screamingvocalist@...> wrote:
|
|
|
|
EJ SHELDON
|
|
|
It work fine when connected directly |
|
|
|
SlimDude
UNO2 does NOT have a MIDI Merge issue. UNO2 is completely different firmware that must be programmed with a computer. None of the usual FCB rules apply.
toggle quoted message
Show quoted text
Regards, Paul Morris The Music Box Recording Studio (902) 249-2050 On Oct 3, 2022, at 12:32 PM, bongoism via groups.io <bongoism@...> wrote:
|
|
|
|
ossandust
Shortly after the UnO2 release I have been doing some extensive MIDI merge testing. I searched the forums and my email archives but I couldn't find the reason why exactly I did this. I do remember that with a heavy stress test I was able to make UnO2 MIDI merge fail every now and then, while the TinyBox (which has the same firmware code) didn't fail once with the same test. This must be related to the MIDI buffer size which is much smaller in the FCB1010. But the failures only happened when firing a huge series of NoteOn/NoteOff messages at unrealistic speed (max. MIDI speed - much faster than how any human could play notes). Under normal testing conditions the merge never failed.
One thing I don't quite understand - when I search for the M-Audio Oxygen49 online I only find a USB MIDI controller (https://www.m-audio.com/oxygen-v-49) , which doesn't even have a regular MIDI OUT connector. While the original post mentions "I have a M-Audio Oxygen49 controller connected to the MIDi In port of my FCB1010"? |
|
|
|
bongoism@...
you might confuse UnO and UnO2 firmware. The original Behringer firmware had a bug in the MIDI merge functionality, which caused hanging notes and other errors. This bug was solved in the UnO firmware upgrade. The UnO2 firmware was based on the code of the TinyBox, which never had a MIDI merge issue. Ok so, does this mean that the UnO2 doesn't fix the MIDI merge issue on the FCB? |
|
|
|
Nick S
The FCB is a lump of hardware that is supplied by Behringer with code that has a MIDI merge issue (bug). Uno is replacement code that contains a bug fix for that issue. Uno 2 is replacement code that works completely differently and never had the bug in the first place, so it doesn't need a fix.
|
|
|
|
bongoism@...
On Mon, Oct 3, 2022 at 02:18 PM, ossandust wrote:
One thing I don't quite understand - when I search for the M-Audio Oxygen49 online I only find a USB MIDI controller (https://www.m-audio.com/oxygen-v-49) , which doesn't even have a regular MIDI OUT connector. While the original post mentions "I have a M-Audio Oxygen49 controller connected to the MIDi In port of my FCB1010"? Hi, Looks like new models only have a usb port. This is the one I have https://equipboard.com/items/m-audio-oxygen-49-silver, it has a MIDI out port. |
|
|
|
bongoism@...
On Tue, Oct 4, 2022 at 06:05 AM, Nick S wrote:
The FCB is a lump of hardware that is supplied by Behringer with code that has a MIDI merge issue (bug). Uno is replacement code that contains a bug fix for that issue. Uno 2 is replacement code that works completely differently and never had the bug in the first place, so it doesn't need a fix.Ok so, in theory I should not be having this issue, but I am. What could the cause be? |
|
|
|
I've done more testing, replaced cables, plugged the keyboard directly into the interface (it works fine), I changed the path and went from the Oxygen49 into a RC-300 and then to the interface and it works fine so, the issue is definitely in the FCB1010.
If I am understanding correctly, enabling MIDI merge is not needed with the UnO2 chip, right? If I am wrong, how is this done? Assuming it is still possible, how do I boot into global config mode with UnO2 chip since holding the DOWN pedal during power on no longer does anything? Any other ideas? Thank you. |
|
|
|
ossandust
I honestly have no idea. If sending FCB1010 patchdumps works fine, it proves that you can send high volume (sysex) MIDI data to the FCB1010 and back to the computer without problem. No idea why the Oxygen MIDI data would behave differently.
|
|
|