stryd_one

I know, the first reaction just made me screw my face up. But with insurance, it can be a blessing in disguise. You generally should end up on top :)

Sweet as F**K!!!

I can fly a Cessna. VH-WWL Most awesome view in the world. If you go to Western Australia, take the Rottnest Air Taxi Service and spend a weekend at the island. You'll thank me for the suggestion later ;)

Right you are, DrB. I figured Google would unearth it but maybe not. Google's algo is going downhill. Yeh sparx I'm still getting around to plugging in my c64 or 128 :) I bought a stack of them and then got the chips from wilba afterwards...seems lame to leave it just sitting there collecting dust! Edit: Now there's a thought: Email the guy who sells the midi interfaces and ask him what they work with :)

Is it even a MIOS app? or is it one of the old projects? Think that should be fine :) Just attach it to a post... Ahhhh there's your problem. See GROT#6 in my sig. Test it with a midi monitor. We could be trying to fix a problem with your VST host and looking at the midibox! Cut the PC out of the equation, it should only act as a very expensive midi monitor for testing what the midibox sends ;) This helps us to isolate the problem.

If you've got a PLED (did i remember correctly?) then it might *say* that it's 4-bit compatible, but many are not - including Wilba's and mine - which is why Wilba made this 8-bit driver. If you have a different LCD it might be the same :( If it didn't work in 4-bit mode, then it doesn't work... Edit: When you ran in 4-bit mode, you had the four unused pins on the LCD itself and also the core LCD socket, connected to nothing, right? If you used an 8-bit style cable with the 4-bit LCD that might explain your problem. Well you won't **** the hardware up, so if you have a working copy of the firmware, then just copy it, and work on the copy. If all else fails, you can roll back to the original :) MIOS has a great feature where the ID of the PIC will select a certain driver. You just have to tell the assembler (GPASM) to build that driver into your hex file. The MB6582 package contains the custom driver that Wilba made. Just find the section in the file. Use the search, you'll find it :) Which ones? We'll fix em up. You worry too much :) You will find once you try it, that it's not as hard as it sounds (or sometimes, that it really is as easy as it sounds, even though you didn't think it would be) Edit: have you searched the forum for 4-bit LCD yet?

Heh... Honestly I'm not sure... I don't think it is. I probably picked up the word from one of my pommy mates. Australia has become a very multicultural society, and I've lived in lots of different places, and picked up words from mates all along :)

That's the "catch" with sketchup - if you want to export, you have to pay for the full version...

So how does torq support relative inputs?

This is easy. Did you insure it for a fixed value? Then that's what you should get. If it's insured for replacement value, then you can either get an equivalent system commercially (andromeda?), or, and this is how I did it with a similar situation, you charge them for the cost of all parts, and construction time X*Y where X is the amount of hours it takes you to build it, and Y is your normal hourly pay rate. Enjoy ;)

See that? That's a smile that only Ecuador's GDP worth of weaponry can bring. Peace, love, unity, respect,.....and tanks for when PLUR doesn't work.

Brilliant!! Hahaha that was my first thought too :D First thing in the morning....

I'm not sure, but did you google C64 sequencer ? I'd imagine any out there are on google.

So, no matter what, the encoder is spinning faster? heheh What we really need to know is what the device needs to receive. Can you tell us a bit more?

Arp-tastic :) Nice build man!

My 2c: DEFINITELY leave room for styroflex. Mismatched caps means mismatched frequency tracking and a few other nasties.... In fact to be honest, if you didn't test this, then you may want to do so before you spend lots of $$$ on PCBs. I'm collecting reading material for you now... I have a lotta links about this so it might take a while to filter (heh) out the crap ;)

stryd's not here, man.

Everything's available, and open source, so anyone can change or add as much as they need - just don't forget to share it when you're done :) You might like to look at the MIDIbox CV or Analog toolbox or MBSID (without SID chips), to use as a CV engine which will convert incoming MIDI messages to analog control.

This IS school! Trick is: you are not only the student, but also the teacher, principal, Mum and Dad, classmates, truant officer and guy smoking behind the cricket shed at lunchtime ;)

Plog and I were chatting about multi-client support a little while back too, and I've been cooking some things up which I'll mention later.... It's still alive :)

"Fix"? you mean "workaround" :) It's definitely best to do it the 'proper' way. I could go into lots of detail about why you should, and why it may not matter, but I'll keep it brief: If it was my midibox, I'd definitely do it Wilba's way ;)

Look, my very own nILS! He followed me offline, can I keep him?

I'll ban you! I'll ban you good!! For the new guys: I don't have any such powers, nor would I use them if I did! :)

Guessing by the original length of 160 lines, and your error at 164, that must be the very end of the file. Does it still look like this: return clrf CS_MENU_REINIT_CFG_CTR goto CS_MENU_BANK_RestoreCfg Note the empty line at the end. You need that. Seems like something's been diced off the end?

Fortunately the SEQ interpolates 24ppqn MIDI Clock to 96ppqn internally. Totally do-able, and TK did it, so you know the timing is bang-on.