bilderbuchi

while we're on this topic, maybe this one is also interesting (all the more so because it's already available afaik): http://www.solid-run.com/products/cubox Named by combining the words 'Cube' and 'Box' and while being less than 2"3 in size, the platform can stream and decode 1080p content, with desktop class interfaces, all in less than 3 Watt (*) and less than 1 Watt in standby. The platform is based on Marvell Armada 510 SoC and includes the following key features - Linux based distributions like Ubuntu, Debian and others Android 800 MHz dual issue ARM PJ4 processor, VFPv3, wmmx SIMD and 512KB L2 cache. 1080p Video Decode Engine OpenGL|ES 2.0 graphic engine HDMI 1080p Output (with CEC function) 1GByte DDR3 at 800MHz Gigabit Ethernet, SPDIF (optical audio), eSata 3Gbps, 2xUSB 2.0, micro-SD, micro-USB (console) Standard Infra-red receiver for 38KHz based IR controllers. No JTAG required. Unbrickable for Developers (**) 100€, so not a 15$ supercheap gadget. including PSU and case (and µSD card), though. projected 15$ price for the rhombus thing is really barebone, full-100k-pcs-volume-discount price, so I kinda doubt they'll reach that..

Sorry to see you got scared away by the trolls. :sad: I'm quite confident you won't get banned by a mod (for what, really?), after all, TKs attitude to the whole thing was positive. Take care, and good luck with your project!

Wasn't that the one used with old floppy disk drives?

I always take my pipe wrench (rohrzange), a small one with flat gripping surfaces (backen), not the heavy duty curvy one. It's adjustable in grip width, so it's actually pretty parallel when squeezing the IDC connector. Works surprisingly well..

I meant hacking a LED wall controller or LED wall itself (and put the leds themselves wherever you want them), then hardware and power, communication requirements probably would mostly be satisfied.

buy a LED wall? :rolleyes: :thumbsup: btw, you missed a "v" in the URL...

Basically, read http://en.wikipedia.org/wiki/Open_Sound_Control - especially the Motivation and Features section. Implementations if you want to know what you could interface it with. I like human-readable addresses, "native" transfer of strings (yeah i now that's probably possible with sysex or nrpn or something in midi), transmission over wireless (potentially to another continent if i wish), control of a variety of devices with your mobile phone/tablet (touchOSC)... What I meant is mapping certain midi messages to OSC messages to allow interaction between osc-enabled and midi-enabled devices/software. like osculator does, for example, just in hardware (therefore, no cpu load on your pc). the missing link also goes in that direction: http://wifimidi.com/. it's also nice to look at libmapper and see what those guys have done: http://www.idmil.org/software/libmapper Mapping Midi/OSC would be useful because most everything understands midi already, but the world is moving forward and more and more devices support OSC (and its innovative use) nowadays - a mapping/translation will enable midi-only devices to still be used in an OSC-centric context.

In this day and age I would also like to see OSC capability on the list of desired features ;-) - could make for a nice hardware OSC<->midi translator/router/mapper. Will you also open source the schems/pcb designs?

http://ucapps.de/ http://www.midibox.org/dokuwiki/ after that, search the forum for any questions.

ha that scope looks awesome :D

ha, so I'm not the only one using these "cases". :thumbsup:

...and that's exactly how I have envisioned it when we discussed it in the other thread... good job! :sorcerer:

frankly, i don't get the arduino-hate and paranoia on here. sure, the approach of this peter lindener was not very subtle (or reasonable), but after a quick ruffling by the community at large he grew more reasonable. also, this thread here shows how it's done , imho (hats off for that btw!). cigue is nothing but corteous, did his homework,... and for the record: i fully respect and understand TK's attitude towards commercial proposals. but i also understand how the midibox community can appear intimidating and abrasive-looking to outsiders at times, so i can see why some threads derailed the way they did. edit: furthermore, the arduino license is far from unrestricted.. a mix of CC attribution-SA, GPL and LGPL.

don't need to automatically convert licenses... many licenses are compatible with each other...also, two projects talking to each other don't need the same license. also, unrestricted commercial utilization is not desired by TK and the midibox community as a whole (and i'd think you'd know that?). why would you want to do that?