bosone

after the first "games", i decided to use this thing as a "Live controller" to automate the sequencer... now i can play/stp/record/move thru measures with this joypad! ;-)

i was thinking about adding some led to my midibox controller (since i bought about 100 leds at 2€ at a flea market!) my midibox setup has become the following: i have now 7 pushbutton assigned to CC, in toggle mode i'dl like to add a led below each button, so that when i press the button (CCval=127) the led lights, and turn off when i depress the button (CCval=0) i see in the main.asm this code: ; This DOUT map allows you to customize the MB64E application to different hardwares ; The MB64E dump structure allows the use of up to 64 LEDs, they are grouped to 8 LEDs per shift register ; Define the used shift registers for the LEDs here ; the shift registers are counted from one - means: 1 for the first, 2 for the second, etc... ; mark unused LED groups with 0 ;; NOTE: by default, the first four DOUT shift registers are used for the encoders #define DEFAULT_DOUT_SR_PIN_01_08 5 #define DEFAULT_DOUT_SR_PIN_09_16 6 #define DEFAULT_DOUT_SR_PIN_17_24 7 #define DEFAULT_DOUT_SR_PIN_25_32 8 #define DEFAULT_DOUT_SR_PIN_33_40 9 #define DEFAULT_DOUT_SR_PIN_41_48 10 #define DEFAULT_DOUT_SR_PIN_49_56 11 #define DEFAULT_DOUT_SR_PIN_57_64 12 i have 4 shift registers and only one ledring for all my 16 encoders, so i have 2 shift register left. i assume i have to set #define DEFAULT_DOUT_SR_PIN_01_08 3 then i read this: ; above these buttons LEDs should be mounted to visualize the selected parameter ; (e.g. to visualize the bank which corresponds with the buttons below) ; Define the two shift registers which are assigned to this function here: ; 0 disables the GP LEDs (not recommented!) #define DEFAULT_GP_DOUT_SR0 5 ; first GP DOUT shift register assigned to SR#5 #define DEFAULT_GP_DOUT_SR1 6 ; second GP DOUT shift register assigned to SR#6 i guess these settings are only for the general purpose button function, which i dont' need (i don't want to visualize the bank or so on... only the state of a particular CC assigned to a button) my question, now, regards where i find and assign the LED <-> button relation, so that to a particular botton will correspond a definite LED. To complicate the things, the 7 buttons to which i'm referring to are a bit messed up... they are the button numbers 2,3,4,17,18,19,22... so they don't refer to a single shift DIN register... if it's too complicate i think i will give up! ;-) thanks anyway!

hi! i have a small keypad with 12 keys arranged in a matrix (like the PC one). i know that with some great tweaking one can handle the matrix encoding/decoding with MIOS but... is there a "standalone" version? what i'm looking for is some simple schematic to "convert" the keypad matrix into 12 standard on/on switches (or even less, i need only 8 buttons of the 12 present) then, i will simply connect these 12 ouput to a DIN module of the midibox without MIOS tweaking... i have also an old pic 16f874/7 to use for this task, if needed

hi! in a flea market, i found an old playstation 1 joypad for 2.5 euro... it has a lot of buttons! i opened it, removed all the chips, resistors, and so on, and i simply directl connected every single button to a midibox 64E DIN input using an old PC parallel port cable! not too difficult, indeed! now i use it to trigger notes events... a strange way to play but, neverthelss, funny and cheap! ;-) PS: i assigned notes events to the different keys completely random, based on a natural C scale (C,D,E,F... no accidents). playing basslines and synth lines "randomly" may be inspiring!

hi! i have just retrieved a small small numeric keypad with 12 keys. it has a matrix concept and 8 output pins. i'm sure it will work based on the same concept of the c64 keyboard.... i have still to look at your code and exampe, but meanwhile can you tell if the integration in midibox64E is straightforward? how did you managed to handle the matrix input and use the button as single inputs? thanks a lot...

what happens if i connect a led matrix to the sid core but i have not built stepC? i have only 1 encoder + some buttons for the menu. i wonder if i can see all the modulation matrix during patch editing or playing and the LFO meter even with a minimal contrl surface... is there some modding to do to the code or will it work "out of the box"?

ehila! benvenuto! allora, la midibox senza lcd è monca... davvero! un lcd 2x16 non retroilluminato lo trovi anche a 5-10 euro anche su ebay (guarda www.ebay.de) e quindi la spesa non è folle e ne vale la pena! per quanto riguarda il collegamento con la tastiera, ti dico quello che ho fatto io: tastiera out e midibox out vanno ad un modulo midibox merger "standalone" l'out del modulo merger va al PC l'out del PC va all'in della midibox per darmi il feedback in alternativa, se non vuoi costruire il merger, puoi attaccare l'out della tastiera all'in della midibox controller, abilitare la funzione merger, e collegare l'out della midibox al PC. in qeusto modo però non puoi mandare dati midi verso la midibox....

uhm.... i thought that maybe it's simpler to change the midibox 16E CC message like this: 1 = BF 11 [00-7F:40] ENC_MODE_ABSOLUTE&NORMAL LED_PATTERN_1 "Transpose V1" +-HEX where: "BF 11 [00-7F:40]" the F stays for midi CC=16, right?

great! :-) nowbut after trying it i found that i need one more step... since the CC dump is flowing from the SID (CC=16 due to other hardware devices) to my midibox 16E (CC=1) i'd like to change the SID CC dump channel number output, if it's possible... i had a look on the SIC_CCOUT.INC in particular in this section: SID_CCOUT_Handler_Loop movf TMP1, W call SID_CCOUT_Get ; get CC parameter value movwf TMP2 ; store value in TMP2 IFSET TMP2, 7, rgoto SID_CCOUT_Handler_Next ; (returns WREG[7] if non-CC value) ;; send CC movff SID_V1_BASE + SID_Vx_MIDI_CHANNEL, WREG iorlw 0xb0 call MIOS_MIDI_TxBufferPut movf TMP1, W call MIOS_MIDI_TxBufferPut movf TMP2, W call MIOS_MIDI_TxBufferPut movlw 8 ; add a short delay of 8 mS for slow sequencers call MIOS_Delay i have tried, with no success, to work on the first lines of ;;send CC movff SID_V1_BASE + SID_Vx_MIDI_CHANNEL, WREG iorlw 0xb0 call MIOS_MIDI_TxBufferPut but since i don't know the exact meaning of the parameters and how to handle them i moved with eyes closed and tried (i want to output midi data on channel 1): movff 0x01 + SID_Vx_MIDI_CHANNEL, WREG iorlw 0xb0 call MIOS_MIDI_TxBufferPut movff 0x01 WREG iorlw 0xb0 call MIOS_MIDI_TxBufferPut movff SID_V1_BASE + 0x01, WREG iorlw 0xb0 call MIOS_MIDI_TxBufferPut neither of these worked... my last try was: movff SID_V1_BASE + SID_Vx_MIDI_CHANNEL, WREG iorlw 0xb1 call MIOS_MIDI_TxBufferPut knowing that 0xb0 output a CC MIDI message on channel "0"... i assumed 0 as the "preset sid channel", and tried to change it to 1, but this time the result was a series of CC ouput to chennl 16 (my default channel)... is there a simple workaround?

well, problem solved after some time, at least!!! both sid and core slave were working (as i connected the midi cables and the optocoupler!) but for some reason (i was doing some tests...:) i changed the slave ID! :P so i reupload everyhthig.... last mios version, sid 1.7a and the correct device ID!

hi! how can i use a key on my SID control surface (for example the one used to choose SID4, which i don't have) in order to produce a CC dump of the current patch on the MIDI out? i'd like the same action provided by the sysex string: i) F0 00 00 7E 46 <device-number> 0E F7 Request CC Dump at the press of a button... thanks!

i plan to buy some old joypad in order to realize something like "press play on tape" did on this video: http://www.pressplayontape.com/dl.asp?id=CannonFodderVideo (in divX) basically, they are playing notes with several kind of joypad... wonderful!

faster than light!!! thanks as usual thorsten!!!

how can i modify the code so that when i change the edited layer (note, velocity, length...) the fast button reset itself? i often use the fast when i change the velocity, but then, when i come back to the note/gate event, i'd like to automatically disable the fast behaviour of encoders... thanks!

Hi! i have 2 sid connected master-slave with step a control surface. suddenly, the slave doesnt emit any sound.... :-( i see that the audio ouput is not zero and there are transients at power on/off, but midi doesn't work and the slave doesn play (while the master do). the channels are OK, and the LINK from master to slave is activated (if i press the link button i see the event from the midi out, so this software part should be OK). since i upgraded the master (only the master) to 1.7a several weeks ago, are there some software trick that i missed (apart the link) in main.asm?? is there a fast way to debug a slave?? if i connect midi in/out to the slave, should i see midi events (ex: ping) even if the device number is 1? any other ideas??? i checked the connections and, at a first glance, they are ok. i even tried to switch audio outs and even the two sids, but the chip are working, and all the voltages seems to be OK. thanks!

thanks! it almost fully works with the SID and its wavetable. the "almost fully" refers to the fact that the wavetable step 0 is not yet transmitted. all the other seems to work! thanks again! matteo

at least we succeeded!! :-) i remember, however, that latest jsynth versions worked... so maybe it's possible! thanks, anyway!

GOT IT!!!!!!! ;D but i think there is a bug!!! :-\ preamble: my SID is assigned to CC16, while its device ID is 00 if i ping with F0 00 00 7E 46 00 0F F7 i obtain F0 00 00 7E 46 00 0F F7 so the device number is 00 in the jsynth windows, i set 16 as channel and 01 as device (01 is the only way to make it edit the parameters...) the problem is that, when you work with the wavetable, jsynth is using the CHANNEL and NOT the DEVICE ID to build the string!!!!!!!! i think that the other parameter transmission is held in a different way, so that the sysex string construction is different, and it works. this is the reason why you saw "0F" as device ID.. it is the channel!! (16 DEC = 0F HEX)... even thought my ID channel was set to 01! another proof: if i change the channel to 1 i'm able to change the wavetable parameters ONLY (the only one that it seems to NOT change is the #1 parameter of first step (step 00). the other seems to work... so, finally i think i understood the situation.... :-) maybe your sid has both channel and ID set to 01, so this bug is not evident... :-) i set to the Channel to 16 becuse the SID is connected with midithru to a korg 01RW! anyway... i hope that my explanation is correct! thanks for your efforts! matteo

well, yes maybe this is the topic.... i will try soon... but meanwhile i still don't understand why the other parameters are working... :-) thanks a lot anyway! i'll report tomorrow!

UNBELIEVABLE.... I did countless test... but still the damn wavetable cannot be edited by jsynth!!!!!!! i reinstalled SID 1.7a MIOS with a small custom change regarding the led out (J5 enabled) and the 6580 filter i installed midijoke as suggested. i installed lates java version i'm using the jsynth release found on your site (JSynthLib-0.20.0_midibox_mod1.jar) so i think everything should be OK... first step: i edit the parameters with jsynth, and using midijoke the sysex are monitored in midiOX. midiOX pass the sysex to the SID via the soudncard ( i can choose between 2 soudcard, neither one works...) everything is OK. the SID is correclty receiving all the parameters edited, BUT NOT THE WAVETABLE ONES!! the only way to update the wavetable is, as said, to save the patch, exit, and reload the patch. second step i connect the SID MIDI IN cable to the SID MIDI OUT cable thank to a midi female-female plug. i sent sysex to the sid in with jsynth, and with midiox i monitor what is actually arriving at the sid. all the sysex message correctly pass thru all the cables. (this mean: i send a sysex message with jsynth; the sysex goes out with the soundcard midi out, it arrives to the midiplug and it is sent immediately back to soundcard midi input. the stream is OK) just to make a simple test, i enter this wavetable sequence in jsynth (starting from a blank patch) STEP 00 PLAY +02 +00 +00 STEP 01 PLAY +03 +00 +00 STEP 02 END +00 +00 +00 and this are the sysex strings that arrive to the SID. F0 00 00 7E 46 0F 01 01 02 F7 F0 00 00 7E 46 0F 01 04 01 F7 F0 00 00 7E 46 0F 01 05 03 F7 F0 00 00 7E 46 0F 01 08 03 F7 nevertheless, no modifications are made to the wavetable sequence................. the wavetable parameter seem the only one which are not edited. last question: what is the last parameter found in the wavetable menu P# after the CC1, CC2, CC3 parameters? my P#1 is set to 1 i suppose it is related to the patch, but i can't figure out what is the use... thanks again!

nope... i have installed the lates java runtime environment, but the problem perist! i have also tried 2 different soundcards: creamware pulsar and soundblaster live... nothing! the wavetable is not update... the only way to send the parameters is to close the patch and reload it... ??? ??? the last hope is to try something like huby loopback device or midijoke

yes... i modify the wavetable and then press "Update"...nothing happens...neither do when i change the line BUT as you suggested, if i close the patch (saving the changing) and then reload it, the wavetable is updated. the situation is indeed very strange... the sid is receiveng sysex since all the other parameters are working.... may it be an old java version? i will try to download the latest version (don't remember which one i have...) thanks!

Hi! i began playin again with my SID. i have installed the JSynthLib-0.20.0_midibox_mod1.jar.zip (found on thorsten site) it seems to me that the "Update wavetable" function is not working... i have checked also with midiox: i sent the midi data from Jsynth to midiox and, while all (well, i have not checked them all....) the other parameters output sysex data, when i press the "update wavetable" button nothing happens... i tried also older Jsynth verions (i recall the button was working), but - i don't know why - they are no wroking now... even if all my midi equipment is off they continues to say "midi driver is flipping out" and they don't start... any suggestion? thanks!

HI! did you guys know www.pressplayontape.com these people are genius... they play covers of old C64 game with real instruments... and they also played live!! i must have their CDs! :-)

i dont' have access to my seq right now, and i dont' use it since some months... i forgot one thing... is it possible to have a midiout for each of the 16 knobs (multiplied for the 3 layer - note/vel/length?) it would be interesting, for me, in order to control a Creamware softsynth which incorporates its own sequencer... :) thanks!