stryd_one

It's a brand new feature :) But yeh... 1.5 year bump! http://www.simplemachines.org/community/index.php?topic=25009 might help?

Topic locked... ask and you shall receive ;)

QBAS made a 16x16 velocity sensitive matrix app for this purpose. Use the search :)

See my sig, GROT #7 - a workaround is not a fix! :) Firstly, as Wilba said, you should use feedback from core (Smart mode) in MIOS Studio. If it doesn't work, then the errors will help to find the source of the problem. Your next stop, is to do all the MIDI Troubleshooting steps. The results of these tests will point at cause of the problem which makes it easier to fix (GROT #6) Well as you can see the sysex string is completed with the F7 byte, so it should stop there. It seems that your PC believes it has sent the whole app, but the core has not received it. I'ts probably a problem with your MIDI input on the core - but the abovementioned tests will confirm that. Edit: The active sense message is probably normal behaviour for your keyboard

He's CrAzY!!!

That really is one hell of a nice enclosure you've made dude.

turuloid: do you know that you can edit your posts? superanimo: wordclock should only be required if you need sample-accurate audio sync, and it won't give you tempo sync. For tempo sync that is perhaps not as accurate (24ppqn vs 44k1/48khz) but perfectly servicable, midi sync is entirely capable, it's what everyone uses. the problem here is not MIDI, it's your client (reason). I'd suggest posting this to some reason forums too. I would have thought you could stop reason, reposition it, and play again - if it's syncing to midi clock it should pause until it receives the first clock signal from the master. If you want to use SPP from the master to reposition reason, and it just won't do it (did you read the manual?) then another app is your answer.

Such nice case work :)

Exactly - Which is why you have to take the delay into account when designing the whole kit, to get the desired effect (all hitting together, or all separated or whatever suits you) I'm not new to this ;)

Ahh you did like me and went searching for the nice eutectic solder huh. I damn nearly fell over when I saw the price - you should try sourcing it in Australia OMG. $80 a 1/2lb roll, I kid you not. Fortunately I found three rolls of nice fine 63/37 Kester with the no clean flux on ebay for $15. You can imagine how fast I clicked that button! (Oh, the packaging looks like its from the 80's hhahha...fortunately no sign of corrosion)

You mean it's been worked around ;) (see my sig, rules 2 6 and 7) J11 *should* work OK... Did you maybe forget to cross over the cables (MI-MO/MO-MI) ? Still, it works! Yay!

That "datasheet" (it's not really) is in german.

Hhehehe Ahh well, then it's a good thing that there's a good free merger project handy :)

That's a nice looking box man :) I like the simple but effective design. Is that a recycled case?

It does sound like yours is broken :( They do seem to be a problematic part, well, more so than any other part. They seem to be very sensitive to heat or shorts, but sometimes just die for no reason.

Excellent :) I'd love to see pics of the inside!

Yes you are, but that's no problem. I do understand what you're trying to do, so I'll repeat myself in more detail as it seems I wasn't clear enough. MIDI master keyboards don't have an internal sound engine. Perhaps it's for this reason, that on some master keyboards, the midi thru/merge function is called local on/off. Yes, I know that is not the correct terminology, but I thought that I should advise you that some master boards use this incorrect terminology, so that you can check it. For a synth that might be a little unusual, but for a dedicated master keyboard it is extremely unusual (because they should be designed for the type of thing you're trying to do). Have you checked the manual and the sysex implementation? You can skip the opto but it won't hurt to leave it there :) In fact, you could just use J11 to connect them...

I think there is some question as to whether that works... I assume that it works OK for you though TK? :)

I helped someone out with a midi input issue yesterday and they had these same test results, and it passed test 7 also - but when he tried a new opto, everything worked OK...

That's normal for any synth/sample/sound source, which is why it's important to synthesise the sound/edit the sample/etc in the correct fashion according to your own taste :) I guess what I'm saying is that fixing this is not the job of the sequencer, it's the job of the sound designer - you :D

linear. It's a feedback loop, so it's already exponential in nature.

You sure? I've never seen a master keyboard that doesn't do that. It might be called "Local=on/off". Anyway, if that's the case, you can just do as you drew.

Latency is not a problem. TK has previously commented on this, just run a search :)

Uhm, so you have a different problem now?

Sorry I meant the connections to the core, and inbetween your AINx4 modules. I think you can test this with the SRIO test app too.