stryd_one

Yeh and you didn't think your synth was such a big deal either. What would you know? ;D I think it looked cool.... but maybe after a while the cool factor could wear off and you'd want a dimmer badly. Just my 2c

Dude!!!! Wow! So let me get this right.. Thats clear plexi with a black plexi back, and you've cut the pointers out of the black so it can shine through? Damn it's amazing what you can do with cheap CNC and a vivid imagination :) Edit: I'm looking again and noticing the details, all the holes for LED's and encoder, and then the notch for holding the encoder in the bottom plate... Nice work man...

Yeh I think it sounds like it has to be either: Your cabling between the PCB and core moving around and shorting/breaking when you flip it over ...or... dead switches.

Maybe over the weekend you can meet me in the chatroom and we can make a really basic seq :)

Funny I was kinda so-so on the ribbons too... maybe a strip of black over the top? It does look hot tho :)

The answer is more Amps not more volts, but IIRC, the 7805 will only handle 1A - you may need to get a special 2A version. I'm no expert on this stuff, so don't blame me if you take my advice and blow it up ;)

Well, it's a lot easier to use a pre-made app and maybe cut down the CS a bit, than to go programming your own seq. Trust me, there's more to it than you think ;)

Doh! -1 Opaque white +1 Clear :-[

Nice tip mike, I never saw that before! LMAO Gotta watch out for that repeated side-side thing hey... that's a recipe for breaking a weak pin off... in the socket. Bad. Only a fool would do that. It took me I mean it would take hours to get the pin out. If you did it. Which I didn't. Honest, it must've been one of the other techs. ;D

Yup, and he'd 'peeled' it off from one side, so the corner pins were bent like 40 degrees out :o

You just described the original MB64seq hehehehe Edit: That's a yes. Just use a timer (or the clockbox like the rest of us eh) to send the notes which you can store in an array, and then use ain_notifychange to change the contents in the array.

hints: One screwdriver on each side if you must avoid using the correct tool - ALWAYS lift it straight up, never lift one side higher than the other Warm pins before bending Never bend oxidised pins, period. If they aren't shiny, no bendy. You can always solder wire (or a new pin if the IC is used with a ZIF socket) onto the bare metal scar where the pin used to be attached (it won't go deep into the ceramic, probably it will snap off at the edge of the ceramic if not further down the leg). Be quick or you'll fry it! I had to straighten the bent pins on my neighbour's P4 last week.... I swear I was panicking so bad!!! I must've warned him 100 times that I was in all likelyhood about to finish the chip off for good, either by static or by breakage :-\ But... it's good!

Yeh, you should just give a pointer to a memory location for it to work. MIOS_PrintCString(variable[0]); Might work... the function should continue until it hits the '0' (the end of the quotes)

I have, but back then everything was through-hole and sitting in sockets... Actually, not unlike Wiba's SID :)

No sweat mate, give me a yell when it arrives and I'll give you a hand if you want :) The linker script may simple but handling the ram correctly could be tricky. I need to go read the datasheet. again. ugh. ::)

Thanks for offering this stuff up mate :D The wiki is definitely the place for this kind of thing... Although you may have noticed if you looked at the two FAQs (hehehe) that when lots of different information goes into one page then it can get confusing. I think that the best thing would be to take your info and put it on relevant pages, and of course you can always make your own pages if there is nothing suitable. For example that TRS jack thing, that could be relevant to the AIN or the SID inputs, so maybe you could make another page with that tip, and put a link to that new page on the SID and AIN modules' pages. You could add the ribbon cabling tip, and make a "Durisian's Cabling Tips' page, and use the automatic table of contents so that you can link to each tip from other pages. At the end of the day, if you take it and plop it all on one page linked to your user space, that is great, because the knowledge is there and can be moved around by others later on if they feel the need.

Yeh it should be a challenge. If you can remove a SID with your big toe only I will buy you a beer!

I got stuck at the typo: event or evernt? If you copy/pasted those then that might be your answer :)

Don't worry guys.... You both have the forum members' good intentions in mind, you are just doing it in different ways. We all love you both :-* ;D I'll take care of these concerns elsewhere, as for this thread I say as always buyer beware, now get your cheap MF's, MFs!

hhehehe my pleasure to help, just so long as you document your cool tricks on the wiki when your'e done ;D

That'd be because noone has done it before - if you write the document then the next guy won't have the same problem ;) In that case 4685 would be suitable. Note that it does not have as much RAM as a 4620, and that some sections of RAM are not accessible by indirect addressing.

That seems strange, but.... OK :) Sounds to me like you have a perfect spare DIN ???

4620 would probably be a better solution unless you want CAN. You don't even need to recompile to change PIC, but if you want to use the additional RAM you will need to edit the linker script (project.lkr) I have written lots about that topic before, so now that you have the right search term, I'll leave you to it. Hint: Check the wiki. :)

MPROC_NotifyFoundEvent Is not interrupt driven, so it is only checked every so often. Also, it checks the bytes recieved against the table to see if they are recognised. This may not be suitable for realtime input. You should use USER_MIDI_NotifyRx, but that is interrupt driven so your code should be fast. Edit: Whoops that doesn't exist in C wrapper... Mayyybe NotifyFoundEvent will be better but I dunno... Better yet, I would use a DIN. Edit: Yeh. USER_SR_Service_* can be used to increment your counter as it is called each 1ms. That will free up a timer. Hope that helps!

;) That's a type of IC removal tool, also works well with sticky knobs.