Peter Lindener

I'm still looking for your send of this "PM"..... that I might have never received.... While my weakness might ne a few typos and spelling mistakes..... ...Your right it sure feels like an episode of the twilight zone to me... ... Form Zombies out to do in Newbie talent, before they would have a chance to demonstrate any sense of usefulness... I would like to be productive in this community might you give me half a chance? _peter

Most well educated engineers know that stability criteria and feedback loop gain are intimately related.. We can conjecture that the same might be true in human affairs... Since feedback loops associated with human dialog involve more than just one person, there stability in some sense by the nature of this context, is a cooperative venture.... That is, while one person can always turn down there part of the loop gain equation, from a more holistic perspective it, really takes a more collaborative style of shared responsibility for all involved to mange the Loop gain equation more as a collaboration. I'm not sure what else it would make sense to say here... suffice it to say I'm not sure about how the midiBox community as a whole chooses to greet newbies. -Peter

Ok, I'm quite flabbergasted... While some are looking up the word stochastic...for which I admire them for doing so, not to mention there modesty in admitting that they did so. And others have been so helpful as to point out where on the form I need to add my self to the Bulk order list for the next LPC1769 based midi Box controller... I have been working on figuring out how MidiBox console I/O might be implemented over TCP/IP via the Expresso board's Ethernet interface, and then how this might hook into both Run-time and compile time configurations switches such that Debug printouts can be done on the midiBox's LCD or UART, USB COM, or via ICP/IP TelNet over the Ethernet Link... Not to mention also looking at how Ableton Live's OSC signaling grammar might want some level of standardization within the midiBox community. I find some, who chiming in who might be needing to learn about sending messages of acceptance to newcomers in the midiBox community... I'm sure that for those who do pull there weight in technical contribution in this community, that most all of them will appreciate the very real work represented in the goal I have taken on as described above.. I will rest my case with that, and hope others will also see that the most positive way forward is to ask them self's what they can do that would also be seen as constructive by the midiBox community. all the best -Peter

Can we get an update: Best estimate on when we will be able to order the PCB and Parts for this wonderful new midiBox core logic board?... I notice additional pictures and assembly directions on this new controller's web page. See : http://ucapps.de/mbhp_core_lpc17.html .. I cant wait....NXP Expresso land here we come! Please keep us update on the progress, (perhaps in an appropriate midiBox news thread). -Peter

Dear Hawkeye - Your reflection regarding information theory on average, in the more general un-biased case, is correct. Your offered observation at its minimum clarifies that you are a well educated man. Then, we might then ponder the challenges of sparse statistical sampling within smaller sociological systems. If you would like to cover the topic more thoroughly, from a rigorous information theoretic perspective, I would feel obliged do do so, perhaps in an appropriate thread. -Peter I like your style... You may have a deal there.

Hawkeye - Yes special software.... It runs on a neural network based CPU.... that has an extra deep lexical recursion stack... I guess is still not clear if your current parser has allocated enough stack space. For a good example of what a pair of these CPUs can do when working in tandem over an extended period of sustained execution time see: http://www.votingmatters.org.uk/ISSUE27/I27P1.pdf Should I assume my message targets are being received by resource limited CPUs...( as a good embedded system designer should be prepared to do, when designing new messaging protocols.? -Peter

Dear Wilba - I see your point with respect to running a filler on midiBox newbies....and apparently soldering skills...fills that bill for you... I also can understand the feeling of many in this community that midiBox is far more focused than the Arduino community...and why midiBox people might want to be keeping it that way.... I think you have made your point....even if the marketing oriented perspective that making efforts to bridge with the Arduino community seems to some how outside the more welcoming perspective, you seen less wanting appreciate for the potential up side of bring new, possibly younger people into the midiBox community.... While I'm perfectly willing to put a few midiBox boards together, I would like to reiterate my earlier reflection that I am not asking you to work theoretical problems in the time/frequency dual space... My point with respect to being up and running out of the box... is that many never get to the place where there feeling confident enough to even entertain even inquiring with your community... Any thing we could do that would make it more likely that some of these people would decide it was safe to venture into the midiBox community without wondering if they somehow need to meet the expectations of someone else who may be less accepting...

Dear Nebula - Thanks for sharing your reflections... I do think that midiBox and Ardiuno share very little, and your right on to reflect that the real-time nature of the MIOS platform is in some ways incompatible with the early on learning process... Then to one thing they will sometimes share is new people who are just coming up to speed and also want to do music..... I'm not suggesting the less musical project person would have much interest in a bridge between these two worlds.... only that easing migration by means of finding the common denominators between these two community's might be a good thing... That is, We can note the same trend happening in both midiBox and Arduino community's... more capable ARM CPUs... all I was suggesting is that if I/O Library and Pin routing compatibility efforts were made in coordination with say the people at leafLabs perhaps everyone might win?? see: http://leaflabs.com/ Thanks for the critical thinking! all the best -Peter

I like the Cat the picture you posted... Yes they are kind of nice to have in the studio... No need to worry about the door...unless someone is planing on throwing me through it..... I'm quit able hold my own in more thoughtful, reflective discussion.... I would presum likewise on your count.. all the best -Peter

Dear Wilba - Thanks for providing an example of thoughtful, reflective dialog. You ask for an example of where the Midi_Box core logic board might be useful in a software project all in its own..... Lets say I'm interested in building a very advanced, DSP based synth module. I would like it to have Midi I/O....but the core logic is Open Sound Control based, and runs on a HalkBoard see: http://www.hawkboard.org/ I'm not sure yet who I should thank...but someone with real vision has already pulled Open Sound Control over Ethernet's UDP into the Midi box equation... More and more innovation these days happens on the software side of this equation... all I'm doing is posing the question...if someone feels more at home just on the software side of things, and he is really good there, do we really want to send him away just because soldering is not his strong suit... While I'm not that guy...and am certainly willing to assemble a few extra boards for the greater good of the MidiBox community... why would we want to be less than inviting when good software oriented talent comes knocking on the door? But there is still a deeper reason, people new to all this digital stuff are encouraged to continue when there there efforts end up working...I'm not saying that learning to solder is less than good....only that its a easier to get someone back on track with software...than to undo the mess of a poorly soldered board.... In particular...without good electronic debugging skills... its easy enough for them to just get discouraged and end up giving up.....now the likelihood of this kind of discouragement happening...is far less if they already have some part of there midiBox project up and running...ie. a known good CPU board...is a good start.... The above reflection would be only more so if we welcomed Ardiuno beginners into this community...On that count I offer this reflection as to exactly why on earth I would even make such a seemingly absurd suggestion to welcome those who are just learning what digital logic is all about: Regarding Arduino....it is not like there is much there that maters other than the people who are just starting out. But out of those new people just learning will someday come the future growth of midiBox.... so I would like to invite, send welcoming message...and build a bridge between communitys.... Yes I know that the Arduino platform is nothing much but someday the people (children) who started there will be our future..... That is all that is truly good about Arduino. just my two cents..... others please chime in!! -Peter

Dear Sid ( monster? ) Now let me see... should I reply to your conjectured ranting or go back to getting GDBserver running on the MidiBox over Ethernet?.... The only reason I'm not soldering my own CORE_LPC17 Module right now is that I'm waiting for them to become available....to little "clueless" newbies like me... As for your lovely suggestion of a deal... I was planing on assembling a second midiBox Core_LPC17 while I was at it...and send it back to Thorsten as a justure of good will to the Midi box community so that someone like who might need it to hit the ground running in doing what there best at (writing software) will feel properly appreciated for what they bring ( I will let Thorsten decide who that should be ).... So I will make you a deal.... I'll help YOU write a better Abelton Live driver.... If you will agree to stop flaming at me and go back to doing something more constructive..... There is a very real reason I have written what I have,... If one reads the midiBox form.... I'm not the first to receive notes like the one you just finished sending me.....and in all candidness....by doing so, your not doing the image of the midiBox community any favors... Now you say ""I can't be bothered to hack the Ableton live API""....and I write back I'm to busy hacking the Abelton API to want to be bothered into replying to rants like yours.....so Grow up and learn to Hack the Abelton API...so I can end up helping you to get the job done....sorry that the best you can manage to to is pick up a soldering iron... all the best wishes towards your further empowerment. -Peter Lindener

Hi Thorsten - Maybe you should have linked me to Here: http://www.midibox.org/dokuwiki/windows_toolchain_svn or http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core&s I had already looked where you suggested: See http://www.ucapps.de/mios32_c.html...'>http://www.ucapps.de/mios32_c.html... It could be clearer at the top level web page where to look....maybe this is just about newbie usability... I did mange to find these other links via other peoples posting on the MidiBox form.... so the docs are there...Just not so clearly visible when navigating from the root web pages. Looking real good! all the best -Peter

Sorry for being a newbie...and thus needing to ask questions that might sound dumb for know there way around the MidiBox sight.... can someone clue me in..? 1. I'm trying to understand the details of how MIOS32 is linked into an application binary... 2. Is there a description of how to do software development using the preferred software tool chain(s). 3. How does one go about extending the MIOS32 library's functionality...is there a GIT hub, for submission of code that one might propose could go into the more formal MIOS32 release ?... 4. Does MIOS32 currently have a version numbering system, how does the community handle experimental branching of the source tree. 5. Is the idea that more than one MIOS App may be supported to run concurrently (dynamically scheduled, both in memory), with shared Midi-stream routing, under consideration? 6. Has there been any entertainment of taking MISO towards dynamically linked shared librarys?

Where else does one bring up the topic of making it easier for newbies to aquire known good hardware to start out on..... I can put it together....but its great for first timers to not run into as many problems ( even if due to there own lack of soldering skills )...... I did want to bring up the issue of the availability of prepopulated boards......not because I need them...or have any interest in making $$$s off there assembly...but because other newbies may not have the experience that I have......ie. I like the idea of being welcoming...even for Arduano users who barely understand how slow there little 8 bit chip is..... I hope people don't end up canning me for inviting these newbies over to MidiBox, ARM Cortex-M3 land.......

Dude!.....did your say CAFFEINE!!! Your right PCCNespresso land is so COOL!..... Lazers to...... man were should I shoot first...... we will just vaporize all of them!!!...you say they only know how to play with 8 bit 10Mz controllers..... well show them a trick or two....... I hear you ca use Music some form of a new fangled weapon..... Its true!!...Ive tried it with my Saxaphone....Pacific Ave in Santa Cruz, CA, USA was completely neutralized this morning by means of playing Adele's rolling in the deep on my Alto.... Need more Mountain Dew!! -Peter