Jump to content

/dev/null

Members
  • Posts

    12
  • Joined

  • Last visited

About /dev/null

  • Birthday 01/01/1

Profile Information

  • Gender
    Not Telling

/dev/null's Achievements

MIDIbox Newbie

MIDIbox Newbie (1/4)

0

Reputation

  1. Hello everybody, I am selling up to nine Sparkfun pads complete/optionally with Duo-Leds (green-yellow) and screws aswell to mount the boards to a piece of wood or something else. I don't need them anymore. They are in perfect condition. I have at least 16 Alps encoder with knobs aswell sitting around waiting to get used for something nice. Contact me the parts fit your project. Shipping from Germany http://www.sparkfun.com/commerce/product_info.php?products_id=7835
  2. This looks very interesting. The only downside is that I already have a standard core with mios running on it. I don't have the parts to build a core32. Do you think the regular core could handle the scan matrix and the 20 encoders? Yes I do want the buttons to represent my clip matrix in ableton and I want the leds to light up whenever a clip is playing. I don't think that getting around with live api will be my problem. I just would need to write an app for the preferably standard core which can handle the scan matrix and the encoders and send simple note on note off messages. one channel for the buttons one for the leds and one for the encoders. The encoders could even send just relative up down data eg note on for up note off for down. There is no need for OSC or any other complicated protocol via midi sysex or whatever. I wish I could just code on the regular midibox platform.
  3. So quite some time went by but unfortunately nobody was able to help me with building my button-led + encoder controller. Still I want to get something done and I am not able to work it out myself and of course I can't ask anybody to do it for me. So I will try again with a much simpler concept. I will forget about the 12x12 and just use 16x4 because it is better than nothing and already working for some people here. Further I will forget about the ledrings for the encoders. My new plan is to build a 16x4 led-button-matrix according to http://www.midibox.org/forum/index.php?topic=10476.30, where I asked for 12x12 but unfortunately never got an answer. My new question now is: Can one core module handle the matrix and 20 encoders (without ledrings) with very little latency for the buttons? What is the most efficient way to come up with a application concerning latency vs programming effort (some c skills still no assemby)? I hope it is easier now to help me out a little. :) --/dev/null
  4. @cimo: well if it makes things easier then let's use a note on message therer, too. I just thought i was gonna use CCs for trigger events and noteOn/Off for toggle events. Two boxes don't seem very convinient to me. But of course it is an option I will consider if everything else seems to hard to do. @stryd_one: yes of course. I thought about wiring all the things up via matrices aswell (initial post). Actually I have the pcbs for the buttons and the leds already and they implement each a button and led matrix. So there are 9 pcbs. Each has a 4x4 led and button matrix. Therefore I would go to interconnect them and have a big 12 by 12 button and led matrix. But from there on I am lost. I have no clue how I can manage it on the software side of things. I can't really write assembly. It is very hard to read already. C would be fine probably. Thanks already for pointing me into some directions.
  5. Thanks for your thumbs up on the reality check. Since I think RGB leds are not really necessary for my project and would overcomplicate things at first i want to take on planning without this option. I also chose encoders with ledrings like in MB 64E instead of potis since it would allow me to change the volume in a diffrent way without the controller having knobs in the wrong position. The interface I want to build is divided into 12 columns. Each column consists of one volume encoder, 8 clip launch buttons, and 4 additional buttons to manage some functions (stop, solo, mute, select track). The columns are numbered 0...11. Here is the entire protocol i would like to implement with the midibox hardware platform: 1. The 12 volume encoders with the ledrings communicate over midi ch. 1. Twisting the encoders sends control messages: Controller: 0-11 (column) and Value: 0...127 (position/volume). Then the software on the host will send back a control message with the same contents. Control messages can also be sent to just change the ledrings while no encoder was touched. In my case there is only room for 8 leds per ledring. 2. The 8x12 clip launch buttons with the leds communicate over midi ch. 2. Touching a button sends a control message: Controller: 0...11 (column) and Value: 0...7 (row/clip 1 through 8 in track) The host software will react with a note on message to turn the led on when the clip starts to play: NoteNr: 0..11 (column) and Velocity: 0...7 (row/clip 1 through 8 in track). In the same way a midi note off message will be sent to turn the led off when the clip has reached its end. 3. Channel 3 is for the four function buttons on each 12 columns. The protocol is the same as it is for the clip launch buttons. Just rows are 0...3 now since there are only 4 buttons each. They have a leds aswell which are controlled in the same manner. Now as you can see the project has 144 buttons and 12 encoders. There are 144 leds for the buttons and 96 leds for the ledrings. Therefore I am well over the limits of a Midibox 64E. It would be nice if someone could tell me how to go about this with the Midibox system and keep the latency for the buttons as low as possible while the latency for all the leds is no big deal. Thanks a lot for further answers. :)
  6. Hello everybody again, quite some time ago I build a Midibox SID and I am really happy with it but now I have some time left and I am ready for my next project: I want to build a controller for Ableton Live (who doesn't? ;-). I want it to be a button matrix of 12x12 buttons. Every button has a LED (maybe even RGB) that goes with it. Each button will send a control message with a parameter. Further it should work as a button matrix to reduce the wiring and DIN modules. So the first button would send control message 1 and parameter 1. The button below it would send control message 1 and parameter 2. The button to its right would send control message 2 and parameter 1. ... For the leds I don't have thought about a protocol yet. Then there should be 12potis for track volume or encoders with led rings. I would appreciate it very much if somebody could tell me if MidiBox is the right choice for my project again (reality check). The only additional requirement is that the whole Interface remains responsive. I mean i want a button press to cause a midi message rather quick so thing stay in sync. Thanks for responses.
  7. Yes I still do have troubles. trying to log in shows the following error: Warning: preg_grep() [function.preg-grep]: Unknown modifier 'd' in /home/midibox/public_html/dokuwiki/inc/auth.php on line 259 Warning: Invalid argument supplied for foreach() in /home/midibox/public_html/dokuwiki/inc/auth.php on line 261 Warning: preg_grep() [function.preg-grep]: Unknown modifier 'd' in /home/midibox/public_html/dokuwiki/inc/auth.php on line 283 Warning: Invalid argument supplied for foreach() in /home/midibox/public_html/dokuwiki/inc/auth.php on line 285 Warning: Cannot modify header information - headers already sent by (output started at /home/midibox/public_html/dokuwiki/inc/auth.php:259) in /home/midibox/public_html/dokuwiki/inc/actions.php on line 91 Could someone please add me to the list?
  8. Hello everybody, I wanted to put myself on the list in the wiki at: http://www.midibox.org/dokuwiki/wilba_6582a_sid_mega_sale but I cannot login or anything. I would appreciate it a lot if somebody could help me out or just put me down on that list. I would like to order 4 6582 SID chips. Thanks. /dev/null
  9. ok i finally got the new opto and time to try it out. all i can say is that it's working now :) thanks for your help. these little ICs obviously are not as robust as they could be.
  10. Thanks a lot both of you for the help. I think I really could narrow it down now to a broken 6n138. I ordered myself some parts today so I will report once I tried it out with the new opto. Btw. my midi interface is an Edirol UM-3EX. The 220Ohm resistor could unforunately not solve my problem but I guess I will keep it in there and hopefully this and the new IC will make it work for me.
  11. OK here I go again: TEST PC1 and TEST PC2: As I already mentioned I am using MIOS Studio on a linux laptop: pc-midi-out -> pc-midi-in first block of the 6581-sid-hex-file: midi-out-monitor: timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 02 0C 00 00 20 15 7B 63 3F 04 3B 5E 1B 78 28 1D 71 5F 42 51 6F 0D 7C 18 6E 78 6F 61 74 77 46 7E 04 4F 3C 39 70 27 3B 63 4F 01 5B 5E 1C 78 0E 7D 71 67 41 1F 6F 0E 3C 00 1E 78 73 61 7F 77 46 7E 0F 67 3C 37 70 7F 3B 63 3F 04 03 5E 1A 78 3A 3D 71 57 43 6F 6F 0D 3C 1F 3E 78 6B 60 0E 77 47 1E 00 6F 3C 39 70 54 3B 63 2F 05 4F 5E 1A 78 3F 1D 71 57 40 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 1F 7F 7A 09 08 00 00 15 48 40 08 01 54 44 01 00 1B 24 20 1C 01 56 22 01 40 0D 12 10 0A 00 67 11 00 40 06 29 08 03 00 31 48 4F 40 03 04 44 7C 00 17 64 27 60 01 3A 22 3E 00 0B 32 13 70 00 78 11 01 00 07 51 08 09 00 3E 08 40 50 03 78 44 05 40 13 24 28 30 00 50 24 03 20 05 42 20 1C 00 0F 11 43 20 06 51 0C 1B 00 23 08 61 60 02 60 46 0E 40 03 44 39 08 00 3A 23 48 60 05 62 1C 64 00 5C 11 66 30 06 29 0E 34 00 38 48 73 28 01 58 48 1B 00 0E 04 40 1F F7 midi-in-monitor: 00000000074542 ms | Sysex message: F0 00 00 7E 40 00 02 0C 00 00 20 15 7B 63 3F 04 3B 5E 1B 78 28 1D 71 5F 42 51 6F 0D 7C 18 6E 78 6F 61 74 77 46 7E 04 4F 3C 39 70 27 3B 63 4F 01 5B 5E 1C 78 0E 7D 71 67 41 1F 6F 0E 3C 00 1E 78 73 61 7F 77 46 7E 0F 67 3C 37 70 7F 3B 63 3F 04 03 5E 1A 78 3A 3D 71 57 43 6F 6F 0D 3C 1F 3E 78 6B 60 0E 77 47 1E 00 6F 3C 39 70 54 3B 63 2F 05 4F 5E 1A 78 3F 1D 71 57 40 24 00 00 00 02 20 00 00 00 12 00 00 00 01 10 00 00 00 09 00 00 00 00 48 00 00 00 04 40 00 00 00 24 00 00 00 1F 7F 7A 09 08 00 00 15 48 40 08 01 54 44 01 00 1B 24 20 1C 01 56 22 01 40 0D 12 10 0A 00 67 11 00 40 06 29 08 03 00 31 48 4F 40 03 04 44 7C 00 17 64 27 60 01 3A 22 3E 00 0B 32 13 70 00 78 11 01 00 07 51 08 09 00 3E 08 40 50 03 78 44 05 40 13 24 28 30 00 50 24 03 20 05 42 20 1C 00 0F 11 43 20 06 51 0C 1B 00 23 08 61 60 02 60 46 0E 40 03 44 39 08 00 3A 23 48 60 05 62 1C 64 00 5C 11 66 30 06 29 0E 34 00 38 48 73 28 01 58 48 1B 00 0E 04 40 1F F7 TEST PROG1: The display already shows the copyright-text and then "Ready." So I guess this is redundant. I had the PIC preprogrammed with MIOS from doc. TEST CORE1: yes the crystal is oscillating. TEST CORE3: I couldn't find any bad solderings. TEST CORE4: Vdd is between 4.98 and 5.01 on all check-points. TEST CORE5: ground is alright, too. TEST CORE6: midi plugs should be connected properly (I think the following tests are also suggesting this) TEST CORE7: polarity of the diode and the diode itself is working. TEST CORE8: resistor values are ok. TEST CORE9: of course I have it cross-linked. TEST CORE10: I don't notice a lot of upload requests. TEST CORE11: The cap etc should be fine. How could I test this in more detail? The alive-message I reveive when powering up is correct. TEST OUT1 and TEST OUT2: I get an "alive-message" when powering up the Core. So this should be redundant. TEST IN1: all the resistors seem to be fine. TEST IN2: the midi plugs should be ok since the following tests work. TEST IN3: the led is lit and flickers when sending a series of sysex-messages. TEST IN4 and TEST IN5: I haven't tried it but it has to work since the previous test works, right? TEST IN6: the optocpupler-test works, too. TEST IN7: I haven't tried it, assuming that the previous test makes sure the optocoupler works. Tell me plese if I am wrong. TEST INOUT1: I was sending the beginning of the 8581-hex-file and the midi-in is empty so no log availible. I hope I got it all together now and thanks for the fast reply stryd_one
  12. Hello everybody, I started to built myself a midibox sid with one core so far. The core seems to be up and running wirth MIOS installed. When I power it up I get the single upload request which makes me think that midi out is working properly. :) Where my problems start is when it comes to the midi-in: I already spent quite some time here: http://www.ucapps.de/howto_debug_midi.html but I don't make any progress: my approach to find out what's wrong was: 1. connect a midi cable between midi-in and midi-out of my midi interface, which is connected to my linux laptop: works fine: I was "uploading" the SID app and the in-monitor showed the same as the out-monitor. So I guess it is not a pc-hardware/software issue 2. Check the resistor values at the MIDI In Port: meassured them and seem to be fine 3. TEST IN3: Instead of soldering I just took an led and connected it between the first two pins of J11: It as lit all the time and when I started the "upload" it was flickering with the sysex messages. 4. TEST IN6: standalone optocoupler-test: shows the expected results. so i skipped test 7 since i didn't want to solder something together and the optocoupler should work after test 6 anyways, right? TEST INOUT1: Yeah thats where things stop working. I just unplugged the PIC, put a jumper between pin 2,3 of J11 but the in-mon stays emty while "uploading". I hope the information is enough. I appreciate your help and of course the whole project!
×
×
  • Create New...