stryd_one

There, a very ugly picture of how it's done. Very VERY ugly ;) uglywheel.JPG

Card #1 is an Aztech Sound Galaxy Waverider Pro 32-3D P/N:MMSN852 Card #2 is an Aztech Sound Galaxy Basic 16 P/N:MMSN810 Card #3 is an Aztech Sound Galaxy Basic 16 P/N:MMSN810 Card #4 is an Aztech Sound Galaxy Waverider Pro 32-3D P/N:MMSN852 Thanks for the high-res pics! :) I'll get that on the wiki ASAP. Edit: Done.

Aciiiiid! :) Thanks again TK!

Read ucapps.de and this forum and the wiki, all the answers you need are there.

Download the source code then! If it helps, here's how I figured out MIOS. I downloaded the MIOS source and an application. I started at the main loop of the app (MBSEQ, FWIW) and read through the code, figuring out what each and every command does, until I had read through it a few hundred times in order to exhaust all the possibilities. Where the code made calls to MIOS functions, I went to the MIOS source and did the same. All in all, it took me a few weeks of using all my spare time. I suggest you do the same. If you don't understand something, you can google it and you'll soon find an explanation. I think that TK has provided perfectly sufficient documentation, provided that you read that documentation and know the background info. If you don't know the background info, it's not hard to teach yourself.

http://www.ucapps.de/cmios_fun.html :-X

That is usually done by mounting two springs or elastic bands to the bottom of the wheel, pulling in either direction. Two pitchwheels is pretty unusual....What's that about?

I think it would be more polite to wait, and if smash is interested, let him offer to stock them. removed

The one on the right is a modwheel the one on the left is pitch. They're just unusual knobs mounted vertically on a pot with a limited throw. If you get a 10k pot with a 90 degree throw, you can use a disc cut from thick plexiglas with a holesaw as the knob, and illuminate it with a LED, looks pretty cool. Check this out

You could use a single core module, without DIN module and with one DOUT, to do either of these projects with a MB64 or MB64e application. I personally would not spend the time to create new hardware and software to do this job, the MBHP does a fine job.

OK figured out what's up with ucapps.de's tables. It's a three-hit combo. Unfortunately once again I think that it's a matter of following the DTD but interpreting it differently. Our three culprits are the TABLE tag's WIDTH and CELLSPACING attributes... <TABLE WIDTH=100% BORDER=0 CELLSPACING="5" CELLPADDING=0> combined with the CSS attributes for the table and it's cells. font-size:10pt; When FF renders the table, it takes the 100% width of the container, creates the cells, subtracts the cellspacing from the cell size, and wraps the text according to that size. When IE renders the table, it takes the 100% width of the container, creates the cells, and wraps the text according to that size, but then the cellspacing cuts down the size of the cells, leaving insufficient space for the text. Obviously the FF way is preferable, but there is are two ways to get them both to work - 1) Just remove the WIDTH=100% and allow the cells to take as much room as they need 2) Subtract the cellspacing from the table width to allow for IE <TABLE WIDTH=95% BORDER=0 CELLSPACING="5%" CELLPADDING=0> 3) Do <TABLE WIDTH=580.... Option 1) means less control but IE and FF both appear to render very similarly, and the result is close to the one we have now Option 2) gives more control, but renders 5% smaller in FF. Option 3) takes into account that all of this sits within a 600px wide table, and spares the 20px of cellspacing. This renders the same in both browsers but is more static. I think that given the non-dynamic nature of the ucapps.de site, option 3 would be best. Of course all that stuff I said before about whther you should bother fixing it still counts :)

I was hoping to get one of those cool trackballs off ebay last month but missed out, but this one does look cool. I like the idea of using them to navigate menus.... Are you ordering some mate? If so, are you interested in adding some to the order for me? We could split the shipping that way, everyone wins ;)

Yeh perhaps it's not a million dollars, but what price can you put on a rare collector's item.... bummer :(

Hi Nikifena, I had a look at your other post. Did you plan on using MIOS but not MBHP?

Yeh I think there's about 30 minutes drive between the three of us... Neiiiiighbours Ev'rybody needs good neeeeeeiiiiiiighbours.... LOL

LOL I know what you mean... I took a look at this and noticed that some were OK and some weren't... turns out it's the height="*" and width="*" statements in the IMG tags... Seems IE assumes *=0. WTF. I'm really not sure what's up with that because I'm positive that I've used it before. I have a feeling that it will resize the image to the object containing it (like a table or something) and because this image is not contained it has a null value for the size attributes of the container. If I could be f*cked, I'd make a page with some tables to test it ;) Anyway just thought I'd let you know the quick fix. I know exactly what you mean with that "get firefox" thing, but the unfortunate truth is that most users still run IE, supply and demand.... Personally, I have to use both for work because of various web-based frontends that don't work right with either FF or IE, but although FF is certainly more strict in it's observations of the supposedly accepted standards (grrr M$) the majority of people use it, so the majority of pages work with it, so it's set as my default because it's the one that works the majority of the time. Of course, then there's the moralistic side of the argument - sometimes it's tempting to say 'no, damnit, i refuse to condone this. follow the standards or miss out on my site.' The thing that really sh*ts me is that we shouldn't have to worry about this at all. How bloody hard is it to get the Mozilla, MS and W3C in a room and sort it out?! I think they're all as bad as each other sometimes....

Hi guys, A little thing has bugged me for ages so I thought I'd bring it up. As a one-time web dev myself I absolutely understand that browser cross-compatibility is a tricky SOB, so there's no pressure to fix these issues but... When using IE; ucapps.de chops the end off of text in some of it's tables and Smash's store's live board maps disappear These are both OK with firefox. I've attached screenshots to demonstrate, hope this helps. I'd be more than happy to try and fix this for you if you don't have the time or inclination, but seeing as I don't do web dev professionally any more I don't know if I could fix it as fast as you guys :) StupidBrowsers.JPG

Those SMD LEDs tend to be very small, might be hard to find one of a useful size... Although with a piece of frosted plastic on top, could be very effective. What about the square LEDs?

Good! :) It'll make you a better techo to feel what it's like to be the end-user calling for help. Try firefox and the map will work. I'll bring this up in another thread...

Has anyone here tried that method we saw recently with sitting the board on a clothing iron to heat all the pins simultaneously?

LOL ;D

hehehe I was too slow. check out the link at the bottom, that guy's got good ideas! http://gregwaltzer.com/egw/arpeggiators.htm

I've got a couple but I plan on using them, sorry mate. Good luck!

Hey man how's the arm? You might want to think about note order and priority going into and out of the buffer. We only have 10 fingers, but what if it's a holding pattern where you keep stacking on the notes? :) And if it's going to be a dedicated arp,then you should have plenty of memory so what the hey. Have you seen the Kawai K5000 arp? That thing is kickass, definitely a good model to work from. Did you have that sequencer thing on the go still, or should I go ahead?

Nice! Thanks Bill!