stryd_one

Wow that's about a million bucks worth of C130 propeller there... Can you do paypal instead? :) Glad it's working!!!

I think this is a totally awesome idea, and the design you mentioned should be a snap to whip up in C, based on the clockbox code. Because it's so simple, and *perfect* timing isn't a must anyway, you just need to whip up a few arrays for the tracks and iterate through them. How's your C? Probably would take just a few hours at most... I'd offer to do this for you but I'm totally swamped (and if I don't finish this document for TK he will banish me to the bottom of the planet... oh, wait.......) ;D Edit: Oh I forgot about the scaling. Ahh that shouldn't be too rough either... and I totally agree with tilt. Give it a button.

Gday boop, Unfortunately, the scale applies to the whole seq, not per-track. However the good news is that you can always add your own scales - and chances are, I've already converted your scale, as I converted every scale I could get my hands on, especially Eastern/Asian scales (I like them too :) ) The seq firmware is designed to have 128 scales max, but you can always recompile the app with your own scales included. See the Re: MBSEQ V3 talk post with all the scales I converted attached to it, and there's a section down the bottom with the excluded scales. Just swap one of them with one of the included scales, and recompile. If you have a scale which isn't in that file, feel free to send it to me (converted to that format if possible, or I have scripts to do it for you) and I will add your scales to the official source as excluded scales, so that anyone can use them in their own seq, and so that you can use the official source whenever there is an update. :) Cheers!

That's right - the 1st layer BSL prevents any uploads from overwriting it. As such, breaking the BSL is near to impossible. LOL. By all means try that - but don't call it a solution and don't blame mios studio ;) If you find that this works, but it doesn't work with "wait for upload req" turned on, then that is not a solution, it's a possible hint at the cause. You should keep troubleshooting in case that little problem grows into a big one, some day...

Actually this is totally different :) This way will be easier on the CPU but is way memory heavy in comparison. There were a few other tips I gave you regarding the timing of the other method, so that the core is doing work when it's not timing specific, that should overcome any problems though. This way will be way easier to code though, so go with this unless you need more RAM later :)

Yeh this is the same thing I've been talking about for a while now (you actually posted to one of the threads, but that was over a year ago so I'll forgive you for forgetting ;) ) the big stumbling block has always been the driver - I've written seqs and controllers for windows but never a driver. When I posted, I had been talking with plog about making the device an evolution of this one, but as it uses a rather different architecture (IIC_MIDI taking care of UART duties, PIC18F in the master core which talks to the LPT port, works standalone, etc) I think I should separate it from this project after all. However, plog has been kind enough to give me some tips on driver dev, which actually led me to some example source code (although very bare) that I had been looking for all along... so I should be able to overcome that problem and get it moving :) I'll start another thread about that project when there's more to tell, and stop hijacking here :)

Yes, I can see that you listed pin numbers, that's the problem. If you list pin NAMES then they actually mean something.

All 12 SR's dying simultaneously is not so unlikely if you've made a wiring error and possibly blown them up (which you have).... however if you're testing 12 of them at this point, then you're not testing correctly. Start with your core, and only one DINx4 module. First, run the SRIO test. If that passes, then run ain64_din128_dout128. If that passes, then add another DINx4 module and repeat. This is about testing one thing at a time, making one change at a time before testing each time. If you do your troubleshooting like that, then when you get a failure, it points directly at the source of the problem - the last thing you changed. I'm not sure about you, but I don't memorise pinouts for all the IC's I use... what are those pin numbers you mentioned? ;)

Well I had to google it, looks nice! I posted a while back about a freeby which seems similar (perhaps not as nice as Lochmaster but ~40 euro cheaper heh) DIY Layout Creator

Funny how when hippies and spiritualists say it for centuries, it gets ignored, until scientists can begin to prove it and give it a name (quantum *) ;D

I think you guys are talking about something different to the OP - he asked about visio, which is a flowchart tool, and thus I'm not so sure he's talking about panel/case design, which you all are... As for a flowcharting app, visio is as good as it gets. I use it extensively for my designs.

Nah man, it's just a matter of knowing what to search for - I thought that a few juicey keywords might get the ball rolling :)

Didn't I already cover this in the chatroom?

Quick post: 1) We're working on a opcode/motu style multi port design concept. Don't ask: it's likely to be vapor for a while, it's not a trivial task. 2) For those who don't seem to know this already, LPT-driven MIDI has the best timing, and USB has the worst. LPT good.

Poly aftertouch means a sensor for every single key...could be tricky! Also, with the 1M resistance, if more than one key is used they could draw a lot of current and maybe damage the AINs, and also introduce noise which could make false triggers. I don't know enough about this to offer much more advice I'm afraid :/ I'm not sure how pressure sensitivity allows you to play chords with two fingers? Sounds like you already answered this question :)

oh f***! I hit modify instead of quote and didn't realise SO sorry man! :( IIRC you said, you might as well convert the schem to protoboard, skip the balancing transformers, and order the THAT's from small bear... And you pointed out that JoeCheep is the What comp. WAY sorry man :(

Hah I never saw that uncyclopaedia article before :D LMFAO.

Did you not include the link because we'll find out it's been there for ages and you have been blaming Focusrite? ;) LOL What a coincidence that the windows support for the superior competitor-owned product was flawed ;)

Sasha: You're right, but fortunately MDF comes in different densities, so you can find it with more wood and less glue. I think I've seen this stuff before, it looks similar to the stuff that they use on the backs of furniture like chests of drawers and such.

There's a newsletter? And here's me, using the RSS feed. sheesh! ;D

NICE layout. [me=stryd_one]deletes his layout attempt[/me] I won't be needing that any more! Thanks Julien! Echo: you should look at the chip first and then ask ;)

1A is the limit of the stock voltage regulator. You can use a different reg, they come in 1.5A and 2A. If you want to know how much is enough, read the datasheets for all your peripherals (LCD, LEDs*how many LEDs you have, segment displays, etc) and use a calculator :) If your LEDs draw too much, then you'll need to add components to handle the extra current such as ULN2003 or diodes. This has all been covered, try searching with some of those keywords :)

You mean the albs ones? You could try asking albs! ;D

I didn't realise it was meant as humour :D

Exactly. I have a few commercial synths that do the same. I'd say go for it :)