audiocommander

hey the description sounds cool :) I asked for any companies in germany that sell spectraSymbol stuff, but the thing is: most spectraSymbol products get produced on demand based on custom specs (like PCBs); so with most orders there are 1000 EUR gone for "making the production masters"... but I've been told they are about to produce some standards for users like us, it sounds like this is happening right now :D I can take a look in my bookmarks if this XY-Pad ordering will fail for any reason (which I do not hope! ;D ) ac. btw: has anybody seen the new KAOSS pad 3? just found a link in our wiki: http://www.midibox.org/dokuwiki/doku.php?id=trsequencer#korg_kaoss_pad_3 :o ...ui...

thanks Twin-x :) In the meanwhile I already grabbed the page with GetLeft and while checking the results I found it had left some errors within; whereas most of the links were formatted correctly, there were some second-level links, that GetLeft had forgotten to put the ".html" ending :( If I knew how to use Grep with a NOT statement, one could correct this in 10 seconds... Anyone knows how I could achieve this? Find: [tt]href="doku.phpid=[something]"[/tt] Replace with: [tt]href="doku.phpid=[something].html"[/tt] Cheers, Michael

probably yes. maybe no. dunno about capacity based touchpads (you know, like the one used for the iPod)... but if you found some of these, nothing is lost, maybe someone here around knows about these... softPots require a lot pressure from the finger, cap-based touchpads are more like touchscreens with almost no pressure required... you know this is like: what kind of hat fits on my head? just try it... even if you're coming across some exotic PS2 touchpads, I know there are people around here who have midified PS2 mice. The worst thing that can happen is that you got 3 touchpads you can't use. So don't spend 500$ on them, if you get 'em cheap, no harm will be done... cheers, ac

as I already said (in another thread?): the most difficult thing is to find the appropriate touchpad. even the samples from spectrasymbol can be different. the one goule has got, has 4 pins, so you could see to get one from there, too. I can't ask the seller about the pins, you got to do this by yourself. just google around a bit – good luck, Michael

hum... this is unlikely a pilot error: it might be that the program behaves differently on mac and win. a typical filename is for ex: "doku.phpid=c_tips_and_tricks_for_pic_programming.html" ...should be okay for other platforms, shouldn't it? cheers, Michael

you could connect the encoder by kroko-wires, so you can easily swap them for testing purposes... then you don't need to solder around ;) the LED should blink twice, but not with the ground connected to the Anode... Cheers, Michael

the search for "touchpad" reveals 49 auctions in Germany ;)

so, folks, time to get serious: no one tried the link of getLeft, right? :P tsss... ;) so did I... but now I tried, because I'm a PHP-programmer too and I cannot imagine that all application developers are so dumb to ignore automatically generated PHP pages. After installing GetLeft (which took me about 5.2 seconds) I am now getting a site-copy of the section "Application Development" from the Wiki, 2 levels deep, 1 level external documents, ignoring PDFs, AVIs, MOVs, ZIPs 8) This fine little app even has an option "update", so you must not snatch everything again once it's updated... I could rip it in depth next week and then seed a file, how is that? Should PDFs be part of the offline version? ZIPs too? Cheers, Michael

the biggest problem should be to get an appropriate pad. there are different kinds of pads out there: softPot based ones like from SpectraSymbol, resistanceBased or capacitanceBased ones from cannibalized old laptops... the best thing for you would be to get some, look out for resistance based sensors or softPots (if they got three or four pins it's perfect; if they got more it could get a bit complicated): order a free sample from spectraSymbol (need some commercial reason for that) or try eBay, I searched once and found a bunch of trackpads. Of course you can also try to mechanically design a new one; I have thought about a strong piece of plexi glued to 4 pressure sensors. by reading the pressure on each corner, you might get a nice reading; but the mechanical effords are not to be taken too easy! The best pieces to look out for are: - Volt-generating sensors ranging from 0 V to 5 V - Resistance based sensors ranging from 0 ? to 10 k? best regards, Michael Edit: behaviours like holding the position or not can be programmed in an appropriate event handling section; it should be necessary to program some lines anyway, but the better the device fits, the easier this is ;)

Hi basti, here you'll find existing encoder connections: http://www.midibox.org/dokuwiki/doku.php?id=encoders (see specifications) As there is no entry about Alps Encoders, you might try and find out the pin assignment. It's best to set the Speed to Normal if you are coding your own application; else just try it; there are just three pins, on of them is ground; most times the middle pin – to make a starting point you could use a multimeter; when it beeps on each turn, you found the ground then test in which direction it counts. there is also a testing application in the downloads section on uCApps. it would be very kind if you could add your informations to the wiki, once you found the right pins :) Cheers, Michael

hm, :-\ what's the issue with auto-downloaders (if restriced to 1 or 2 levels, html-docs only, staying on the domain?) http://sourceforge.net/search/index.php?words=offline+grabber&sort=num_downloads&sortdir=desc&offset=0&type_of_search=soft&form_cat=18 @stryd: if you want to provide an offline version, I could help (but not now, maybe if you pm me in one or two weeks?) would be traffic friendly if we do such a thing just once and seed a zip or CD-Rom instead of everyone grabbing everything all the time...

this sounds very coool 8) I got also some LED-arrays here, waiting to be built in... :) This is a great idea! I was about to suggest the same :) – it's been a long time since I've been to France (et mon français est très mauvais ;D) and if I'll go there, I'll make a stop in Paris for sure (maybe already this winter?) I had a meeting with Seppoman (the one who built the MIDI-Sofa) some weeks ago, this was great... I got these from Conrad, they are about 6,- to 8,- EUR each; so I'm sure you get them for 3,- to 5,- EUR from a "normal" shop ::): just type "FSR" in the searchfield (ARGH, Conrad is too dumb to get a site where you can send links >:( ) it's range is from 2kO if you press very hard to 20 kO if you press very gently; so I just added a 7kO resistor in parallel: [tt] ----FSR---- | |--- S + ----| | | |--- GND -----7k----- [/tt] It might be that the results gets a bit unlinear, but to be honest: I haven't noticed it :-\ ;D By varying the value of the 7k, you can make the FSR more or less pressure sensitive... I'm using these since 2003 and I really like them. In contrast to the Distance Sensor which are great for weeping and wooshing, playing a pressure sensor allows one to be relative exactly and accurate once you got used to it... sure, if you want you can peek into my sensorizer code (as I'm also using code from you, as already mentioned ;D ) – the main calculation is: max-min = range (10 bit) factor = range / 127 => for example 4 if f = 1,2,4,8,16 you can use bitshifting which is the same as a division / 2 each shift; so x >> 1 is the same as x/2; aka x >> 2 is the same as x/4 ...but it is of course much faster than dividing. So I'm using the complicated division routine just for factors 3,5,6,7 and if possible take a look to keep the factor even :) I think there was a great thread started by bill about nibbles and stuff in the C-Topic! So long (got to work now a bit so I can afford more sensors ;D ) take care, Michael Edit: Noticed I mixed up ">>" with "<<" >> is a bitshift to the right which is the same as a division through 2 << is a bitshift to the left, which is the same as a multiplication by 2

:) thanks! I've built my first instrument in 2003 and used director, then I rewrote it with Objective-C and now I'm working on shifting the whole stuff into hardware-boxes... About the sensorizer, I meant my wiki-userpage: http://www.midibox.org/dokuwiki/doku.php?id=audiocommander ...but the doku is not done completely; I'm still working on the sensorizer-page... (and your division function is still in good use, although preferrably fast bitshifting calculation is used instead :)) and I've not soooo many exotic sensors connected to, basically two Sharp Distance Sensors (the long range ones), and one FSR (Force-Resistance Sensor) that can be played very exactly once you got a feeling for it – together with one mid-range Sharp Distance Sensor. Because I've build my Sensorizer in an open way (with connectors), I won't hard-wire new sensors, but am able now to experiment a bit... as the Sensorizer provides an AUTOSENSE feature ( 8) ), this is very easy to do... I also implemented a "from/to" function which is great for all kinds of sensors, because you can restrict the range and then trigger the values with a really fine-tuned stepping... The Pedal now provides three different (combineable) modes: Filter (plays only when pedal down), Panic (on release), Hold (sends MIDI sustain) and combinations of all. Esp. the Panic function is very cool, because you can add rhythm to the elsewise slow sensors... maybe I'm also putting up a small video ? I am planning to implement two linear softPots from SpectraSymbol (the 8cm long ones, two stripes right next to each other)... next thing I want to do is experimenting with brainWave sensors :o and I've been also interested in Accelerometers, but until now they've been too expensive for my taste... What I have already done is to connect a skin-resistance sensor, which is a lot of fun if two people are using that; I've called it Kontaktstation... you can make body-contact-music... and last exhib. I had kissing girls... but hey, maybe that's info for another thread :) Anyway, I wanted to build the sensorizer as open as possible to use any kind of new sensors and store patches for the ones I have calibrated – I know the current project state is far from being perfect, because I've been a bit in a hurry, but at least it's working quite well, and AFAICS there are no buffer overflows... Sorry for long post, mate! ;D Cheers, Michael

well, in technical terms, this is exactly what the wiki-server is doing all the time ...sending HTML-sources to you ;)

just look around for some programs; there are a bunch of them that will do that for you. but please be careful and read the instructions twice; programs like these can create an incredible amount of traffic if misused... and that's bad for the page-owner and (maybe) also for you. Another option is to use a Pro-Version of Acrobat, it has also a site-fetching function. Set the values to remain on the domain and restrict the depth level! Or do it the old way: just store some html-pages that are relevant for you; I think most of the Wiki is still quite manageable ;) Cheers, Michael

;D now even more...

have you added the Encoder to the table in mios_tables.inc ? if you did so, try to call an easy function to determine if everthing is wired right, eg: on ENC_NotifyChange(): MIOS_LCD_Cursor_Set(0x0); MIOS_LCD_PrintCString("Encoder down"); Cheers, Michael

My 2c about Max is that it's proprietary and a lot too expensive, so I don't work with it; but I'm working on this for the MBHP platform: The Sensorizer is ready (see my userpage, pics still missing), Syncronizer & Harmonizer still to be done. In the meanwhile you just have to watch out for some software that converts CC's to NOTE_ONs. When your soundoutput is a single-voice synth, you don't even get no probs with NOTE_OFFs. Or you wait a bit... :)

hallo Braintu, das mf-programm ist (wie alles andere zum downloaden auch) auf uCApps unter downloads. die Funktionen, die du siehst, haben darüber im Kommentar eine Beschreibung, wozu sie da sind. z.B., musst du was in den Init() Bereich schreiben, wenn du was initialisieren möchtest, also beispielsweise einen Timer einreichten. Der Timer dann wiederum pollt die Funktion Timer() an... ganz einfach. Wenn du etwas mit einem Button machen möchtest (=DIN) musst du nur die entsprechende Abfrage in die Funktion DIN_Notifiy_Change() schreiben, denn die wird von MIOS aufgerufen, sobald sich ein Wert eines DIN-Pin ändert. Analog das gleiche mit AIN_Notify_Change()... MIDI-Messages werden im MPROC_() abgefangen. Hier muss man nur zwischen einer kompletten 2- oder 3-byte langen Message unterscheiden -> MPROC_NotifyReceivedEvnt(); einer vorkonfigurierten MIDI-Message -> MPROC_NotifyFoundEvent() oder z.B. einem Statusbyte -> MPROC_NotifyReceivedByte() Aber wie gesagt, steht eigentlich alles in den Kommentaren über der jeweiligen Funktion. Grüße, Michael

If you want to build a cheap low-tech solution, there are also non-contact switches. They got two feathers inside and only close the circuit if you shake them ("Rüttelkontaktschalter" jogswitches ???). They are cheap, lightweight, nearly undestroyable and by mounting some of them in different directions, I think it might be possible to get some interesting data out of it... Cheers, Michael

From what I know the sieve has to be developed similary to a photography or PCBs. You can print your design to a film (or a special thick foil with a laser printer; that's sufficient for most cases) and then the sieve has to be exposed on light by overlaying that film. I'm not sure what happens next, but if it's done, you have a perfect sieve to start printing :) I want to get into this and get some knowledge from my college mates, but I don't know when and where, but if I'll learn it, I'll post it here ;) Cheers, Michael

cool :) I wanted to access this function in _asm, but it's fine hearing that, thank you! When I saw your bug report, I was very reliefed in another point: as I'm using SDCC v 2.5.4. I have always had problems initializing all bytes of an Union; I just thought I did something wrong ::) Best regards, Michael

cool :) It would be great if you could update this information on the wiki-summary page: http://www.midibox.org/dokuwiki/doku.php?id=soundcards_with_ymf262_and_or_yac512_chips thanks alot - regards, Michael

Hey Goule, nice to hear from you again :) wonderful timing to bring this thread back to life, because I just finished my sensorizer; rewrote the whole code... it supports connection of up to 8 (different) sensors with a bunch of real cool features. Now I'm back from a gig where I tested it excessively and it did a great job! The generated values work great and it's a lot of fun making music with it! :D I'll have to do a bit of a clean up, edit some photos and will release my sourcecode somewhen this or next week, will keep you all updated in this thread! Cheers, Michael

:) congratiulations, too :) if I can be of any help, don't hesitate to ask! I just upgraded the sim-files, so that they support a bit more functions, tilted out some bugs and added some headers, so that implementing it is a bit easier. Although, if your breadboard-circuit is right, I got the feeling that maybe your chips are not fully damaged... I think it's quite difficult to distroy a chip purely by code. Have you tried it by resetting and connecting it only to RS232? As my sensorizer is done now (have to release it now...), I'll be back working on my SpeakJet-Control program, which is still very buggy until this point, but I'll resume working on it next week and will hopefully be able to release something very soon... Cheers, Michael