stryd_one

That "or" should be "AND". You should always do both of those things. If it doesn't work, then you have something to fix.... and smartmode+wait for upload request might help you figure out just what that is :)

Have you tried the midi troubleshooting? What were the results?

Chatroom? It's good for this kind of thing!

I assume that you're testing it with the PIC off or better yet removed.... But no, that's not normal. You've shorted something there...

Seems nicely done :)

My guess is that MMJ or your midi interface are causing the problem... Have you power cycled the machine? Checked the logs? What do they say?

Hells yeh! Way to go CF!

:-\ weird.... And I know you did it right the first time cause I'd nag you if you didn't hahahah.... weird!

Eagle won't do CS PCBs of that size uinless you pay megabucks or steal it like a dirty lowdown thief. See my signature regarding that. ;)

Now?

Good luck!

search says: http://www.tkk.fi/Misc/Electronics/circuits/vga2tv/circuit.html http://www.avforums.com/forums/interconnects-speaker-cables-switches/199751-diy-scart-vga.html Cheap to buy: http://www.amazon.co.uk/Hama-SCART-To-VGA-cable/dp/B0002W69MY

Sorry, google_one is a different guy ;) That's a good price... Surely Alps have a matching shaft part?

Sounds like a debouncing issue.

Yay! That was fast! thanks Twinny! Don't worry about the boxes, they never did work right :( Maybe a newer version might sort it out, we'll see... Durisian and I will look at the current crop of plugins. Durisian are you still in?

Probably still cheaper and much easier to use a higher res encoder, no? I've seen 360degree pots, and they were like $40 each.

Yeh, less jitter, at the expense of latency... But.. I think you'll find that the timestamping is not part of the USB MIDI protocol itself, and as such, not all drivers support it. For example in windows, the drivers using WDM can have the messages timestamped, but they can also just be fired out, FIFO style. Non-WDM USB MIDI drivers (and those not implementing all the WDM capabilities) don't get the timestamp from the app, so the timestamping has to be generated in the driver and decoded by the interface hardware, and when that is done, it's a proprietary solution. In fact, most drivers seem to make the timestamping, if it is even passed to the hardware, a proprietary implementation. If this weren't the case, almost all USB midi drivers would have comparable timing, and it'd be good. Alas that is not the case :(

I saw holes for LEDs in those pics?

A man walked into a bar Ouch.

I did that once... looked at the board upside down, and posted before engaging brain :D

Score! Nice one skrasms! I knew there'd be a "real" schem out there somewhere. That's even better than the one I knew from before. Can't wait to see what you're going to hack now :D Keep us posted dude!

Well said tilt. Especially the "cut the ground pin" thing. I hate that! Cimo: you're a gee-eek, neener neener neeener!

Sweet :)

Awesome, thanks for letting us know!

Perhaps the original suggestion might be easier to implement - use IIC_MIDI for midi, and use the core for RS232 ?