stryd_one

sorry tokyo, I did have some trouble understanding your post. Are you trying to access the second bankstick from jsynthlib?

Wrong bug, ours is another one....

Yeh I thought that might be the go... I guess I was hoping that C had some magic pill for me heheheh Thanks for the advice mate!

Ahh nice. Thanks for testing it :)

If this is possible, I'd love to know how, it'd be a real lifesaver. I hope one of you clever midiboxers might be able to help! I have an array of 8x16 1-bit flags stored as ints. For the purpose of clarity, I'll scale down my example to 4x8 X-Axis[4] = {10001001,01110000,10000010,00001100} or... 10001001 01110000 10000010 00001100 Now it's easy to get the bits from the X axis and it allows me to iterate through the row quickly by reading the byte, bitshifting, then testing the carry bit, to test the bits one by one. Cool. Is there an easy and fairly quick way to get a column out of the Y axis? Preferably without it doing stupid amounts of pointer math! ;) Maybe for performance's sake it would be best to keep two sets of the data? I get a very strong feeling that I'm missing something ;D

Lookin good!!

More very good reasons why I've been complaining about USB for the last 5 years....

Unless you wanna drum well ;) heheheh I do like those fingerpad MPC stylee things but they're no replacement for drum triggers, more like an alternative to using a piano keyboard to program....

You'll need to init the special chars twice, once for each display... I haven't toyed with this much, but try setting the cursor position to one on the 2nd LCD before running the MIOS_CLCD_SpecialCharsInit the 2nd time. I've checked the MIOS source and I'm pretty sure that'll do it :)

In this post, in the second image down, there was no device in the list. You sure that was the same on his PC? Cause if Windows doesn't show it there, but Sonar sees it, that's unusual... IE theoretically impossible, because that window gets the list by using the same MMAPI call as sonar... I thnk TK has since retracted that :(

Well, that application is in ASM not C, so there is no main.c, but main.asm, and that is where you can make the changes: ;; use 64 pots movlw 64 call MIOS_AIN_NumberSet You can probably guess that this should be changed to: ;; use 40 pots movlw 40 call MIOS_AIN_NumberSet And... ;; define number of shift registers: for 128 buttons and LEDs, we need ;; 16 registers. Btw.: thats the maximum number of supported DIN/DOUTs movlw 16 call MIOS_SRIO_NumberSet Each Shift Register handles 8 digital IO, so 16 SR's means 128 IO... You want 20, so you need 3 SR's, so change it to: ;; define number of shift registers: for 20 buttons and LEDs, we need ;; 3 registers. movlw 3 call MIOS_SRIO_NumberSet Done! As you can see, sometimes a great deal of information can be taken from reading the comments from TK in the source files. I know that it can be a heavy read, but it is a good way to learn :)

The problem here is with Windows or maybe the driver on your PC... The visibility of the port to sonar, is secondary to the port appearing in windows, which it doesn't on your PC. Sonar, or MIOS studio, both get a list of available midi ports from windows. If it works OK on your friend's PC, it's probably not the midibox which is at fault. The EUSART bug does not effect the appearance of the device in windows either, only the data that is sent later on. There are no working revisions of the PIC. I think you'll find that formatting and reinstalling windows will sort this out.

Yes, 12v is too much :(

Lookin good!

If I were you I'd spend the time to find a more appropriate spare part :)

IIC MIDI Module page says: There is also a reduced "OUT only" version available, which only contains the parts that are required for a single MIDI Out port - this version is especially interesting for people, who want to use the module as workaround for the EUSART bug. Note that this circuit could be downstripped even more by removing the Power and Tx LED, but in this case debugging could get difficult. So yes :)

Oh... That's assuming that you already checked thoroughly with the soldering and schematic to make sure the circuit is ok.

Ohhh. If the power LED isn't lit, that's very strange, because the LED is lit as a part of the initialisation routine on startup. Obviously it is booting OK to some degree, as it is responding to IIC, but other pins are not working. Did you maybe overpower it, or solder with the PIC inserted? If you have a burner or jdm, I'd try reloading the firmware.

:) Good luck!

Well the activity LED's kinda say it all... Have you got the seq configured to use it - are you sure it's trying to send midi via IIC, not the core midi port?

Heheheh I just got the joke, Back by popular demand! LMAO! Thanks for the story Mike :) Great shot huh!

Tried this? iic_midi_sw_loopback_v1_0.zip

I'd look at the regulator, caps and rectifier... A multimeter might help here.

This is way outta my area, but don't the LEDRings get wired in a matrix?

http://www3.alps.co.jp/indexpdf_switches-e.html Scroll to "Multi control devices" :)