audiocommander

Hey I just noticed, that I did get no notifications for the last two weeks or so - not even private messages! I tested my mail account and it's okay - I'm also running a SMF-Forum on my own server and I get notifications from there, so I assume it's nothing related to SMF 1.1.5. My guess is that there went something wrong at the server move (if I'm not the only one) - or that my Spam-Filter is eating the notifications. :-/ Anyone else having problems with notifications from here lately? Best, Michael Edit: changed the topic title to reflect the poll-question

Sorry für die Reaktivierung dieses alten Topics, aber ich habe hier ein Video bei eBay gefunden, das sämtliche deutsche Zoll-Fragen ziemlich gut und knapp erklärt: http://community.ebay.de/media.html?id=3686 Kurz: Zollbehandlung automatisch möglich, wenn außen Rechnung dran und Angaben über den Inhalt der Sendung, Gebühren fällig ab 5,- EUR, Bagatellregelung bis 22,- EUR möglich über 22,- EUR (ab 12/2009 über 150,-) in jedem(!) Fall Zollabwicklung! Gebühren: ZOLLEU (ca. 0% bis 15%) + EUST (19% MWSt) Grüße, Michael

http://www.midibox.org/dokuwiki/introduction_to_ucapps.de

Hi and welcome :-) no, you cannot use a core module to upload the firmware via midi, it has to be burnt with a PIC burner. Here are the instructions: http://www.midibox.org/dokuwiki/speakjet_breadboard_construction#burning_the_pic16f_firmware I can also burn the firmware for you, or we'll find someone near you (where are you from?) - in case you don't have no Burner :) I can give further instructions, just never been asked so far =) Basically it's just four SHARP IR-Distance sensors that can directly be connected to the AIN-Pins of the Core. I have to look up if I disabled the AINs in the application release, but this is quickly recompiled. I'm about to go on holidays, but I am monitoring this topic. Normally I'm answering quite fast, but I may not always have an internet connection throughout the next two weeks, so please bear with me for the next couple of days ;) Cheers, Michael

I think there are some misunderstandings here, because writing a *.mid file (and reading / playing it back) are a bit different from just receiving MIDI data, which was not clear to me while reading your first post and the topic title. As it seems to me that you'd like to work with *.mid files which are already existing, it might be easier not to invent the wheel again: There's a project that sounds like it could be useful to you. Note however that it's not related in any kind with MIDIbox - and it's ATMEL and not PIC-based: http://www.lehmayr.de/e_mrmidi.htm You could feed the MIDI-Out of this player/recorder into a MIDIbox Core that drives your valves. Regards, Michael

;D A strange screen where people think their MIOSStudio has expired sounds more confusing to me than a note, that the link to mmj is a beta version known to work for most, but unfortunately not all macs up to now Demo-versions are a lot less useful than any beta program. Also we don't know for how many people it actually works, because normally they just tell us if it doesn't work :-7 cheers, Michael

you're welcome. I really do love working with Xcode... so I hope it was worth sharing this knowledge :D

is there a chance to get the updated colors back with the server move? :-X cheers, m.

thanks for the warning! are you taking over the server? arrr.... ;D

Hi 80, no worries, bad error: the <code>Plugin in the wiki has been broken / downgraded and I haven't noticed that! It is now fixed and the code should be visible again: http://www.midibox.org/dokuwiki/how_to_use_xcode2_as_ide_on_a_mac Best, Michael

This topic has been moved to MIDIbox SID. [iurl]http://www.midibox.org/forum/index.php?topic=11850.0[/iurl]

sure, here's an example: http://www.ucapps.de/mios_c_send_range.html hmm... okay...

http://www.midibox.org/forum/index.php/topic,2510.0.html => http://www.seetron.com/lcd_an2.htm#crimp I got a crimp tool for 8,- € :-\ It's no fun when you got no/wrong tools. Best, Michael

if the 256 bytes are too less for you (which probably is not the case if you intend to store just one patch to be read after starting up), you could also just store a reference to your bankstick patch to point to an "autosave" patch or the last opened/stored patch. That's how I've done it and it works fine. Also, no double read/save operations are required. rgds, m.

Hi, the memory size of the PIC depends on the specific PIC you are using. two topics, that should cover your basic questions: http://www.midibox.org/forum/index.php/topic,5962.0.html http://www.midibox.org/forum/index.php/topic,8904.0.html best, Michael

...and btw some details about how it works: ACSyncronizer starts as MASTER; if a clock-byte is received, the state is set to SLAVE and the timeout counter is reset; in the ACSYNC_TICK Loop the timeout counter is incremented; if the timeout counter exceeds its limit, we know that the clock hasn't been received for a while = automatically fall back to SLAVE: // if in SLAVE-MODE check if master is still alive if( mclock_state.IS_MASTER == 0 ) { ++mclock_master_timeout; // check for timeout if( mclock_master_timeout > MASTER_IS_ALIVE_COUNTER ) { mclock_master_timeout = 0; // fall back to master mode mclock_state.IS_MASTER = TRUE; ACSYNC_BPMSet(bpm); // set old bpm value and reInit Timer // request display update acapp.displayNeedsUpdate = 1; } } [/code] pretty simple ;-) Cheers, Michael

Hi, you're looking at the wrong place - Midi Clock is no event (like a three-byte NOTE_ON or CC), it's a single byte and therefore in this function void MPROC_NotifyReceivedByte(unsigned char byte) __wparam { #if SENSORIZER_INTERFACE_SYNC // forward byte to Syncronizer ACSYNC_ReceiveClock(byte); #endif } [/code] and in ACSyncronizer.c you will find the appropriate handler: [code=ACSyncronizer] ///////////////////////////////////////////////////////////////////////////// // This function should be called from MPROC_NotifyReceivedByte // to update the MIDI clock ///////////////////////////////////////////////////////////////////////////// void ACSYNC_ReceiveClock(unsigned char byte) __wparam { switch(byte) { case MIDI_CLOCK: if( mclock_state.IS_MASTER ) { // fall back to slave mode mclock_state.IS_MASTER = FALSE; ACSYNC_BPMSet(0); // stops timer (passive call in SLAVE mode) // request display update acapp.displayNeedsUpdate = 1; } else { // reset lifesign counter (master is alive) mclock_master_timeout = 0; // call timer ACSYNC_Timer(); // passive timer call in SLAVE mode } break; case MIDI_START: ACSYNC_DoRun(); break; case MIDI_STOP: ACSYNC_DoStop(); break; case MIDI_CONTINUE: ACSYNC_DoPause(); } } it's all there :) Best, Michael

Hi! sorry, haven't monitored this topic, because I'm not used to the seq and asm applications ;-) Yes, definitely agree to stryd, just download the sensorizer source from the link above and take a look at ACSyncronizer.h and .c These classes are an adopted version of TK's clockbox and support an auto master/slave switch. You may also look at the main.c file for the forwarding and routing of midi messages. If you have then concrete questions, just ask in this topic - Best, Michael

Hey Shum - nice to hear that - glad I could help :) Best, Michael

Hi, for Absynth 4 see UserManual page 123 (4.9.5. MIDI Page -> PitchBend). It is clearly documented that every patch can interpret the pitchbend signal differently. have you taken a look at the midi specs page, so you'll know the difference between #cc and #pitchbend? if you know the difference, it's no problem to send pitchBends, either by using a software mapper (cc to pitchbend, quick&rough solution) or hacking the mb64 firmware if it's not supported anyway. I'm sure this shouldn't be too hard (sorry have no mb64 and am not used to asm - and therefore don't know this) best, Michael ps: You could try configuring your mb64 by using the controller of MIOSStudio or something similar...

the wiki box css is broken again: http://www.midibox.org/dokuwiki/ ;(

Hi, as far as I know, the bending range of Absynth is related to the relevant patch and not to Absynth in general. Therefore I don't see no reason why you shouldn't be able to use your Ribbon Controller. I'm sure there is an option to enable PitchBend signals (though I can't say anything more, because I do not have a MB64). For the difference between PitchBend and CC see http://www.midibox.org/dokuwiki/midi_specification Regards, Michael

Hi, does it work, when you're avoiding the number in your var-name? so don't do this: int FX1; but instead: int fxOne; if this doesn't fix your problem, you're using a multiplication somewhere ( "*" ), but haven't imported the sdcclib (as stryd_one already wrote) Best, Michael

Hi, in this case the ALL is relatively useless, but in general, a Union has the advantage of reading all states at once. So, for example if you have 8 bits that store 8 different settings, this union can be adressed as an 8bit number and easily stored and read back. see: your favorite C-book -> Union ;) best, Michael

Hi Olivier,