bosone

con il C non ho proprio esperienza... io sono partito dalla versione MIOS, che si segue abbastanza bene per come è scritta... conta che la gran parte delle cose che ti serve modificare sono nel main.asm (o simile... c'è un nome che non ricordo mai tipo setup_MB64.asm...)... ad ogni modo dovrai settare per avere 64 potenziometri (visto che si va solo per potenze di 2) e ricordarti di mettere a massa tutti contatti non utilizzati sui moduli AIN poi, una volta modificato il MIOS del MB64e devi compilarla con l'apposito programma mspasm http://www.ucapps.de/howto_tools_mpasm.html http://www.ucapps.de/howto_tools/mpasm4.gif e installare perl per convertire il file hex (assemblato con mpasm) in sysex per caricarlo via midi http://www.ucapps.de/howto_tools_hex2syx.html dai che ci salti fuori! :-)

thanks again for your work!!!

regarding db50xg, i know that somewhere, on internet, there are schematics to make a PCB to connect the db50xg via midi to a PC (for exampel), making it a standalone synth. i had downloaded the files once, and i have to find it if you are interested. moreover, there is a shareware editor for the db50xg (somewhere in the net...) which permit to use the daughterboard to its extreme (as for example making using 4 oscillator all together to make 1 voice).

i too think that the money should go to thorsten! :-)

well... maybe one can write some customization in the MIOS code, one it is setup, to send either controllers or note. for me, the best option is to have different notes on the same channels... but the point of dcer10 makes sense... and maybe even best would be to have toggle controller (0/127, press once=127, press twice=0) with different CC numbers on the same channels... but i feel that once the routine has been implemented in MIOS one should be able to "easily" change the sent midi event from a controller, to a note or to change channel and event (note number, CC number...) thanks anyway!

wow! :-) i feel that the toggle buttons should to transmit of the same channel, or maybe on the channel assigned by the mixer map, for maximum flexibility... thanks!

i confirm is nearly what i was looking for! i assigned the same channel to all the 16 "mixer events". then the "CC1 setting" (from CC assignement) was set up with CC numbers from 0 to 15 and the "CC2" setting with CC from 16 to 31. now the seq3 acts more of less as a midibox 16E controller! the best addition, now, would be to use the 16 GP buttons to send midi events to remote control for example the solo/mute tracks of the sequence (sonar, cubase...)... to to this they should work as "toggle buttons" (as in the midibox16E)... and the led should lit or turned off following theyr status... maybe this behaviour sohuld be possible only when CC1/CC2 pages are selected...

great! i didnt investigated yet the mixer mode, since i supposed not to be useful for me... i'll try soon!! :-) if the buttons would send for example note on/note off (which are held until the second touch of the button) or CC=0 at the first touch and CC=127 at the second touch, they can be used for example to solo or mute the tracks of a PC sequencer....

since the new pic seems to have lots of possibilities... what about the possibility (if it's actually possible!) to setup a mode for the seq3 in order to use the 16 pots, and all the buttons (beside one to turn off this mode!) as "standard" midi controllers (CC) like the midibox16E? maybe assignable only in the MIOS code and not by the user to not make things too complicate... or is this already available?

i'm a stupid! :P ::)

certo che si può mettere dentro lo scatolotto! la puoi mettere dove ti pare, è questo il bello! ;)

i'm using latest sequencert beta (build67) with no customization when i select events -> layer assignement 4 or 5 (the one which should be dedicated to drum mode) i experience an odd behaviour: it happens that when i select that track (ex G1T1), the 3 layer A,B,C are "linked" between them. so, for example, if i turn on the second note event in G1T1 A, immediately the same event is turned on also in G1T1 B and G1T1 C, making the whole track assignment useless... this happens also when i turn off the events or i select accent or roll... do i miss something or is this a bug?

after endless tries i succeeded... i turned off the midibox. tunrned on and started the upload procedure just after the power on.... but tomorrow i will download the latest mios studio! ;-) btw, the new features seems terrific!!! ;D

i have just mounted the new PIC 16F4620 (i have MIOS 1.9) with MIDI IIC module. the hardware is correclty working and midi out is received. BUT.... when i try to load the SEQ V3 HEX application (latest build), using mios studio beta 7_4 things go in the wrong way. the uploading procedure goes well, but at a certain point i receive some error messages: ... some Checksum OK message (a lot...) .... Sending block 00007E00-00007EFF Received Checksum: 14 - OK Sending block 00007F00-00007FFF Received Checksum: 6A - OK Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Sending block 00008000-000080FF Received error code 04: Write failed (verify error or invalid address) Aborting after 16 errors and at this point the uploading stops, and the hardwrae stops working. i have to transfer again mios 1.9 to let the midibox reboot (and read the "ready" meassage) i tried with several PC midi hardware out (i have three different physical midi out in my system) but none worked, always the same problem i also tried to use the "manual mode" upload procedure in mios studio, without hardware feeback, but it didnt worked as well... in this case i even tried to raise the delay time between packets to 400 msec i even try to mount the PIC in another hardware i have (the midibox 64E) but the problem remains and the uploading is not possible! to finish the debug, i tried to mount in the sequencer (always using mios studio and the HEX file) the old V2.4, which was correctly uploaded and it's running.... what should i do ??? any hints?! thanks!

great work... just some question... can you share the design of the LDR schematic? i don't quite understand if the LDR sensor are just variable resistors which maximum rate is 10K or if they need some sort of adaptation to midibox... when can i bought them and how much did you pay for them?? thanks!!

hey! that was the original question! :P actually, i can't imagine what possible i CAN do with that thing... but building it would not cost too much money and effort... the "real" problem would be that on my desk i have no more space to put it!!! ;D ;D ;D

i read several times in the forum that some people is using the C64 keyboard with some matrix decoding as a midi controller. my question is: do you use it for notes event, for CC events (on/off)... i.e. how use did you find for your musical applications??? is just a kind of enquire in order to learn if i should eventually build one... ;D actually... just a minimal core configuration would be needed, right? :P

i foudn that my pic16f88 cannot be programmed by my old jdm programmer... i even asked to some guys from the engineer department to help me, but the pic that they programmed for me is not working... i'm not sure, but if i use PICgm Programmer i can autodetect the PIC type and if i read the memory it say that it's all 0000 is that true? i'm pretty sure that my MIDI IIC module is built correctly, but givin 5V to the PIC, the IIC power led (connected to the PIC) is not lighting... eventually, can i ship the PIC to someone which are using a midi IIC module, just to have also a test of the PIC?? (this would be the last solution!!) :P

i tried to build a midi IIC module, and asked some collegue to burn for me the PIC 16f88, since the programmer i was using (ICPROG) didn't support this pic. now, i discover that the IIC module is not working, and (as thorsten said me), there must be something wrong in the pic programming, since the power led is not lighting... even if all the other connections seems ok... i foudn another programmer, winpic800, which supports the 16f88 and jdm programmer... do someone have experience with this configuration?? moreover, the winpic800 asks me for some details regarding pic cionfiguration... what should i setup?? in particular: ID: should be 0010 if i understood well OSC: i can choose between: LP, ST, HS, EXTCLK, INTRC I/O, INTRC CLKO, EXTRC I/O, EXTRC CLKO i suppose is EXTRC something... but which of the two?? then there are some checkboxes: WDTEN (x) PWRTEN MCLRE BOREN (x) LVP CPD DEBUG CCMPX (x) CP andi signed with (x) those enabled by default. finally, i see a column with "WRT" which can be either: off, 0000-00FF; 0000-07FF; 0000-0FFF and two checkboxes named FCMEM, IESO can someone give some help!??! :-) ??? ??? ??? i will try to build the 40 to 18 pin adapter for the jdm programmer, i hope that it will work... :P another question, regarding MIDI_IIC schematic: i read in the page: "An additional 1k pull-up resistor is required between the Vd and SC line (normaly soldered directly at CORE::J4) in order to allow "clock stretching". Thats a method to delay serial transfers when a slave cannot response immediately on a master request. The pull-up resistor for the SD line is already available at the core (CORE::R2)." ??? i see that this resistor is not present, either in the core or in the MIDI IIC midi out only version schematic... should i add it?!?! when i build the midi IIC module i forgot it... :P

in a few words... how is it connected?? is it a new additional interface or something to replace the existing one?

hi! finally i got my PIC 16F88 programmed, so i can build the midi_IIC module. just one (dumb!?) question... i understood that the IIC module has to be connected to the core PIN J4... is it right?? because in that pin there is already the bankstick... do i miss something? in this case, should a "bridge" be built so that to the J4 PIC there are either the bansktick and the midi_IIC ? or i misunderstood how to connect midi_iic and the sequencer core??? (or remeber wrong something?!) and, another question: the new PIC18F4620 witht the seq V3 snapshot you send me is already "ready" to use the MIDI_IIC module... i suppose... (since you ARE using the midi_iic for debugging seq V3, right?) is this correct? ??? ???

:o :o speechless!

i could be interested! :-) how much does it cost? i had a free XY pad sample, but i never figured out how to use it... if this one works exacltly as a 10K pot, it would be great!!

so we can start to search for PIC18F4620 to replace the old sequencer brain... ;D is this the only part to replace (apart to assemble the midi IIC module) or should we order something else with the new pic?! btw... GREAT NEWS!!

hi! just for curiosity, how much time do you spend in creating patterns for a song? and what "technique" do you use in doing this? do you create a pattern, then copy it and make small variations? do you use one entire pattern for drum, one for bass, lead and so on? please, share your tricks in sequencer use! :-)