Jump to content

shmuu102

Members
  • Posts

    10
  • Joined

  • Last visited

    Never

Posts posted by shmuu102

  1. Thanks for the help previously.... it was easier to edit, and recompile than i remember.

    (Im building a cubase controller with 2 cores, one 64, and one 64e... the 64e is the one giving me problems.)

    but, im still having problems with a few of the DIN inputs... some just seem to be dead, or unused.

    I would like to keep the menu keys, but get rid of all the other special function keys that are set by

    default. I make some changes in main.asm (set some options to "0") but it didnt seem to make a difference.

    I have assigned 36 encoders and 50 buttons. I am using 4 din modules, but the last 4 encoders dont seem to function.  I will have to paste the code edits from home.

    thanks in advance for any advice./

  2. by chance are you usings cubase?.. 

    i cant get cubase to echo the midibox commands back, to turn on and off the led's....

    eveything works fine when i use midiox, because it is echoing the input back to the output.

    but, in cubase, pushing buttons does nothing to the leds ( but changes the settings in cubase.,

    ,however using the mouse to chance the parameter that the button controls, correctly changes the leds...

    is there a line of code i could add to make the button toggle the led as well as the midi signal?

    thanks

  3. can someone tell me how to map incomming midi events to led's on the dout module.?? (in applications like the midibox64 and 64e)

    the tutorials and walk-thru's  touch on this, but dont go into detail.

    an example of my proble is this:

    on my transport controls, i assign a button to send an event to cubase, and cubase echos the event back out ( presumably to the led), so that when you press play on the midibox, and then stop with the mouse inside cubase, everything still jives....

  4. i was assemblingand testing  my Motorfader baord i got from smashtv, and installed everything according to the top screenpring on the board (blindly ignoring the schematics :( ).    several regulators and and a handfull of diodes later, i noticed that one of the 4 1n5818's was backwards for each  driver.  Can someone confirm this, or

    have the paint fumes just started to take effect..??

    and what do you think are the chances the drivers "lived" thru that ( my guess is nil)..

    thanks all....

  5. I am having some problems uploading syx  files to my midibox, im prob just missing something small, but i have checked everything i could think of and an at an impass.

    The only way i can seem to upload to my midibox is with MIOS Studio, (hex files only) .  I have tried MIDI-OX, (read all the web FAQ's, set the port routing, changed the buffer settings and delays,  turned off the feedback)  . It seems to send it ok, my midibox just seems to ignore it.  Same with the Vmidibox64e ( which is really what i would like to use, rather than code it all in asm)

    here's what im using

    Midibox core (new ver kit from smashtv)

    midiman 2x2 midi io usb interface

    din kit from smashtv

    mios 1.8 uploaded on the midibox (id 0000)

    Midi-ox  ver 7.0

    Mios studio beta 4-3

    i have uploaded some hex files, and i get feedback from some rotary encoders that seems correct, but i cant get the vmidibox64e  to upload. If i could convert ths syx to hex, i should be able, but that seems like avoiding the problem rather than fixing it.

    any help here would rock... thanks

×
×
  • Create New...