stryd_one

Writing to any one of the LCDs doesn't take any longer than any other LCD... but if you have 4x as much screen and you writet to all of it, it'll take 4x as long.... (plus a little bit of overhead) I think MTE noticed TK's hint in the function reference and is running with it... it's fun :)

a bit of stiff cardboard won't hurt the pins either :)

Cool! Well most people find that a nice CS is just as hard as the electronics and far harder than the electronics... And that's going to be the easy part for you... I think you'll be fine! :)

The switch statement is one thing but my point was the other part... I'm glad you're with me now! (only took like 5 posts hahahah) Yeh it's far from elegant... I'm not sure why you can't build the meters into the edrum? How about a learn mode, so you put a channel on the midibox into learn mode, hit the pad you want it to react to, and from then on, it monitors velocity for that note? I'd still build into the edrum if possible.

You don't have to be crazy to DIY here, but it helps....

Are you getting core reset midi messages? How's it go with the LCD backlight disconnected? Are they ultrabright leds'? They are a bit large for my liking, but the silver colour goes nicely with the red and black. Nice looking box!

There's special foam you should use, and the old fashioned way was foam with foil on top to keep all the pins shorted... I think the idea was to ensure nothing jumped through the chip because the foil was always the shortest (least resistive) path to anywhere.

Hey dude Cimo is totally right. Anyway just for info: El bizarro. Does anything change, or get moved, or anything? Does the temperature in the room change a lot? Think of anything you can that changes... If there is anything. "Intermittent bugs suck" was my 'thought for the day' in the chat two days ago. And they do. They're the hardest thing to fix. You're correct, it's regulated... however, if the external voltage were low enough, and it was rated to 9V from 220....lets see..(lazy man breaks out calculator.... Calcutta rules.) 220/9 out = 24.4444444444444444 out*8.6 out = 210.2222222222222222 8.6V is stryd's magic voltage. I have problems every time I drop below that, even though it should BOR before it acts strangely. (Offtopic: My lucky number is 86. Coincidence? Probably!). So if your mains drops below 210.2' volts, you *could* see problems, if you're using a 220:9V transformer. If the lights are constantly dim (not dimming and then coming back, but staying dim for long periods) it's possible...But this is *very* unlikely. Chances are, it's along the lines of what cimo said. There's not much scaling to do here really... just add a step in somewhere, like 'if val=126, val=127' Err, I think you're referring the TK's magical scale7bit function, and it is asm optimised. You probably sow it wrapped up in C :) It's magical because it uses multiplication and not division, and does so using the PIC's hardware multiplier, so it happens in just a few cycles. TK is boss :)

zzzzzLOLzzwhat?! hey whatnow? oh... zzzzzzzzzzzzzzzzzzz ;D

Yeh but now I'm curious what you're building :)

One, or all of them? SO means serial output, I guess you are shorting the SO pin from the core, to ground - no data is sent when you do that... but yes, it could indicate a problem with the connection between that pin on the DOUT, and the core, as it suggests that the LED is lit because it's told to be lit (you're preventing that signal from arriving if it's pulled low by the voltmeter). Look for a short between a positive rail like Vss, and the SO pin... You should try the SRIO interconnection test app. Don't forget to upload it with the latest version of mios studio in smart mode with 'wait for upload request' turned on. Read the readme file and source code comments for instructions, and when you test the lines, test them at various points (on the PIC, on the pad, on the jumper, on the input and output of each DOUT) HTH!

That's the GM spec :) mirv: how does the midibox know which note# to monitor?

Well I guess that depends - is the MBSeq intended to be used primarily as a performance sequencer or a studio sequencer? The v1 was always quite studio-based but there are some performance-related things in v2, so it's hard to tell what direction to take... But I'd say that the MBSeq is still most useful in a studio environment, in which case this is not the kind of thing that it's meant to do... Edit: Still laughing at your FILO buffer ;D

Ahhhh... So how does the midibox know which note to show on which LED meter?

Welcome aboard Benjamin :) It kinda depends what you're building? If you check out the pages on ucapps.de you'll find your answer. It's strongly recommended to search around the ucapps.de and wiki pages and the forum before you post, because there's lots of information like this to be found. Good luck!

24 channels of midi thru? Otherwise, that's what I was talking about :)

Both those ideas are in my seq ;) In the first one you can control the current step of a track with another track, and in the second you hold a button down and hit the step to jump to that step. It doesn't reset the clocks though, that way it stays in sync; so you have to hit it before the step actually plays. I wonder if the MBSeq could do it? the first one might already be possible with the loopback ports, the second one I'm not sure...

I guess I can see both sides of the fence here... because there's no real tried-and-tested way to do the bipolar PSU, it's a bit sketchy to get stuck into it, and if you're new, you don't really know when you have all the info... I mean... How do you know you haven't missed something, if you don't know anything about what you may or may not have missed?* It's an unnerving feeling. But the guys are right, you'll be set to go with what you've got, and a bit of luck :) And, if you want to earn some serious brownie points, document it for us with pics and text and schems and test results and such, so that future NV-alike people will have no fear :) *Can anyone remember the GW Bushism that sounded like that?

And my first though was; Then why not: Hehehe. I shoulda read the post, before I bit ;) 24*8 = 192 = Too many leds to run direct off the DOUT chain... but you'd be mad not to do a matrix for this. You could easily use some existing code and possibly even enhance it to update the columns individually per-channel. I assume you mean drum channels though, as midi tops out at 16... so how will the edrum send the velocity data to the midibox? Lyle touched on this earlier, but you haven't responded to him yet... How you plan on the boxes communicating is not clear... this is your big obstacle, do this one first...

Careful... old fashioned luddite "learn theory, and practice" speeches may cause others to confuse you with stryd_one... Edit: still it's best to leave the screen (and everything else) unobscured wherever possible

HAAAAHAHAHA!!!!!

I'm not sure how more clear I could be, than to say 'yes' 'is good' 'for a JDM' ? You've been very patient though... Hopefully you now know why it is best to keep posts ontopic - otherwise people ignore them and you end up asking over and over ;D

I answered that the last time you asked ;)

That's why I said "before being recorded"...but this requires a secondary note buffer, and TK has pointed out that there is insufficient resources :( Tap tempo is fun but really is a gimmick. It can be easily replaced by changing BPM with an encoder, and experienced players can guess a BPM with better accuracy by ear anyway.... so I'd definitely say that more reliable recording would be a higher priority.

excellent! If you peel back the tabs from the sides (not the top) it's easier to get at them... also, if you flatten the 'bump' on a steady surface they should be more uniform.