stryd_one

I'll leave the fourier synthesis to my k5k, but I was thinking.... I wonder if this could be ported to a 16F88 module, controlled by IIC ? Could be a good basis for a DCO synth if you stacked the osc's up... Forgive me, I haven't read the code... Flat out at the moment :(

I've seen dudes do similar making skateboards. You have to use some pretty serious equipment to curve it well. I was thinking the other day about curved cases too... I came to the conclusion that fibreglass might be the best way to go, but my glassing skills are pretty damn limited...

Seeing as Artesia likes to cross-post his advertisements I'll do the same with my diss ;) There we go

My 2c... I think they're overrated. Total gimmickware. Just keeping things balanced ;)

Thanks! You could use the wiki for that :)

The black paint, it came out really pro, I thought the inside deserved a coat as well ;)

I'd check and make sure the compile target is set up OK... I've got a feeling that adding files in a certain way causes all of them to be set to compile, rather than just main.c ? I'm totally guessing :-\ I might have a go at this after dinner :)

That looks really nice, shame you didn't do the inside!

Welcome to the board mate :) Look forward to seeing the finished products!

Thx for the C translation! ;) FWIW I haven't forgotten the tables for the scales... I'm doing them little bit-by-bit, they're a bit low on my list, but I'll be sure to have them ready when TK says he will be releasing the new SEQ. In the meantime, I'm soldering so that I can hear the results and spot errors like those - thanks AC!

Exactly, now you're feelin me :)

Pot is short for potentiometer :) If you're not too sure what that means, I'd recommend running a search for some Electronic basics links ;)

Sorry I don't agree. The difference between a UDMA, SATA2, SCSI320 and FC drive, over 7200, 10K and 15KRPM, is huge. Also you have to factor in the cost of the motherboard and any additional hardware to drive it all... Memory isn't quite so subject to that, but for eg, if you're using lots of samples and using an app that is able to stream direct from disk, you'd possibly gain greater benefit from spending the money otherwise spent on 512MB of RAM, on upgrading to the next higher speed of drive...

wha? So the "e" in "test" is like 2.5mm tall? I thought it looked pretty messy, but I didn't realise it was a macro photo ;) Is this the tutorial you guys are using? I notice there's a kind of bubbly/pitted look in the black area, is that the texture of the etched aluminium, or the paint? I'm kinda interested in this whole etching thing for front panels, but I want a black panel with metal lettering/ines and I'm not so sure that'll work out OK...

Got a tube of them here, and known-good schematics (thanks to a kind donor ;) ) and I'll be breadboarding and setting them up for midibox control after some other projects are done.

buh? I dunno, I'm pretty sure that's right.... You made any alterations that might be conflicting? Maybe it's a hardware fault?

I'm gonna be a little different and answer your question with another question: What do you plan on doing with it? A DAW wears a lot of different hats these days, and obviously doing it on the cheap means making compromises. What you need to do is maximise your return on investment, by investing the lion's share of your limited funds in areas where you require higher performance, and compromise in areas which don't matter so much. For example if you're doing sample playback, you'd be better off with a fast drive and/or more RAM (depending on whether your sampler streams direct from disk) than spending big bux on the CPU... But for a live PA synthesis box, you want CPU grunt and RAM, but the drive is not so important... That's a very simplified example of course, the more specific you can be about what you need from the box, the more specific the performance tweaks can be. So I'll wait for more details about what exactly the box will do before I answer with a real answer :)

Glad it helped mate. The way the wiki headings work is really good for this kind of doco, because it allows the name to write out the entire procedure, but it makes it easy for the reader to skip to the parts they are interested in, so there's no information overload. I really like it :) I'm building a PC for the lab at the moment and over the course of this week I'll be updating the doco to include some stuff I missed, and to reflect new features in C::B - including how to get that nice graphical tree-view display of the variables when debugging, like in the XCode pic that AC posted (OK it's not that pretty but it's the same functionality). I'll also be posting links to the C::B, SDCC and GDB manuals, which can be really handy, and you might want to get before I finish ;)

www.piclist.com :)

Heh, he's been listing those for months :) This post probably should have gone in the official ebay thread though... just a thought for next time.

TK recommends two 2x40's yeh. According to the doc I always refer to a 4x40 will interface in pretty much the exact same way. I should have remembered that I'm using FF now and I can search my bookmarks :) I've edited my last post. In short: Yes, it'll work, No coding req'd... But it might look funny. Check out TK's Screenshots page for an idea of what will get broken up.

Welcome to the board alex. All you need to know is Here Here and Here For more info, please see my signature ;) Hehehe seriously though, you'll benefit a lot from searching around the three sites to gain more knowledge. All the things you're after can and have been done :)

Nobody has mentioned how totally f#&%!n awesome that first image looks. Hey TK I think that might look nice on the ucapps.de gallery?

It'll chop up the menus, but if that doesn't bother you.... FWIW the hd44780 spec doesn't allow for displays that big, they're handled as two 4x20's, IIRC, or two 2x40's, if I don't ;) Edit: I don't RC at all ;) a 4x40 works like two 2x40's stacked atop one another. See my next post.

sorry guys, MBFM is in ASM not C.