• Content count

  • Joined

  • Last visited


Everything posted by jeb

  1. Hello, I've done this midibox several months (oops... it's years, now... !) ago, but now I have bought (much more expensive) real analog synths, and I don't use it anymore... It is designed to control a Minimoog VST Plugin (ex: Arturia Minimoog V, or other free versions) If somebody in France or near Strasbourg is interested, please mail me. (or anywhere else, but I think the shipping will be expensive...) My mail : basquin at freesurf dot fr. IMGP1695.JPG
  2. I can send photos, etc. Please contact me : basquin at freesurf dot fr ! jeb
  3. Hello, I was not offended :) Best regards, Joseph
  4. Hello ! A "Minimoog" VST controller Midibox.... Jeb IMGP1707.JPG
  5. Hello, Comme j explique ici :, j ai construit un controleur qui marche etc. mais je n ai plus de place ni l utilisation etant donne que j ai achete un vrai synthe analo. Du coup a vendre... J ai des photos si interesse. Suis en Alsace. A bientot jeb ps: je precise que c est pas du tout une activite commerciale c est juste une vente d occase !
  6. Hello, > You post your fancy new controller on 2007-12-10 > and want to sell it on 2007-12-16? It s not a new one ! I have built it about 1 year ago as I said in a previous post. It is fully functional. But the thing is that I have recently bought a real analog synthesizer... I recognize it is difficult to sell something I have personnaly created, spent time on it, etc. but I do not use it enough and I have very little space... So... jeb
  7. Hello, About the Midibox, it is MB64, with lots of pots, designed to control Arturia Minimoog or any other VST : there are exists **free** Minimoog VST. It IS finished and fully functional. I spent more than 100 euros for electronics (with shipping, wall adapters, and misc.), more than 50-60 euros for pots and knobs, 40 euros for the case wood making, imitation leather, etc.  And really *a lot* in misc things that I even cannot remember. You can mail me to do a proposal : basquin at freesurf dot fr. Joseph PS: TK, Why do you find it strange ? I explained I ve done it *not for commercial purpose* (I only sell this one !!)...  The problem is indeed that I have bought a real analog synthesizer and that I do not need this one anymore... (Moreover I do the same now as I did with my LEGO as a child : I enjoy *building* a unit, but then I less enjoy *using* it, and I go to another (currently not an electronic one) project ...)
  8. here you can see some photos  on the thread in the "midibox of the week section": jeb
  9. If somebody is interested, I sell it now... ! It's working great, but I have now bought a real (much more expensive) analog synth... and I have no more space in my 2-room apartment... You can contact me here : basquin at freesurf dot fr. I'm living in east of France, near Germany... jeb
  10. hello, i have a c question : i have a global array :                  unsigned char test[2][2]; each time a certain button is pressed, i want to reset my array to the default array {{1,2},{2,2}} (this is just a 2*2 example, the array in my code is much bigger). int this case the following line doesn't work : test = {{1,2},{2,2}}; i don't want to use a loop for this ! do i have to use pointers ? thanx jeb
  11. in french we call it "skaï", it's imitation leather... 6 euros/meter.. here another close up picture : IMGP1695.JPG
  12. some small questions

    hello, i've made several small midiboxes (one year ago... see my other post)... i'm currently building a new one, and i have one or two small questions... 1) what range has been tested for power ? is 12V  AC ok or too much ? 2) is there an interface for a power led (i don't want to build a ?OUT module for this!) 3) i have 50 kohm faders... will it be okay ? i remember i had problems with 100k pots... will these 50k be okay ? if not, i don't remember how to make them work (i cannot replace them for my specific project!!) WITHOUT jitter... any idea ? thanks in advance!
  13. hello, i have several "modes" in a global  variable : unsigned char mode; and the value of "mode" is changed by pressing some buttons. I have : function Tick() {   switch (mode)   {  case 1 :  Function1 (); break;     case 2 :  Function2 (); break;     case 3 :  Function3 (); break; ...} } aren't these tests (with if, switch, etc.) every times Tick is called (so very often !!) a waste of time ? is it possible to do pointers to functions ? example : pointer ...    mode_functionptr; whose value is changed when the button is pressed. with then : function Tick () { mode_functionptr();        //without tests! } ///////////////// just another small question : how to do a "switch/case" on two variables ? is : switch(i,j) { case (1,0) : ... case (2,1) : ... ... } possible ? thanx in advance !
  14. FM Patch Book

    Hello, Do you know any website or pdf or book with FM presets ? I know there are lots of preset, banks, .syx, etc. for dx7 on the web etc. but i would like to have a paper version of the patch in order i can "feel" a bit how to create beautiful sounds... (open each preset with a DX software + screenshot + print would be a bit long....) Do you know any FM Patch Book ? Thanks
  15. secondary midi input

    hello, i have done a midibox (with my own program based on the midiinout128 example) with pots, buttons, etc. i want to add a secondary midi input that will be merged with the first one. i did like in the midi merger project : RA4 (from the PIC of the core, i.e. pin #6) to a second optocoupler with resistors, diode, etc..... do i have to remove the R2 1K resistor if I use the second midi input ? because there is already a 1.2K resistor between PIC RA4 and 5v  (provided by the second MIDI (optocoupler, etc.) module (see midimerger.pdf)).... what do i have to add in the code ? thanx jeb
  16. secondary midi input

    hello, thanx a lot. a multiplexer would be good for me (much cheaper !! and easier than building a complete core with a PIC...) could you just give me the name of the chip needed (74?? , 74157 ?) and then i promiss i will do it by myself without asking any questions.... ;) thanx jeb
  17. secondary midi input

    thanx a lot for your response ! how to use a digital multiplexer ? (which reference?) which pins are to be connected ? with this solution, will it be real merger ? or is it a solution only when we are sure that the MIDI messages from the 2 MIDI IN do NOT come at the same time ? thanx in advance ! MIDIBOX is great !!
  18. secondary midi input

    hello, 1) what happens if i connect the 2 outputs of the 2 octo-couplers (one for each MIDI In) to the same core ? pin 6 of octocoupler 1 (MIDI IN #1)  \                                                   ------------- pin 26 of PIC18F      (pin RX) pin 6 of octocoupler 2 (MIDI IN #2)  / will it work if i'm sure message won't come AT THE SAME TIME (from the differents outputs) ? 2) if i do : pin 6 of octocoupler 1 (MIDI IN #1)  ---> pin 26 of PIC18F      (pin RX) pin 6 of octocoupler 2 (MIDI IN #2)  ---> pin 6 of PIC18F      (pin RA4 like for the merger project) I want to use the inputs NOT BOTH AT THE SAME TIME. how to tell MIOS that MIDI comes from pin 26 or pin 6 ? 3) any other switching option ? apart putting a mechanical switch (that's what i've done!) ? jeb
  19. secondary midi input

    hello, ok if this doesn't work... in fact i don't need to merge 2 inputs... i have to use MIDI IN #1 at a certain moment and MIDI IN #2 at another moment. but never both at the same time. in fact i'm looking for a solution that allow me NOT to unplug one cable and replug another... that would be boring.... is it possible to select one of the two MIDI IN ? (not to merge them if not possible) with a button for example or dynamically in the code that would ""switch""" the input. for the moment i have done it with an inversor (mechanical) switch but it's a bit boring... i would like to switch it from the code .... jeb
  20. hello, i have a  unsigned int  that i want  to put on the LCD like this : 500 ->  "5.00" 1253 -> "12.53" 12 -> "0.12" how to do this ? with the dot as a character... i don't want to use any div 100 or modulo 100 because it doesn't work (i can't do _mulint work, etc. because even if i include this file, the problem is "__gptrget1 or something like that) i don't manage to use the classical C sprintf / printf functions that would be useful here ! (i have put the include stdio.h) when linking, the linker says : missing definition for symbol "_sprintf" required by.... thanx in advance, jeb
  21. thanks a lot Wilba !!! but MIOS_HLP_Dec2BCD brings me wrong value in MIOS_PARAMETER1, MIOS_PARAMETER2, MIOS_PARAMETER3... for example for x=100  (unsigned int) PAR2 = 0x56 ?? PAR3 = 0x00 ??? that's strange ! i've read a previous post about issues about Dec2BCD but i didn't really understand what was the conclusion !! thx,jeb
  22. Thanx Lall ! The idea with << for the double switch is great !!!!!!    My second value is only 0 or 1 so (<<  1) is enough ! between : switch ((i<<1) + j); {  case 0x010:  //-> corresponding to i = 1, j = 0     case 0x011:  //-> corresponding to i = 1, j = 1     ...     case 0x031:  //-> corresponding to i = 3, j = 1 } and switch (i) { case 1: if j then ..... else .... case 2: if j then ..... else ... ...} which is better in terme of time consume ? thanx
  23. hello there is a problem with the linker, even with libsdcc.lib      in /lib and set up in the .lkr file. always the same problem : error: missing definition for symbol "_sprintf", required by "_output\main.o" i can include : #include "sprintf.c" but then it is another file that makes problem  : _vfprintf then i include : #include "vfprintf.c" then it is another one .... then i include the .c file then another one... this can continue very long ! is it normal that one should include all these .c files for the different functions when one needs to use a function ???!  ??? i gave the example with printf, but with memcpy, etc. it's the same ! thanx
  24. hello > The pointers would be even slower than the switch statement that's not possible : the pointer to the function is *changed* only when a button is pressed  (so in the call of DIN_NotifyToggle), so not so often at all ! the pointer would replace a // switch (mode) case 1 : Function1(); ... // by a // Functionptr(); // where Functionptr points to Function1, Function2, or Function3. is this possible in C ? how to do a pointer to a function with SDCC ?