audiocommander

...and don't forget to post your project on the UserProjects Wiki page! ;)

I was searching this forum and found an interesting suggestion from Shadyman: This solution would take the load from the midibox server and could be integrated into the forum gui... seems like a good compromise :) regards, Michael

don't worry, cimo :-* that's why I meant the "new" IRC, I wasn't intending going back to the "ancient" one, warming up old issues :( ... IIRC somebody registered another channel some days before we got the flash chat module? regards, Michael

then shouldn't we be in the middle of an iceage, now that everyone's a pirate that owns a cd-burner (or a videocamera or a music recorder or a pen or ...)? ;D (I love that chart anyway)

I'm not really amazed about this. My hoster is domaingo which has good prices, but Chat-software is forbidden, because it draws too much processing powers from the servers. So I can imagine that a flash-chat-server is probably eating up even more resources... so I do perfectly understand Twinny about this decision. I also think it's better to keep this site up & running and eliminate stuff that makes it slow or unreachable (besides the possible effect that some other things Twinny is hosting might be endangered as well!) Maybe we can instead add a link to the new "official" IRC-channel somewhere? That should be fine, shouldn't it? ;) Best, Michael

Hi matyt, I don't understand what your question is exactly, so I guess you want to find out how to change the midi channel if you send a message by code. The channel must not be set once, it is sent along with every midi message. Check out these basic links: 1. http://www.midibox.org/dokuwiki/midi_specification (a good & quick summary how midi messaging works with more links if you'd like to dig deeper) 2. http://www.ucapps.de/mios_c.html (also scroll to the bottom to find c examples) 3. http://www.midibox.org/dokuwiki/application_development (general app dev infos) Regards, Michael

it's a php script; the extra line is probably a bug (a "\n" too much somewhere), and the misbehaviour of a single quote is a common problem when scripting, because in PHP a single and double quotes both can begin/terminate a string. So I guess one must add a check for a quote and then -if found- add a trailing slash before "\"... that may probably be easy (or not, I haven't looked at the code). I think, the best way would be to contact the name, 'cause if you're going to hack the boxes-plugin, we all might forget about this sooner or later .... then one year after Twinny is updating something - woosh - and all hacks are gone :-\ Maybe there's even already an update available that fixes these issues? Still better a buggy boxes plugin than none :) best, Michael

http://www.midibox.org/dokuwiki/wiki:playground ;) I wouldn't call it "broken", just seems you discovered some bugs, that can be easily "worked around"... - and boxes shouldn't contain too much info anyway, just a quick overview or an important announcement Cheers, Michael

really? I'm always suffering badly when I have to read white text on a black screen, because I still see white stripes - well five minutes after I looked at the screen. Anyway: aren't there some CSS modifiers for the browser of your choice? For Safari, there's Safari Stand which can alter almost any CSS. I'm sure, there's something for Firefox, dunno about IE... Cheers, Michael => 8) hehe...

ehrm... have you switched on your display, mate? ;D

Hi Martin, it's gone a bit dormant, yes, but besides the missing HUI, the application is quite stable. You can trigger all allophones (all sounds) and control the pitches Just take a look at the features: http://www.midibox.org/dokuwiki/speakjet_application_software_v_0.2#features (missing information for v02 can be found in v01; basically it's the same, just a bit more and lots of bug-fixes and the new AIN-control -> handtracker) ...and the SpeakJet datasheet: http://www.magnevation.com/pdfs/speakjetusermanual.pdf ...and the board construction, all pins (and audio-out) are marked: http://www.audiocommander.de/downloads/midibox/mbhp_iic_speakjet_13.board.pdf http://www.midibox.org/dokuwiki/speakjet_breadboard_construction I guess, you already found the main doku-site where all the above information is linked... http://www.midibox.org/dokuwiki/midibox_speakjet Best, Michael

Hi, Captain Hastings has created a MIOS GLCD character creator: http://www.midibox.org/dokuwiki/graphical_lcds and direct link: http://compiler.kaustic.net/glcd/ best, Michael

okay, this seems to be too complicated, I guess it's easier for you to check the update or use Mandolane. In case you still want to use the script: I guess you're trying this with a PIC18F4620... then you should do what the error message tells you: add [tt]-mem_64k[/tt] to the line where you call the script. (The script defaults to PIC18F452's with less memory.)

yup, you can do that ;) Edit: ...but of course, you have to read the AIN states, because you don't know what to hand over to this notifier function; so it might be easier, if you read and send the states in the Init() ... or even better: split your functions into useful parts and call those...

it's for example included here http://www.ucapps.de/mios/ain64_din128_dout128_v2_0.zip

There's a script called "hex2syx.pl" (normally in the "tools" folder of the application) to convert the .hex to an uploadable .syx file: 1) open the terminal 2) type [tt]cd [/tt] (Space) and drag the tools folder into the terminal window, press return 2b) the hex2syx.pl must be set to "executeable". You have to do this step only once: [tt]chmod 750 hex2syx.pl[/tt] and press return 3) type [tt]./hex2syx.pl [/tt] (Space) and drag the .hex file into the terminal window, press return 4) the .syx file should now be generated. For a Windows-How-To see http://www.ucapps.de/howto_tools_hex2syx.html regards, Michael Edit: I've put this information in a new Wiki-Page: http://www.midibox.org/dokuwiki/hex2syx

Hi napierzaza, you could test uploading with SysEx Librarian. Before you upload, go to Preferences and vary the timing settings. Mine works fine with 750 ms length pauses. If you have troubles there as well, it's not Mandolane. And if you don't have troubles there, you have a convenient method of uploading your programs, but are still able to use MIOSStudio for other purposes ;) Best, Michael

salut :) (sorry, the following is too hard for me to write in french) : it may be that the MIDI clock manager of the kII introduces problems to your setup; it has a master-/slave detection; I don't know exactly what happens in this version when there are many devices working together - I worked a lot recently on the sync module, but for the ACSensorizer and not for kII, because there weren't many users building this project. I'm currently extremely busy, but if you concretise your problems with the sync, I may release an update for you. Salut, Michael

hmm, I really don't know what you're after - The Pic is a microcontroller and consists of memory and a processing unit that together perform basic mathmatical operations by moving around values in registers with the aim to set some logical values on some hardware-pins (high or low). That's it. It's pretty abstract, so that's what I meant with MOVLW and MULP instructions in the ASM code. The bootloader is just a simple program to set the PIC in a state where it can receive and store another program in its memory. So, either you want it technically, then you have to look at the datasheet (which contains far more than just a technical spec, it has 5.8 MB and contains everything you need to know about registers, memory, instructions - everything!) or you want a theoretical overview (which is contained in the wiki and on ucapps.de). But noone can save you from the hassle of reading it ;) Regards, Michael

hmm... you seem to have read the PIC's datasheet very fast... :P you can open the sourcefiles (*.h / *.asm) in any text-editor. ...although I do not understand, why you're trying to decypher asm code while the technical documentation of the chip itself is presented on a silver plate - in plain english text with a shimmering sexy blue link to click on - good luck with this, regards, Michael ps / Edit: have you seen this page? http://www.midibox.org/dokuwiki/mios

To be honest: Unless you aren't a ASM-Pro (which I don't think you are when you're asking how to open the files), I do not think it'll really help you to read thousands of code lines with MOVLW, TBLRD and MULP instructions ;D maybe the pic's datasheet'll be a little bit more helpful: http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010296 ehhrmm... how about "download"? :-X

Hi, MIOS is neither a "script" nor is it written in C (it's ASM). All there is, can be found at the download section: http://www.ucapps.de/ You should really spend some minutes reading the basics ;) Regards, Michael

bonjour matoz, je comprends bien le français, mais je suis très mal dans l'écrire/parler :D mais je vais l'essayer: 1/ c'est le SpeakJet chip. tu pouvais essayer de changer (améliorer?) le section "high-pass filter" (on the downside, if you filter the high hiss, the output will get very dull, you can compare this by swapping your loudspeaker from the filtered output (J5) to the unfiltered one (J3) ) 2/ comme j'écrit dans ma PM, tu trouve le "midi implementation chart" dans "IIC_SpeakJetMidiDefines.h"; je ne sais pas, pourquoi tu a difficultés côntroller via MIDI, j'ai un KORG microKONTROL, et c'est bon ;) salut, Michael

gut, das mit den Leerstellen gilt übrigens auch für "Program Files", wenn du einen Ordner "Programme" hast oder "Programs" würde ich für den Installationspfad der Tools/Programme dringend letztere empfehlen! Dass du mit dem einfachen (nachtraeglichen) Umbenennen von "Program Files" in "ProgramFiles" wahrscheinlich dein System killst, brauche ich wohl wahrscheinlich nicht zu erwaehnen, tue es aber trotzdem vorsichtshalber ;) Gruß, Michael

Was mir auch sehr komisch vorkommt: Im Standard-Skeleton gibt es kein "Porject" sondern nur ein "Project". Versuch's doch bitte noch einmal mit der unveraenderten Original Vorlage (Skeleton). Vielleicht hast du ja auch irgendwo einen Fehler oder noch mehr Buchstaben-Verdreher im Code eingebaut... Ach ja: und zwischendurch auch mal die temporaeren Ordner "output" und "build" (falls es sowas gibt) loeschen; denn ansonsten linkt der Linker nur die evtl. falschen Dateien immer und immer wieder (-> "Clean" before "Build") Gruß, Michael