Support
Looper's Delight
|
Support |
|
|
Ahh, so I guess without soldering directly to the board, and without a complete re-write of the code, it won't happen immediately. But don't give up on your efforts! I (and I am sure several others) would gladly void our warranty (mine is up now anyway), to make this thing do what we want. It is too bad Behringer didn't ask people what they wanted in a midi controller...I think we all would have paid $20 more for more memory, or the ability to assign CCs per patch rather than globally. I have 1 exp pedal to control feedback in the EDP, 1 for the volume of my synth...none left over for a wah. Woe is me. Thank you for your continuing efforts to unravel this thing. Dave Eichenberger http://www.hazardfactor.com > Behringer cut a lot of corners, most likely to maintain some > overall target cost of the unit (which is probably the number > one reason why the unit sells so well, sadly). They chose a > serial EEPROM chip (the main non-volitile storage chip - > permanent memory) which is only 2Kbytes big. This is a $1.50 > chip. For about $3.00 they could have used a pin-for-pin chip > from the same manufacturer which is 64Kbytes big (32 times > the storage for only twice the price). Note for all you > tweakers that this is a tiny surface mount chip soldered > directly on the board, so its not easy for a trained tech to > change, let alone a random user. > > Because the chose a tiny little wimpy memory chip, they had > to jump through a lot of hoops in implimentation to get 10 > banks of midi data storage out of it. Basically they do not > have room to store the data direcly as midi data, they have a > simple compression scheme which only allows for their idea of > usefull midi data assignments. Their data storage routine is > SEVERELY CRIPPLED. There is no possible way to support > multiple midi channels for an expression pedal, no way to > support sending note messages to more than one midi device, > and most importantly, no way to support sending arbitrary > strings from a button press. Unfortunately, the way they've > designed it, without a complete code redesign, this cannot change. > > If they redesigned the firmware implimentation (and this > would be a huge redesign effort) they could support these > things a la the PMC controller. > However they'd still have the upper limitation of 2K of > non-volitile data, which would mean something more like only > being able to use 2 or 3 banks rather than 10. > > I think this is one more case of a marketing department > compromising the overall quality of a final product. By > saving that extra $1.50 on the cost of goods, they forced > their designers to severely compromise the functionality of > the product. Who really knows what would have happened if > they put more memory in there, and released a product that > could be upgraded over time, but was more expensive. Maybe > they wouldn't have sold as many if it was more expensive. Or > maybe there would be lots of people wanting to do esoteric > midi stuff drooling over it and buying two. Basically you > can't have your tea and eat it too - either cost or > functionality, its always a big question. > > Bottom line: Keep sending your ideas to Behringer. They > need to know what their customer wants so they can design > good products. But don't expect results any time soon. > They've designed themselves into a cost cutting corner, which > they could only get out of by issuing new and improved hardware. > > Jon >