stryd_one

Well this is pretty simple really. MTE - Are these files made with a cracked copy or not?

Yeh no need for two chatrooms :)

how big are those?

Why is that?? Are they the same length sysex string?

Uhm I know it would be a pain in the backside, but have you considered switching cores with your SID? There is a lesson in this - always test everything *before* you case it up and then again afterwards :)

Sooo weird. Different board, different IC, different wiring... The only common points left there are the core and the encoders themselves. Did you use different encoders too?

More RAM? I mean, hey it's your time, but if I was going to rewrite MIOS for a new uC, I'd want to see a lot more benefit for my work than a light increase in any resource, be it RAM or processing power or IO.... Uhm what I'm saying is, why trade your Mercedes for a BMW? Trade it for a Ferarri! I think that analogy made more sense ;) Edit: Although it would be interesting to see if the AVR was any faster! How about the Propeller ? The multitasking capabilities could be REALLY useful for MIDI... Not sure how widely available it is though, and it's very new, so it might be a dead technology in the future... I'm not a good person to recommend a suitable IC but there was a lot of hype around this...

Well the idea is to send several of those bytes appended to each sysex message. This means that your matrix gets the sysex, and then while it spends time loading that information, it also receives, and hopefully ignores, the active sense messages that follow it. The next sysex message can't be sent until the first one has finished sending, so all of your active sense data acts as a "spacer" inbetween the messages ...and? ;) It's not really relevant any more, it's clear that the problem isn't your cabling but the matrix's slow response... But FWIW, sending notes and CC's OK does not imply that sysex will be OK - as I said earlier, sysex messages tend to be more susceptible to corruption in poor cabling. Because of this, CC's and notes might work 100%, but sysex might fail. I have a midi cable which was a cheap one I bought in a rush one time, and has poor shielding, and does just that.... I've also seen the same problem happen where midi cables were run alongside power cables, and when midi cables were routed through cheap synths or midi interfaces.

Ooops I got all confused in this thread... I forgot to post this: You have already noticed the last part, but something we both missed is TK's solution. Give that a try!

Well you don't really want it to send when the pot stops moving, more like you only want to send one sysex message every N milliseconds, where N is the amount of time the OB takes to recognise a sysex message, plus some time to be safe... I would have a timer running which triggers the sysex messages to be sent using variables, and set those variables whenever the pot is moved. You can use the timer functions directly, or if your application is already using the timers, you can put a counter in the timed function.

I like this thread dude :) Did you see my DIY Layout Creator thread? Not sure how it compares to your demo, I don't even know if it's good, but I found the link recommended on a synth DIY page and I'd never seen anything similar... Is your demo time-limited? Or some other limitation?

Just a thought guys...rather than busting chops to try and find parts which are expensive and obsolete, why not work on finding replacement IC's for a AOUTv2 and SHX8v2?

Nice work on the case :) A tip for avoiding the leeching of paint under masking tape - do lots of very light coats.

Are they really good quality (IE did they cost a lot?) midi cables with no other device in the loop?

Shouldn't be too rough.. MIOS_LCD_Cmd can be used to send the command... You'll need a flag and a counter... This could be done at the OS or application level, the only tricky part is ensuring that you don't increase the load on the core checking for movements all the time... A thought - you might want it to keep running in case you don't touch anything when the device is running, eg if you hit play on the seq and walk off to play a synth.

I would definitely be looking at the soldering... Had a look at the pics in your other thread, and I was thinking that maybe one of those tracks on the veroboard might not be broken? That kinda depends on how it was faulty All kinds of things. Possibly, Possibly. Not very helpful am I? Yeh it's a weird one. That behaviour, putting the same IC back in and now it doesn't work at all... That's interesting. I'm guessing dry solder on the IC socket, and changing them over busted it completely loose? All of this points to wiring problems hey...

I'd say you've got that backwards... If you design the hardware first, and then have trouble making MIOS work with it, you'll be in trouble. As it stands, I think you'll be OK, but I thought I should point that out...

It's good to be an environmentalist. Oh yeh that old thing... Interesting thoughts from a pro shop doing the same as us:

I'm pretty sure you can send a command to put the display to sleep... Darnit now I have to read the datasheet again. Yay: The Datasheet says

I feel that :'(

Looks pretty good from here! Why didn't you get SIL connectors instead of soldering to the SIL pins?

Well, the AVR isn't really that much more capable than the 18F... Search the forums for TK's comments on the AVR. Basically, you would spend a lot of time for very little benefit, if any at all. Unfortunately a very tantalising comment was eaten on Friday the 13th, something about TK's ideas for the next generation core... I don't think that's going to happen... There's some groundwork laid out in FPGA synthesis, but that's audio not midi...

Good idea.... PLED users take note :)

Hey snaper welcome to the board :) I understand English is not your first language, but typing in caps is considered screaming in pretty much every language ;) This forum is full of people playing with live electricity, so maybe you should save your screaming until you're getting electrocuted :o I took time out of my day off sick to check this post because you had me worried for your safety! Anyway I hope your midibox is a huge success :) For a simple project with some transport control, maybe you could consider the clockbox project. It has an LCD, but you will probably need an LCD for debugging anyway.

I'd be interested in this if we include the IC's for the SHX8 board...