Jump to content

LO

Members
  • Posts

    370
  • Joined

  • Last visited

Everything posted by LO

  1. Yeah these are working just fine on my box You can use buttons instead of touch sensor LO
  2. mmmmmmm Dis forum has been heading down a not so nice path lately Time everyone chilled out a bit If you dont like someones suggestion or idea just dont reply? (if you cant be constructive) or else this forum will go the way of all the other web boards peace brothers (and sisters!) Dats my 2cents ::)
  3. mmmmmmm Dis forum has been heading down a not so nice path lately Time everyone chilled out a bit If you dont like someones suggestion or idea just dont reply? (if you cant be constructive) or else this forum will go the way of all the other web boards peace brothers (and sisters!) Dats my 2cents ::)
  4. like it! Thats a cool idea to re-use the P/S box!
  5. like it! Thats a cool idea to re-use the P/S box!
  6. Recycle! find an old cool looking case buy a drill and some files & paint and spend a few days to Modify it! easy and cheap
  7. Recycle! find an old cool looking case buy a drill and some files & paint and spend a few days to Modify it! easy and cheap
  8. You could mod the mouse wheels to act like encoders Do a search on this on the forum D2K has done this!
  9. You could mod the mouse wheels to act like encoders Do a search on this on the forum D2K has done this!
  10. Hello can I use vmidibox to access the MF_module when it is configured as MB_Link Endpoint device ID 2? The reason I ask is the MB64 (MB_Link fwd point deviceID 1) Receives sysex dumps from vmidibox no problem but I cannot get the endpoint to receive sysex :/ BTW I am setting the device ID via the sysex menu on the core (this is correct?) Cheers LO
  11. Hello can I use vmidibox to access the MF_module when it is configured as MB_Link Endpoint device ID 2? The reason I ask is the MB64 (MB_Link fwd point deviceID 1) Receives sysex dumps from vmidibox no problem but I cannot get the endpoint to receive sysex :/ BTW I am setting the device ID via the sysex menu on the core (this is correct?) Cheers LO
  12. I havent got the layout nearby.... but if J5 is the AIN on the core? then yes clamp any unused to earth. Hope that makes sense! Good luck LO
  13. I havent got the layout nearby.... but if J5 is the AIN on the core? then yes clamp any unused to earth. Hope that makes sense! Good luck LO
  14. Yo Dan I aint tried it but..... If you are using the Yamaha CBX driver? when you install it asks for single or multi port use I would assume if you select multi you should be able to utilise both Com1 and Com3 I have only 1 LTC at tha mo so I cant test LO
  15. First read up on the MIOS page then you need to do the following as stated in the main.asm file found in each archive Required tools: ; o Download the free available MPLAB IDE environment from the Microchip ; Homepage http://www.microchip.com ; o Download and install Active perl from http://www.perl.com ; o Download and install MIDI-Ox from http://www.midiox.com ; o Download and install the MIOS Bootstrap loader from http://www.ucapps.de and ; ; Following steps are required to reassemble the source code: ; o Start MPLAB IDE ; o Open the project file (*.mcp) from this archive ; o Open the main.asm file, here you can find all available include files ; o Change the files for your needs ; o Start "Project->Make" or just press the F10 button ; o After that, a new main.hex file can be found in the directory ; o convert the main.hex file to a .syx file in the command shell with: ; perl hex2syx.pl main.hex ; or just click on "convert.bat" ; o thereafter a main.syx file can be found in the directory. It ; can be uploaded to the MIDIbox NG with MIDI-Ox (see additional ; instructions in the MIOS bootloader archive) ; And you should be OK Good luck LO
  16. Hi This is exactly what I am doing with my box I will post some pictures soon as I get hold of a digital camera. it is based on the 16F MB64 at the moment with a MF module connected via MB_link. I dont have a need for an HC clone at present and it is very flexible as to what is assigned to what control also Cubase has banks for channels 1-8, 9-16 or what ever you specify. LO
  17. just try burning the PIC? my voltages are similar and Ive burnt 10+ PICs now, but maybe I was just lucky? LO
  18. almost any bridge rectifier will do just take care for the pin outs. or take some diodes and make your own. Or leave it out if you are using a DC P/S (be careful with the polarity)
  19. sure.... if you have a program or hardware capable of receiving the midi ::)
  20. oh OK Thanks, I did wonder if that was the case mmmmm more good reasons to switch it to the 18F! LO
  21. LO

    Traktor

    no but traktor has an excellent midi learn function
  22. OK so my MB64 and MB_MF are now talking on the same line! now it is ment to be possible to have all data displayed on one LCD?! how do I do this??? they have different device ID's one is set to MBlink FP the other to EP but still they only display on the relative core (not shared) any idea's........ anyone??........help.....please.......
  23. Sounds like its working! With the 18F the only file you burn the hex for is the Bootstrap loader all other programs must be loaded via midi. Mios must be loaded first by hitting send very quickly after seeing the "F0 00 00 7E 40 00 01 F7" string Once it has rebooted you are free to load other files. NB they must be the files from the MIOS download section you cannot use the old 16F test programmes If you have an LCD it would be a good idea to connect it otherwise you would have no idea what is happening. Virtual midibox is not working with MIOS yet wait for the MB64 port to MIOS then it should work. LO
  24. Hi Im pretty sure the 18F uses a completely different instruction set to the 16F therefore the hardware is 1:1 but the firmware is not 1:1. :( LO
  25. ummmm yeah 15v straight in to the 7805 thanks ill try the 7809 caps are 6n8 I think? ill double check tonite
×
×
  • Create New...