699 USD
Count me inš
Got to admit this sounds really good, I also love the sound of their odyssey, I think Behringer are killing it at the minute
I must agree with you, the people who buy Behringer mostly are not the poor third country musiciansā¦
Poor artist go with anything they can find to make art, 10 dollar guitar, bucket for drums, what ever⦠for them creativity is not a choice, and having things, it is about something in the hart and mind, and feeling the urge to express it, to communicate it to other.
Donāt let wanting more things destroy that beauty in you!!
Art is in the making always, as long as we are alive.
I just watched the new demo from Daniel Fisher. Iād be all over one of these in lieu of the Perfourmerās true polyphony, but I really need CV per oscillator.
Guys, how do u set up the desired midi channel??
Thanks!
Also is there a user manual? Not quick start one.
Can probably use the synthtribe app ( links will be on behringer site ). ⦠this seems typical and most their synths.
Otherwise I have no idea.
Hi there,
hereās a demo video of the MonoPoly with some Patches for Ambient, Techno and Electronica. Maybe you find it useful:
Sounds fantastic! So much character.
Got mine in today! Itās a beautiful machine and I love how it sounds. Thereās that weird gap in the middle keys that isnāt present anywhere else. Is that anything to be concerned about?
Looks like a very close fit on the left. If it doesnāt actually rub its probably ok. I would ask for a replacement if it does. (Assuming you already tried pushing it the other way).
Is it ok to try and move it on my own? Appreciate the response!! Thank you.
I just checked some of my keys. They all have varying gap sizes between keys, but none quite as bad as the one in your pic. I can push them sideways until they hit the next key and they just spring back, so I doubt that what I suggested would make much difference, but pushing it to the right until it touches the next key should not do any harm and would still be worth a try.
Looking at a photo of the Monopoly at Sweetwater. It looks pretty close to exactly the same. Iād say thatās probably just the way they fit together. If it plays fine it is just a cosmetic issue.
Anyone else found the following problem with the poly arpeggiator mode?
In the original Korg MonoPoly, setting the arpeggiator to poly mode and turning the clock (MG2) all the way down allows you to play round-robin style where the oscillators trigger in sequence. However on the BonoPoly this method just retriggers VCO1 every time.
The correct behaviour occurs when the unit is set to USB-MIDI clock source, but not when using the internal clock, so I suspect it has something to do with how the clock is reset upon key press in internal mode.
Internal clock mode (incorrect behaviour): internal clock - YouTube
USB-MIDI clock mode (correct behaviour): usb midi clock - YouTube
Original Korg MonoPoly (intended behaviour): Korg MonoPoly Tutorial and Demo - YouTube
Iāve submitted a support ticket to musictribe in the vain hope that theyāll fix this via firmware update but maybe if a few more users piled on there might be a better chance. Personally I think this is a killer feature of the original and a massive shame it doesnāt work here 
It works fine with internal clock on mine, but the clock source needs to be set via the app every time you need to change it (āautoā-recognition does not work).
Also, did you update the firmware?
Yeap set to internal clock and latest firmware 1.0.8. To be clear the arp cycles through the oscs in the usual āhold down a chordā way, but the trick with MG2 set to minimum and playing a melody manually does not work the same way a Korg does. The link to once upon a synthās video shows what I mean. Does yours work like that?
Unfortunately Iām away from it until next week. I believe I did get it to behave as described, but canāt confirm right now.
Did you also check if:
Latch: off
Trigger: single
Autodamp: on
Are other clock or trigger inputs interfering? (Unplug)
The manual says that the first arp struck requires MG2 > 0.
An update if anyoneās interested: Iāve been in contact with Behringer support and theyāve provided me with a beta firmware that fixes this issue! I assume it will be made public some time soon. Honestly amazed that a large company would dedicate development time to one whinging user 
Thatās great service! Out if interest do you know who you dealt with? The reason I ask is Iām sure when they were having firmware issues with the RD8 there was a forum user (a different forum) named Jamie who Iām sure either went to work for them or was involved in some way in addressing the issues.
