nILS

When you send that sysex String to the core you should get a response from it. What is it?

uh oh.

Okay, here we go: http://www.schickt.de/temp/Grabbag_-_mbFM.mp3 This is a modified version of the grabbag theme (more instrument changes) played on my mbFM (except for the low volume SB Live drums). No external effects or anything used. ------------- end of real reply, start of OT mode ---------------- While I was fiddling with that I remembered how screwed up writing midi songs was back then, cuz they sounded great on your computer and sucked on everybody else's. So to compare the whole thing to different instruments I present to you: http://www.schickt.de/temp/Duke_Nukem_-_Grabbag.mid That's the original (yes, I installed the game and went through the whole kextract duke3d.grp *.mid thing) "grabbag.mid" from Duke Nukem 3D only slightly changed (removed some notes at the end to have a somewhat decent ending rather than a looping version) While I was at it I played it over my sbLive soundscard and my Roland XP-30 as well: http://www.schickt.de/temp/Grabbag_-_SBLive5_1.mp3 http://www.schickt.de/temp/Grabbag_-_XP30.mp3 I think it would be neat if some more people would play the midi file on different instruments. The midi file has all the volume, fx *cough*, and instrument settings in it - so go for it ;D

[ot-mode]Synchronize a human drummer? Hmm, I don't think the 5V from a DOUT will work as electro-shocks. Needs More PowerTM[/ot-mode]

Easy link: http://maps.google.com/maps?f=q&hl=en&geocode=&q=53.308290,+-0.781250&ie=UTF8&ll=53.303416,-0.774901&spn=0.005642,0.013475&t=h&z=17&iwloc=addr

The "exactly like in the schematic" thing is a really good idea. Don't try to optimize anything any further unless you really know what you're doing ;D

Funny how seeing it came from stryd_one made me *not* click the link :-) *whack*

Yes, you may, but I thought the point was to have cables :-) Besides "easy to implement" I believe what I suggested is pretty simple, right?

Funny how reading "Feng Shui" made me *not* click the link :-)

That's the original post, which I couldn't post a couple of days back when the forum was down a lot: As I always like the idea of patch cables, I just did some tests with it. Basically you hook the sockets up to GND and a DIN pin. You'll need cross-over cables for this though - when you plug in one side of a cable nothing happens. When you plug in the other side, you're closing 2 switches rather rapidly, invoking 2 DIN_NotifyToggle. Same for unplugging a cable - you get 2 DIN_NotifyToggle. Set up some vars: unsigned char tick, count, one; "tick" is the internal timer that counts the "ticks" between two DIN events. "count" counts the number of events in a pair, so it's either 0 (no event yet) or 1 (one connection has been closed). "one" just stores the pin of the first event so we know which pair has been connected. What I did is I set up the timer to something rather slow: MIOS_TIMER_Init(0x03, 65535); The timer function increments a small helper variable:void Timer(void) __wparam { tick++; }[/code] Finally the DIN event handler:[code]void DIN_NotifyToggle(unsigned char pin, unsigned char pin_value) __wparam { if (pin_value == 0) { // something was put in if (count == 0) { // and it was the first one tick = 0; count = 1; one = pin; } else if (tick < 10) { // good one MIOS_LCD_Clear(); MIOS_LCD_CursorSet(0x00); MIOS_LCD_PrintCString("+ "); MIOS_LCD_PrintBCD2(one); MIOS_LCD_PrintCString(" "); MIOS_LCD_PrintBCD2(pin); // reset count = 0; } } else { // something was removed if (count == 0) { // and it was the first one tick = 0; count = 1; one = pin; } else if (tick < 10) { // good one MIOS_LCD_Clear(); MIOS_LCD_CursorSet(0x00); MIOS_LCD_PrintCString("- "); MIOS_LCD_PrintBCD2(one); MIOS_LCD_PrintCString(" "); MIOS_LCD_PrintBCD2(pin); // reset count = 0; } } } All it really does is: * check if the button is pressed or depressed (basically does the same thing for both, so I'll only go into detail for the "pressed" part) * check if "count" is 0 which means this is the first event, if so * increment count, memorize the pin number and reset the tick * if count == 1 then it's the second button IF the tick (which is incremented by the timer) is < 10 (basically some nasty debouncing to allow regular buttons to be used along with the patch field) * second button means: we've got a connection. Display that on the LCD, reset the count * done Working really good for me. And it's fun. Only thing I'm wondering now is - how could I use this ;D DrBunsen: Does that answer you question?

Time to reset the "487 days without accidents broken sids" counter then... BTW, this could solve your tube-cutting issues:

Go Twinnie!

Pascal: Ja, mir ist im Nachhinein auch aufgefallen, dass sich Dein Post auch so lesen lassen würde. Nojo, ich dachte eben "erstmal draufhauen, dann weiterfragen" - kennst mich ja ;D

TK: Sure, but if you don't mind I'd rather put together a version that doesn't have the nasty clicks and pops and "change the patch during playback"-holes in it. So if you don't mind, give me a week and I'll make a nicer one :-)

I fiddled around with the idea a bit and found it to be really easy and fun :-) Basically, all you need is some sockets and cross over cables - connect one pin to GND and one to a SR. Now, if you plug in one side of a cable nothing happes. As soon as you plug in the other end of the cable you'll get 2 DIN event quasi simultaneously. I'll post the source when I get back home on Sunday.

Das haben wir schon einmal geklärt, ne ;D Jetzt schauste mal hier hin (http://www.ucapps.de/midibox_sid/mbsid_v2_communication.pdf) und sagst wie viele Widerstände Du siehst. Dann schaust Du wie viele Du hast, lötest die 3 falschen ab und alles ist gut.

Use whichever you please :-) Correct. (Although you could just perfboard the second DINx4 as it really only needs to be a DINx1) That's really up to you isn't it? Possibly a MIDI Through? Definitely some buttons and a case ;D

...or just solder the damn jumpers ;D It's not like it would require dozens of them.

Since what you just posted looks correct (at first sight) I'd guess you messed with some other part of the source code or your encoder is broken or your DIN is not working. a) try another encoder b) connect the encoder to a different SR c) download a clean version of the source

As a switch does exactly the same as thing (opening/closing a circuit): yes. I don't really now what you mean by "waiting for a second event", but: yes.

Right here on my PC. I should have added: PM me, if you're interested. I'll give them them some final touches and possible publish them here (if it's okay with TK)

In case someone's interested: Without sockets: With sockets:

There ya go - I picked some random patches from the "midibox_fm_voices.syx" bank an played the same riff for all of them. That doesn't really do the FM much justice to be honest, but it might give you an idea of some of the possibilities :-) http://www.schickt.de/temp/fm.mp3 edit: Whoops, seems like I misplaced the file... I hope to have it back up in a bit. Offsite doco...

You could use 5000mm motorfaders and use the box as an elevator ;D That way the MTC display could easily be the floor display.

Let's put it this way - just because a car has an engine it's not a mixer. The mb64 sends NoteOn/Off events, it may still not quite be what you need ;-) My 2 cents: a) Since I didn't really get to understand what excatly you want your box to do - would you mind telling us? Not just the transposing part - the whole box b) Get the C skeleton and start writing some code to get some LEDs blinking, display something on the screen and send some MIDI - that's easiest way to get into programming