Jump to content

audiocommander

Frequent Writer
  • Posts

    1,358
  • Joined

  • Last visited

Everything posted by audiocommander

  1. Hi James, You can only connect up to 2 LCD displays (if the used application supports this). But you can easily show the output of each AIN on one display using custom Level characters. Have you seen the "LED-Pots" from MIDIbox64E? http://www.ucapps.de/midibox16e.html Regards, Michael
  2. Hi, mb64 is written in ASM. this sounds like you possibly want to program your own application. see here: http://www.midibox.org/dokuwiki/doku.php?id=application_development and here: http://www.ucapps.de/mios_c.html there are lots of examples on the bottom of that page, for example like this one: http://www.ucapps.de/mios_c_send_din.html If you know a little bit C or any other programming language, this should be no big problem. Although you should of course consider that mb64 has many cool features your own app won't have (at least not until you re-program these. You might also want to check out some C-based applications from the ucapps download section and adapt these. regards, Michael
  3. it's been mentioned a few times in the SpeakJet thread: http://www.midibox.org/forum/index.php?topic=2870.msg64528#new the voice sounds a lot poorer than the speakJet, but it's synth capabilites are somewhat better. since the connection and the serial transmission mode is similar to the speakJet, it should be easily connectable and usable with an adapted IIC_SpeakJet_Module. However, as the commands are quite different from the SJ, one first has to port the kII speakJet driver application to the SoundGin command set. I planned to do that somewhen (I already have a soundGin here), but I want to complete kII first (still got to do some stuff with the synth section); so it's definitely not something I would wait for ;D ... but everyone's free to start porting the application :) cheers, Michael
  4. Hi MidiBox mates, I found some nice looking new LCDs at Reichelt/Germany for about 12 EUR + optional Background LEDs: http://www.reichelt.de/?ARTICLE=60633;LINKID=1024 (datasheet available from there) The LCDs have a ST7036 Controller, which is instruction compatible to HD44780 and should therefor be compatible to MBHP/MIOS: http://www.lcd-module.de/eng/pdf/zubehoer/st7036.pdf What I like about the modules, is the variety of available colors for a reasonable price and they are quite compact. What's also very nice, is that you can simply plug them onto a PCB (with or without background LED-module) and solder very easily. They can be operated with 5Vs and (some additonal Caps required) also with 3.3 Volts! As these modules provide 4-bit and 8-bit modes as well as and SPI-Interface, I'm a bit lost with the connections and what I should do with the Background-Illumination... anyone knows how to connect these? And do I need to connect "V0"? I thought I better try asking before killing my first module :) Any comments welcome! I attached a drawing I made, to make the connections clearer:
  5. ... I can see the PDF, but I can't find any note about the used controller. You can also check out this page to find more compatible controllers: http://www.midibox.org/dokuwiki/doku.php?id=hd44780_compatible regards, Michael
  6. yeh, what a pitty. I usually copy all my important stuff to a second HD, burn DVDs often and additionaly store my most important files on my gmx online storage drive (just in case my house burns down... that can happen too!) the german GMX freemailer has a 1 GB online storage for all accounts ;) and googlemail is also nice to keep some data, although this is of course not very secure for private data; I'd not trust this v much even with encrypted attachments Cheers, Michael
  7. hehe... ;D my kitty usually prefers to sleep in my opened books right on my desk... and I simply can't make her go 'cause she's always looking so nice and peaceful (not that young like yours but nevertheless a cutie) That's why I mostly use internet lookups nowadays ;D
  8. I haven't been around here that much as usual the last week, but I didn't notice any problems (neither from germany nor from england) Cheers, Michael
  9. i'd be willing to help, but it's all a bit stressful atm :-\ also: I'm not really a perl hacker in the meanwhile... But I think everything's good that helps making mbhp platform independent... cheers, Michael
  10. Hi, well, I can't give you any universal answer to that, because every sensor is different. In case of the Sharp sensors you can connect the Vout to the Ain Pin. But you cannot directly mount a resistor the the AIN. Just search this forum or look to the Wiki Page (Sensors). I answered this question several times. yeah. "V" is good. They have a very thin operating "line". But again: you have to try this and find the right positioning. I would not mount it before being sure it works well. There are - of course - also other light sources that could interfere with the sensors; everything that's coming near the infra-red light spectrum. Yes, it's hard to find these. I get them from Conrad. Very expensive, but... :-\ You could also solder cables directly to the connectors and make your own connectors at the end of the cable. Regards, Michael
  11. Hi. This is basically what I'm doing since quite some time now, though I don't use normal inputs like Keyboards but sensors. -> The ACSensorizer 0.4.x I wrote (tba) has most of the realtime features you are describing (Quantisation, Harmonisation). -> AFAIK the MBSeq has a Chord Function. -> There should be an MB app around here that's called Magic Chords or something, a stand-alone arpeggiator box. Besides that, in the meanwhile most of these tasks are easily possible within Ableton Live. Regards, Michael
  12. there's a german topic and Warenkörbe for the Core and the SIDs. Thorsten said he would upload the files to his page once there are a bit more... http://www.midibox.org/forum/index.php?topic=8503.msg59427#msg59427 regards, Michael
  13. I know this page from the past, but 77$ for a sensor that's available for 15$ in a normal electronics shop... wow. :o IMHO they can sell their i-CubeX for whatever price they like, but to sell a normal sensor with a 700% increased price is a bit :-X @stryd: these links are pretty cool. FSR's and Flex-Sensors are hard to find... ...and ACSensorizer 0.4.3 is completely finished, I'm testing it these days, but I'm pretty confident it'll run fine over a longer period of time. So I expect a release as soon as I'm back from the next exhib (end of May) ... (And I'm really proud of the new features. I fear this could be a real killer app, so I'm not the only one anymore making my kind of music :-\ ;D )
  14. Hi Bill, you can either use MIOS_GPCounterGet() which is incremented every millisecond or setup your own timer. Both can be found in the function reference. Hope this helps, Best regards, Michael
  15. ahh... ok :) yes, this should work fine. maybe it would also work if your pedal has a higher resistance (eg 50k), but that could have an impact on the other pots. You should be careful however if it has a lower resistance than 10k. Best regards, Michael
  16. du müsstest einfach nur deine Verkabelung schlau anlegen. z.b. hat der Electribe (zumindest meiner) einen thru, (allerdings muss der Out dann zum Kp2 oder 303); oder du benutzt ein USB Midi-Device mit mehreren Outputs (gibt's schon sehr günstige mit 1xIn, 3xOut; das teuere sind i.d.R. mehrere Inputs), damit könntest du die Clock parallel an alle drei Geräte senden. Grüße, Michael
  17. :o wow! congrats Wilba! I'm awestruck... Cheers, Michael
  18. Hi canrull, I just tried this, it's actually a lot easier than I expected 'cause you don't have to mess with MIOS-Address ranges ::) You just have to call MIOS_EEPROM_Read or Write (or Page-Acess). The adress range is simply from 0x00 to 0xFF (PIC18F452). // two chars unsigned char bank = 12; unsigned char patch = 127; // save to EEPROM MIOS_EEPROM_Write(0x00,bank); MIOS_EEPROM_Write(0x01,patch); // read from EEPROM bank = MIOS_EEPROM_Read(0x00); patch = MIOS_EEPROM_Read(0x01); Best regards, Michael
  19. ahh, ACSensorizer 0.4.3 is ready :) I just finished the most important updates (Quantizer, Harmonizer, Patchname-Support, Auto-Master/Slave, just to name a few). I'll make some testings the next days and if I can't find any errors, I'll release a first beta-version. Cheers, Michael
  20. jipee, this is my first crosspost ;D (thanks to stryd who pointed me back to this old thread) I think you might be interested to hear that. 25$ for 4x4 buttons incl. PCB sounds like a fair pricing to me... chers, Michael
  21. Hm... looks nice, but indeed... 90 bucks phew... I mean that's nearly 1/3 the price of a fully assembled microKONTROL and there you have the same but illuminated (16 velocity sensitive pads) plus case, encoders, sliders, joystick and keyboard. and: you need 16 AINs. Another question is if the resistance is in a useful range for MBHP to be directly connected to the AINputs. I know this is a bit offtopic, but I have the impression that the button pads at sparkfun are now cheapter than before? 4x4 Rubber Button Pad 10,- $ 4x4 Button PCB 15,- $ Not velocity sensitive but illuminateable :) And maybe one could mount additional FSRs below the pcb... just a thought... Cheers, Michael
  22. I have absolutely no idea what you mean with that sentence, but you can see which parts of the GUI can be remote-controlled in Live if you enable the "MIDI" mapping button on the top right of the Live-Window. Generally spoken, if you're working with a PC and especially with Ableton Live, you can assign nearly any action to nearly any Controller Number on all Channels, therefore it should be no problem to do whatever you like when Live receives CC#7 (VolumeChange or any other Midi-Message) on Ch xy (1..16). And – if this is not suffient –, there are programs available to filter your midi-messages and enable you to convert one message to another. I recommend MIDI-Pipe for the Mac, but there should be similar program for PCs or Linux. Regards, Michael
  23. should be possible, I think. Preferrably the sensor selection (1 to 8 ) Edit: hmm, not so sure anymore. might work, but who knows if an encoder can be simulated by two buttons? I haven't tried... If it does not work, well, 3$ for another encoder does not seem to be harder than changing the code :-\ Besides that, the complete GUI can also be controlled by Midi. There's a remote control application shipping with the next beta, unfortunately only for Mac OS X...
  24. Hi bosone, theoretically yes, practically every circuit needs to be adapted, so the voltage can be measured. As you know, that's quite easy for resistance based sensors, but that may not be very straightforward for capacity based touchpads (like the iPod has one). You cannot connect these directly to the AINs, but there are some ICs to help you converting capacity input to voltage ( http://www.audiocommander.de/blog/?p=66 ). However I have never tried this with touchpads, nor do I know if this will work. I think there should be also some older touchpads that use resistance (requires a bit of pressure). In the best case you find two outputs (4 or 6 wires incl. Vdd / Vss) which you may directly connect to the AINs of the Core/Sensorizer. So you would use two inputs for the XY pad and can configure each Axxis seperately. Cheers, Michael ps: don't expect the ACSensorizer Release in May, but Beta versions are possible anytime! Edit: About TouchPads, SoftPots and other interesting stuff: http://www.midibox.org/forum/index.php?topic=5023.0
  25. naja, also ich finde soooo schwierig ist das nun auch wieder nicht, wenn man's von unten nach oben betrachtet (es baut ja aufeinander auf): 1. nach dem Brennen (BURN) zeigt das Display Balken an. 2. nach dem Upload von MIOS (per MIDI) sieht man READY. 3. nach dem Upload der Applikation (z.B. MB LC) eben den Screen der Applikation Ich habe diese Grafik gepostet, weil du sagt, du hättest MIOS "erfolgreich" hochgeladen und siehst aber anscheinend nur schwarze Balken. Das bedeutet, dein LCD ist wahrscheinlich okay, nur MIOS ist halt eben wahrscheinlich nicht oder nicht richtig geladen. Ich habe halt nix dazu geschrieben, weil das schon 1000 mal hier im Forum erklärt wurde, bei uCApps und im Wiki sowieso... und ich dachte, dir kommt der "Balken-Screen" vielleicht bekannt vor :-\ Kann mich natürlich auch täuschen und du hast nen kaputten LCD. Würd' mich aber schon wundern... Grüße, Michael
×
×
  • Create New...