stryd_one

You might be surprised... When I got a shipment of 300 knobs I counted them three times, absolutely convinced that there should have been more than that. I have 45 of the waldorf knobs here in a ziplock bag, and it fits in the palm of my hand. They don't take up as much space as you'd think.

I think you based it on TK's Seq v2. You want v3. Trust me :)

I think this story makes a tiny bit more sense if you haunt the chatroom ;) A tiny bit!

Just to avoid confusion... or maybe create it (doh) that's not completely true... You write your code (*.c) and then it is complied by SDCC to output PIC assembly (*.asm) Then the PIC ASM is assembled into object (*.o) files by GPASM Then the .o files are linked using GPLink to make HEX files. These have the exact data that will be burned into the PICs program memory. The the HEX files are converted to MIDIbox compatible SysEx (*.SYX). You only need this step if you are uploading by normal midi, most of the time these days we use the hex files with MIOS Studio, which converts them on the fly and also has the 'smart mode' to make uploading less error-prone. This whole process is automated for you, you just need to run make.bat and it takes care of the rest. If you use codeblocks, you can hit a button or keyboard shortcut, and it will run the make.bat for you. It also monitors the output of that script, so if SDCC finds an error in your code at line 99 column 10, it will automatically jump to the relevant file, and highlight the line with the error and tell you what's wrong with it (in a cryptic kind of way). As I say, don't worry too much about all this, you'll undoubtedly 'get it' as soon as you try it :)

Search for 'perfboard layout'. Click first hit. Enjoy ;) http://www.midibox.org/forum/index.php?topic=7737.0

It's not that tall :(

Well when you compile your C application, it generates code in PIC ASM - which is that special language you spoke of ;) Theoretically, C is the same for all platforms, although there are exceptions, and SDCC is one, although the basic syntax is the same, so if you learn C for your PC the knowledge will transfer to MIOS, no worries. Code::Blocks is an IDE, which is basically a text editor on steroids. It will do things like syntax highlighting and autocompletion to help you write the code, and will interact with GDB to help with debugging your application. Don't worry about what these things all are, you'll soon find out when they are helping you :)

Thanks TK :D

Cool, thanks! My FM isn't finished yet :( But I'll keep you posted....

::) There goes any chance of the female midibox crowd going public! hehehe oh dear....

I'd like one and a half pink and green knobs, sent to Ayers Rock, on a net woven from the hair of 10000 lustful virgins. ;D

Again? not quite :) Earlier, you said leave the pins open - but I was talking about the PIC pins, not the LCD pins (tabs is probably a better word) This most recent time, I was talking about the LCD pins, the ones on the LCD module, not the core... Now that he has connected the D4-D7 pins to the core, given that the port is set to be an output in the init code, but the pins are left low in 4-bit mode, I thought that would have the same effect as grounding those LCD pins? Just want to figure out exactly what's happening here, as these 4-bit issues seem to be more common lately, and I'd like to be of more assistance next time...

Hahahah Well, I think that if there's a moral to this thread, it would be: "This is how you can do it, if you really need to.... which you almost never should!" If you find yourself needing to refer to this thread, chances are, you're doing it wrong ;D

It's just general browser compatibility issues... text and image alignment are the big ones.... We'll talk when you're back into it.

Is it too late to order a set? ;D

... in outer space.... ;) There's no reason that your PSU should be noisey, it may be the quietest around - but zero noise won't really happen... If you're after a PSU with schematics and partslists and instructions etc then you should look for NorthernLightX's work, there's a monster thread all about it.

Great news :) What'd you connect them to? If it's a 4685, with the normal ID, it should be running in 4-bit mode, so if you connected them to the LCD and it started working, then maybe the spare pins on the LCD (not on the PIC as I said earlier) need to be grounded? (because the PIC pins for D4-D7 will be open) Who's Tom? hehehehe

I thought I'd just say that spending a few extra bucks on a soldering station was a really wise call for me, it just makes the whole process so much easier. I got a hakko 936 clone (carefully chosen... the only difference with mine is the hakko logo is missing) which I've been slowly replacing clone parts with genuine. The parts are easy to come by and the iron is bang-on for what we're doing here. If you search ebay for solder* 936* you'll get the stuff. It's a bit more than 3 quid but definitely worthwhile IMO.

Whoops, we are now IN that subforum ;) Goblinz if you do decide to use Code::Blocks, give me a shout, and I will update the documentation first :) Some things have changed.... Nothing major, but enough to maybe throw you out on the first try...

Hi Julien, You should be able to find several posts and a wiki page or two on this subject, however, most agree that the easiest path to take is the c64 PSU, if you are able to get one?

Eep! thanks TK! :)

That'll be the part where the light bulb over your head sparks up, right :) As you are beginning to see it's not always so simple as that ;) Aside from the technical implications which seppo has mentioned, there are practical limitations, such as the 0.1mm LSB which Seppo mentioned. Not a lot of point in having 16bit message resolution, and 10bit finger/controller resolution ;) Then you'd end up doing many turns to get where you want. Imagine it with a soft takeover function, you could do several turns of your hand in the time taken to reach the takeover point, you might as well just punch in the number you want with a keypad... Imagine it without soft takeover, you'd change patches or whatever and then you'd have to mangle your sound for 2 or three seconds while you turn the pot to where you want it. You'd probably be better off using an encoder with a customised acceleration function. Or coarse/fine controls. Or a keypad. or........ etc etc. Point is: What control will be most suitable, will really depend on what it is controlling. If you're unsure what it'll be controlling, then you are designing a solution for a problem which doesn't exist yet, and what you'll essentially have is a very interesting and well thought out paperweight ;) Even with the example you gave of setting wavetable positions, I can think of several good control methods, but which one is most suitable, would really depend on exactly how you use the wavetables. It's a tricky subject. Because TK did it that way ;) I have a few theories but I don't honestly know heh You're not the first to take this path, and so far I don't believe anyone has seen the need for additional bit depth once they're tried it.... YMMV but I think you'll find that 10b is good enough for the vast majority of cases. and if not... Hey it's easy to try an upgrade later!

.... and you reckon you can't do ASM?! ;) Looks good to me at a glance... Does it work? You could optimise a tiny bit with stuff like the following perhaps... The gotos are a bit heavy... But I dunno if it's worth the effort to be honest :) IFSET MIOS_PARAMETER2, 0, goto CS_KEYMODE_NOTE_OFF ;; we're setting a note to on movlw 0x64 ; set velocity to 100 goto CS_KEYMODE_DONE CS_KEYMODE_NOTE_OFF movlw 0x00 ; set velocity ti 0 CS_KEYMODE_DONE could be: ;; set default note velocity movlw 0x64 ; set velocity to 100 ;; change to a note off if button has been released IFSET MIOS_PARAMETER2, 0, movlw 0x00

It sounds as though it's not even booting MIOS.... You said preprogrammed - was that by smashtv? Does the 7805 get hot at all? If so it might be best to stop here... Otherwise......... After your upload, did the core reboot by itself? Or did you have to power it off and on? When you boot and expect MIOS to load but just see the row of black bars, what do you receive on your midi interface? Is it just one message, or many? Have you tried to upload MIOS again? If you try to upload an application does the upload work? Does the app seem to work (except the LCD of course) Wilba once mentioned something about grounding (or was it connecting) the spare pins on the PIC when using 4 bit mode... You might wanna search for that, I had a very quick look but can't find it... Of course take the advice above also :) Good luck!

...and there's no mios driver for them............yet.....