stryd_one

Hey Shum would you like to document this on the wiki? :)

Yeh we like that! :) I might make a thread in english for that one, in case some people aren't reading the french forums

Nah that'd be too smart. ;D Good point sinnsyk. You've already got a perfectly good signal, it's just only on one channel. WAYYY easier to mangle serial bytes than PCB's. and that 'board has ooodles of space for an LCD, and most probably for the core module internally, so you could run wire from the fatar PCB, to the core module, and to the existing midi plugs. Hey I have to highly recommend a PLED display like Wilba's for your board. The first thing I said when I saw it was "Imagine that mounted flush on a black box, it'd look so damn nice, like the lettering was just shining right out of the metal". Well actually that was the second thing I said, right after I stopped swearing at how nice it was ;) It just occurred to me, I could do the same thing with my KX-76 It has the bomb action, but the interface is so crap, it's all programmed in hex using two 7-LED digit displays :-\ Plenty of space internally too. The MIDI Router would be a good way to do this. One MIDI In, a few Outs, and maybe some modifications to the code for custom features...

What about jsynthlib or sounddiver or unisyn or similar? Using a librarian won't increase the internal capabilities of your gear though....

Excellent, that's the bit you need to know. If it's a scanning matrix you should be able to adapt QBAS's velocity sensitive keyboard scanning matrix code. He will hopefully email it to me shortly and a certain moderator will host the files for the community :)

F*ckin rookies. That's not vintage! "Oh...it's weighted, nobody plays those anymore, they're no good for drums" argh! I love that board. I've got a fully weighted yamaha KX-76 at home, probably a little more like vintage than yours ;) You could buy a new weighted keyboard, but be prepared to spend upwards of a grand to get one. You could almost certainly hook it up to a midibox, but of course it depends on how the keys are attached (speaking electronically, not mechanically). A MIOS core could give you as many split zones as you want, or you could have them act like different keyboards by using pedals to switch to virtual boards, you name it.... You could have like 127 zones spread over 127 virtual keyboards, in theory ;) Can you get your hands on a service manual for the board? Right now, yuo need to find out how the keys are connected/scanned,switched etc etc.

Exactly. It seems sometimes that this protocol is implemented only for the sake of saying that it's there. Maybe in a few years time it might be relevent, but for those of us running lots of outboard and doing very little (if anything) 'in the box', it's irrelevant, and probably always will be.

you're after midi_evnt.inc, line 114 :)

You're close :) I'm trying to make all the sequencer parameters available.

Yeh but he wasn't talking about groove/shuffle, he was talking about delaying hits due to the time it (supposedly) takes a drummer to move his arm the extra distance to the next drum. Personally I never had that problem. My drumming is tighter than MIDI ;)

Ahh about this grounding issue.... I should have read the whole thread before I replied. Don't confuse AIN's with DIN's.

If it has a KS0108 controller, go for it.

To simplify, when the wire is grounded, there is a stable signal, because the circuit is completed, and all the electricity has somewhere to go. When it is 'floating', then it picks up interference, just like your car or TV antenna would. That interference is measurable by the core module, so it is converted into MIDI. It's not good. As for the 'professional' midiboxes... They can't touch TK's design :) It would only be a small change to the firmware, if you have some ASM or C experience it will be very easy.

So AC I hope the wrapper fix did better than the Socceroos ;)

Uhm maybe I missed something but why not just do this in software? One encoder, four momentary switches which 'patch' the encoder to four functions... why not add four LED's to show whether the encoder is patched for that controller.

An idea...Because it does not need to make notes strike early, but only delay them, that feature could be built into a standalone device. That way you can both have your cake and eat it too :) Just a single core and maybe a tiny LCD would do the trick, you wouldn't even need a DIN or DOUT...

USB and ethernet are fairly different in application though. Not really the same functions and capabilities. Personally, I like good-old fashioned MIDI. :)

Oh my Lord.... I think I'll laugh at that one... While I plot my revenge ;) Is anyone else interested in doing this interval controller/sequencer? Shouldn't be too hard really... If not, I'll still do it anyway, but it might take a lot longer :( I've pretty much got the scaling engine written in my head already, but now it's a matter of thinking of ways to implement it...

Search the forums for fracsid :) Unfortunately he never posted the source code which is very disappointing :( But maybe if you email him.... This will take some level of programming skills though .....

Hey welcome to the board :) So what is that little switch bank with the diagrams there?

:o :D ;D :P :-* :-* :-* Oh TK you are such a tease!!!!!! ;D Progression parameters?... The mind boggles :)

Hi TK, No urgency, but when you have a minute.... Could you explain why the address to the high byte is moved from FSR0 to FSR2, and the FSR2 pointer incremented before reading? Taking the information from the SDCC manual, I know the data should go into FSR2+2...So why the move from FSR0L? Perhaps that information in the manual is outdated? I was also wondering why you didn't just do PREINC0? I am convinced that I've missed something here ;) I know you are busy, so although I would love to understand a little better, please only answer if you have the time.

I know there's a little hurry :) Yeh I just remembered the soccer, I was going to watch it and then I opened that damned datasheet! hehehehe

Since I stayed up to 1m to figure that out and you just walked off... ;) ;D FSR* is a File Select Register, it's used to address a section of the PIC's onboard SRAM. PREINC* Pre-increments this address before reading the RAM at that address Scope out 5.4.3 INDIRECT ADDRESSING on Page 69 of the PDF datasheet for the 4620,I reckon it'd make sense to you - C or ASM it's all addressing :)

Not Version 3, But Revision 4 C. Smash's is different to that one (The onboard MIDI ports are the giveaway) Check out http://www.avishowtech.com/mbhp/mbhp_coreR4c.html for R4C Here is the doco for V3: http://www.avishowtech.com/mbhp/mbhp_coreR3.html