Jump to content

Captain_Hastings

Members
  • Posts

    208
  • Joined

  • Last visited

    Never

Everything posted by Captain_Hastings

  1. Maybe replace with and keep ?
  2. Yep, should be no problem...
  3. And the Sega Megadrive (Genesis) Mk1 used a Yamaha YM2612... ;D
  4. And the Sega Megadrive (Genesis) Mk1 used a Yamaha YM2612... ;D
  5. Yo Stigmata, I think with a/this midi router you're able to route any of the inputs (or merged inputs) to your choice of the available outputs (optionally filtering events). It seems obvious what it is to everyone here, except you and me ;D Hope i guessed right... ;)
  6. Check the Reason MIDI-implementation chart. Try either assigning the appropriate control id to the pot on your midibox, or set it to a ctrl on a channel other than 1 and use midi-learn. Hope that helps!
  7. That's a cool idea... :D These things are also used in infrared theremins and LEGO mindstorms. I found this interesting link: http://www.acroname.com/robotics/info/articles/sharp/sharp.html
  8. Usually i try to gently lift ICs by putting a small flat scewdriver between the chip and the socket. Don't use too much force and avoid tilting the chip too much or the legs will bend and break. OR you can try one of them special chip-lifter-plier-type-of-thingies. If the phucker is firmly stuck, just have a bit of patience removing it... ;)
  9. Thorsten, I noticed that if you visit the forum from www.ucapps.de, it links to http://forum.ucapps.de/ (which is the forum on http://www.midibox.org/ framed). This gives me problems in Internet Exploder... i can't stay logged in! Most probably: because the cookie for the login is set on the digitaljunk.org domain and not on the ucapps.de domain... (yep, one of them security settings) If i login on ucapps.digitaljunk.org, no problemo...
  10. Yep, you'll need a midi-thru port on the midibox. This will send all data from the keyboard thru the output of the midibox as well as the events from the midibox itself. There is an additional schematic on the midibox plus page (http://www.ucapps.de/midibox/midi_thru.gif). cheers!
  11. ;)
  12. To say that Chirac rocks goes a bit far in my opinion... In fact when he resumed nuclear bomb testing in French Polynesia in 1995 ("absolutely no ecological impact") i think he was even nowhere near being fonky. But of course it is positive that Chirac and Schroeder spoke up the way they did against the war that is to save Ariel Sharons' bottom... (sorry, i got a bit carried away there ;D - politics, iew!)
  13. All the best wishes to you Thorsten and all MB folk! The projects and this forum are truely amazing... thanks again. cheers!
  14. Whoa! :D Fantastic Thorsten!! About the PICs, i got hold of a PIC18LF452-I/P... is it also possible to use this version? regards
  15. Whoa! :D Fantastic Thorsten!! About the PICs, i got hold of a PIC18LF452-I/P... is it also possible to use this version? regards
  16. Jazeker, je kan met een 4x16 display in 1 keer de status van alle 64 pots aflezen. Ik geloof dat je via de virtual midibox editor van Serge die optie (4 lijnen ipv 2) mbv sysex kan aan/afzetten. cheers
  17. Jazeker, je kan met een 4x16 display in 1 keer de status van alle 64 pots aflezen. Ik geloof dat je via de virtual midibox editor van Serge die optie (4 lijnen ipv 2) mbv sysex kan aan/afzetten. cheers
  18. (ok, Stigmata beat me... i must type faster... Â ;D ) Hi there, There are some schematics on the site that help explain the different modules. This is one: http://www.ucapps.de/mbhp/mbhp_midibox64.gif Some clarification: AIN4 = a module with 4 ICs, each handling 8 analog inputs (for potentiometers) If you want 64 pots (or faders), you will need two of these modules. DIN4 = same thing, it gives you 32 digital inputs (for pushbuttons, necessary if you want to control the menus on the LCD) DOUT4 = 32 outputs per module, for LEDs (indicate when a button is pushed, or wether or not a button is active when in toggle mode, or status of an incoming midi event...) You will need a Core module with the MidiBox64 firmware and an LCD display (not required, but mighty funky...). Backstick modules do not require a seperate PCB, it's just an EEPROM connected directly to the Core module (see bankstick pages). Read the MBHP, MidiBox64 and Q&A pages, there are a lot of tips and info in there. If you had little experience with electronics (like me...) it takes a while and you'll have to read everything a couple of times to figure things out, but it's really addictive stuff once you get into it, be warned! ;) cheers!
  19. aaah... ik zie :)
  20. *ting* Erm... ok, ignore the nr of revolutions thing, i just realised that i'm probably dead wrong about that one... It'll probably just mean you'll have to turn the knob longer/shorter. Â :-[ About the mouse... think there are 2 types: optical encoders and mechanical encoders. I think mechanical ones might possibly be used without any modification (some reserve with my statement here...)? Optical ones (a led, an eye and a perforated wheel): well maybe, i dunno. Maybe one could measure a usable signal somewhere in the circuitry with a scope... But then again i'm a newbie myself really... Â ;)
  21. Yep, nice idea... I found two threads on the old forum about this: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=old_forum;action=display;num=10308161150 http://ucapps.digitaljunk.org/cgi-bin/yabb/YaBB.cgi?board=old_forum;action=display;num=10308161220 (There are some links there to pages explaining how to build your own encoders as well.) What is important is the nr of pulses per revolution the encoder sends (must be 36 i believe). How is the design for the Traktor controller going btw? cheers!
  22. Ivm die potmeters bij Reichelt: daar moet je dus toch een P6-MUTTER per pot bijbestellen ??? Ik had ze per email gevraagd of er een moer bij zat en volgens hen wel... voor de zekerheid toch bijbestellen dus?
  23. Aangezien de IA ging over de blauwe LCD heb ik het toch maar niet gedaan... ben nog wat aan het twijfelen (en rekenen...) zie je  ;)
×
×
  • Create New...