audiocommander

no, [tt]unsigned[/tt] is neither a bool-value nor a bitfield. it just sais that it's no negative number. For example, [tt]unsigned char[/tt] is a basic type (typedefinition) and means that the number (char) is not negative. (mit / ohne Vorzeichen) signed char: -127 to 127 unsigned char: 0 to 255 char: range depending on compiler, normally -127 to 127 Here's a link to a very good C book in german: http://www.galileocomputing.de/openbook/c_von_a_bis_z/ and btw - we got an extra board for native german language requests: http://www.midibox.org/forum/index.php?board=18.0 Regards, Michael

Hi Artesia, the SID app is written entirely in ASM; and there's no C++, just plain C; but I guess this won't help you unless you want to code a complete Control-Core ;) sorry, I'm no ASM-coder, so I cannot point you to any real useful stuff regarding this issue, but maybe I could clearify some basics :-\ best regards, Michael

beautiful :D are the LEDs dimmed and therefore reflecting the pot's state or just illumated all the time? Cheers, Michael

ahhaha, WOOOOSH! now it's my brain exploding but at least it's nice to know, that I'm not the only one developing strange wild and beautiful schematics (even if in my case 9 out 10 schematics are bloody wrong... but nice to look at anyway) ;D hehe... Cheers, Michael

It's not available in mbseqv2. And yes, I meant that file. But mbseqv3 isn't released yet, so you got to try. A midi-implementation chart is normally done with all the rest of the docs once a version has a first stable release. 0x40/ 64| - | - | reserved ... | | | 0x7f/127| | | [/code]

just look into the implementation charts. they can be found in any relevant project that receives/sends midi!

Bill's code is right. Now you should look up in the MIDI-Implementation Chart if this is supported by the device: there's a file called "sid_cc_implementation_chart.txt" inside the sid directory that contains the entry: [tt] 123 | 7Bh | Assign Wavetable Parameter #3 to Controller | 0: off | 0[/tt] so ALL NOTES OFF is not supported with the SID application. Regards, Michael

out of the box: no but I think you just have to enclose [tt]MIOS_MIDI_Start();[/tt] and [tt]MIOS_MIDI_Stop();[/tt] around all places where [tt]MIDI_Tx_BufferPut()[/tt] is called (Clock). And set the Linker option for the Merger (see C-Function Listing). This should make it compatible for linked Cores. Best regards, Michael

http://sdcc.sourceforge.net/ :-X

hi poldie_pl, you should read the c-function list at the C-Page on ucapps.de http://www.ucapps.de/cmios_fun.html Then we have a quite good growing infobase at the wiki (section application development) with good tutorials on how to set up IDE's, though you're fine too if you like to use a simple texteditor. http://www.midibox.org/dokuwiki/doku.php?id=application_development Then you should grab the SDCC-Skeleton as basis. David is right to point you to the examples, though the MB64 is coded in ASM, so it's not suited to learn C. The download section at ucapps.de lists all available C-Projects ordered by programming language (see bottom of dl-page) http://www.ucapps.de/mios_download.html There are a bunch of additional examples spread here in the forum and on the User-Wiki Pages. Best regards, Michael

IIRC under 10.3.x you have follow these steps to make JAVA5 the default surrounding for apps: http://www.midibox.org/forum/index.php?topic=5230.msg41214#msg41214 ;) With 10.4.x this has changed. Cheers, Michael

The last time I included the lib it took about 5k of space (too much for my taste for one or two divisions). I'd be interested to know if it's less in the meantime, although I doubt it. I've heard different opinions here, but IMHO, it's best to avoid complex divisions, use bitshiftings if possible (*2 and /2), or add __asm-optimized divisions (eg from the piclist) if needed and use the hardware multiplier (asm). Sofar I never needed any pointerMath, so I can't say anything about that. Cheers, Michael

Hi Karlchen, it's always hard to say what's going on from the distance, but the messages you see are definitely cheesy. Do have something else running that could be sending a clock? Is the clock coming repetitive or just once? -> if it's repeating: are you sure, you wired the I/O of MIOSStudio right? I don't know how relyable Mike's PICs are. SmashTV's are extraordinarily relyable. So I thing it's more likely that there's an error with your solderings somewhere rather than you got a bad PIC. If noone else is answering the next few days: could you post a bit more informations (and maybe some longer snippets of what messages occur when you're switching the Core ON). Cheers, Michael

wow these are really looking great! Sasha mentions a lasercutter. Now I want one, too :-X Cheers, Michael

Hi and welcome. I think this covers up most of your questions: http://www.midibox.org/dokuwiki/doku.php?id=introduction_to_ucapps.de Regards, Michael

the MPC1000 is a MIDI-Production Workstation from AKAI: http://www.thomann.de/de/akai_mpc1000_black.htm (available in other languages as well). That guy wrote an alternative firmware for it. I don't know how it could be connected in any way with midibox.org ??? The pages are available as well by google's autotranslation. So at least on can assume what it's all about :) Nym wants to add a sensor to this, but as it's hard to know: - what's inside the AKAI MPC1000 or - how the personalized firmware is working (it's not open source; saving is disabled until you put in a password-phrase) it's nearly impossible to give any hints. Cheers, Michael

mess has been so kind to already mail the code for strglength to your last topic: http://www.midibox.org/forum/index.php?topic=8374.msg58278#msg58278

Hi Rio, you have to include the mioslibsdcc. You can find a description how to include it inside the download page (README.txt). IIRC, the lib can be downloaded at the C-Page; but I guess you already have it. Regards, Michael

Haha, yes, I ignored this neat little application (template) much too long :) of course, I do :) As soon as my current project is finished and all bugs ruled out, I'll put up the sources (as always). Maybe later a small standalone Quantize Box 8) Who knows? ;D Or are you interested only in the master/slave part personally? I could post the relevant code sections here... Cheers, Michael

heya, I was just plain' around with the clockbox class and extending it with a MASTER/SLAVE mode, so that it automatically switches to SLAVEmode if a CLOCK is detected on the MIDI-IN and falls back to MASTER if no more clocks are received. (ohh, I'm so excited, it works so great!!!) ;D ;D 8) 8) Because I want my app to be able to run for a veeeeery long time, I checked the meter count and think I discovered a small bug: unsigned char mclock_ctr_measures; // counts the measures (up to 65535) I guess this should be an [tt]unsigned int[/tt]. It's a great template, btw! :D This was just what I needed right now for the magic speakjet interface and the upcoming quatizer module :D Cheers, Michael

Klar, schau doch einfach noch mal in Ruhe auf die mbhp_iic_midi Seite ;)

Hi dcer10, You can find all the specs here: http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_basic#required_hardware The sensorizer is restricted to 8 Analog Inputs. Therefore no AIN-Board is needed. That's because it would be too much calculation. Also, be aware that the GPs actually use current; 1 SHARP sensor needs about 20 to 50 mA. If you hook up 8 of them, up to 400 mA are needed, which will increase the power regulator's temperature noticeably (or even succeed the power supply's features!). I use it with 2 – somethimes 3 – Distance Sensors and an 800mA supply and it runs fine. No, it's just for one pedal, but you can specify which sensor(s) should react to the pedal or not. You can use anything that outputs a Voltage between 0 and 5Vs, but it's the sensorizer's reason to live, that it must not be exactly 0 to 5. You can for example use a sensor that delivers 0.5 to 1.5 Vs and setup the Sensorizer to trigger CC's in the range of 35 (@0.55V) to 85 (@1.5V). So be creative :) The interface is quite configureable and you can easily hook on a bunch of voltage based devices. There's a lot more out there than IR distance sensors or skin restistance circuits, just experiment a bit and I'm sure you'll find the perfect ones for you ;) You don't need to hook up the same devices, you're free to mix 'em. Each of the eight allowed sensors can be configured independently! Farnell.com is quite cheap and that's where I got them. Conrad has them but is 150% more expensive. Just search google for "Sharp distance senor IR" and $ or EUR and you will find plenty of shops. It would be an overkill to list all the detailed infos here, 'cause there are plenty of different models differing in range. So it's up to you what you like best. I like the 1.50m and 80 cm models. Just watch out, that you don't buy those with digital output (just ON/OFF) but instead get those with an analogue voltage range! Cheers, Michael ah, and btw: I hope you realized, that nearly everything is already implemented, but one basic feature is yet missing: the NOTE OFF triggers. I will add this when my ACSyncronizer Classes are ready. I'm currently over it, but can't promise any time. Don't expect it too soon. The problem herewith is that everything depends on note lengths and corresponding NOTE OFFs must be sent, too. That's not trivial and should work right to prevent hanging notes. In the meanwile, CC's will be just fine I think. AFAICR you can use a CC->NOTEON conversion tool (should be something available) and use it (with the Pedal as note-off switcher) with some monophonic sounds. Or use it for triggering (I've also done that: you can distribute samples over a range and trigger these).... you know, possibilities are endless :D

Hi dcer10, I'm fine; thanks. A bit too much to do and too less time to continue my MB-projects like I would, but I guess that's not much different from others :) -> The Sensors go to an AIN board, right. -> I would not recommend mixing sensors with 10k-Pots, I experienced jittering on the Pots which is (friendly spoken) quite annoying. Since I'm working only with sensors (AIN) and Encoders (DIN), that's no prob anymore. -> My second Sensorizer Project is complete, it supports up to 8 sensors and has very few settings. You can check it out at the Wiki. I have not released any sources yet, 'cause I got no time for it and noone asked. If you'd be interested, I can release a package. Here you'll see both sensorizers http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer I mean the second one: http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_basic I think the HUI of the first one is too complicated (can't remember what knob does what), so I'll definitely stick to the second one. I'm currently working on the clock module to syncronize the sounds. A harmonizer is already implemented! The rest (CC-Assignments, Sensor-Config, Bankstick-Support) is already working quite stable. That means I use it on stage an in exhibitions and never experienced a problem so far. And I like the simple interface: The left ENC selects the sensor (1..8 ), the right the menu (eg Harmony), the two bottom ENCs the settings (eg Basenote, Scale). The three buttons are: PANIC, (2nd) PEDAL, LOAD, SAVE. And yes, it's my own firmware and has nothing to do with an MB64/e. And remember that it's restricted to 8 sensors max, so you don't need no AIN. -> the problem in implementing the SHARP sensors with an MB64 are: - jittering of AIN - getting the full range (0 to 5 V needed, 0.5 to 3.2 V delivered from the sensor) electronically and not by code (don't think it makes sense to hack the ASM-coded MB source). That means if you'd connect a sensor to an MB64/e, you'd get all the time the lowest signal 12 (ALL the time!) and the max would be 76! -> CIMO started to experiment, but I haven't heard from him for a longer while -> Wilba explained to me how this would be achieveable, but to be honest: I'm no electronics pro and there are too much problems for my taste (negative voltage, and very complicated product range when it comes to opamps). And I never found any open circuits in the internet, which is a bit cheesy I think. Anyway, that's what he told me:

Because for my taste I'm answering too much PM's lately, I decided to open up a new topic here. I asked Dcer10 and he had nothing against it, so I copied his questions and my answers here :)