• Content count

  • Joined

  • Last visited

Everything posted by tonedef

  1. Small eschema sanity check?

    Sweet thx! Very much appreciated!
  2. Small eschema sanity check?

    I'm looking to build my own custom board, but I want to make sure I have the core concept down for a basic DIN, before I move on to adding more components. Totally new at doing my own circuits, so any input would be appreciated! When I'm done I'll post it all, in case it's useful for anyone. Thanks! basic_din.pdf
  3. kicad schematic files for MB modules?

    Oh, okay. That sounds good. Having the modules was just for a starting point to ensure I'm doing it right, since I've never attempted this before (want to try to squeeze everything I want in with less boards/cabling). I'll try my hand at tracing them and compare it to the files you have. Thanks Phatline & borfo!
  4. Okay, my google fu is not up to par, and this is my first go at KiCad, but: I've been trying to find schematic files I can open in KiCad (i.e. not pdf's) for the Midibox modules. How do you all do this? I "think" it's possible to import the .brd files in KiCad, if I use the nightly build. Not sure what's an efficient work flow.
  5. I had trouble with the MIOS_Studio download for Linux (maybe because I have the 64 bit version of Ubuntu 14). It just didn't work for me. So here's a tutorial on how to make MIOS_Studio (actually MIOS_Studio_Debug) on Ubuntu in case anyone else has the same issue ----------------------------------------------------------------------------------------------------------------- Open a terminal. Make a svn folder, and get the recent mios32 repo: cd ~/ mkdir svn svn co svn:// when it's done, unpack juce: cd ~/svn/mios32/trunk/tools/juce unzip Go to the mios_studio directory for linux: cd ~/svn/mios32/trunk/tools/mios_studio/Builds/Linux I had a bunch of missing packages that I needed to install. You can try do a make first, but I needed these: sudo apt-get install libasound2-dev sudo apt-get install libx11-dev sudo apt-get install libxinerama-dev sudo apt-get install libfreetype6-dev sudo apt-get install libxcursor-dev After that, do a make: sudo make If all went well, MIOS Studio should ready for you in the build folder: cd build MIOS_Studio_Debug If it runs, go ahead and quit it, and copy it to your desktop or wherever: cp MIOS_Studio_Debug ~/Desktop Done! You can now double click the icon and it should just work.      If Make Fails ------------------------------------------------------- If make results in an error (e.g. missing file), you might need a package or two. To figure out which package has the file, use apt-file: sudo apt-get install apt-file Then update it: apt-file update So here's an example of an error during make: ../../../juce/modules/juce_events/juce_events.cpp:55:23: fatal error: X11/Xlib.h: No such file or directory   #include <X11/Xlib.h> Find a package with this file by doing this: apt-file search X11/Xlib.h which gives you this: emscripten: /usr/share/emscripten/system/include/X11/Xlib.h ivtools-dev: /usr/include/IV-X11/Xlib.h libghc-x11-dev: /usr/lib/haskell-packages/ghc/lib/X11- libhugs-x11-bundled: /usr/lib/hugs/packages/X11/Graphics/X11/Xlib.hs libroot-core5.34: /usr/lib/x86_64-linux-gnu/root5.34/cint/include/X11/Xlib.h libx11-dev: /usr/include/X11/Xlib.h you probably want libx11-dev (libroot-core5.34 might also work), so: sudo apt-get install libx11-dev Before you run make again though, do a clean: sudo make clean and try again: sudo make
  6. Okay so I'm having a bit of trouble figuring out how to take the current keyboard range and on each successive press of a button, shift it down by one octave. It has to be relative, because I also want an increment button as well.   I'm assuming it'd be something like:   event_button id=1  kb_transpose= current_value + 12 event_button id=2  kb_transpose= current_value - 12   Sorry if this has been covered before, (I looked but maybe I didn't search for the right terms?).  Thanks for any help!
  7. button presses = +/- keyboard transpose?

    Sorry I've not been on the forums in awhile, but yes! If you've got some code to share, I'd love to take a look. I've been trying to accomplish this via the NGC file, but haven't had much luck. I'm currently using the NG app which does everything else I need, just not the keyboard octave shifting... Thanks Robin!
  8. debugging

  9. keyboard octave button

  10. to debug

    From the album nextSteps

    My new synth. Lots of work still to go
  11. Fatar. Nothing?

    Ah, forgot to add EVENT_KB... just when I thought I was getting the hang of things... :smile: Thanks TK!
  12. Fatar. Nothing?

    Okay. I'm getting closer. I have all the analog pots in place. Well, 64 of them. I still have the aftertouch, mod wheel, and pitch bend to deal with plus all the dio's. Right now I'm trying to figure out the fatar keyboard. I've tried swapping the connections, but for some reason I can't get the midibox to recognize it: In MIOS, I have this: KEYBOARD n=1 rows=8 dout_sr1=1 dout_sr2=2 din_sr1=1 din_sr2=2 din_inverted=0 break_inverted=0 din_key_offset=32 \ scan_velocity=1 scan_optimized=0 note_offset=28 \ delay_fastest=5 delay_fastest_black_keys=0 delay_slowest=10 Maybe I have the connections wrong to the KB module? All I have connected right now is just the Fatar KB -> KB module -> J8/9 of my LPC17 module.
  13. NG and AINSER64. Next steps?

    Ok. Thanks to TK, I've got everything running. My core shows up in MIOS Studio, uploading .hex files works, encoders on my DIN's transmit, and my AINSER64 looks like it's working when I upload the MIDIO128 project (albeit, missing a few pots I've not attached yet).   However, when I upload the NG project, my little green LED doesn't light up at all, and nothing happens when I spin any of the pots, so it doesn't look like the AINSER64 board is being recognized. Do I need to do some programming at this point? Totally cool to dive into this, but I wanted to make sure I'm not missing something, like, the NG should see the AINSER64 board,  but I've foobared it somehow.   Any hints are much appreciated... thx!
  14. I was just using MIOS Studio, and was able to get it to talk to my midibox lpc17 just fine. I uploaded the  new bootloader to it, all okay. Then the MIDIbox NG  1.026 project. Everything was working, DIN's where being recognized, but something was flaky with the AINSER64, so I wanted to do some debugging.   At that point I realized I had an old version of MIOS Studio (2.2.x), so I went to upgrade it first. I downloaded the current version 2.4.6, replaced my old one with it, and now... it won't recognize the midibox. Unplug/replug/restart etc. don't have any effect. MIOS Studio just won't see the midibox.   Am I doing something wrong? 
  15. Got it! JOY! Thanks TK... re-upped everything and all is well... now I just have to debug my AINSER64 and my DIN chain :)
  16. No joy... fired up Logic, and it does show up there too. Plus Logic will also respond to some of the rotary encoders connected to the DIN boards (seeing midi data coming out of it, when I turn the knob).   Tried redownloading MIOS Studio again and using that. Same result... I must have borked something, but I just don't know what.
  17. Yeah, I tried that yesterday... same message. Audio MIDI Setup shows MIOS32 Bootloader...
  18. OSX Mavericks, and Apple's Audio MIDI Setup does show the MIDIbox NG. I was a bit erroneous, MIOS Studio  does see the midibox, it just cant communicate with it. Querying just generates an error:   No response from MIOS8 or MIOS32 core! Check MIDI IN/OUT connections and Device ID! For debugging see also   Help->MIDI Troubleshooting     And attempting any uploads to the unit, gives:   Reading project.hex project.hex contains 69312 bytes (271 blocks). Range 0x00000000-0x00010eff (69376 bytes) - PIC Bootloader (ERROR!) ERROR: Range check failed!   Thanks TK, for any input. You're always helpful...  
  19. Is this possible, or do I need to get another AINSER64 board?     I'm building a keyboard controller. I have 1 AINSER64 with all the 64 inputs being used, can I chain a kb module to it? In other words, can I simply connect the J1 output from a kb module to the J2 input on my AINSER64 board? 
  20. J1 Fatar_kb_module --> J2 AINSER64?

    oh... duh. man how did I miss that.... sorry :whistle:
  21. MIDIbox NG Concept

    Maybe I read something wrong (or I'm just ignorant)... but the confusion to me is that the MB-KB appears to have a plan for functionality that overlaps the MB-NG quite a bit. So for people who just want a custom keyboard controller with a fist full of knobs and buttons, what are the limitations in the MB-KB (assuming a future ver. supports 128 pots + a bunch of DIN/DOUTs), that would necessitate building a MB-NG to go with it? Is it just fewer DIN/DOUT's, or something else? Either way I'm stoked that the MB-NG is out soon! The news has finally got me off my ass to drill my panel. This will be the best Christmas present :) Thanks TK!
  22. Building...

    Got a whole big box of parts from SmashTV! Finished all the modules except for the core, which I'm working on now. It's going together fast; I must say these PCB's are very nicely done...
  23. Parts ordered!

    Finally got off my ass and ordered all the electronics to make this puppy happen. :sorcerer: Making a fully stuffed midibox64e. Going to try with the LPC17 core, so I don't even know if I'll be able to getting working until TK releases the NG stuff for it. Anywho is what I'm trying to make. Going with regular LED's per Hawkeyes rec. and I'll wait on knobs and make a dummy layout to see if the spacing is too tight per ilmenator's and Tbreath's concerns... Total damage so far: $160 from mouser + $258 AVI Showtech = $418
  24. Okay so my core isn't being recognized by MIOS Studio (or anything else). LED flashes, looks like it boots etc. but it won't come up. Bad flash? I have the LPC Link separated. Since it's on headers, I went ahead and tried to flash it again, but now it's showing up as "Ed:02: Failed on connect: Ee(92). Unknown error" in the IDE for OSX. On windows, still can't flash, but I get "02: Failed on connect: Ep(01). Target marked as not debuggable." instead. I tried booting into the ISP bootloader (GND the ISP pin, #51->#54) no go, even with flashmagic over ethernet (can't communicate). Any ideas?